Trend analysis and environment: building a crisis-proof company

What is a trend analysis for?

It answers a question no metric can answer: which developments are changing the rules by which success happens in your market?

Pericles put the underlying attitude into words two and a half thousand years ago. The task is to be prepared for the future, not to predict it. That's more than a nice phrase, it's a work instruction: you're not looking for a forecast, you're looking for preparation.

It starts with trend scouting, which means leaving your own knowledge silo. Connect developments from research, technology and society, along with the solutions other companies find, especially young ones, into a cross-industry picture. Watch only your own industry and you'll be the last to see every change.

How do you find the trends that affect you?

Trends are usually sorted into three orders of magnitude. Microtrends are individual observations; they serve as inspiration. Macrotrends bundle many of them and are the level you work on. Megatrends like climate change summarize everything and are too coarse for a decision.

For most companies, working with existing macrotrends from innovation databases and industry assessments is enough. Scouting entirely on your own only pays off once your question is highly specific.

To get started, one round in the leadership team with a single question is enough: which development of the past three years surprised you most? The answers reliably show where your field of vision has blind spots, and they cost you an hour.

The more useful work begins after that. A trend everyone knows about doesn't help. The question is what it means for your offering, your processes and your business model.

How do you assess a trend?

Along three criteria, each on a scale from one to six. Together they produce a trend radar from which a recommended action can be read.

The classification leads to one of three recommendations: act, prepare or observe. The value lies less in the number than in the discussion about it. When two people on the leadership team rate the same trend a one and a five on influence, that's exactly where the conversation needs to happen.

A trend radar is also a communication tool. On a single page it shows what you're paying attention to and what you're deliberately ignoring, and it makes a decision visible that would otherwise stay unspoken. Update it once a year and you'll also see which assessments have shifted.

Pay particular attention to the combination of high influence and low capability. That's the spot where a company gets caught off guard even though everyone knew about the trend.

What belongs in the environmental analysis?

The forces that act from the outside without you being able to influence them. As a structuring grid, a slight variation on a classic has proven itself: political, economic, social, technological, ecological and legal factors.

The grid is a means to an end. Its value is that you don't forget anything, not that you fill every category equally. In a mechanical engineering company, regulation and raw material prices are usually the decisive fields; in a service business, it's demographics and the labor market.

Work with a concrete question per factor instead of a category. So instead of "regulation": which rule currently under discussion would change our calculations? A heading turns into an observation task with an owner.

In practice, this analysis is the one most often dropped, because it's hard to back up with numbers and because everyone believes they're sufficiently informed. Yet these are exactly the forces that topple entire business models, usually with plenty of lead time.

Why consequences instead of probabilities?

This is the most important idea in this module. Focus on assessing consequences, not on how likely a change is. You can't know the probabilities of the future. You can estimate consequences.

That leads to two questions per influencing factor: which change would be dangerous for us, and which would make us stronger? And following from that, an assessment of your resilience: are you fragile at this point, robust, or do you actually gain from volatility?

The practical rule: clear out of your future whatever is prone to disruption. Anything fragile will break eventually, and you can't plan when. The combination of low upside and high downside deserves special attention. Either be very well prepared for it or eliminate it.

This way of thinking changes what you talk about in the leadership team. Instead of debating whether an event will occur, you debate what you'd have to do today so it doesn't knock you over. The second question can be answered, the first one can't.

Here's what that looks like in a mid-sized company: a supplier generates 40% of its revenue with a single customer. Nobody knows the probability that this customer will go away. Everybody knows the consequence. That's enough to make a decision.

How do you phrase the findings?

Separate the observation from the judgment. "Demand for remote maintenance is rising" is an observation. "We need to invest in remote maintenance" is already a decision and belongs in the next step, not this one.

As in every module of the situation analysis: as sentences that contain a cause and a consequence. That turns a list of trends into a statement about you.

Keep it tight. Five to eight findings from both modules combined are enough for a workshop. Show up with twenty and you'll get a sorting debate instead of a decision.

Two examples from the book set the tone: "The need for automation keeps growing and is changing our business model." Or from the environment module: "Customers, banks, and regulators are demanding stricter environmental documentation, which ties up significant resources for us and, in the worst case, affects our license to operate."

For every finding, record what it's based on. A trend statement without a source can't be verified a year later, and that's exactly what separates an analysis you can build on from one you have to start from scratch every time.

Both sentences are uncomfortable, verifiable, and lead straight to a decision. That's the standard for this module and the reason it pays off, even though it doesn't produce a single number.