About DramieFlow
Most diagrams are static.
Real systems aren't.
DramieFlow has six ideas. If you can hold these in your head, you can read any diagram here.
Nodes
PlacesSituations in your system — where someone can be right now.
Where am I right now?
Paths
Ways to moveConnections between places — things that can happen next.
What can happen next?
Dramies
People trying to get things doneSmall agents that move through your diagram like real users. They carry information, make decisions, get confused, and do unexpected things.
What happens when someone actually tries this?
Clerks
MessengersLive inside places. They carry requests out, wait for responses, and bring answers back.
How does information move when people are waiting?
Guards
GatekeepersAppear at places that have entry requirements. They check whether a Dramie or a Clerk-delivered request has the right luggage before access is allowed.
Who gets blocked at this step, and why?
Luggage
InformationWhatever a Dramie knows or carries as it moves.
Why can this Dramie go here but not there?
How it fits together
- Places describe situations in your system.
- Paths describe how things can move between situations.
- Dramies act like real people and try to complete the flow.
- Clerks carry requests and responses between places.
- Guards enforce requirements before entry is allowed.
- Luggage represents information carried through the system.
Press Play and watch the Dramies explore your diagram.
If they get stuck, confused, lost, or angry, your users probably will too.
What it's not
- ✗Not an automation engine
- ✗Not a workflow executor
- ✗Not a replacement for real metrics
DramieFlow is about understanding, not running production logic.