I Have Led Teams From 5 to 3,000+. The Mechanisms Changed. The Responsibility Didn’t

Over a 35-year career in product engineering, I have led teams at almost every scale.

One of my earlier leadership experiences was managing a team of five engineers working on telecom software for Nortel Networks' Class 5 switching systems. Across those 35 years, I have led teams and organisations ranging from five people to more than 3,000. Today, I lead an organisation of more than 300 people at AlgoShack.

Vadeesh Budramane, Founder & CEO, AlgoShack Technologies

If you had asked me at each stage what leadership required, I probably would have given you a different answer every time.

I would have been wrong every time, too.

Because the fundamental job never really changed. It just took me three decades to see that clearly.

The Lesson Has Nothing to Do With Scale

When you lead a team of five, you know everyone.

You know whose code-review comments are too harsh and whose are too soft. You know who needs a deadline broken into three smaller milestones and who does their best work when given the objective and left alone.

Leadership at that size is largely about attentiveness. It is almost intimate.

When you lead three thousand people, you cannot possibly know everyone that way. You begin relying on structures: reporting lines, dashboards, OKRs, reviews, and management layers.

It is tempting to believe that leadership at scale becomes a fundamentally different discipline - less personal and more systemic.

I believed that for a long time.

I built processes. I trusted the processes. And I watched good people quietly disengage anyway, because sometimes the process was doing the listening instead of me.

What I eventually understood was that the size of the organisation changes the mechanism through which you lead. It does not change the fundamental responsibility.

At five people or three thousand, the job remains the same: remove the obstacles between capable people and their best work, give them clarity about what matters, and be honest with them about what is actually happening.

Clarity Is Not a Luxury of Small Teams

There is a comforting myth that small teams get clarity for free: you are all in one room, so of course everyone knows what matters.

They don't.

I have seen five-person teams drift for weeks because nobody said clearly which of three competing priorities mattered most.

And I have seen organisations of several thousand people move with remarkable alignment because leadership was relentless about repeating the same few priorities in every relevant forum, every week, until doing so almost felt boring.

Clarity does not automatically disappear when organisations grow. Nor does it automatically exist because an organisation is small.

It is a leadership discipline regardless of headcount.

The moment I stopped assuming that smaller teams had clarity by default and started treating clarity as something leadership owed every team, the quality of execution changed.

The way you create that clarity may change with scale.

With five people, you might explain the priority yourself.

With fifty, your managers need to understand it well enough to carry the same message.

With three thousand, you need a leadership system that reinforces that message consistently across teams, meetings, and decisions.

The mechanism changes.

The responsibility for clarity does not.

The Truth Gets Filtered Through Layers

Another challenge becomes more visible as organisations grow: information changes as it travels.
There is a natural tendency for people to tell leaders what they think those leaders want to hear. The greater the organisational distance between leadership and the people closest to the work, the more that tendency can compound.

In a team of five, you might discover a problem because someone mentions it over lunch.

In an organisation of three thousand people, the same problem can travel through multiple reporting layers, with each layer unintentionally softening it, until what began as a serious concern reaches senior leadership as a footnote on a slide.

That is why I have made a habit of creating ways to hear directly from people several layers away from me.

Sometimes that means skip-level conversations. Sometimes it is an informal discussion. Sometimes it simply means spending time with the people closest to the work and asking questions without a presentation sitting between us.

The purpose is not to bypass managers.

Good managers are essential to scale.

The purpose is to make sure organisational layers do not inadvertently filter out the signals leadership most needs to hear.

As AlgoShack grew into an organisation of more than 300 people, one challenge became increasingly important to me: how do we make sure bad news can travel through the organisation just as quickly as good news?

Because when problems become harder to communicate upward, they rarely become smaller. They simply become more expensive by the time leadership sees them.

What Actually Scales, and What Never Should

Systems should scale.

Dashboards should scale.

Reporting structures, operating rhythms, performance reviews, and management layers should evolve as the organisation grows. They are necessary because no leader can maintain the same direct relationship with several thousand people that they had with five.

But building better systems should not become an excuse for becoming disconnected from reality.
I have watched leaders confuse the two: assuming that because they had built stronger management systems, they had earned the right to become less personally connected to what was happening inside the organisation.

I have come to believe the opposite.

Good systems should create enough visibility and consistency that leaders can spend their attention where systems are weakest: judgment calls, difficult conversations, ambiguous decisions, and signals that will never fit neatly into a dashboard.

The goal is not for a leader to personally intervene in everything.

That does not scale, and it should not.

The goal is to build an organisation where leadership can still reach the truth when necessary - and where people throughout the organisation feel able to tell that truth without having to navigate unnecessary layers of fear or interpretation.

What should never scale away is your responsibility to know, through both formal systems and direct channels, whether the people doing the work have what they need and whether leadership is hearing reality as it actually is.

After 35 years, I have come to believe that leadership at scale is not about becoming more distant from the work.

It is about building mechanisms that allow you to stay close to the truth even when you can no longer stay close to every person.

The team size changed. The responsibility never did.

Vadeesh Budramane is the Founder and CEO of AlgoShack Technologies. A product engineering leader with more than 35 years of experience, he has worked across healthcare technology, embedded systems, fintech, telecom, and enterprise software.