First Nations management research
How Many Strategic Priorities Should a First Nation Have?
The useful number is the number of distinct changes the Nation can govern and deliver. Counting headings alone will not reveal whether a plan is focused or overloaded.
A plan with four priorities can conceal forty competing initiatives. A plan with seven can be manageable if each has a clear outcome, an accountable owner and a realistic sequence. Before arguing for three, five or ten, decide what the word “priority” means in the plan.
A smaller list is not automatically a more focused strategy
The management problem is often a mismatch between the public language of a plan and the commitments inside it. “Healthy communities” may describe a lasting outcome. “Establish a coordinated intake service this year” is a bounded change. “Answer service enquiries” is ongoing work. All three matter, but treating them as equivalent priorities makes both resource allocation and reporting difficult.
Arcus recommends separating three levels: the community outcomes the Nation seeks over time; the changes leadership commits to during the planning period; and the initiatives currently authorized to deliver those changes. The number of outcomes can remain stable while the number of active initiatives rises or falls. This protects continuity without pretending that every ambition is funded for immediate delivery.
The decision is therefore twofold: how many distinct commitments should the strategy make, and how much work should begin concurrently? Reducing the first number while leaving the second untouched creates a shorter document, not a more executable plan. This distinction complements the resource choices examined in strategic planning when priorities exceed resources.
What published First Nation plans show—and what they cannot prove
Squamish Nation’s public summary of its 2026–2030 strategic plan sets out four priorities, supported by measurable objectives and commitments. It connects the four-year plan to a longer generational vision.1 The relevant design feature is the relationship between levels: the top-level count does not describe the entire delivery workload.
A different historical example appears in Kwanlin Dün First Nation’s 2019–2020 annual report. Page 19 identifies seven priorities in the 2018–2022 strategic plan and uses them to organize annual reporting.2 Here the priorities also provide a structure for communicating the government’s breadth of work. The example describes that reporting period; it is not a claim about the Nation’s current plan.
These documents establish that different structures are used. They do not establish that four or seven produces better results. Governance arrangements, responsibilities, staffing, resources and community choices differ. A published list is evidence of a planning design, not an evaluation of its effectiveness.
The First Nations Financial Management Board describes integrated planning as connecting priorities with operations and spending.3 That provides a stronger management test than copying another Nation’s number: can each commitment be connected to an operating plan, available resources and a review decision? The analysis and decision framework below are Arcus’s interpretation, not a numerical standard prescribed by these sources.
Diagnose why the list feels too long
The categories may overlap. Housing access, family stability and community wellness may include the same proposed initiative. If the same work is counted three times, merge the delivery record and show its contributions to several outcomes. Do not erase distinct community concerns merely to eliminate repeated words.
The commitments may exceed delivery capacity. If different initiatives all need the finance lead, the same project manager or a small group of language speakers in the same month, the constraint is concurrency. Renaming ten commitments as five broad themes will not free those people. Sequence launches, obtain support where appropriate or reduce scope.
Decision authority may be unclear. Work can stall even with a short list when staff cannot resolve routine choices or when decisions repeatedly return to Council without a recommendation. Review delegated authority and escalation paths before reducing the number of priorities. Where the Nation’s rules reserve a decision to Council or community processes, plan for that requirement explicitly.
The plan may be carrying unresolved differences. A large list can preserve competing promises without deciding between them. The remedy is a transparent decision process, including whose needs would be affected by deferral. A facilitator should not use an arbitrary numerical cap to settle a question that requires the Nation’s own political or community judgment.
Use recent evidence to distinguish these explanations: duplicate initiative records, a six-month schedule of staff commitments, delayed decision logs and the unresolved issues from community engagement. Each diagnosis implies a different intervention. A shorter list is justified only if it changes decisions or delivery.
Choose a structure that fits the work
A compact set of change priorities suits a period when leadership needs to concentrate effort on a few identifiable improvements. Each priority should state the change sought and a time horizon. The advantage is visible accountability; the risk is that members interpret the shorter list as withdrawal from other responsibilities. Publish the continuing service commitments beside it.
A broad outcome structure with a limited annual delivery portfolio suits a Nation that needs to represent interconnected community aspirations while controlling what starts now. Each outcome can contain several initiatives, but only the authorized tranche has current owners, resources and milestones. The trade-off is additional discipline: the administration must prevent the “later” list from quietly becoming an unfunded promise.
A staged strategy suits a period when major dependencies are unresolved. For example, a service redesign may require a mandate decision before recruitment and implementation. Approve the first stage and define what evidence releases the next. This reduces premature commitments, but it needs clear communication so staged approval is not mistaken for indecision.
These structures can be combined, but every layer should perform a distinct job. If an additional theme, committee or dashboard does not improve ownership, resource choices or accountability, it may be adding administrative work without improving governance.
Count the workload beneath the headings
Consider a hypothetical plan with four priorities and five proposed initiatives under each. That is twenty initiatives. If each initiative requires a two-hour monthly review involving four staff, attendance alone consumes 160 staff-hours a month: 20 × 2 × 4. This excludes preparation, follow-up, Council decisions and delivery work. It is a planning illustration, not an observed First Nation benchmark.
Renaming the same twenty initiatives under three priorities does not reduce those 160 hours. Starting eight initiatives would reduce the equivalent attendance calculation to 64 hours, but only if the other twelve are genuinely deferred and no longer require the same active review. Their obligations, risks and readiness still need proportionate oversight.
This does not mean eight is the right number. One land-use negotiation may require more specialist and leadership time than several small operational improvements. Assess workload by role, month and decision point. A single total can hide a shortage in the one role every initiative needs.
Cost the chosen structure in three parts. First, estimate the transition cost of consolidating plans, resolving ownership and explaining changed commitments. Second, budget recurring coordination, reporting, engagement and evaluation. Third, recognize the opportunity cost: time spent managing the portfolio is time unavailable for other services. Use the Nation’s actual staffing costs and availability; do not substitute a generic consultant-to-staff ratio.
Capacity-building may be preferable to deferral when a shared support role unlocks several valuable initiatives. Test the recurring cost and succession arrangements before creating the role. A temporary coordinator can improve reporting without solving a permanent shortage of operational staff.
Original Arcus decision framework
Six tests for a defensible priority count
Apply these tests to the whole portfolio before approving the number. A failed test calls for a design change, not automatically another round of consultation.
Use a consistent unit
Separate enduring outcomes, term commitments and initiatives. Compare like with like before counting.
Show the separate decision
Keep two priorities distinct when they require materially different choices, accountability or measures. Merge labels only when the work is genuinely shared.
Expose shared constraints
Map delivery and decision time by role and month. Include existing service work and realistic contingency.
Limit active commitments
Identify what is funded and ready now, what is staged, and what requires another decision. Assign one accountable lead to each active initiative.
Make deferral visible
Show where community needs remain in the longer plan, why action is deferred, and what would change the decision.
Test delivery, not neatness
Review bottlenecks, missed decisions and emerging needs. Change the active portfolio when evidence warrants it.
Would adding one more priority change the resource decision—or simply give existing work another heading?
Make the decision in a structured working session
Before the session, administration should assemble a single list of commitments and initiatives, identify overlaps, and map proposed work against current service responsibilities. Ask each accountable lead to identify the next meaningful milestone, required decisions, critical dependencies and credible staff effort. Keep estimates as ranges where uncertainty is material.
During the session, Council and administration should first agree on the planning levels and the criteria for separating priorities. Then review the proposed portfolio against the most constrained roles. Test at least two alternatives: the proposed portfolio and a smaller or staged version. Record what each option delays, enables and costs. Council’s role is to determine direction and approve trade-offs through the Nation’s established processes; management’s role is to explain delivery implications and implement authorized decisions.
Within the following month, translate the decision into a concise public explanation and internal work plans. Show the complete set of long-term outcomes, the active commitments and the conditions attached to later work. Give every initiative a single record even if it contributes to several priorities. Finance and operational leads should use the same record when preparing budgets and progress reports.
At the first quarterly review, examine whether work is actually moving: unresolved decisions, missed milestones, overloaded roles and commitments that began without authorization. If the portfolio is too large, identify the specific change to scope, sequence or capacity. If it is too small to address urgent needs, explain what additional resources or trade-offs would make expansion credible.
The right number is an accountable decision
No universal count can substitute for a Nation’s mandate, community priorities and delivery conditions. The useful number is the one that allows leadership to make meaningful choices and the administration to carry them out. A clear hierarchy, an honest limit on concurrent work and a visible path for deferred needs provide more discipline than a memorable number on a presentation slide.
From priorities to delivery
Build a priority structure your Nation can govern
Arcus supports First Nations in clarifying strategic commitments, testing delivery capacity and connecting priorities to budgets, departmental plans and Council reporting.
Discuss a strategic priority reviewEvidence and source notes
- Squamish Nation, Strategic Plan 2026–2030 public summary. Evidence of four priorities linked to objectives, commitments and the generational plan. The full members-only plan was not accessed.
- Kwanlin Dün First Nation, Annual Report 2019–2020, p. 19. Historical example of seven strategic priorities organizing annual reporting; not a current-plan assessment.
- First Nations Financial Management Board, Finance: Integrated Planning. Guidance connecting priorities, operations and spending. Its Financial Administration Law requirements depend on the applicable framework; no universal legal requirement is asserted here.
Research reviewed October 18, 2026. Examples are descriptive, not causal evaluations. The workload illustration and six-test framework are original Arcus analysis for adaptation through each Nation’s own governance processes.