Making a Diagram Somebody Else Can Edit

No affiliate links on this site, and nothing here is ranked.

The requirement in the title

"Somebody else can edit it" is the whole specification, and it is why this task is not solved by drawing something.

A diagram is a document with a working life. A layout, a process, a wiring arrangement, an organisational chart — each gets revised, and the revision usually happens when the original author is unavailable.

Which makes the format the decision rather than the drawing surface.

What you already have

A sketch photographed, which is faster than every application and is the right answer for anything explanatory and disposable.

The drawing tool in your office suite, which is present in both major ones, adequate for boxes and arrows, and editable by anybody with the same suite — which is the whole point.

A presentation slide, used as a canvas, which is the most widely available diagram editor in existence.

And a spreadsheet with borders, which is not elegant and produces perfectly serviceable floor plans and grids.

When something dedicated helps

When the diagram is large enough that manual layout becomes the work — dozens of nodes, connections that must reroute when something moves.

When it must follow a standard notation that others will read strictly.

When several people edit it at once.

And when it is generated from something else — a diagram produced from a text description, which changes when the description does and cannot drift out of date.

The format question

Ask what the file is before choosing a tool.

An open, documented format can be opened by other tools in ten years. A proprietary one cannot, and a diagram nobody can edit is a picture.

Text-based diagram formats — where the diagram is written as text and rendered — are the most durable option available and are readable and editable in any text editor.

And an image export is not a diagram. It is the output, and keeping only the export is the commonest way a diagram becomes unmaintainable.

Where they go stale

All of them, quickly.

A diagram is a snapshot of an arrangement that changes, and an out-of-date diagram is worse than none because people trust it.

Two remedies. Date it visibly, on the diagram itself, so that its age is obvious to anybody reading.

And keep it minimal. A diagram with forty elements will not be maintained; one with eight might. Which is the same argument as the rest of this site applied to a document rather than a purchase.

What to check before buying one

Whether the free tier covers your use, which for occasional diagramming it commonly does.

Whether the export is editable elsewhere, not just an image.

Whether other people can open it without an account, which is the requirement in the title and the one most often failed.

And whether you will use it more than twice a year, which is the frequency question and usually settles it.

The diagram that should have been a list

Frequently the answer.

A process with eight sequential steps is a numbered list, and it is faster to read, easier to maintain and searchable — none of which a diagram is.

Diagrams earn their place where the relationships are not linear: things that connect to several other things, layouts where position means something, flows that branch.

Where the structure is a sequence, write the sequence. The impulse to draw it is usually about how it will look in a document rather than about the reader.

Sending it to somebody

Two files, not one.

The editable source for anybody who may revise it, and an image or PDF for anybody who just needs to see it.

Sending only the source produces "I cannot open this". Sending only the image produces a request for the source three months later, usually when nobody remembers which tool made it.

Note the tool in the filename or alongside it. Ten seconds, and it answers the question that otherwise takes a search through everybody's memory.

Standard notations, briefly

Worth using where the audience reads them and actively harmful where it does not.

A diagram in a formal notation shown to somebody who does not know it communicates less than boxes and arrows would have.

Ask who is reading it. For an internal note to two colleagues, plain shapes are correct. For something an engineer, an inspector or a contractor will work from, the standard notation is the requirement and departing from it causes real errors.

Keeping it with the thing it describes

A diagram in a shared drive, separate from the document it belongs to, drifts.

Put it in the same folder as whatever it explains — the job, the process document, the installation record — which is the arrangement everything else on this site arrives at.

A diagram nobody can locate is a diagram nobody updates, and the two failures reinforce each other.

Version, briefly

Diagrams get revised and the old one keeps circulating.

Put a version or a date in the file name and on the diagram itself, so that two copies in circulation can be told apart by anybody holding one.

It costs nothing and it prevents the specific failure where somebody works from a layout that was superseded. A separate outside reference is Airtable.

The short version

• The requirement is that somebody else can edit it, which makes the format the decision rather than the drawing surface
• A photographed sketch is faster and correct for anything explanatory and disposable
• The office suite's drawing tool and a presentation slide are the most widely available editors and are editable by anybody with the same suite
• Dedicated tools help at scale, for strict notations, for simultaneous editing, and where the diagram is generated from text
• Text-based diagram formats are the most durable, and an image export is output rather than a diagram
• Diagrams go stale quickly: date them visibly and keep them small enough that somebody will maintain them