Methodologies
Hybrid: where real life usually lives
Many small organisations need a hybrid method. You might use predictive planning to secure board approval, funding and compliance, but use adaptive cycles to build and test the actual service.
Hybrid should be deliberate, not messy. Decide which parts need control, which parts need flexibility, and where decisions will be reviewed.
The best methodology is the one that helps the project create value. A project is not successful because it used Agile, PRINCE2, Lean or a perfect Gantt chart. It is successful if it delivered the right outcome, used resources responsibly, involved the right people, and created benefits that mattered.
If the team cannot explain how the method helps deliver value, it may just be process decoration.
Lean: useful when waste is the enemy
Lean is useful when the project is about making an existing process better. The basic question is simple: which steps create value, and which steps are waste?
For a small business, this might mean reducing food waste, speeding up order fulfilment or simplifying customer enquiries. For a charity, it might mean making volunteer onboarding less painful, reducing duplicated admin or improving how donations are processed.
Lean does not have to become a wall of Japanese terminology. The practical idea is enough: map the process, find the delays, remove unnecessary steps, and improve the work with the people who actually do it.
Use Lean when the problem is not that you need a new thing, but that the current thing is clumsy, slow or wasteful.
Choose the method that fits the mess
Project methodologies have a strange ability to turn sensible people into sect members. Waterfall people. Agile people. PRINCE2 people. Lean people. People who say “Scrum” with the emotional intensity of a minor prophet.
Small businesses and charities do not need a methodology religion. They need a way of working that fits the project, the team, the risk and the amount of uncertainty involved.
A methodology is not a badge. It is a working agreement about how the project will move, decide, learn and control itself. It should help the team deliver value, not trap them in rituals copied from a much larger organisation with better coffee and a project office.
Start with the project, not the method
The first question is not “should we use Agile?” The first question is “what kind of project is this?”
If the outcome is clear, the deadline is fixed and the work has to follow a known sequence, a predictive approach may be best. A charity fundraising event, office move, compliance update or venue refurbishment often needs upfront planning, clear milestones and tight control.
If the outcome is uncertain and users need to test the solution as it develops, an adaptive approach makes more sense. A new donor portal, customer app, service redesign or marketing experiment may need short cycles, feedback and adjustment.
If the project is about improving an existing process, Lean thinking may be useful. The aim is to remove waste, reduce friction and focus on what actually creates value for the customer, service user or team.
Most real projects sit somewhere in the middle. That is why hybrid approaches are often more realistic than pure textbook methods.
Predictive: useful when the path is known
Predictive, or plan-driven, methods work best when requirements are stable and the cost of getting things wrong is high. You define the scope, plan the work, sequence the tasks and control changes carefully.
This is useful for projects where people need certainty: construction, events, compliance-heavy work, grant-funded delivery with fixed reporting requirements, or projects involving safety, legal or regulatory obligations.
The weakness is obvious. Predictive methods can become rigid. If the project environment changes, or if users only understand what they need after seeing an early version, the plan may start defending itself against reality.
Use predictive methods when control matters more than discovery.
Adaptive: useful when learning is part of the work
Agile and adaptive methods work best when the project needs learning, testing and feedback. Instead of pretending the team knows everything upfront, the project moves in shorter cycles. Build something small, test it, learn, improve, repeat.
This can work well for digital projects, campaigns, service design, product ideas or anything where user feedback should shape the final result.
The danger is fake agility. Calling something “agile” does not make it flexible. If there is no prioritisation, no decision discipline and no regular learning, it is not agile. It is just improvisation with a nicer name.
Use adaptive methods when the project needs discovery, not just delivery.
Strategy is not planning
Strategy, planning, implementation and governance are related, but they are not the same thing.
Strategy chooses the direction. Planning works out the route, resources, timeline and responsibilities. Implementation does the work. Governance checks whether the work still makes sense, still has authority, and still deserves support.
Confusing these creates trouble. A detailed plan is not a strategy. A busy organisation is not necessarily a strategic one. A project delivered on time can still be the wrong project. That is the uncomfortable part people often avoid: good execution does not rescue a bad choice. It just delivers the mistake more efficiently.
Choose what not to do
A useful strategy creates focus. It says yes to some things and no to others. This is where many small organisations struggle, especially charities and mission-led businesses. When the cause matters, every opportunity can feel morally important. Every grant looks tempting. Every partnership seems worth exploring. Every service gap feels like something you should fix.
But saying yes to everything is not generosity. It is strategic self-harm.
A charity that chases every available funding stream may end up running projects that do not fit its mission, confuse staff, exhaust volunteers and make the organisation harder to explain. A small business that copies every competitor may lose the thing that made it distinctive. A team that keeps adding initiatives without stopping anything is not becoming more ambitious. It is building a museum of unfinished intentions.
Strategy requires trade-offs. What will you not do? Which customer or beneficiary will you prioritise? Which projects will you pause? Which “nice idea” does not deserve resources right now?
The strategy is often hidden in the no.
Tools to use
Use to choose between different approaches based on uncertainty, risk, stakeholder involvement and regulation.
Methodology Matchmaker
Use to understand whether the project needs more structure, more flexibility or more oversight.
Project Complexity Checklist
Use to review an existing process and identify steps that waste time, money or energy.
Lean Waste Walk Checklist
“Responding to change over following a plan.”
— Agile Manifesto
Recommended reading & sources
Project Management Institute – Pulse of the Profession 2024
A useful industry report on current project delivery trends, including the move toward hybrid and value-focused approaches.
Project Management Institute – A Guide to the Project Management Body of Knowledge (PMBOK Guide)
A widely used project management reference for understanding project principles, lifecycles and good practice across different types of work.
AXELOS – Managing Successful Projects with PRINCE2
Helpful for understanding structured project governance, business cases, stages and controlled delivery.
Beck, K. et al. – Manifesto for Agile Software Development
A short foundational text explaining the mindset behind adaptive delivery, including feedback, collaboration and responding to change.
Womack, J.P. and Jones, D.T. – Lean Thinking
A practical introduction to Lean principles, especially useful for organisations trying to reduce waste and improve value.
Rigby, D.K., Sutherland, J. and Noble, A. – “Doing Agile Right”
A useful read for avoiding fake agility and understanding when agile methods actually help.