Project consulting is the work of writing a roadmap this project can actually follow, before anyone is asked to execute against a blank page. In Johannesburg that usually means a sponsor wants movement, and the team wants a line they can see. MetaServ does that writing from 340 Witch-Hazel Street, Highveld, Centurion, Gauteng, 0157, then sits with the people who will run the work, on-site in Johannesburg or Midrand when the room matters, and on a call when it does not. There is no MetaServ office in Johannesburg. The roadmap is still theirs.
What should project consulting produce before execution starts?
A roadmap is not a strategy chapter. It is a sequence the delivery team can pick up without inventing a second plan in the corridor. It names the outcome in one sentence, the constraint that is not negotiable, the first decisions, and who will use the result. Expert support from the first strategy conversation is useful only when that conversation ends with those names written down. A workshop that ends with themes is still a conversation.
Skilled people join where the work needs them. On a Johannesburg programme that might be two days in the sponsor's room to force the outcome into plain words, then remote work from Centurion while the draft is marked up, then a shorter session with the Midrand leads who will live with the sequence. The point of project consulting is the line, not a resident team that stays after the line exists. When the line exists, delivery takes over. Keeping consultants in the doing column after that is how a roadmap becomes a permanent meeting.
What does a usable roadmap contain?
Write it for the person who was not in the strategy conversation. A delivery lead in Pretoria, opening the document on a Thursday before travelling to Midrand, should not need the workshop transcript. Each step needs an outcome, an owner, a date, and the dependency that would stop it. Leave off options that have not been chosen. An option sitting in the plan is a decision pretending to be work, and Johannesburg will start one version while Pretoria starts another.
- The outcome, in the sponsor's words, short enough to read aloud.
- The constraint: budget, date, or a limit on who can be pulled off current work.
- The first three decisions, each with a person who can make it.
- What will count as accepted, so execution knows when to stop.
The Project Management Institute treats the early definition of scope and stakeholders as part of getting a project ready to run. Project consulting at MetaServ stops at the same doorway. If the team still cannot say what "done" is, the roadmap is not finished, and starting execution would only create activity to report on later.
How do Pretoria, Johannesburg, and Midrand share one roadmap?
The failure mode is a beautiful document that only the people in the first room have seen. A Johannesburg steerco approves a direction on Tuesday. The Midrand team hears a summary on Wednesday and fills the gaps with what they already intended to do. The Pretoria delivery lead, working from 340 Witch-Hazel Street, Highveld, Centurion, Gauteng, 0157, receives both versions and tries to reconcile them before Friday. That reconciliation is not consulting. It is the cost of not sending the actual roadmap.
Send the document, not a retelling. Mark the open decisions in the text, not in someone's memory. Ask the Midrand lead and the Johannesburg sponsor to comment on the same lines. Do this before dates are promised in a forum the other city does not attend. A roadmap that cannot survive a comment from someone who missed the workshop is not ready to execute. Project consulting includes that round of comments. It is not a courtesy added at the end if there is time.
Centurion is the base, not a fourth version of the plan. One file, one owner of the draft, and a date when that draft becomes the line execution will follow. After that date, changes go through delivery, not through a second consulting thread.
When is the consulting engagement finished?
It is finished when a team that did not write the roadmap can run the next two weeks from it, and when the sponsor can point at the constraint without opening a slide. It is not finished when the workshop felt productive. Felt productive is a mood. A line someone else can follow is a product. If the engagement is still producing new options in week six, it has slipped into avoiding a decision. Name the decision, record it, and stop.
Where the risk is already visible, read risk management for Pretoria programmes before the roadmap pretends the path is clear. The same services sit together on the services page. To start from the blank plan rather than from a status report, contact MetaServ on +27 10 880 6465 or at info@metaserv.co.za. Bring the outcome you think you are chasing, and the constraint you are not willing to break.
What should a team ask before project consulting starts?
What should stay visible for project consulting for Johannesburg teams?
A team that needs a roadmap before execution has a line to follow is not asking for a longer workshop. It is asking for a sequence someone else can run.
What is the other point of project consulting for Johannesburg teams?
It is asking for a sequence someone else can run.
What should a sponsor bring to a project consulting session?
Bring the current project consulting note as it stands today, not a blank example.
