One decision.
Made well.
When you have one clear call to make and the cost of getting it wrong is real, a Decision Sprint is where you start.
→ Book a free Right Fit call
The Founder's Desk · The Intensive, 8 Weeks · Case Study 04
Structure Before
Strain
An infrastructure business was growing fast, winning large contracts, and running every project through the same small group of people who built the company. No structure. No oversight. No way to see what was at risk, until something went wrong.
The Situation
Winning work.
Losing control.
The business had spent a decade building a reputation in civil infrastructure. The pipeline was strong, government contracts, utility upgrades, multi-year frameworks. Revenue had doubled in five years. The problem was everything beneath the revenue.
Projects were being managed in spreadsheets, WhatsApp threads, and the memories of three people who had been there from the start. Reporting to clients was inconsistent. Budget overruns were discovered late. Resource conflicts were resolved by whoever shouted loudest. The founder was still the de facto project director on every job.
A major contract had recently been delayed due to a resourcing clash no one had seen coming. The client held the relationship, for now. A second miss would cost the business more than the contract.
"We've never failed to deliver. But I can feel us getting closer to the edge. I don't have visibility over what I don't know is at risk."
The Actual Question
Not: do we need a PMO?
But: what kind, and when?
The founder had already decided that some form of project management structure was needed. The real decisions were harder: what shape should it take for a business this size, how quickly should it be built, who should lead it, and what should it govern first?
Getting this wrong in either direction was costly. A PMO that was too heavy would slow down a business that won work on speed and relationships. A PMO that was too light would provide false confidence without actually reducing the risk that was already there.
The Reframe That Mattered
The risk wasn't
project execution.
The instinct was to hire a Project Manager and give them a process. More structure on individual projects. Better Gantt charts, cleaner handoffs, tighter milestones.
But the actual failure mode wasn't project level. It was portfolio level. The business had no way to see across projects simultaneously. No one was tracking which resources were committed where, which clients were most at risk, or which contracts had scope that could blow out. The problem wasn't that individual projects were managed badly. It was that no one was managing the whole.
Instinct said
Hire a project manager
Put a PM on each major job. Add process at the project level. Reduce the founder's load on delivery.
What was actually needed
Build portfolio visibility first
Stand up the oversight layer before adding execution resources. Know what is at risk across all projects before adding more projects to manage.
What We Explored Together
Five structures.
One rule.
"Governance earns its place when leaders can see what they couldn't see before."
The Trade-offs That Mattered
Every option weighed
against the actual risk.
| PMO model | What it creates | The risk |
|---|---|---|
| PMs per contract | Execution rigour per project. Founder gets breathing room on delivery. | Portfolio blindness persists. Resource conflicts still invisible. Founder still holds context no system carries. |
| ✓ Staged PMO build | Visibility before volume. Portfolio reporting from month one. Governance framework built once the oversight layer is working. | Slower to full implementation. Requires a high quality PMO Lead hire in month one. The quality of this hire determines everything that follows. |
| Contract PMO Lead | Immediate capability. No permanent headcount commitment. Specialist from day one. | Institutional knowledge stays outside the business. Exits when the contract does. Does not build for the business's next stage. |
| Technology first platform | Centralised project data. Dashboard visibility. Reduced reliance on individual memory. | Tool adoption without governance design. Data without accountability. A well configured tool over a broken process is still a broken process. |
| Full PMO from day one | Complete function immediately. Maximum structure from the outset. | Change fatigue in a business that runs on speed and trust. Too much, too fast, in the wrong sequence. |
What Was Delivered
Six documents.
One clear build plan.
01
PMO Design Blueprint
The recommended PMO model for a business at this size and growth stage. Function scope, reporting lines, mandate, and what it does not govern in stage one. Built to earn trust before it extends its reach.
02
Staged Build Roadmap
Three stages with defined triggers before each stage begins. Stage one does not conclude until the portfolio reporting cadence is embedded and the founder confirms the visibility gap has closed.
03
PMO Lead Role Scorecard
The profile, accountability framing, and first 90 day mandate for the PMO Lead hire. What this person needs to have built before, what they should not need to be told, and the signals that indicate the hire is working.
04
Portfolio Visibility Framework
The minimum reporting layer for stage one. What the founder needs to see weekly, what the leadership team needs monthly, and the four data points that would have caught the resourcing clash before it became a client incident.
05
Governance Decision Register
Which decisions the PMO owns, which it informs, and which remain with the founder and the delivery team. Designed to protect speed on operational decisions while adding oversight where the risk is highest.
06
30 Day Activation Plan
What stops immediately. What gets centralised before the PMO Lead starts. The three conversations the founder needs to have with the delivery team before the first governance meeting. First thirty days sequenced so the PMO earns credibility, not resistance.
The Sequence That Replaced the Risk
One thing at a time,
in the right order.
Now
Build the oversight layer
Before adding any execution resource, the business needs to see across its entire project portfolio. Resource commitments, contract milestones, and client risk mapped in one place. The founder stops being the only person who holds the picture.
Next
Build the governance framework
Once the portfolio is visible, build the governance layer. Who approves what, at what threshold, and with what information. Project stage gates introduced. Delivery standards documented. Not imposed, built with the delivery team so they own it.
Later
Scale delivery capability
With oversight in place and governance embedded, the business can now hire project managers, onboard subcontractors, and pursue larger contracts without the risk returning. Growth is no longer held together by three people and institutional memory.
Signals tracked · On time delivery rate · Resource utilisation across portfolio · Client escalations by month · PMO Lead time to embed · Founder hours recovered from project coordination · Contract pipeline vs delivery capacity ratio
What Changed
A build plan replaced
a lurking liability.
The founder stopped treating the absence of structure as a risk they could outrun with hard work and good relationships. A clear sequence replaced a growing sense of exposure. The PMO became a designed decision, defined scope, staged timeline, right hire, right sequence, rather than something that would eventually be forced on the business after a worse client incident.
3
Stage build plan with a trigger before each stage begins
30
Day activation plan with sequenced founder actions
6
Documents. One clear PMO mandate from day one
If you're growing faster than your governance, let's work it out.
The Intensive gets you to a clear structure, a staged build plan, and a first move you can make this month. With the reasoning behind it.
Book a Right Fit Call← Back to case studies