Running 25 projects at once without losing control
Managing a large portfolio is less about working harder and more about a few simple routines. These are the ones I rely on.

For years I have run portfolios of 25 or more live implementations at the same time, across several time zones. People often ask how. The honest answer is that it is mostly routine, not heroics.
One view of everything
Every project lives on one board with the same few fields: stage, next milestone, health, owner and blockers. If I need to open five tools to understand a project, the system is broken.
Health by exception
I do not review every project every day. Each project manager rates health honestly each week, and I spend my time on the ambers and reds. Green projects get a quick look, not a meeting.
Standard stages and gates
Every implementation follows the same stages, from kickoff to sandbox, testing, sign-off and go-live. Clear entry and exit rules for each stage mean fewer surprises and easier handovers between people.
Protect the team’s focus
- Batch client calls into fixed slots.
- Use written updates instead of status meetings where possible.
- Escalate early. A problem raised on Monday is cheap; on Friday it is expensive.
Automate the reporting
Status reports should build themselves from the project board. I use automation and AI to pull updates into a weekly summary, so managers spend their time on decisions, not formatting.
Scale comes from consistency. The more the same routines repeat, the more projects a team can carry well.


