Connections

A connection is a line between two cards (or between a card and a sticker). Connections make explicit a relationship that position alone can’t carry — “this leads to that,” “this depends on that,” “see also.”

Line styles

• Solid is the structural connection. On a process map it shows the primary flow; on a sitemap it shows “this page links to that page” as part of the information architecture. Solid edges define meaning.
• Dotted is the secondary reference — “see also,” “related to,” “cross-link.” Dotted edges add context without changing the shape of the map.
• Thick is for emphasis. Use sparingly.

Connections can carry a label that names the relationship (“redirects to,” “blocks,” “implements”), and can be directional (with an arrowhead) or undirected.

Some map types render connections prominently; others hide them. A flow map shows them — they are the structure. A story map or kanban hides them by default, because lane and column position already carries the structure and rendering every implicit edge would clutter the canvas. But the data is always there: integrations (the MCP, CSV exports) can read connections regardless of whether the canvas draws them.

Caution

• Don’t use connections to encode something position already carries. On a kanban, a card in the “Done” column doesn’t need a line to the “Done” header.
• Don’t break the map type’s grammar. A sitemap tree should have one parent per node; a second solid incoming edge breaks the tree.