Corporate cosplay vs real scale: scale without bureaucracy

There’s a moment in a business when “moving fast” stops feeling like momentum and starts feeling like strain.

The team is busy. Sales might even be up. But the same issues keep resurfacing, just louder now because the volume is higher. Things that used to “work well enough” suddenly don’t: handoffs, decision-making, content, delivery, forecasting, focus. Growth starts amplifying every weak link.

That’s usually when someone says: “We need to professionalise.”

Sometimes they’re right. But what often follows is the wrong kind of maturity: more meetings, more reporting, more process, more theatre. The organisation looks more grown-up, while execution gets slower and outcomes don’t improve.

I’ve spent most of my career drawn to a very specific part of the work: cracking messy problems, getting clear on what actually matters, and then doing the harder bit - turning that clarity into results. Working independently has pulled me even closer to reality: you don’t get to stop at the answer. You have to live with whether it works next week.

So this isn’t a piece about “best practice”. It’s about the few disciplines that help teams scale without suffocating themselves — and how to keep the substance of professional management without slipping into corporate cosplay.

Corporate cosplay, defined

Corporate cosplay is when a company borrows the forms of professional management without installing the substance.

It’s the belief that maturity looks like:

• heavier planning cycles,

• more dashboards,

• more stakeholders in every decision,

• “proper” governance everywhere,

• and a calendar full of updates.

It can feel reassuring. It can even look impressive from the outside.

But it often does one thing very well: it makes you slower.

Real scale is much less aesthetic: Make the engine work. Then scale it.

And be ruthless about the difference between those two activities.

Why this matters for corporates too

Although I’m talking a lot about founder-led businesses, none of this is just “start-up stuff”. If anything, corporate teams need it even more, because complexity is always waiting to creep in.

James Allen and Chris Zook’s work on the Founder’s Mentality makes a blunt point: as organisations grow, they often lose their edge - the insurgent clarity of what they’re here to do, the obsession with the front line, and the owner’s mindset that keeps decisions sharp.

What I’m sharing below is my practical, weekly-operating version of that: how to turn those ideas into focus, trade-offs, metrics, and a cadence that actually moves performance.

Where the river narrows, the work gets real. Fix the constraint, and flow returns.

Lesson 1: Strategy isn’t usually missing. The constraint is.

Most leadership teams don’t lack ambition. They don’t lack ideas. They don’t lack analysis.

They lack agreement on the one thing that matters right now.

If you can’t name the constraint, everything becomes a priority. Teams start ten things and finish none. You get motion, not traction.

The practical question is: What is the single constraint that, if improved, unlocks the next step, and if not improved, makes growth fragile or value-destructive?

In a founder-led business, that constraint might be acquisition economics, content throughput, conversion, fulfilment capacity, retention, cash.

In a corporate team, it’s often decision latency, unclear ownership, incentives pulling in different directions, a gap between “head office” and reality, or a product/process complexity tax nobody wants to name.

Same principle either way: pick the constraint, or the constraint picks you.

And if you want a fast diagnostic: look at where the organisation is quietly compensating with heroics. That’s usually your constraint wearing a disguise.

Lesson 2: Follow behaviour and the money. It cuts through the noise.

When a business is under pressure, the loudest story wins.

The most senior person’s view wins. The most recent crisis wins. The team’s favourite project wins.

A more reliable approach is boring, and that’s the point:

• follow customer behaviour (where do they hesitate, drop, complain, churn?), and

• follow the money (where is contribution created or destroyed? what has to be true for growth to be profitable?).

This isn’t about building a perfect analytics stack before you act. It’s about avoiding the most expensive mistake available: scaling a leaky engine because the top line looks exciting.

This lesson translates cleanly into corporate life too. Big companies can have excellent reporting and still be oddly blind to what customers are actually experiencing — and to how value is really being created at the front line.

If your internal debates don’t resolve after you’ve looked at behaviour and the money, it’s usually because the debate isn’t about facts. It’s about trade-offs someone doesn’t want to own.

Which brings us to the next lesson.

Lesson 3: Focus is not a value. It’s what you stop doing.

Most teams think they have a prioritisation problem.

More often, they have a stopping problem.

They keep launching “good ideas” in parallel. Not because they’re foolish — because it feels safer to do many things than to bet on a few. Especially in environments where being busy is mistaken for being effective.

Real focus looks like:

• pausing initiatives you like,

• cancelling projects that have momentum but not impact,

• delaying “brand work” (or “platform work”, or “re-org work”) until the fundamentals are stable,

• and resourcing a small number of moves properly.

This is where corporate cosplay shows up fastest: teams create rituals that simulate focus (planning days, re-prioritisation workshops, slide packs with traffic lights), but avoid the hard calls that create actual focus.

If you want to test whether you have focus, don’t ask for the list of priorities. Ask:

• what did you stop last month?

• what did you say no to this week?

• what are you deliberately not touching this quarter?

