Your first move: pick the work that keeps getting stuck. Tell Nav where it should end and how you’d know it got there. We agree that before anything is built.
Engineering below the horizon, the dream above it: the course climbs on toward Māhutonga, the Southern Cross. Illustrative chart. Not for navigation.
Chart DM01 · Dreamineering · Edition 3 · October 2026
Your workflows are your business.
Every quote, order, hire and invoice is a flow of data and decisions. When it breaks, it breaks in the same four places. They’re marked on the chart.
Nobody named the outcome
No one knows where the work should end.
Nobody owns the yes
Work waits on whoever is busiest.
It all runs through one head
When that person is away, the work stops.
Nobody can prove it worked
Tools ran. Nobody knows if it got better.
Face reality before you chart progress.
The map is not the territory. Start where the work should end. Trace it back. Clear what’s in the way. Each step has what you bring, the test it must pass, and what you keep. No step starts until the last one passes.
1Name the outcome
Say where the work should end, and how you’d know it got there. Set what agents may and may not do.
You bring
whoever makes the call. In a small team, that’s you.
Pass when
one outcome in one sentence, and someone who owns it.
You keep
a one-page brief.
2Trace it back
Start at the outcome. Follow the data and decisions back to where they begin. We draw it with the people who do the work.
You bring
the people who do the work, and access to the tools.
Pass when
the people who do the work recognise the picture.
You keep
a map of how the work really flows.
3Find the friction
Mark where work waits, gets retyped, comes back, or sits with one person. Time it. Agree the target and when to stop.
You bring
a few weeks of real cases.
Pass when
the worst blockage named, with a baseline, a target and a stop rule in writing.
You keep
the scorecard.
4Clear it alongside
Clear the worst blockage on real cases, beside the old way. Customers see no change yet.
You bring
a safe place to test, and time to check the results.
Pass when
the work flows faster, without harm. If not, we stop and you keep what we learned.
You keep
evidence, or a cheap reason to stop.
5Let it flow
Switch over with checks, a fallback and a tested way back. Agents earn more say only as the evidence comes in.
You bring
whoever holds the keys to your tools and data.
Pass when
checks tested, your people running it, the old way one step back.
You keep
a running workflow, and its runbook.
6Keep it flowing
Check the gauges each week until the target is met. Then your own Nav and first mates keep it flowing.
You bring
a short weekly check-in.
Pass when
the target met, you sign off, and the runbook works without us.
You keep
proven value, and a crew you can trust.
The needles we move.
Busy agents aren’t the goal. Flow is. We agree these numbers before we build. Each has an owner, a baseline and a target. If they don’t move, we stop or change.
Flow time
From start to outcome.
Wait share
How much of that time the work sits still.
Rework
How often it comes back.
Cost per outcome
What each finished job costs, people and machines.
Value
Net benefit, after every cost.
Where you are today The target you agree
Daily
Clear what’s stuck.
Weekly
Real work against the target. Keep going, change, or stop.
Exit
Value proven. You sign off. The runbook works without us.
Technology can optimise the game. It can’t tell you which game is worth playing.
The quality of our intentions matters more than ever. AI amplifies whatever it is pointed at, the better and the worse sides of our nature. So before the machines speed up, a crew agrees its setpoint: the shared values it steers by.
Get those right and a crew can thrive in chaos. When cause and effect can’t be seen, you act first, then sense and respond, together. We believe AI and tokenised assets will make that the normal weather for every business.
From Matt’s essay The Setpoint (2026). Acting first in chaos is from Snowden and Boone’s Cynefin framework, Harvard Business Review (2007).
Flow is the goal, and the reward.
The right work, done well, with progress you can see. Psychologists call it flow. It happens to one person, and to whole teams at once. Dreamineering is the thinking behind it: directing intention and attention so the work keeps flowing.
One person in flow
Csikszentmihalyi found three conditions: a clear goal, immediate feedback, and a challenge that stretches your skill without swamping it.
A whole team in flow
Sawyer found flow can be shared: a goal everyone holds, close listening, building on each other’s ideas, everyone taking part. Caltech researchers measured it in 2021: teammates’ brain activity falls into step.
Agents don’t feel flow; they set up its conditions. They keep the goal in view, read the gauges and clear the waiting, so people can do their best work together.
A hive-mind of people and AI
When people, firms and agents share goals, data and trust, flow runs between businesses too. Innovative ecosystems that survive the speed-up, then thrive: that’s the hive-mind we’re building toward.
Sources: Csikszentmihalyi, Flow (1990). Sawyer, Group Genius (2007). Shehata et al., “Team Flow Is a Unique Brain State,” eNeuro (2021).
We all need a prompt in the right direction.
Each workflow is a recipe: the outcome, the steps, and the evidence it worked. Run it yourself, or bring us in.