Skip to content
Interface language: English
Imperium / Signal

Three futures for a company: scenarios that do not pretend to be forecasts

Use alternative scenarios to test company decisions, identify dependencies and plan signals for review without treating the exercise as a forecast.

Article language: English

A seated woman beside a glass sphere with dark reflections.
In this article

Next year's plan can be remarkably unanimous. Every customer wants what the company already intends to sell, the contact channel works as before, and the partner replies on time. The cautious case has slightly smaller numbers. The ambitious case has slightly larger ones. The surrounding world behaves identically in all three columns of the spreadsheet.

Scenarios help us move beyond that picture. They describe different possible conditions in which a company might have to operate. They let us test what remains sensible under different changes and what depends on a particular condition. We do not have to believe one chosen story in order to use it to assess what we do today.

First choose the decision you want to test

Imagine a Polish company offering solutions to modernise production workstations. It is considering developing its business in Japan. It wants to know whether to prepare an offer for factories directly or concentrate on working with integrators. This is a methodological example, not a description of current Japanese buyers' preferences or a market forecast.

The decision gives the scenarios their boundaries. The company can consider how customers' needs and access to their projects might change. It does not need to predict the entire economy at the same time. It does need to understand why the chosen changes would affect the planned scope of cooperation.

In its guide to using scenarios, the OECD presents them as deliberately fictional images of alternative futures, used to learn and act in the present. The chapter comes from a publication about education. Here the useful distinction is between a scenario, a prediction and a ready-made recommendation.

In our example, the result should be a comparison of actions the company is considering now: preparing material, choosing people to speak with and examining how cooperation could work. Conclusions should lead to questions and possible trials. If an exercise produces only attractive names for three futures, return to the decision for which the meeting was organised.

Choose a time horizon that suits the direction under consideration. In this exercise we might describe the conditions for cooperation in five years, then ask what preparation is needed today. A brief fluctuation in next month's enquiries calls for a different planning tool. Do not mix it with a long-term scenario when the company wants to assess a change in how it works and the capabilities it needs.

Keep the company's present constraints in the starting description. A scenario may assume different market conditions, but it should not quietly give the Polish company a new technical team or service network without explanation. These are possible actions of its own, still to be assessed. Otherwise every future becomes easy because the character in the story acquired every necessary resource between two slides.

Uncertainty should change how you act

Gather the factors relevant to the choice. Separate what the company can decide for itself from changes in its environment. Preparing local material is an action of its own. The direction of customer needs and how customers organise purchasing require external research. A scenario should not quietly turn the company's plan into a fact about the market.

In the Futures Toolkit from the UK Government Office for Science, scenarios can be built around factors that matter greatly and whose direction of change is uncertain. The matrix approach uses two sufficiently distinct axes. This is a public-policy workshop method; a company must justify its own axes using its decision and evidence.

In our example, one axis might concern the type of project: a predominance of upgrades to existing workstations or of new workstations. The second might concern how contact is organised: a greater role for integrators or greater willingness by factories to speak directly. These are working dimensions to investigate, not established trends. Check whether they are genuinely distinct and whether the extremes make sense for the chosen segment.

Do not choose two names for the same phenomenon. “A growing number of orders” and “higher demand” do not create two independent perspectives. It also helps to avoid an axis where one end means “good” and the other “bad”. A future can favour one cooperation model and make another difficult. That is precisely the difference we want to see.

Three stories should impose three different requirements

Two axes with two ends produce four combinations. In a short exercise we can discuss three selected stories while retaining the fourth in view. Do not present that selection as the complete set of futures. Check whether the omitted combination reveals a significant dependency that would be convenient to overlook.

First story: upgrade projects dominate and integrators lead the contact. Our company needs material explaining how its solution works with an existing workstation, the limits of its own contribution and the data needed for assessment. It becomes important to understand the role of the partner combining different parts of the solution. A general catalogue of technological advantages may not be enough for that discussion.

Second story: new-workstation projects dominate and factories speak directly with suppliers more often. The company needs a way to understand the user's task and material for assessing a particular trial. It must also see what capabilities the customer expects from a supplier. Being ready to make contact does not prove the company can perform every required task.

Third story: factories make direct contact, but most matters under consideration concern existing workstations. The company will need to establish the existing arrangement, constraints and scope of work with other contractors efficiently. This case may require a different description of the offer from the one for an integrator, even if the product's final application is similar.

For every story, record what would need to be visible in reality for its conditions to become relevant. Examples might include the type of enquiries, required input material or the people participating in discussions. Do not invent exact shares and dates merely to make the description look more serious. Precision should follow from evidence, not the appearance of a presentation.

