Back to articles

Strategy & Organisation

Everyone is busy, but where are we actually going?

Why organisations can fail not because of too little effort, but because of a lack of shared direction

Three people look at a wall full of sticky notes; beside it, the view opens onto a landscape with a winding path.

A company can be full of movement and still make hardly any progress. Projects are running, meetings take place, key figures are discussed, employees are fully occupied. Every department can explain what it is currently doing. But when asked which shared result this is meant to bring closer, the answers turn out to be surprisingly different.

One group talks about growth. The second about cost reduction. A third wants to reduce risks. The IT team is working on a new platform, sales is demanding additional features, production finally wants stable processes. Each demand is understandable in its own right. Taken together, they can block one another.

The obvious reaction is then often: we need to prioritise better. That may be true. But prioritisation only helps if it is clear by which criteria decisions are made. Without a shared direction, you can re-sort a long task list and still remain without orientation.

Being busy is not yet progress

In many organisations, performance becomes visible indirectly through activity. Those with many appointments are considered in demand. Those who respond to numerous requests appear committed. A project that produces a new presentation every week gives the impression of constant movement.

This activity can be productive. But it can also hide the fact that the decisive questions remain open. What are we working for? What change is to come about, and for which people? And which activities actually contribute to it?

I would therefore separate three terms: activity describes what we do. Result describes what comes out of it. Impact describes what changes as a result for customers, employees or others affected. A new piece of software is a result. That employees can reliably find information, prepare decisions more quickly or avoid errors is a possible impact. The impact must be verified, not merely assumed.

This distinction can be uncomfortable. It makes visible that intensive work does not automatically produce a relevant change. A team can meet deadlines and deliver the wrong thing. A department can improve its local key figures and thereby worsen the overall process.

How goals drift apart

Take a medium-sized service company. The executive board calls for better customer orientation. At the same time, sales is given an ambitious sales target, customer service is to shorten its handling time and IT has to cut operating costs.

After a while, tensions emerge. Sales sells custom solutions because they promise sales. Customer service tries to close these cases as quickly as possible. IT points to missing standards and rising maintenance effort. All three areas partly meet their targets. Nevertheless, the customer experience deteriorates.

The example is hypothetical, but its mechanism is familiar: local goals can produce rational behaviour that is harmful to the whole. The solution then does not lie in demanding even more motivation from each team. First, conflicting goals must be made visible and decided in a binding way.

The question "What is more important?" must not be permanently delegated to the employees doing the work if they lack the authority to decide. Leadership must carry the conflict. Otherwise, an unresolved strategic tension turns into a personal dispute between departments.

Vision is not a nice sentence on the wall

The term vision has a bad reputation when it is confused with abstract statements about excellence, innovation and the future. Such a statement can fit almost any company and therefore hardly helps in a concrete conflict.

A usable direction must be distinguishable. It should explain what change an organisation is striving for, for whom this change matters and how one can tell whether one is getting closer to it. It does not have to anticipate every operational decision. But it should help to choose between justifiable alternatives.

For the business context, a simple test question can be formulated: can employees understand the connection between the purpose of their company, the concrete goals and their daily work?

If this connection is missing, the vision becomes decoration. Then almost anything may be started in the name of the big goal. The very opposite would be needed: a shared direction must help to reject initiatives that are interesting but do not fit the agreed priorities.

Strategy comes from decisions, not adjectives

Strategy means making decisions with limited resources. Anyone who wants to achieve everything at the same time may not yet have made the actual choice.

In a strategy meeting, therefore, the question should not only be which initiatives are desirable. Just as important is the question of which ones are deliberately not pursued. What will be ended? What will be postponed? Which customer group will initially receive less attention? Where do we accept a disadvantage in order to gain a relevant advantage elsewhere?

Such decisions are prone to conflict. They limit room for manoeuvre and disappoint expectations. Precisely for this reason, they are sometimes replaced by terms everyone can agree with. Nobody objects to "more quality", "greater customer proximity" or "more efficient processes". But these words do not decide what happens when quality requires additional time and efficiency at the same time demands more speed.

A good strategic statement must stand up to the concrete conflict of goals. Otherwise it is more a wish than a source of orientation.

Where shared understanding gets lost

Between a decision by the executive board and daily action lie many translations. A strategic intention becomes a programme. The programme becomes projects. Projects give rise to tasks, budgets, responsibilities and key figures. With every translation, assumptions can be lost or new ones added.

A project manager may understand "simplification" as fewer process steps. A specialist department understands it as fewer queries. IT thinks of a smaller number of systems. The terms seem identical, the expectations are different.

