We don't collect testimonials after a single workshop. These comments come from sponsors and project leads we've worked alongside through ERP rollouts, fit-outs, and internal automation programmes.
"The weekly report finally gets read by our steering committee. Before, we were sending long status emails that nobody opened. Now the RAID log is part of every meeting and decisions actually get made."
Operations Director
Manufacturing firm, Gauteng
"We were mid-way through an ERP rollout and losing track of dependencies. The resource levelling alone saved us from burning out two key team members. Documentation stayed lean enough that people actually updated it."
Programme Manager
Financial services, Western Cape
"What stood out was that they worked inside our existing tools. No new platform to learn, no heavy process. Just clear milestones, a maintained RAID log, and a coordinator who kept sponsors informed without nagging the team."
Head of Marketing
Retail brand, Gauteng
Mid-sized operations in Gauteng and the Western Cape moving from ad-hoc tracking to structured delivery.
These are the practical concerns that come up most often when a team decides to bring in an independent project coordinator. The answers are straight, without the usual consulting fog.
We work inside whatever you already use, whether that is Microsoft Project, Smartsheet, Jira, or a simple shared spreadsheet. The point is to add structure without forcing your team to learn a new platform. We set up the schedules, RAID log, and reporting in your current environment so adoption is not another project on its own.
We start with a short discovery phase to map your delivery gaps and understand the stakeholders involved. From there we draft the project charter, build the milestone plan, and set up the RAID log. The first two weeks are mostly about getting a clear baseline so that weekly reporting has something real to reflect.
We avoid the trap of building heavy process documents that nobody opens after the kickoff. Our templates are short, focused on decisions and next actions, and tied to the weekly rhythm. If a document does not help someone make a decision or unblock a task, we cut it.
Most of our work sits with mid-sized operations running ERP rollouts, office fit-outs, marketing campaign launches, or internal process automation. These projects usually have a clear sponsor but no dedicated coordinator, which is exactly where we step in to keep things moving and visible.
Weekly reporting is built around what the steering committee needs to know: progress against milestones, open risks, decisions required, and anything that is blocked. We keep the format consistent so that reading the report takes minutes, not an hour. The goal is a report that gets read and acted on.
That is exactly the situation we are used to. We start with the smallest governance pieces that give immediate value, like a clear milestone list and a simple RAID log. Over time the structure grows as the team sees the benefit. If you want to understand how we approach this transition, our guide on setting up a PMO covers the first 90 days in detail.
We collect feedback the same way we run projects: at checkpoints, in plain language, and with enough detail to act on it. These are notes from sponsors and coordinators we have worked alongside in Gauteng and the Western Cape.
Operations manager, logistics software rollout
"We had been tracking tasks in a shared sheet for a year. The first thing that changed was the weekly report: it showed the steering committee exactly where we were stuck and what we needed from them. Decisions that used to take weeks started happening in one meeting."
Marlene du Toit
Cape Town
Project sponsor, office fit-out programme
"The RAID log actually got used, which surprised me. Risks were named early, owners were assigned, and nothing sat in a document for three weeks. It made the difference between reacting to problems and seeing them coming."
Sipho Nkosi
Johannesburg
Marketing lead, campaign launch
"Resource levelling was the part I did not expect to matter. We finally saw who was overloaded before the campaign went live, and we adjusted the timeline instead of burning people out. The reporting stayed lean enough that we kept updating it."
Naledi Mokoena
Pretoria
A note on how we gather these
We ask for feedback at project close-out and again three months later, so the comments reflect whether the structure held after we stepped back. Names are shared with permission. If you want to speak to a reference in your sector, we can arrange that during a discovery session.