Operating Without a Safety Net: Lessons from Startups, Scale, and Enterprise

A few days ago, on one of my regular long-distance commutes to HQ, I ran out of podcasts and found myself with something that has become surprisingly rare, a bit of quiet thinking time. My mind drifted back over the last few years, across time spent in early-stage startups, companies going through hyper-growth, and large Fortune 500 organisations.

What struck me was not just how different those environments are at a surface level, that part is obvious. Startups are faster, less structured, and more ambiguous. Larger organisations are slower, more defined, and more predictable.

What stood out more was how consistently those environments have changed how I operate.

Each time I have gone through that cycle, I have found myself recognising patterns earlier, trusting my instincts sooner, and moving with a level of clarity that simply was not there the first (or even second) time. That is not because the environments become easier, but because I better understand how they behave, particularly when the structure around you is still forming.

Over time, a pattern has become clear to me. In a startup, the systems you would normally rely on do not yet exist, and that forces you to operate differently. The early phase is not just about learning the business. It is about adjusting how you make decisions in the absence of the signals, structures, and processes you are used to relying on.

This mindset changes your relationship with uncertainty. In a startup, there is very little between you and the reality of the business. You feel ambiguity sooner, decisions carry weight earlier, and there are fewer buffers to absorb the discomfort that comes with that. Learning to work effectively in that environment is one of the most important shifts the early stage demands.

Your north star may not shine as bright.

The first place I tend to feel this shift is in how progress is measured.

In a larger organisation, there is usually a clear way to orient yourself. Targets, dashboards, OKRS, forecasts and operating rhythms provide a shared reference point. Even when those signals are imperfect, they help calibrate performance and provide a sense of whether things are broadly working.

In a startup, that reference point is often incomplete, and sometimes misleading.

Earlier in my career, I remember sitting in a regional leadership discussion where, on paper, everything looked fine. Pipeline was healthy, activity levels were high, and the numbers suggested we were on track. At the same time, the conversations did not feel right. Customers were engaged, but not committed. Deals were progressing, but without conviction. There was a gap between what the metrics were telling us and what the reality felt like.

The numbers are never the full truth, they are just one version of it. That gap is difficult to navigate, because there is no clean way to prove it in the moment. You either trust the numbers, or you trust your judgement.

In a more mature organisation, I have often found that you can wait. There is more data, more history, and more people involved in validating decisions. Even if something feels off, you can let it play out and see what the next set of numbers says. The difference in a startup is that you are forced to act on that reality much earlier.

In a startup, that luxury rarely exists. The data is incomplete, the situation is moving, and waiting for cleaner signals often means you are already behind. You end up acting on what you have, which is usually a mix of partial data, pattern recognition, and instinct.

That shift in reaction matters, because it changes your perception of what good judgement looks like. It is no longer about being right with perfect information, it is about being directionally right early enough to matter.

Laying down concrete, knowing you may need to jackhammer it away.

One of the benefits of being around in the early days of a company is that you get to see how and why processes come together in the first place, and the problems they were originally designed to solve.

What often feels like unnecessary process is usually the result of something that broke earlier. A team needed consistency, clarity, or a way to stop the same issue happening repeatedly, so they introduced structure. Over time, the company grew around those decisions, and what was once pragmatic started to feel heavy.

In a startup, you are living that process in real time, but without the benefit of hindsight.

You introduce structure because the absence of it starts to hurt. You define ways of working because ambiguity slows things down. You document things because relying on memory stops working once the team grows beyond a small group.

The difference is that you are doing this without knowing what “right” looks like yet.

You are effectively pouring concrete while already suspecting that parts of it will need to be broken up later. The system you are putting in place is necessary, but unlikely to survive unchanged as the company evolves.

That creates a constant tension between speed and completeness.

If I have tried to design everything properly upfront, it has slowed the business down. If I have avoided structure altogether, things have become inconsistent and fragile. Most teams, myself included, move between these extremes before finding something that works for the current stage.

