Setting Up a PMO That Actually Sticks
A practical guide to establishing a PMO in a mid-sized South African company. How to start small, focus on the highest-impact governance pieces, and earn trust with sponsors in the first 90 days.
Read the guideA few practical pieces that sit well alongside the scenarios on this page. Each one digs into a specific part of getting structured delivery going without turning your operation into a paperwork factory.
A practical guide to establishing a PMO in a mid-sized South African company. How to start small, focus on the highest-impact governance pieces, and earn trust with sponsors in the first 90 days.
Read the guideWhy your RAID log gets ignored and how to make it a living tool. Structuring it for clarity, assigning ownership, and weaving it into your weekly rhythm so it prevents surprises rather than recording them late.
Read the articleSimple techniques to balance workloads across your team using tools you already have. How to spot overload, adjust timelines, and talk trade-offs with stakeholders in plain language.
Read the pieceWant to see how these ideas apply to your own delivery gaps? Book a discovery session or read more about how engagements are structured.
Most mid-sized operations we meet are not failing because of bad people. They are failing because project information lives in scattered emails, personal notebooks, and a shared drive nobody trusts. Our role is to install a light governance layer that makes delivery visible without turning your team into process administrators.
You will not get a mandate to migrate to a new platform. Whether your team lives in Smartsheet, MS Project, or a well-structured spreadsheet, we adapt our scheduling and RAID maintenance to what is already in use. The point is consistency, not software loyalty.
A 40-page project charter that nobody opens after kickoff is waste. We keep charters, RAID logs, and weekly reports tight enough that updating them takes minutes, not an afternoon. If a document does not help a decision, we cut it.
Weekly reports should surface what changed, what is blocked, and what needs a sponsor decision. We write them in plain language with a clear structure, so your steering committee spends meeting time deciding, not decoding status colours.
The gap between a project sponsor and the people doing the work is where most delivery risk hides. We sit in that gap. Resource levelling, RAID log maintenance, and milestone planning are handled by someone whose only job is to keep the delivery moving and the communication honest.
We have coordinated ERP implementations where a missed dependency costs a month, office fit-outs where contractor sequencing matters more than Gantt polish, and marketing launches where the creative team needs protection from scope creep. The context differs; the discipline does not.
A discovery session maps your current planning, scheduling, and reporting practices against what your projects actually need.
A few clarifications so you know exactly what we mean by the terms used here, and what you can expect from a working relationship.
We work with mid-sized operations in Gauteng and the Western Cape. Typical projects are ERP rollouts, office fit-outs, marketing campaign launches, and internal process automation. If your situation falls outside these examples, the discovery session will still help clarify whether we are a fit.
It means moving from ad-hoc task tracking to a clear project charter, milestone plan, RAID log, and resource levelling. We keep documentation lean enough that people actually update it. We do not introduce a new platform unless you ask for one; we work inside your existing tools.
Weekly reports are written for steering committees, not for a filing cabinet. That means a short status summary, decisions needed, and risks that require attention. If a report is not being read, we adjust the format rather than adding more detail.
We adapt to the project management software, spreadsheets, or shared drives your team already uses. The goal is consistency and visibility, not a forced migration. If a tool is genuinely holding you back, we will say so plainly and suggest a practical alternative.
We map your current delivery gaps, look at how decisions are made, and identify where coordination breaks down. You leave with a clear picture of what needs to change, whether or not you continue with us. There is no obligation attached to the session.
We are an independent practice, not a software vendor or a staffing agency. That means our recommendations are not tied to selling you a licence or filling a seat. We are accountable for keeping sponsors informed and teams unblocked, and we measure that in every engagement.