Future Backwards

Start with the future worth building, then work backwards.

Future Backwards is Stephen Rea's way of turning business ambition into product direction: define the future the business needs to earn, understand the jobs customers and users need to get done, then work back to the products, teams and AI-enabled systems that make it real.

The future state has to include the work people are trying to do.

A future state is weak if it only describes the company from the inside: revenue targets, operating models, technology choices, efficiency goals or a more impressive roadmap. Those things matter, but they are not enough.

The useful future also describes how customers and users will make progress. What job are they trying to do? What currently makes it difficult? Where do they lose confidence, context, time or trust? What would make the experience feel not just usable, but properly understood?

That is where design leadership earns its keep. It turns ambition into choices the business can act on: what to build, what to stop doing, what to simplify, what to automate, what to slow down, and what standard of quality should travel across the organisation.

The question is not simply what can we make next. It is which future would make the right work less difficult, more trustworthy and more valuable.

AI is not the strategy. Better judgement is.

The businesses that benefit most will not simply produce more screens, decks or prototypes. They will get clearer about the future state, the jobs their customers and users need done, and the difficulty worth removing.

Future State

Define the future worth building

Make business ambition concrete enough to test: customer outcome, user job, product model and commercial value.

FutureJobsValue
Jobs

Understand the work people need to do

Separate customer, buyer, user and operational jobs so the product serves real progress, not just a list of features.

CustomerUserBusiness
Product Judgement

Make difficult things less difficult

Decide where to remove friction, where to keep useful checks, and where delight can emerge from clarity and confidence.

FrictionTrustDelight
Team System

Build the AI-enabled operating model

Shape workflows, standards and review loops so AI speeds learning without weakening accountability or taste.

FrameGenerateJudge

A practical map from ambition to action.

Future Backwards gives senior teams a way to connect the customer future, product direction and operating model before delivery momentum hardens around the wrong assumptions.

Commercial outcome

What does the business need to improve: growth, retention, margin, efficiency, trust, adoption or confidence in a strategic move?

Customer progress

What are customers trying to get done, and what would make that progress feel more valuable, reliable or differentiated?

User difficulty

Where do people lose time, certainty, context or confidence, and which parts of that difficulty should be removed rather than hidden?

Product model

What objects, states, permissions, journeys and service moments need to fit together so the experience feels coherent?

Team capability

What standards, roles, critique habits and decision rights need to exist so good judgement can travel without a bottleneck?

AI workflow

Where can AI improve exploration, synthesis, testing or quality, and where does human accountability need to become sharper?

How the work moves.

01

Frame the future

Make the future specific enough to argue with. Define the commercial result, the customer change and the product qualities that would make the future worth building.

02

Map the jobs

Separate buyer, customer, user and operational jobs. Different people may be asking the same product for confidence, speed, control, proof or a reduction in risk.

03

Find the difficulty

Look for the places where the current experience makes people carry too much uncertainty, effort, context switching or organisational complexity.

04

Shape the model

Turn the thinking into product models, service maps, prototypes, standards or decision frameworks that leaders and teams can actually use.

05

Design the conditions

Decide how teams will learn, critique, use AI, protect quality and keep making better product decisions after the initial intervention.

Where the work shows up.

The value is practical: clearer product direction, less wasted effort, stronger design standards, better leadership decisions and teams that can use AI without losing taste, evidence or responsibility.

Advisory and leadership support

Help senior teams connect design, product quality and AI-enabled operating change to commercial outcomes.

Product and service direction

Work backwards from customer and user jobs into product priorities, service moments and experience quality.

Design operating model

Shape roles, standards and review loops so teams can move faster without fragmenting judgement.

AI-enabled product teams

Use AI to increase learning and option quality, not simply to make more average work faster.

Customer confidence

Design moments where people understand what is happening, why it matters and what they can safely do next.

Commercial value

Turn design from a presentation layer into a clearer path to adoption, trust, efficiency and stronger product decisions.