Clarity Before Scale: A Conversation with Saikat Das

In fast-moving organisations, speed often feels non-negotiable. But as teams scale, so does the cost of misalignment. In this conversation, Saikat Das shares what he has learned from building and leading at scale—why clarity must come before execution, how leaders prevent rework, and what truly sustainable momentum looks like.

Saikat Das

Leadership | Global Capability Centres | Operating Models | Scale & Execution

Saikat Das is an Enterprise Technical Program Leader at a global retail organisation, with over two decades of experience across service organisations and Global Capability Centres. He has worked closely with global enterprises as they scaled delivery, built long-term capabilities, and navigated complex multi-stakeholder environments. His experience spans platform-led initiatives, enterprise transformation, and operating at scale across geographies. Alongside his industry work, Saikat engages with academic institutions and industry forums to share practitioner perspectives. He writes from lived experience, with a focus on decision-making, clarity, and leadership choices that shape sustainable scale.

You have worked inside organisations where speed was often non-negotiable. Looking back, what were the moments when slowing down would have led to better outcomes?

Saikat: Most of the time, speed was pushed for understandable reasons. There was pressure from the market, from leadership, or from commitments already made. Looking back, the moments where slowing down would have helped were always before execution started. When we jumped into delivery without being fully aligned on intent or decision rights. A short pause there would not have slowed us down. It would have prevented a lot of rework later. Many delays I have seen were not because teams moved slowly, but because they had to correct things that were unclear at the start.

In your experience, what are the first three things that must be clear before an organisation commits to large-scale transformation or expansion?

Saikat: The first is why this change is happening now and what problem it is meant to solve. The second is who decides when priorities conflict, because that happens sooner than expected. The third is who owns outcomes when things do not go perfectly. When these three are clear, teams can move fast with confidence. When they are not, scale tends to magnify confusion.

Global Capability Centres are often built quickly to meet immediate demand. What clarity do leaders typically overlook before scaling headcount or capability?

Saikat: What often gets missed is clarity on the role the centre is expected to play. Is it meant to execute work, to co-own outcomes, or to fully own platforms and decisions. Headcount usually grows faster than shared understanding. When that happens, teams spend energy managing expectations rather than creating value. Early clarity on role and authority changes how people hire, plan, and take responsibility.

Headcount usually grows faster than shared understanding.

How do you distinguish between momentum that is healthy and speed that is merely reactive? What signals do you watch for as a leader?

Saikat: Healthy momentum feels calm and focused. People know what matters and can make decisions without constant escalation. Reactive speed feels noisy. Meetings increase, escalations rise, and decisions keep getting revisited. One signal I watch closely is how decisions are made under pressure. If capable teams hesitate or wait, speed is probably covering up uncertainty.

Healthy momentum feels calm and focused.

You have spoken about intent and decision rights. Why are these foundational, and what tends to break when they are left ambiguous?

Saikat: Intent and decision rights give people confidence. When intent is unclear, teams pull in different directions. When decision rights are unclear, people hesitate even when they know what needs to be done. What breaks first is confidence. Then ownership. Eventually pace slows. This often gets labelled as a talent issue, but in my experience it is usually a clarity issue.

At scale, misalignment compounds quickly. Can you share an example where lack of early clarity created long-term complexity?

Saikat: I have seen situations where a centre started with a delivery mandate but was gradually expected to own platforms and outcomes. That shift was never clearly stated. Different teams adapted in different ways. Governance layers increased and decision-making slowed. Years later, more effort went into untangling roles and responsibilities than into building new capability. The complexity did not come from scale itself, but from unclear intent early on.

How should leaders balance the pressure to deliver results quickly with the responsibility to design systems that endure?

Saikat: Speed and durability are not opposites. Delivering fast without clarity creates problems that show up later. Taking time to define intent, decision rights, and ownership is not slowing down. It helps delivery sustain itself. The balance comes from knowing where to pause briefly so that teams can move faster for longer.

What advice would you give mid-career professionals who are being pulled into speed-driven roles before they feel ready? What clarity should they seek first?

Saikat: I would tell them to seek clarity before judging themselves. They should ask what decisions they are expected to make, how success will be measured, and who owns outcomes when things are mixed. Feeling unready often comes from unclear boundaries, not lack of capability. Getting clarity early helps people settle into the role and grow into it.

Looking back, what clarity did you personally arrive at later than you wish you had about leadership, success, or scale?

Saikat: I realised later than I should have that leadership is less about pushing speed and more about reducing ambiguity. Earlier in my career, I associated momentum with progress. Over time, I learned that clarity creates progress that lasts. That realisation changed how I approached decisions, teams, and trade-offs.

Leadership is less about pushing speed and more about reducing ambiguity.

If organisations were forced to ask just one question before accelerating, what should that question be and why?

Saikat: They should ask a simple question: What are we assuming is already clear? That brings hidden gaps into the open—about intent, decision rights, and ownership. If those assumptions are wrong, speed only locks them in. Asking this question early saves a lot of correction later.

Key Takeaways

• Pause before execution, not during rework

• Define intent early to prevent teams pulling in different directions

• Clarify decision rights so capable teams do not hesitate under pressure

• Establish ownership so accountability does not dissolve during scale

• Watch for the difference between calm momentum and noisy urgency

Closing Reflection

In the rush to grow, speed can look like competence. But this conversation reminds us that what sustains performance is not urgency—it is clarity. When intent, ownership, and decision rights are defined early, teams do not just move faster. They move with confidence, coherence, and durability.