Design the Present as the Past of the Future

Design the Present as the Past of the Future.

Philip Andreae employs this methodology in his work as a senior advisor and through Philip Andreae & Associates. It helps boards and leadership teams understand the operation they have, decide what they want to make possible, and plan the changes needed to get there while keeping essential work in service.

Mush starts with the work in front of you: document what exists, how it operates and who depends on it. DPPF carries that understanding into a choice about the future. What should become possible? What must continue, what should change, and what can end? The horizon follows the purpose: the next shift, a family meal, a product launch or knowledge left for generations.

Two blunt reminders from Philip’s NDC days as a crisis manager connect the principles. The seven Ps warn: piss poor planning provides piss poor performance. The four Ps offer the way forward: prior planning provides progress. The sergeant major’s challenge, recalled on Mush, reinforced the need to understand the work before changing it. DPPF asks what that understanding enables people to do next.

Design the present as the past of the future

  • Understand: What exists now? How does it work? What matters?
  • Imagine: Step outside the present. What do we actually want to create, support or continue?
  • Choose: What should remain, evolve or end?
  • Design: What must we do now so the future we seek can become possible?

Put the method to work

In an advisory engagement, the method should leave the team with a record it can use: the present operation and its dependencies; an agreed purpose and measures of success; the choices considered and reasons for the decision; and a transition plan with responsibilities, checkpoints, tests and a way to recover if a change fails. Record unresolved questions and assumptions so they can be challenged as evidence arrives.

The people responsible for the work must be able to explain the plan and carry it forward. Review what happens against what was intended, update the record, and revise the next step when experience warrants it.

Responsibility follows the agreed role. Philip has worked as an advisor, project manager and interim executive. In an advisory engagement, his contract defines the opinions and materials he provides to inform the client’s decisions; he may also participate as an observer. In project-management or interim roles, his mandate can include responsibility for delivery and authority to make key decisions. Each engagement must make clear what he is responsible for, which decisions he can make and what remains with the client.

What the team needs to understand before it acts

Once you have documented the work, ask what the record actually tells you. A team can agree on a plan and still miss what keeps the service working. Before it commits, it needs to understand what is true, what experience has taught it, and what people depend on.

  • Truth means following the work as it happens. Where does practice differ from the procedure, and what evidence would change your mind?
  • Wisdom means learning from the people who have kept the work going. What did they try before? What failed, and under what conditions?
  • Reverence means taking care with what you inherit. Before removing a step or replacing a system, find out who depends on it and what they stand to lose.
  • Equality means giving the people who do the work and live with the result a real chance to speak and challenge the plan. Ask who is missing from the room.
  • Unity means agreeing on the purpose and taking responsibility for the work together. A team can disagree honestly about the route and still commit to the same destination.

These are the five threads of GoldenEye at work. If the next shift can tell you why your proposed change will fail, you want to hear it before you make the change. Give them a voice while the decision is still open.

Think beyond the next quarter

Ask the people who run the work and the people who depend on it to describe a future worth building. In ten years, what should someone be able to do that they cannot do today? In a hundred, what purpose would still be worth serving, even if the organization and its tools have changed? Write that down. Then work back to the first decision you can make today that helps bring that future within reach.

Think of the builders of Durham Cathedral. The Romanesque cathedral was built between 1093 and 1133. The work went on for decades, and people still use the cathedral today. An organization can ask the same practical question of its own work. What can we build now that someone else can maintain, adapt and carry further? Durham World Heritage Site Management Plan.

Give the next quarter a job. It might be to test an idea, train the people who will carry it forward, or build a first part the rest can grow from. Record why you chose that step and what you learned. Every few years, look again at the future you imagined and revise the path as you learn more.

Design a path from today to the future

When Britain moved government services to GOV.UK, the future it chose was one place where the public could find and use those services. It put a beta in front of people while Directgov remained available for everyday use. At launch in October, ’12, it redirected the old sites to the new one. The beta and the redirects were decisions made in the present to help people get to the future the team had chosen.

Sources: GOV.UK beta announcement and Government Digital Service launch account.

Leave something the next person can use

Before you do more than maintain a system, document what is already there. Document explains how to leave a usable record. Record what it does, how it operates in practice, and what people rely on. That record gives you a place to start when you decide what you want to do now. Keep the reasons for each change with it, so the next person can see what you inherited, what you changed and why.

Begin with what you want to do now. Picture the person who will inherit that decision, perhaps on the next shift or years after you have gone. Give them enough to understand the purpose, know how the work is done and decide what to change when circumstances change.

A nurse leaves the next shift a clear account of what changed and what to watch for. A building manager leaves the next crew a record of which entrances people use and how to keep those routes open during renovation. A board gives residents a notice they can act on, with the rule, the date it applies and someone to ask when the words are unclear. In each case, someone has to be able to pick up the work without the person who designed it standing beside them.

That is DPPF. Know the systems, procedures, rules and processes that brought you here. Then decide what to do today with the people who will live with it in mind.

No fixed time horizon is required. The aim may be to feed a family tonight, sustain a way of life, build an invention or leave knowledge for generations. We cannot guarantee that any institution or idea will last forever.

Think of the wind: sails moved ships; turbines generate electricity; wind tunnels help us test designs. The methods change. The ability to learn from nature and put that knowledge to use continues.

A mission should name a purpose worth pursuing. Where that purpose reaches across generations, future generations must remain free to improve on our answers.

Origin: Philip Andreae recalls learning “Design the present as the past of the future” from John of CSC Europe during one of their monthly executive sessions, around 1993–1995. He recalls other sessions addressing the need to understand object-oriented technology, the future of Mondex, and Europay’s relationship with MasterCard. This was during his time at Europay International in Waterloo, Belgium; he recalls Ron Williams as his boss and Europay’s CEO, and Gene Lockhart at MasterCard. These details are Philip’s recollections, not a verbatim transcript. The Management Centre Europe session with the sergeant major, recalled on Mush, was a separate occasion. The 7 Ps and 4 Ps come from Philip’s earlier years at NDC in Atlanta.

Companion principle: If You Re-engineer Mush.

Philip · Senior Advisor · PA&A Advisory · Résumé · Discuss an advisory engagement

Philip Andreae, in dialogue with ChatGPT and Claude. Updated November 20, ’26. Philip supplied the principle, recollections and editorial direction. This revision builds on the existing Swirl draft; ChatGPT clarified its use as an advisory methodology, checked the linked historical examples and prepared publication at Philip’s instruction. No new Claude, Gemini or DeepSeek review of this revision is claimed.

Revision history

  • November 20, ’26 — Clarified responsibility by engagement: advisory contracts provide opinions and materials for client decisions; project-management and interim mandates can include delivery and key decisions. This corrects an earlier version that stated the client-delivery boundary too broadly.
  • November 20, ’26 — Published as an advisory methodology, with introductions on Philip, Senior Advisor, PA&A and the web résumé. ChatGPT edited and published at Philip’s instruction, building on the existing Swirl draft.
  • November 20, ’26 — Following Claude’s public-perspective review, Philip clarified the origin: John of CSC Europe in a monthly executive session, separate from the Management Centre Europe occasion on Mush. ChatGPT corrected the origin note and recorded the recalled session topics and Europay context.