Risk management is the practice of finding what could stall the plan, naming a person who can act on it, and changing the plan enough that momentum survives. For a programme based around Pretoria, that work has to happen before the date is already missed. MetaServ keeps its base at 340 Witch-Hazel Street, Highveld, Centurion, Gauteng, 0157 and reviews risks with the people who own them, whether they are in a Pretoria project room, on a Midrand site, or in a Johannesburg meeting. No separate office is required for the register to be real.
What does early risk management look like?
Early means while there is still a choice. A supplier who has not confirmed, access that only works on certain days, a decision that lives in a diary three weeks out, a dependency on a team that is already at capacity: these are risks when they are still movable. The same facts, discovered the morning the work was due, are delays. Risk management that begins at the delay is a post-mortem with a future tense.
The people closest to the work usually see the risk first. A delivery lead in Midrand sees the access problem. A finance partner in Johannesburg sees the approval that only happens once a month. A coordinator in Pretoria sees the clash with a public holiday that nobody put on the plan. Early means those three observations land on one list in the same week they are noticed, not in the steerco pack after the damage is polite to discuss. Identify is a verb with a deadline. The deadline is "while we can still change the sequence."
Who owns a risk, and what does reduce actually mean?
Own means a person who can act this week, not a function name in a column. "Operations" cannot chase a confirmation on Thursday. A named person can. If that person is on leave, the line names the cover before the leave starts. A risk with no owner is a diary entry. It will still be there when the week runs out, and it will have company.
Assess means saying, in ordinary words, what happens to the outcome if nothing changes, and how soon that happens. A matrix score that nobody can explain to a sponsor is not an assessment. Reduce means a change in the plan: a different sequence, a smaller slice, a decision brought forward, a piece of work stopped so the risky dependency is not on the critical path. Lowering a score without changing the work is decoration. The ISO 31000 guidance treats risk as the effect of uncertainty on objectives. The practical version is the same. If the objective and the next action are not both visible, the register is not yet risk management.
- One sentence on what could stall the outcome.
- One person who can act before the next review, plus cover if they are away.
- One date when the action is either done or escalated.
- The effect on the plan if that date passes with nothing done.
How does momentum survive across three cities?
Momentum is the rest of the plan continuing while the risk is being worked. It dies when every conversation becomes the risk, and it also dies when the risk is hidden so the status can stay green. A Pretoria steerco that only hears good news, while Midrand is already working around a blockage and Johannesburg is waiting on a signature, is not calm. It is late.
Keep one register. The owner updates it where the work is, which may be a laptop on a Midrand site or a call from Johannesburg, and the Pretoria review reads that same register. Do not keep a local list "for the site" and a cleaned list "for the sponsor." The sponsor's version is the one the site will be judged against. If a near miss happened, it belongs on the list. Near misses are how the next city avoids repeating the same stall.
What should the review refuse to carry?
Refuse a risk that has no owner and no date. Refuse a row that is really a complaint. Refuse a score that changed because the slide needed to look calmer. Refuse to let the register grow into a history of everything anyone has ever worried about. A review that tries to discuss forty rows will discuss none of them. Take the few that can stall the outcome this month, give them the meeting, and leave the rest either closed, accepted with a named reason, or dated for a later look.
The frame around this is ordinary project management in Pretoria and Midrand: the risk sits on the same plan as the work, not in a side file. See where it fits among MetaServ's services. From 340 Witch-Hazel Street, Highveld, Centurion, Gauteng, 0157, the review can be in the room or on a call. Contact MetaServ at +27 10 880 6465 or info@metaserv.co.za, and bring the current register, including the rows you are embarrassed by. Those are usually the ones worth the hour.
What should a risk review settle first?
What is the first useful step for risk management for Pretoria programmes?
The people who own a risk still have to keep the plan moving. A register that only grows does not do that.
What is the other point of risk management for Pretoria programmes?
A register that only grows does not do that.
How does a split team in Pretoria, Midrand, and Johannesburg get risk management help with risk management for Pretoria programmes?
Email info@metaserv.co.za or call +27 10 880 6465. MetaServ works from 340 Witch-Hazel Street, Highveld, Centurion, Gauteng, 0157 with teams in Pretoria, Midrand, and Johannesburg, on-site or on a call.
