{"id":2708,"date":"2026-01-09T06:55:00","date_gmt":"2026-01-09T04:55:00","guid":{"rendered":"https:\/\/andresass.com\/nicht-kategorisiert\/transformation-tempo-schnelligkeit-vs-gruendlichkeit\/"},"modified":"2026-05-15T16:15:28","modified_gmt":"2026-05-15T14:15:28","slug":"transformation-speed-vs-thoroughness","status":"publish","type":"post","link":"https:\/\/andresass.com\/en\/insights\/transformation-speed-vs-thoroughness\/","title":{"rendered":"Fast enough, thorough enough: The right pace in transformation"},"content":{"rendered":"\n

Why the question \u201cfast or thorough\u201d is the wrong one<\/h2>\n\n

The pressure is real. The market will not wait. Competitors are not sleeping. Investors want to see results. So the message is: faster. More pace. No time for perfection. <\/p>\n\n

Six months later: three projects stall at the same time. Mistakes made in the rush have to be corrected at great expense. The team is exhausted, quality suffers, and the supposed time gain has long since been used up. <\/p>\n\n

\n

The question is not \u201cfast or thorough\u201d. The question is: Where to be fast and where to be thorough? If you do not distinguish between the two, you will end up being neither. Pace is not an end in itself. It is a tool that must be used correctly. <\/strong><\/p>\n<\/blockquote>\n\n

A CEO I supported demanded \u201cmore speed in execution\u201d from his team. Three months later, he asked me for an analysis of why nothing was moving forward despite all efforts. The diagnosis was sobering: execution was not too slow. Decisions were taking too long. On average, the team waited four weeks for approvals while working in parallel on three initiatives\u2014none of which was prioritised. More pressure would not have solved the problem; it would have made it worse. <\/p>\n\n

The difference between pace and frenzy<\/h2>\n\n

Pace and frenzy are often confused. They are the opposite of each other. <\/p>\n\n

Pace<\/strong> means focused energy on what matters. Clear priorities, fast decisions, consistent execution. Pace comes from clarity. Frenzy<\/strong> means unfocused energy on everything at once. Constant changes of direction, rushed decisions, half-finished results. Frenzy comes from a lack of clarity. <\/p>\n\n

Pace<\/th>Frenzy<\/th><\/tr><\/thead>
Focused<\/td>Scattered<\/td><\/tr>
Prioritised<\/td>Everything at once<\/td><\/tr>
Decides quickly, but deliberately<\/td>Decides rashly<\/td><\/tr>
Accepts imperfection strategically<\/td>Produces imperfection due to lack of time<\/td><\/tr>
Delivers results<\/td>Creates activity<\/td><\/tr><\/tbody><\/table><\/figure>\n\n

Organisations that confuse pace with frenzy confuse motion with progress. They are busy, but not productive. As John Kotter shows in his research on organisational change: urgency is productive; frenzy is destructive. The difference is not the energy level, but the direction. <\/p>\n\n

\n

Real pace does not come from more pressure. It comes from less friction and clearer direction. <\/strong><\/p>\n<\/blockquote>\n\n

When speed is critical<\/h2>\n\n

There are situations in which pace is genuinely decisive. Recognising them is a leadership responsibility. <\/p>\n\n

Market windows close.<\/strong> If a competitor is faster, the lead can become impossible to catch up. First-mover advantages are real. Here, speed matters more than perfection. <\/p>\n\n

Crises require a response.<\/strong> If the business model is under threat, if clients are leaving, if regulatory changes are looming, waiting is not an option. In a crisis, a wrong decision is often better than no decision. Standstill is deadly. Acting quickly, even with incomplete information, beats perfect hesitation. <\/p>\n\n

Momentum must be used.<\/strong> After a successful first phase, when the organisation has energy and successes are visible, that is the moment to continue. Momentum cannot be stored. If you pause, you lose it. <\/p>\n\n

Decisions block progress.<\/strong> If teams are waiting, projects are stalled, and uncertainty is paralysing, a quick decision is more valuable than a perfect one. The cost of waiting often exceeds the cost of a suboptimal decision. <\/p>\n\n

When speed is harmful<\/h2>\n\n

Equally, there are situations in which pace makes the problem worse instead of solving it.<\/p>\n\n

When the direction is unclear.<\/strong> Running fast in the wrong direction is worse than moving slowly in the right one. Before you accelerate, it must be clear where you are going. Otherwise, you are only accelerating the burn rate. Anyone who steps on the gas without strategic clarity<\/a> will hit the wall faster. <\/p>\n\n

When mistakes are costly.<\/strong> Some decisions are hard to reverse: mergers, major investments, leadership-level staffing decisions. Here, thoroughness is not a delay; it is risk management. <\/p>\n\n

When people cannot keep up.<\/strong> Transformation without acceptance is instruction without execution. If you move faster than your organisation can follow, a gap emerges between announcement and reality. This gap creates transformation fatigue<\/a>. <\/p>\n\n

When quality makes the difference.<\/strong> Client experience, safety, regulatory compliance: here, shortcuts can become more expensive than the supposed time gain.<\/p>\n\n

When the team is already at its limit.<\/strong> Even more pressure on exhausted people does not create acceleration. It creates mistakes, illness, and resignations. Pace at the expense of people is short-term thinking. <\/p>\n\n

\n

The art is not being fast everywhere. The art is knowing where speed helps and where it harms. <\/strong><\/p>\n<\/blockquote>\n\n

Decision speed vs. execution speed<\/h2>\n\n

An important distinction: fast decisions are not the same as fast execution. Both matter, but they must be managed differently. <\/p>\n\n

A division head from the energy sector described the problem to me like this: \u201cWe need three months to make a decision, and then execution is supposed to happen in six weeks. People rush off, make mistakes, and in the end everything takes longer than if we had planned properly from the start.\u201d This is a typical pattern: slow decisions are compensated for by frantic execution. That does not work.<\/p>\n\n

Decision speed depends on clarity about criteria and priorities<\/a>, availability of relevant information, leaders\u2019 willingness to decide, and acceptance of uncertainty. Execution speed depends on resources and capabilities, clarity of responsibilities<\/a>, process quality, and the team\u2019s motivation. <\/p>\n\n

\n

The biggest time losses do not occur in execution. They occur while waiting for decisions. <\/strong><\/p>\n<\/blockquote>\n\n

The right pace for different topics<\/h2>\n\n

Not everything deserves the same speed. A deliberate differentiation helps. <\/p>\n\n

Fast<\/th>Thorough<\/th>Iterative<\/th><\/tr><\/thead>
Decisions that block others<\/td>Strategic course-setting decisions<\/td>Product development<\/td><\/tr>
Responding to client feedback<\/td>Leadership-level staffing decisions<\/td>Process optimisation<\/td><\/tr>
Corrections of obvious errors<\/td>Investments with long-term commitment<\/td>New ways of working<\/td><\/tr>
Communication in times of crisis<\/td>Changes to core processes<\/td>Technology implementation<\/td><\/tr>
Pilots and experiments<\/td>Cultural change<\/td><\/td><\/tr><\/tbody><\/table><\/figure>\n\n

The categorisation is not set in stone. But it forces a conscious decision: What pace is appropriate here? <\/p>\n\n

When \u201cfaster\u201d makes the problem worse<\/h2>\n\n

Sometimes the call for more pace is the problem itself.<\/p>\n\n

Faster masks a lack of clarity.<\/strong> \u201cWe need to get faster\u201d is often a symptom, not a diagnosis. The real question is: Why are we slow? Missing decisions? Unclear priorities? Too many parallel initiatives? More pressure solves none of these problems. <\/p>\n\n

Faster overloads the system.<\/strong> Organisations have a capacity for change. That capacity is limited. Anyone who ignores it does not create more results, but more resistance<\/a>, more mistakes, and more burnout. <\/p>\n\n

Faster prevents learning.<\/strong> If you only keep running forward, you have no time for reflection. Yet especially in transformations, learning is decisive. What works? What does not? What do we need to adjust? Without these loops, you simply repeat the same mistakes faster. <\/p>\n\n

Faster signals panic.<\/strong> If leadership suddenly demands speed, the organisation asks: What do they know that we do not? Frenzy from the top creates uncertainty at the bottom. <\/p>\n\n

What you can do as a manager<\/h2>\n\n

Pace is a leadership decision. It cannot be delegated. Three levers are decisive. <\/p>\n\n

Differentiate and create decision-making capability.<\/strong> Not everything has to move at the same speed. Define explicitly: What has priority? Where do we accept 80% solutions<\/a>? Where do we need 100%? This clarity gives the team orientation. If decisions take too long, it is rarely due to a lack of will. It is due to unclear responsibilities, missing information, or fear of mistakes. Address the causes instead of increasing pressure. And communicate the why: pace without a rationale creates resistance. When people understand why speed matters, they will support it. <\/p>\n\n

Remove obstacles and find the bottleneck.<\/strong> Often it is not the work itself that is slow, but everything around it: alignment, approvals, waiting times. Identify these friction points and eliminate them. The Theory of Constraints teaches: a system can only be as fast as its tightest bottleneck. Often, this bottleneck is a single person, a department, or a process step. Speeding up everything else achieves nothing as long as the bottleneck remains. Find it, widen it, and the whole system will flow faster. <\/p>\n\n

Protect capacity.<\/strong> Fewer parallel initiatives mean more capacity for each one. Focus<\/a> is the underestimated lever for speed. If you do five things at once, you do none of them properly. Accept imperfection strategically where it is acceptable. The question is not: Is this perfect? The question is: Is it good enough for the next step? <\/p>\n\n

Reality Check<\/h2>\n\n

Before you demand more pace, answer three questions:<\/p>\n\n

First: What exactly is currently preventing us from being faster? If you cannot formulate the answer in one sentence, the diagnosis is missing. <\/p>\n\n

Second: Which decisions have been waiting for an answer for weeks, and what are they blocking?<\/p>\n\n

Third: What can we drop to create capacity for what matters?<\/p>\n\n

If the answer to the first question is \u201ctoo little pressure\u201d, take a closer look. That is almost never the real cause. <\/p>\n\n

The Uncomfortable Truth<\/h2>\n\n

The call for more pace is often a reflex, not a strategy. It feels like action, like leadership strength, like urgency. But real pace does not come from pressure. It comes from clarity, focus, and removing obstacles. It comes from decisions being made instead of waiting. From priorities that are priorities, not just lists. <\/p>\n\n

Sometimes that also means: slowing down to go faster. In motorsport, every driver knows: if you do not brake before the corner, you crash. If you brake, you exit the corner faster. The same applies to transformations. <\/p>\n\n

The fastest organisations are not those with the most pressure. They are those with the greatest clarity. Look at your project list tomorrow: Which of the ongoing initiatives would move faster if you made a single decision that has been postponed for weeks? Make it. <\/p>\n\n

Further Insights<\/h2>\n\n

Transformation fatigue<\/a><\/strong> \u2013 When quick wins become a permanent strategy, the organisation becomes fatigued. Pace without recovery leads to exhaustion. <\/p>\n\n

Quick wins vs. sustainable transformation<\/a><\/strong> \u2013 The balance between rapid successes and long-term change determines success.<\/p>\n\n

All Insights can be found in the overview<\/a><\/strong>.<\/p>\n","protected":false},"excerpt":{"rendered":"

More speed, more pressure\u2014and six months later everything is stuck. The question is not fast or thorough. The question is: Where to be fast and where to be thorough? Three levers for real pace. <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[230],"tags":[235,250,256],"class_list":["post-2708","post","type-post","status-publish","format-standard","hentry","category-insights","tag-leadership","tag-strategy","tag-transformation"],"_links":{"self":[{"href":"https:\/\/andresass.com\/en\/wp-json\/wp\/v2\/posts\/2708","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/andresass.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/andresass.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/andresass.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/andresass.com\/en\/wp-json\/wp\/v2\/comments?post=2708"}],"version-history":[{"count":12,"href":"https:\/\/andresass.com\/en\/wp-json\/wp\/v2\/posts\/2708\/revisions"}],"predecessor-version":[{"id":3018,"href":"https:\/\/andresass.com\/en\/wp-json\/wp\/v2\/posts\/2708\/revisions\/3018"}],"wp:attachment":[{"href":"https:\/\/andresass.com\/en\/wp-json\/wp\/v2\/media?parent=2708"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/andresass.com\/en\/wp-json\/wp\/v2\/categories?post=2708"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/andresass.com\/en\/wp-json\/wp\/v2\/tags?post=2708"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}