The methods, habits and tools I use to keep projects on track, people informed and results measurable.
- Clear processes
- Collaborative delivery
- Measurable results
Neither method is a religion. I use the structure of PRINCE2 for governance and control, and agile habits for building, testing and adjusting quickly.
PRINCE2 for control
- Clear stages with decision points
- Defined roles and responsibilities
- Business case checked at every stage
- Formal risk, issue and change control
Agile for delivery
- Short cycles of build, test and feedback
- Real users testing early and often
- Priorities adjusted as we learn
- Visible boards everyone can read
A live view of a typical project, stage by stage, and what I do in each one.
Understand
Stakeholder workshops and requirements analysis. Before any plan, I find out what the organisation actually needs and who it affects.
- Stakeholder mapping
- Requirements workshops
- Business case
Plan
A plan people can follow: scope, schedule, budget and resources, with a RAID register from day one so risks are visible early.
- Project charter
- RAID register
- Budget and resources
Deliver
Coordinating cross-functional teams and vendors, tracking performance and stepping in early when something starts to slip.
- Performance tracking
- Escalation routes
- Vendor management
Test and hand over
User acceptance testing, training and structured handovers, because a system that nobody uses has not really been delivered.
- User acceptance testing
- Training
- Implementation handover
Learn and improve
Post-implementation reviews and Plan-Do-Study-Act cycles turn every project into lessons for the next one.
- Post-implementation review
- PDSA cycles
- Benefits tracking
PDSA is a simple cycle used across the NHS to test changes safely. Tap each stage to see it applied to a real project.
Cycle
keep improving
Stage 1 of 4
Plan
Decide what to test and what good looks like. Write the scenarios real users will go through.
In practice
For DOC Express: every farmer journey, from registration and enquiry to wallet top-up, checkout and tracking.
Four letters that stop surprises. Pick one to see what it means, with a real example from DOC Express.
Risks
Things that might go wrong. Each one gets an owner, a likelihood, an impact and a plan.
From DOC Express
"Customers might order against past-date stock" became a rule to block it.
Planned and resourced, waiting for its start date.
Moving as planned. No action needed from you.
Something could slip. You will hear what, why and my plan.
Done, tested, handed over and signed off.
- Clear, honest status updates. If something is at risk, you will hear it from me first.
- Plans that people outside the project team can actually read.
- Shared accountability, where every voice is heard and no one is micromanaged.
- A steady focus on the result: the problem solved, not just the system installed.
Planning and delivery
- Microsoft Project
Jira
Confluence
Visio
Data and reporting
Power BI
SQL
PowerPoint
Collaboration and automation
SharePoint
Power Automate
Microsoft 365
Healthcare systems
- Meditech
- Soliton
- ICE Desktop
New to project jargon? Here is what the words in my case studies actually mean.
A structured project management method used widely in the UK. It breaks work into stages, with clear roles and decision points.
