Understand complexity by mapping it.

No more hours spent lining up shapes and colouring them by type. Complexity draws the map and keeps it tidy, however many steps and branches there are, while you can still style it your way.

An output that goes nowhere, or an input that comes from nowhere, is listed as an issue. Not ready to map a branch yet? Add the input anyway and connect it later.

Share a map with as many reviewers as you like. They comment right on the steps. Set a PIN to keep the map from prying eyes. Then go through the comments and update the map.

Want to workshop the poster-sized map? Export it as SVG or PNG.

When many actors take part, it gets hard to see who does what, and when the work passes on. Give each a lane: one for Sales, one for Development. The interaction points stand out.

Pick a step and follow every path from it or to it with the arrow keys, checking each step on the way. Or select everything that comes before it or after it, to see all the ways at once.

Light up everything that leads to a step or follows from it. Use Bird's eye to see the whole map at once and jump to any part of it.

Invite people to look or to edit. Several people can change a map at the same time: you see who is there and what each is editing, and nobody overwrites anybody.

Give a map's link to an AI assistant. It reads the whole map, steps, branches and all, and answers your questions about the process. Coming soon: your AI makes maps for you from your own data.

Want to keep some steps together? Group them. Want them out of sight for a while? Close the group. Want to see only what is inside? Hoist the group, and everything else is hidden.

Want to ask more about a step, but later? Tag it "For later". See a trouble spot? Tag it "Problem". Tags make it easy to come back to a map and pick up where you left off.

Few people can read a BPMN diagram, yet we ask stakeholders to review them. It is like a musician handing out sheet music instead of playing! A Complexity map needs no training.