That is why it is not enough to announce a vision once. Shared direction comes from repeated clarification. What does the goal mean in this situation? Where do conflicting goals arise? Which assumptions have changed? And what do we need to decide anew?

Organisational research on so-called sensemaking describes how people jointly develop meaning and orientation for action out of ambiguous situations. For practice, this need not give rise to a new buzzword. What matters is that an organisation must not take the meaning of a change for granted.

A useful touchstone: what would we stop doing?

I consider one simple question particularly telling: if the stated direction really applies, what work would we do differently tomorrow, or stop doing altogether?

If there is no answer to this, the direction may be too general. Anyone who promises more customer orientation should be able to explain which decision would turn out differently in the customer's favour in a conflict of interests. Anyone who prioritises standardisation must say which exceptions will no longer be approved in future. Anyone who puts people at the centre should show which existing incentives or processes are incompatible with this.

The answer does not have to contain every detail immediately. But it must reveal a consequence. Without a consequence, the vision remains a form of words that commits nobody to anything.

Verify impact, don't just tick off deliverables

It would be unfair to demand an immediately measurable benefit from every activity. Some investments first create the preconditions. Research, training and work on culture often do not show their impact by next Monday. Nevertheless, they too should have a comprehensible impact hypothesis.

An organisation might, for example, decide that customer enquiries should no longer get lost between several offices in future. From this it derives an initiative to clarify responsibilities and information flows. The project can be technically completed while employees continue to forward emails because nobody has clarified the responsibilities in a binding way.

A final report focused solely on deliverables would report success. An impact-oriented view also asks: how often are enquiries still being forwarded? Do employees know who is allowed to decide? Has the situation improved from the perspective of those affected?

The measurement must suit the matter. Figures make sense, but not everything can be neatly squeezed into a single key figure. A combination of observable results, qualitative feedback and an honest look at side effects is often more meaningful than an artificially precise index.

Leadership also means bearing tensions

A clear direction does not eliminate conflicting goals. It is what makes them workable in the first place. A company can want to be economically viable, socially responsible and technically reliable at the same time. In concrete situations, these goals will have to be weighed against one another.

It would be convenient to cover up these tensions with appeals to team spirit. Employees are then supposed to find a solution together, even though they have neither the resources nor the decision-making authority. This leads to frustration and often to unofficial compromises whose consequences nobody explicitly takes responsibility for.

Good leadership also consists in taking up such conflicts, disclosing the basis for decisions and making a reasoned choice. Whoever decides should explain which alternative was not chosen and what risks this entails. This does not automatically increase agreement. But it creates traceability.

From the big goal to the next sensible step

A shared direction only becomes effective when it translates into daily decisions. This does not require a monumental new method. Often four clarifications are enough: what concrete result are we aiming for? What difference should this make for those affected? Who decides when requirements compete? And which ongoing activities will be stopped or changed for this?

A fifth point is often forgotten: when do we check whether the assumptions still hold? A good direction is neither a daily whim nor an unchangeable dogma. It must be stable enough to provide orientation and open enough to learn from reality.

The organisation therefore needs a rhythm in which deviations are not seen as a disruption of the success story, but as necessary information. Anyone who wants to achieve an impact must be allowed to know when it fails to materialise.

Orientation must also remain open to new information

A clearly formulated direction can itself become a problem if it is defended against every new observation. The market changes, an assumption about customers proves wrong or a technology does not deliver what we expected. Then the vision must not serve as the reason why nobody should voice doubts any more.

The distinction between purpose and path helps. The purpose can endure over a longer period: for example, we want to handle customer enquiries more reliably. The path there may change if a proposed platform is not suitable or a process correction promises more impact. Those who mix up these levels often cling to a solution because they do not want to give up the overarching goal.

Leadership therefore needs not only the ability to explain a direction. It must also be able to state which observations will trigger a new decision. This strengthens commitment without sacrificing the ability to learn.

How I would recognise progress

Not by the fact that all calendars are full. Nor solely by the fact that projects are completed on schedule. But by the fact that employees can explain how their work contributes to the shared goal, that conflicting goals are decided promptly and that the results make a demonstrable difference for the people affected.

Perhaps we would need to start fewer projects at the same time for this. Perhaps scrap some key figures. Perhaps forgo an attractive but unsuitable opportunity.

That is not necessarily less ambitious. It could be the precondition for making any progress at all.

A company needs not only people who achieve a lot. It needs a shared idea of what their effort is worthwhile for and what impact it should achieve. Only then does being busy become movement with direction.

Related insights