The omitted fourth combination would join new workstations with contact led mainly by integrators. Before closing the exercise, ask at least briefly whether it requires something the previous stories did not reveal. If it does, develop it separately. The number of scenarios should help a discussion about a decision, not close the set after the third attractive name.

Aeneia conceptual photography

For the contact axis, also define what “direct” means. A factory may discuss its need while an integrator remains involved in delivery. Our axis describes the dominant way cooperation begins, not the disappearance of every other participant. This distinction protects against building a fictional future on an ambiguous word.

Put the same idea through different conditions

Now compare one action across all the stories. Material that clearly describes the application and required data may be useful in several cases. An extensive offer assuming permanent responsibility for a whole implementation may depend on capabilities the company does not yet have. The difference reveals a condition to check before making a promise.

Separate actions useful in several futures, conditional actions and those worth postponing for now. There is no need to score every item from one to ten. A sentence explaining why matters more. “The material helps both the integrator and the user establish the scope of a trial” provides a clearer basis than an average score alone.

If the plan includes a new tool, scenarios can prepare questions about whether to build, buy or keep the work manual (in Polish). A tool may be justified for repeated enquiries; before their structure is understood, a smaller trial may be needed. Do not assume that a solution working in one story will be equally necessary in the others.

A recognised hypothesis can then become a business experiment (in Polish). A scenario helps reveal a condition; an experiment tests a specific assumption in a limited trial. Neither replaces the other. Three stories about the future do not confirm how a particular person will react to the proposed material.

When comparing actions, describe the condition for increasing scale. The company may prepare a small discussion document without promising permanent support across a broad market. A larger commitment may require confirmation of needs, a partner or the company's own capabilities. This lets learning begin without hiding the difference between preparation and readiness for wider delivery.

Check who does the work in each case. Material for an integrator may need a different description of cooperation from material for a user. If the company assumes identical support effort in both cases, it should justify that assumption. A scenario should reveal requirements even when meeting them is less convenient than the original expansion story suggested.

Do not combine every desirable feature into one favourite story. The result could be a plan for a case in which everything helps the company. Include inconvenient but meaningfully possible conditions too: a different contact point, a greater role for others' capabilities or a need for a longer explanation of the application. This remains an exercise in possibilities, without invented probabilities. If the team separately forecasts a specific event, keep a record of confidence and later forecast accuracy (in Polish). Do not transfer its numerical assessment to the entire scenario narrative.

Local knowledge can change the axes

When entering a foreign market, it is easy to build scenarios solely from headquarters' experience. Every future then assumes channels, roles and needs familiar from Poland. Ask people who know the selected market which assumption is already too broad or inaccurate. The relationship between local-branch discretion and headquarters (in Polish) can matter to the quality of this research.

Aeneia Oriens helps research a specific market in Korea, Japan or China and prepare material and questions for conversations. For scenarios, a useful scope is local evidence about a selected uncertainty: participants' roles, purchasing arrangements or application. Research should show its basis and limits rather than pretend certainty about the future direction.

Aeneia Oriens

Examine the local basis of a scenario before building it on your company's own habits. Start with the market, segment and uncertainty that changes the proposed way of working.

Discuss the evidence for a market-entry scenario

For current observations, East Asian market monitoring (in Polish) can help. It should answer a specific scenario question. A collection of general economic news may say nothing about the needs of the selected customer. Record the source, date, scope and which assumption the material can test.

For the chosen axis, separate industry-wide data from information about your segment. Overall growth in machinery orders does not confirm the structure of needs at the factories you want to speak with. It may provide context while different material is needed to test the scenario. Record that gap before commissioning research so the next report does not answer the same overly broad question again.

Decide what you will do after a new signal

Naming a signal is not enough. Agree who will assess it and what discussion it could trigger. A series of upgrade enquiries might prompt the company to test new offer material. One unusual message might merely be recorded for observation. Not every event should immediately change the direction of the whole company.

A plan can also be examined through a premortem, a discussion of possible failure before starting (in Polish). Scenarios change the environment; a premortem asks about reasons a particular plan might fail. Together they reveal both an external condition and a dependency the company itself overlooked.

At the next review, retain earlier assumptions and the reasons for changing them. If discussions show that an axis does little to distinguish actions, it can be replaced. Conclusions depending on that axis must then be assessed again. Do not present the new version as though the earlier exercise had contained knowledge acquired only later.

Finally, return to the order of changes: website, automation and expansion (in Polish). The exercise should help choose the next step and name the condition for a larger commitment. The company does not need to decide which future will win. It should know what to check now and how it will recognise when its own plan needs reassessment.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear