Governance
Keep it lightweight
Good governance does not require heavy bureaucracy. A small organisation does not need a corporate board pack for every minor project. It does need a few clear habits.
Before starting, define the sponsor, project manager, decision-makers and approval limits. During delivery, keep a simple decision log and review risks regularly. For larger projects, use a small steering group that meets at agreed points, not whenever panic becomes available.
For multiple projects, use a basic prioritisation method. Rank projects by strategic value, likelihood of success, resource demand and risk. Some projects are “pearls”: valuable and achievable. Some are “white elephants”: low value, low chance of success, but somehow still eating time because nobody wants to offend their creator.
Governance is the courage to choose.
Common governance problems
The first problem is unclear approvals. A project starts because “everyone agreed,” but nobody knows who actually authorised the budget, deadline or scope. Later, when the project needs more money or time, the organisation discovers that agreement and approval are not the same thing.
The second is founder-dependency. A founder or senior leader informally approves work, changes priorities, or protects favourite projects from scrutiny. This may be efficient in the short term, but it weakens the organisation. If everything depends on one person’s judgement, memory or mood, the governance system is not a system.
The third is role overlap. People are pulled between normal duties and project work, with no clear priority. Staff and volunteers end up serving two masters: the project wants speed, the organisation wants business as usual, and nobody has decided which one wins this week.
The fourth is weak escalation. Problems stay at the wrong level for too long. A volunteer struggles silently. A supplier delay becomes critical. A budget issue is mentioned casually but not formally raised. Governance should create a route for problems to travel upward before they become dramatic.
Who gets to say yes?
Governance sounds like a word invented to make a meeting worse. In reality, it is much simpler than that.
Project governance is the system that decides who has authority, who is accountable, who approves changes, who monitors risk, and who steps in when the project starts drifting. It is not the same as day-to-day management. Management delivers the work. Governance makes sure the right work is being done, for the right reasons, with the right level of control.
For small businesses and charities, governance often exists informally. The founder decides. The board “keeps an eye on things.” The project lead asks whoever seems available. Decisions are made in conversations, remembered differently, and documented only when something has already gone wrong.
That may feel flexible. It is also how confusion gets a permanent address.
Governance has a hard and soft side
The hard side of governance is structure: roles, decision rights, approval points, budgets, reporting, risk reviews and escalation routes. These are the mechanisms that stop a project becoming a free-for-all.
The soft side is culture: honesty, judgement, accountability and the willingness to ask uncomfortable questions. A project can have all the right forms and still be badly governed if nobody is prepared to challenge a weak plan, question a pet project, or admit that the benefits no longer justify the cost.
Good governance needs both. Hard governance without integrity becomes box-ticking. Soft governance without structure becomes wishful thinking with nice values.
Why governance matters in small organisations
Small organisations have limited money, limited time and limited people. That makes governance more important, not less. A large organisation may survive a few wasteful projects. A small charity or business may not.
Governance helps answer basic but essential questions. Does this project fit the mission? Do we have the resources? Who owns the decision? Who approves changes? What risks need oversight? When should a problem be escalated? At what point do we stop?
Without those answers, organisations keep projects alive because someone cares about them, because money has already been spent, or because nobody wants the awkward conversation. That is how “strategic initiative” slowly becomes “white elephant with a calendar invite.”
Sponsor and manager are not the same job
One of the most useful governance distinctions is between the project sponsor and the project manager.
The sponsor, board or steering group owns the bigger decision. They approve the project, secure resources, monitor whether it still makes sense, resolve major conflicts and protect strategic alignment. They should be asking: is this project still worth doing?
The project manager owns delivery. They plan the work, coordinate the team, manage tasks, track progress and raise issues. They should be asking: how do we deliver this properly?
In small organisations, the same person may sometimes do both roles. That is not automatically wrong, but it is risky. When one person approves the project, manages the project, reports on the project and decides whether the project is still justified, oversight becomes a mirror. And mirrors are famously generous in the right lighting.
Even if roles overlap, the questions should not. Someone still needs to step back and challenge the work from the outside.
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 separate sponsor, board, project manager and team responsibilities.
Governance Roles Checklist
Use to record what was agreed, who approved it, and when.
Decision and
Approval Log
Use to decide which projects deserve resources and which should be paused, reshaped or killed humanely.
Project Portfolio Matrix
“Corporate governance is the system by which companies are directed and controlled.”
— Cadbury Report
Recommended reading & sources
Cadbury Report – The Financial Aspects of Corporate Governance
A foundational governance report, best known for defining governance as the system by which organisations are directed and controlled.
Larson & Gray – Project Management: The Management Process
A practical project management text that explains how projects are selected, structured and controlled inside different types of organisations.
Glaeser – The Governance of Not-for-Profit Organizations
Useful for charities and mission-led organisations trying to govern work where success is not measured by profit alone.
Leblanc – The Handbook of Board Governance
Helpful for readers who want a deeper understanding of how boards should operate, including in public, private and not-for-profit settings.
Project Management Institute – Governance of Portfolios, Programs, and Projects: A Practice Guide
A useful guide for understanding how organisations oversee not just individual projects, but the full set of initiatives competing for time, money and attention.
Laasch – Principles of Responsible Management
Good for connecting governance with ethics, responsibility and sustainability in everyday management decisions.