If the answer is “not much”, you don’t have focus. You have a wish.

Lesson 4: One KPI can do more than a dashboard of twenty

Once the constraint is clear, you need something the organisation can steer by.

This is where well-meaning teams often disappear into dashboards.

They build a cockpit with twenty instruments, and then wonder why nobody can fly the plane.

What tends to work better is brutally simple:

• one primary KPI that reflects the constraint,

• a small number of input metrics the team can actually influence,

• and a cadence where decisions are made against that KPI every week.

The KPI matters less than what it forces:

• tight definitions (what counts, what doesn’t),

• one shared version of the truth,

• and an end to “we’re doing great” stories that don’t show up in the economics.

This is an unglamorous point, but it’s a real one: I’ve seen teams stall for months because they never agreed on definitions. Everyone reports success. The business doesn’t feel it.

A single metric, well-defined and used properly, is often the fastest route to alignment.

And to be clear: this isn’t “metric obsession”. It’s decision discipline. The whole point is to reduce noise, not increase it.

Lesson 5: Progress is bottleneck removal, not opportunity hunting.

There’s a difference you feel when you move from advisory into operational work.

In theory, people talk about “opportunities”.

In practice, you spend most of your time removing what’s blocking the engine.

At the scaling stage, the constraints are often unsexy and physical:

• not enough creative to feed performance channels,

• weak handoffs across the funnel,

• unclear roles so everything escalates to two people,

• operational capacity lagging demand,

• systems that were “fine” at one level and break at the next,

• a backlog of messy basics nobody wants to deal with.

This is where pragmatic rigour matters: not perfect analysis, but clear diagnosis and decisive action.

A useful reframing here: Stop asking “What could we do?” and start asking “What is currently stopping us?”

That shift alone can save months.

Lesson 6: When you win, the constraint moves. That’s not failure, it’s the game.

One of the most predictable patterns in scaling is:

You fix one thing, performance jumps… and the next bottleneck becomes painfully visible.

That’s not bad news. That’s progress.

The mistake is treating the next constraint as a surprise or a crisis, rather than the system doing what systems do.

This is why “professionalisation” shouldn’t mean building a heavier machine.

It should mean building a repeatable loop:

1. name the constraint,

2. align around it,

3. remove it,

4. absorb the growth,

5. repeat.

That loop is the operational backbone of founder-like execution in any organisation — small or large.

In corporates, this is the difference between “transformation as programme” and transformation as a living operating rhythm.

Lesson 7: The real value of a consulting toolkit is decision quality under pressure.

The most useful things I’ve carried across contexts aren’t frameworks or neat decks.

They’re the disciplines that hold up when the work is messy:

• structured problem-solving without analysis paralysis,

• clarity on trade-offs (and the courage to name them),

• simplifying complexity into a few decisive moves,

• building alignment quickly across functions,

• and keeping a cadence where decisions get made and learning accumulates.

In founder-led businesses, these skills prevent chaos without killing speed.

In corporate teams, they prevent bureaucracy from becoming a shelter for slow thinking and slower execution.

A blunt way to put it: In a scale-up, you can’t afford to be vague. In a corporate, vagueness becomes a lifestyle.

The antidote in both cases is the same: precision where it counts, and momentum behind the few moves that matter.

A practical “minimum viable discipline” (without turning into a corporate)

If you want to make this tangible, here’s a simple way to start — whether you’re running a scale-up team or a corporate initiative that’s stalled.

Step 1: Pick the constraint (48 hours)

Get the relevant leaders in a room and force an answer:

• what is the constraint?

• what evidence supports that?

• what happens if we don’t fix it?

If you leave with “it depends” or “we have a few”, you haven’t done the work yet.

Step 2: Define the steering metric (one week)

Choose one primary KPI tied to the constraint. Define it properly. Agree the data source. Agree the cadence.

If the KPI can be gamed or misunderstood, it will be.

Step 3: Run weekly “decision meetings” (not update meetings)

One meeting, one decision list, one owner per decision.

Less presenting. More choosing.

If your meetings are mostly people “sharing”, you’re cosplaying coordination.

Step 4: Sprint the bottleneck (two weeks)

Pick the biggest blocker and run a short sprint:

• what will we change?

• what will we measure?

• what’s the stop rule?

• what will we do if it doesn’t work?

This is how you build an organisation that learns quickly without turning learning into a hobby.

Keep the physics. Ditch the ceremony.

Founder-led businesses don’t need corporate rituals to scale. Corporate teams don’t need start-up chaos to move fast.

Both need the same underlying physics:

• clarity on the constraint,

• ruthless focus,

• one steering metric,

• bottleneck removal,

• and a cadence that turns learning into action.

The ceremony is optional. The physics isn’t.

If you’re scaling and it feels fragile, don’t reach first for more process. Reach for better decisions, made faster, about the few things that actually move performance.

That’s what real professionalisation looks like.