What has become clear to me is that you are not building the final version of anything. You are building the next version that allows the company to move forward.

And because that structure is still forming, more of the burden shifts onto how people work together.

When people become the system.

That is where things become more difficult to diagnose.

In a startup, many of the issues that slow you down do not present as obvious problems. There is no clear system failure, no single broken process, and no metric that tells you what is wrong. Instead, progress starts to feel uneven.

Conversations take longer than they should. Decisions that seemed clear become unclear again. Work moves forward, but not always in the same direction. Everyone is busy, but the output does not quite match the effort.

More often than not, this comes down to alignment.

Not in the abstract sense, but in very practical ways. One person believes a decision has been made, while another assumes it is still open. One interprets urgency, while another assumes flexibility. The same words are used, but they carry different meaning. That has changed how I look at larger organisations.

In a larger organisation, structure absorbs some of this. Roles are defined, processes reinforce expectations, and there are enough layers to catch misalignment before it spreads too far.

In a startup, those buffers do not yet exist.

Small gaps in understanding compound quickly. What starts as a minor misinterpretation becomes duplicated work, missed expectations, or frustration between people who are all trying to do the right thing.

The instinctive response is often to add more structure. More meetings, more updates, more process. Sometimes that helps, but it rarely addresses the root cause.

What has consistently mattered more is how people communicate.

Not just sharing information, but ensuring that people interpret reality in the same way. Making assumptions visible before they turn into problems. Taking the time to confirm not just what was said, but what was understood.

That often feels slower in the moment, but in my experience it prevents a significant amount of rework later.

There is also a behavioural layer to this that has become more obvious to me over time.

In an environment with limited structure, experienced people, tend to compensate by stepping in more. Solving problems quickly, providing answers, and keeping things moving feels like the right thing to do, particularly in the early days.

Over time, however, it creates dependency.

People begin to check in before making decisions. They rely on quick answers instead of working through problems themselves. Gradually, decisions funnel through fewer people, and the team becomes slower as a result.

The shift I have had to make as a leader is subtle, but critical. My role moves from being the person who provides answers to being the person who creates clarity and capability in others.

Because in a startup, alignment does not come from structure.

It comes from people.

The anxiety of the infant company. Lean into it!

If weak signals force you to rely more heavily on judgement, imperfect structure pushes more onto people, and people themselves become part of the operating system, then the emotional reality of startup life is almost unavoidable.

There is no real safety net.

In a startup, there is very little between you and the reality of the business. You see problems earlier, you feel uncertainty more directly, and decisions carry weight sooner. That closeness creates clarity, but it also creates discomfort.

That discomfort is not a sign that something is wrong. It is a natural outcome of working in an environment where the business itself is still taking shape. What has changed for me over time is not the level of uncertainty, but my relationship with it.

You have to become comfortable being uncomfortable.

That is far easier to say than it is to do. Even with experience, it is something I am still working on. The difference is not that some people have eliminated the discomfort, but that they have learned to operate in spite of it. From the outside, that can look like confidence. In reality, it is often just familiarity with the discomfort, and a willingness to keep moving anyway.

You have to stop interpreting uncertainty as a sign of failure and start recognising it as part of the terrain. You have to trust that your experience, judgement, and ability to adjust will carry you further than waiting for certainty that is not available.

As businesses scale, some of this gets lost. That is not necessarily a criticism, it is often by design. Mature companies need repeatability, protection from volatility, and mechanisms to reduce unnecessary risk. But one thing the early stage gives you, and the later stages inevitably soften, is the habit of operating without a finished map.

That, more than anything else, is what this phase teaches you.

After spending time across startups, hyper-growth environments, and large enterprises, the most consistent takeaway for me is not about scale or structure, but about how my definition of good has changed.

It is no longer about predictability, control, or completeness. It is about whether we are collectively moving in the right direction, learning quickly, and staying aligned as we go.