Is your risk process helping you —
or slowing you down?
What MCA-Nepal learned about turning risk management into a tool that works for your team, not against it.
Risk management is one of the most skipped steps in project management — and it is easy to understand why. When it is not done well, it feels like a vacuum of time: long registers, routine meetings, and little connection to real decisions. But when it is done well, it is one of the most powerful early warning tools a project team has. This issue looks at how MCA-Nepal, working together with IPM and their project management consultant team, reset their approach and made risk management something worth doing.
Keeping it simple. Keeping it useful.
During a recent IPM support mission in Kathmandu, the IPM team worked together with MCA/MCC-Nepal and the PMOSS, MCA’s project management consultant team, to rethink their risk management process from the ground up. This was a collaborative effort — bringing together the people who run the program, the consultants who support it day to day, and IPM’s methodology expertise.
The shared goal was straightforward: reduce the administrative burden on staff while keeping decision makers informed of what matters. The result was a leaner process focused on one question — what can we do about this risk, right now? A six-week review cycle was put in place, giving MCA leadership a regular and predictable moment to surface emerging problems and agree on next steps before they become crises.
Risk Management in the PPMM: From Register to Real Action
The Practical Project Management Methodology (PPMM) treats risk management not as a compliance exercise, but as a structured conversation — one that should lead to decisions and actions. A good risk process does not try to capture every possible problem. It focuses on the risks that leadership can actually do something about, and makes sure those conversations happen on a regular schedule.
The PPMM supports MCA teams in building a risk process that is proportional to their program’s size and complexity — one that is easy to maintain and directly useful to the people who run the program. The approach in Nepal is a good example of this in practice.
Right-size your process.
A risk register that no one reads is not managing risk. Start with what your team can realistically maintain and review on a schedule.
Focus on what you can control.
The most useful risk entries are the ones where your team has a mitigation action — not just a description of what might go wrong.
Create a regular moment for the conversation.
A six-week review cycle with the right people in the room means problems get seen early — not after they become issues on the project dashboard.
Read the full PPMM — and put it to work.
The PPMM covers risk management and nine other project management areas designed for MCC programs. Download it and see what your team could be doing differently — or reach out to IPM to talk through how to apply it to your program.
IPM 