Nonprofit implementation guide
Guide 2: Establish governance and decision rights
Give scope, design, data, risk, budget, and acceptance decisions a visible owner.
Name roles at the level of real decisions
Identify the executive sponsor, business owner, project lead, system administrator, data owner, privacy or security reviewer, finance or procurement owner, adoption lead, and acceptance authority. One person may hold several roles, but the decisions still need names.
Ask who can approve a changed workflow, release data, add cost, move a milestone, accept a limitation, and declare the system ready for use.
Use a short decision path
Set the evidence required, advisers, response window, and escalation threshold for recurring decision types. Keep working sessions separate from approvals so a large meeting does not become the default authority.
Record the date, owner, question, considered options, evidence, outcome, and downstream effect. Revisit a decision when its assumption changes, not whenever the team becomes uncomfortable.
Make status useful
A status review should show accepted outputs, near-term decisions, risks above threshold, staff commitments, changed assumptions, and the next go or stop gate. Percent-complete estimates without this context can hide the work that matters.
Escalation is a control, not a failure. The team should know how to raise concerns without waiting for the next scheduled meeting.