Seven Days on the East Coast

The situation

It was late 2000. QTera had a $250M contract to bring their product live across the United States East Coast. The first $75M tranche was already paid. The pressure was real.

What wasn’t working was everything else.

Twenty-five-plus field technicians spread across multiple states. No single point of accountability. Every team lead reporting upward through different channels, on different schedules, with different information. The project managers back at base were receiving fragmented updates that didn’t connect into a coherent picture of where things actually stood. Teams had been working around the clock for weeks. Fatigue was compounding the confusion.

Nobody was underperforming. The people were capable. The structure wasn’t.

The approach

The intervention was architectural, not motivational.

The first change: a single chain of command. Every technician in the field now had one reporting line. Every team lead had one escalation path. Information stopped moving laterally through informal channels and started moving vertically through a defined structure.

The second change: a daily call. Fixed time, fixed agenda, fixed format. Every lead on the call. Status collected once, centrally, then distributed once. No side conversations running parallel to the official picture. No one working off stale information.

The third change: decisions were made on the call, not after it. If a team was blocked, the call resolved the block. If a dependency needed to be pulled forward, it happened in real time. The call wasn’t a reporting ritual — it was the operational mechanism.

Nothing technically complex. No new tools, no new hires, no reorganisation of the underlying work. Just a clear structure for information to flow through.

The outcome

The entire East Coast went live in seven days.

No overtime. The teams that had been working round the clock for weeks finished the job on a normal schedule. Not because the work got easier — because the waste got removed. The time people had been spending coordinating, chasing updates, and waiting for decisions was now time spent on the actual rollout.

The manager responsible for the project had been living with months of escalating pressure. When it was done, she hugged me. That’s not a metric, but it stays with you. It was relief at a level that only comes from something that genuinely could have broken.

What this illustrates

There is a version of leadership that shows up to build confidence, resolve conflict, and energise a team. That version has its place.

There is another version that shows up, looks at the structure, and fixes it. Quietly. Without theatre. The problems in most struggling projects aren’t human problems — they’re information problems. Who knows what, when, and through what channel.

Structure isn’t bureaucracy. A clear chain of command doesn’t slow people down. It removes the overhead of figuring out who to talk to, and it means the right person gets the right information at the right time.

When that’s working, capable people do capable work. The chaos was never the teams. It was the container they were operating in.

---

This is the kind of problem fractional leadership is built for — coming in at the right moment, fixing the thing that’s actually broken, and handing back a system that works. If you’re facing something similar, let’s talk.