Dreamineering
Dreamineering is the discipline of engineering preferred futures. It begins inside-out with a story of what is worth becoming, works top-down to define the outcomes and standards that future requires, works bottom-up from present reality and available capability, and learns outside-in from the people and evidence affected by the result.
Every intentionally created future begins as a story of a preferred reality. The story gives direction, but it is not proof. Dreamineering keeps intent honest by turning the story into an explicit setpoint, composing a feasible bridge, and letting observed consequences challenge what its authors believed.
Four simultaneous perspectives
These are perspectives on the same discipline, not sequential stages.
| Perspective | Question | Authority |
|---|---|---|
| Inside-out | What future is worth creating, and why? | The dreamer or customer's values, purpose, identity, and intent |
| Outside-in | What do other people and reality reveal? | Customer response, context, outcomes, and independent evidence |
| Top-down | What must the wider system make true? | The preferred future, setpoint, outcomes, standards, and constraints |
| Bottom-up | What can the local network actually compose? | Present capabilities, relationships, actions, experiments, and receipts |
Inside-out does not mean ignoring the customer. It means establishing an honest purpose and capability before projecting a promise outward. The customer owns their preferred future; another person may clarify it, but must not manufacture it to fit an offer. Outside-in evidence then has authority to challenge the internal story.
Three nested loops
At personal or organisational resolution:
imagination → intent → action → experience → reflection → evolved intent
At engineering resolution:
Reality → Dream → Bridge → execution → Gauge → variance → correction
At distribution and business resolution:
foundation → capability → Playbook → belief → journey → venture → action
customer evidence → receipt → decision → improved capability
The loops nest because a future is not finished when an artifact ships. The result must reach the beneficiary, produce an observation, and change or confirm a decision. A product surface proves that something can be built; only beneficiary or independent evidence can show that it created customer value.
What Dreamineering is not
- Not manifestation: imagination matters, but it does not substitute for action, an external Gauge, or a falsifier.
- Not planning: a plan sequences action; Dreamineering also tests whether the destination deserves commitment and whether reality supports the story.
- Not requirements engineering: requirements describe a system contract; Dreamineering begins with the beneficiary's preferred future and retains the authority to stop when the contract would not create that future.
- Not sales persuasion: the method may support an agreement, but it may not invent the customer's dream, urgency, or evidence to make a sale.
Apply the discipline
Use the Dream Specification to state intent, value, belief, control, capability, bridge, and outside-in return in one stable contract. Freeze the setpoint, Gauge, and review window before action so later evidence can teach rather than rewrite the standard silently.
Failure modes
- Intent without return: the internal story becomes self-sealing because customers and consequences cannot challenge it.
- Evidence without purpose: local signals optimise a system whose direction was never chosen honestly.
- Standards without capability: a top-down target becomes theatre because no feasible network can compose it.
- Capability without setpoint: available tools dictate the future instead of serving it.
- Output called value: deployment, volume, or completion is presented as a beneficiary outcome.
Changes my mind: a competing discipline can preserve dreamer authority, freeze success before action, compose present capability, and give outside-in evidence equal power to change the next decision more clearly.
Context
- applied-by Dream Specification — the stable public method contract.
- measured-through Standards — the setpoint and Gauge remain fixed through the review window.
- learns-through Evolution — authorised lessons raise or correct the next baseline.
- distinguished-from Manifestation — rehearsal is one possible practice, not the whole discipline.
Questions
Next question: Which preferred future is worth making explicit enough that reality can disagree with it?
- Who owns the preferred future and who is affected by it?
- What must remain true even if a faster or more profitable route appears?
- Which observation would change the story rather than merely change the tactics?