How to Plan Development—Especially When You See Further Than Others

Insights

Vision provides direction, but development requires a pace the organization can sustain.

An ambitious vision can be a major organizational strength—provided it is translated into actions that the team can understand, carry, and implement in everyday work.

One of the most difficult leadership situations occurs when a leader sees possibilities that the team does not yet understand or cannot translate into practice. The leader notices new trends, draws inspiration from more mature management models, and wants to build an organization that is more accountable, flexible, and autonomous.

The intention may be excellent. The problem begins when the vision is implemented faster than the organization is ready to carry it. Greater accountability is then replaced by uncertainty, autonomy by chaos, and development by frustration on both sides.

The problem was not the vision itself. It was the pace, sequence, and lack of sufficiently strong foundations. So how should development be planned when you see further than the organization is ready to go today?

Begin with an honest diagnosis of the organization

The first mistake made by leaders with a strong vision of the future is viewing the organization mainly through the lens of where they want to take it. They see potential, a future operating model, and a development direction, but may overlook that the team still operates according to different rules, needs, and habits.

Before implementing major change, it is therefore worth checking where the organization actually is today: how people make decisions, what they need in order to act responsibly, how they understand collaboration, what motivates them, and which mechanisms of the working culture are ready for the next step—and which still need reinforcement.

Are roles and responsibilities sufficiently clear?
Can the team make decisions without constantly referring back to the leader?
Is autonomy understood as accountability for outcomes, or merely as the absence of structure?
Does the organization have indicators that show the actual effects of work?

Plan the next step, not a giant leap

Organizational development rarely works as a leap into a complete, ideal model. More often, it is a sequence of well-chosen steps that strengthen successive team capabilities: accountability, agency, collaboration, decision-making, autonomy, and learning.

Attempting to skip several stages at once usually creates tension. The team receives solutions it cannot yet use, while the leader becomes frustrated that people do not understand the direction. In reality, the issue is often not unwillingness but the absence of foundations needed to carry the new way of working.

“Development means building a road the organization can actually travel.”

Translate the vision into concrete action

The fact that a leader sees the longer-term direction does not mean the entire organization can immediately act as though it has already arrived. Vision is necessary because it gives change meaning. It cannot, however, replace current goals, clear tasks, and operating principles.

The leader’s role is to hold the broader direction while guiding the team through actions that are possible here and now. This means translating an ambitious vision into real operational decisions.

What are we changing this quarter?
Which decisions will we make differently?
What behaviors do we expect from leaders and teams?
Which processes will we strengthen first?
How will we know that the change is beginning to work?

“Vision should set the direction, but the map used by the team must reflect the organization’s current stage of development.”

Use language the team can apply

Leaders with strong vision often use language that describes the future direction well but does not always help people understand what they should do differently today. Concepts such as “self-management,” “greater autonomy,” “teal organization,” or “holistic approach” can be inspiring, but they remain too general unless translated into concrete decisions, rules, and behaviors.

Employees usually need answers to more practical questions: who makes which decisions, what am I accountable for, how do we measure outcomes, what changes in my daily work, what should I bring to the leader, and what should I resolve independently or with the team?

The message then stops being an abstract idea and becomes a practice that people can understand, rehearse, and gradually integrate into everyday work.

Strengthen the foundations before introducing advanced solutions

Organizational development does not mean cutting the organization off from earlier ways of working. More mature operating models require foundations that often need to be organized first: clear accountability, effective communication, decision-making ability, measurement of outcomes, and trust-based collaboration.

Without these foundations, advanced solutions may quickly turn into chaos. People gain more freedom but still lack shared rules, decision criteria, and clarity about who is responsible for what.

Before implementing ambitious changes, check whether the organization has sound fundamentals:

clear roles and areas of responsibility,
transparent decision-making principles,
indicators showing real work outcomes,
communication that also allows difficulties to be discussed,
the team’s ability to learn from feedback.

Najważniejsze

Podsumowanie

An ambitious vision is a major leadership strength, but it is not enough for an organization to develop in practice. Its value emerges only when it is translated into a pace, language, and actions that the team can understand, implement, and sustain in everyday work.

It is therefore worth:

beginning with an honest organizational diagnosis,
planning the next realistic step rather than a giant leap,
translating vision into concrete actions and decisions,
using language the team can apply in practice,
strengthening the foundations before introducing more advanced solutions.