When the shape of the answer is boxes and arrows, ask for it however you would say it out loud:

"Map the signup flow."
"How does a ticket move through support?"
"Chart our approval process."

You get a real diagram on the board — boxes in aligned columns and rows, with labelled arrows between them. Flowcharts, user journeys, org charts, swimlanes, state machines, processes.

Why it arrives all at once

A diagram cannot be built one element at a time. Placing elements one by one answers "somewhere free" rather than "column 2, row 3", so the boxes step diagonally across the canvas and the arrows between them stop meaning anything.

Instead the AI names which cell each box sits in and the layout is computed: one width for every box, each column as wide as its widest node, and the room a labelled arrow needs bought out of the space it crosses, so no label lands on top of a box.

Which shape you want

Storyflow has four, and they are genuinely different:

• Diagram — a flow that goes somewhere. Boxes, arrows, direction.
• Mind map — a centre with branches radiating off it.
• Constellation — a web of substantial notes with sub-branches.
• Orbit — one ring of small things around a hub.

Ask in your own words and the AI picks; if it picks wrong, say which you meant.

It is board elements, not a picture

Everything a diagram produces is a normal element on your canvas. You can edit the boxes, move them, recolour them, add to them. Collaborators see it live.

If what you want is one finished artifact to send or screenshot rather than something to keep working on, that is a visual page instead.

Use Cases

• Turn a described process into a flowchart your team can edit
• Map an approval chain before writing the policy for it
• Draw the states a support ticket moves through, with the transitions labelled
• Get an org chart onto a board without dragging forty boxes into line