Future state
Define the commercial and customer future the business is trying to create, in language teams can work with.
Future Backwards needs product judgement.
Future Backwards is how Stephen connects customer jobs, user difficulty, product quality, team capability and commercial value. It starts with the future worth building, then works back to the decisions that make it real.
The point is not the future. It is the backwards.
Future Backwards is not prediction theatre. It is a discipline for making strategy useful. Start with the business you need to become, then work backwards through the customer outcomes, user jobs, product decisions and team capabilities that would make that future believable.
That matters because many organisations talk about future state at a level where everyone can nod along. Better experience. Better AI. Better growth. Better efficiency. The value appears when those statements are forced into sharper questions: who needs to make progress, what is currently difficult, where does confidence break down, and what would have to change in the product, service and operating model?
Start with the job, not the feature.
Products become more useful when teams understand the progress people are trying to make. In business software especially, the buyer, customer, user and operator may all need different things from the same product. One person may be buying confidence. Another may be trying to complete a difficult task. Another may need visibility, control or proof that a process is working.
That is where design leadership has to be precise. If a product only fulfils the task mechanically, it may be usable but forgettable. If it chases surface delight without understanding the job, it may be attractive but commercially weak. The better move is to design a future state where the right jobs become less difficult, more trustworthy and more valuable.
Less difficult is a sharper promise than easy.
The aim is not to make people artificially happy. It is to make difficult work feel understood.
Easy can be a lazy ambition. Some parts of a product should be quick and quiet. Others need care, confirmation, explanation or a useful pause. If money is moving, risk is changing, data is being trusted or a decision has consequences, removing every piece of friction can make the experience weaker.
The better word is contentment. Users should feel that the product understands the difficulty of the work and helps them move through it with less drag, more confidence and fewer unnecessary surprises. Delight then becomes something earned by fit, clarity, timing and detail, not something sprinkled on at the end.
AI changes the tempo, not the responsibility.
AI can help teams explore faster, summarise research, generate options, draft content, simulate flows and prototype directions. That is useful. It also means teams can now move very quickly in the wrong direction, with more confidence and better-looking artefacts than before.
This is why Future Backwards matters more in an AI-enabled organisation. The question is not simply what the team can produce. It is which future the team should be producing towards. Someone still has to judge what should exist, why it matters, how it creates value, where the risks are, and whether the experience will actually help customers and users do the work they came to do.
The operating model
Jobs to be done
Separate buyer, customer, user and operational jobs so product direction serves real progress, not just feature demand.
Difficulty map
Find where people lose time, context, confidence or trust, then decide which difficulty should be removed, reduced or protected.
Product judgement
Choose what to build, remove, automate, standardise or slow down based on value, risk and evidence.
AI workflow
Use AI to widen exploration and improve learning without flooding teams with plausible but weak output.
Value loop
Connect design decisions to adoption, confidence, operational cost, product quality and commercial effect.
How Stephen helps
01
Frame the future
Turn ambition around growth, AI, transformation or customer experience into a concrete future state that can be tested and challenged.
02
Map the jobs
Understand what customers, users and internal teams need to get done, then identify where the current product or service makes that work harder than it needs to be.
03
Make the model visible
Use product models, service maps, prototypes and decision artefacts so leaders can see the choices rather than discuss them in the abstract.
04
Design the team conditions
Shape standards, critique habits, roles and AI-enabled workflows so teams can make better decisions without everything returning to the centre.
05
Connect to commercial value
Tie design decisions back to adoption, trust, efficiency, quality, growth and the confidence the business needs to move.
The thesis
Future Backwards is a way of designing from consequence. It does not start with a feature list, an AI tool or a set of screens. It starts with the future the business needs to earn, then works back through the jobs people need to do and the product decisions that will make that future real.
A good future state does not promise happiness. It creates competence, clarity and contentment. The customer can see why it matters. The user can get through difficult work with less drag. The business can see how design is turning better judgement into commercial value.