First Nations Management & Leadership · Arcus perspective
Why Adding More Staff Doesn’t Always Fix First Nations Service Delivery
When services fall behind, an additional position can look like the most direct response. Sometimes it is exactly what the organization needs. In other circumstances, a new employee enters the same unclear process, waits for the same approvals and inherits the same competing priorities. Leadership then carries a larger payroll without resolving the problem that prompted recruitment.
The decision is not whether staffing or organizational improvement matters more. It is which combination will make a particular service reliable. Chiefs, Councillors and senior administrators need an account of the work, the constraints and the resources required. This article offers management analysis, not a claim about how frequently staffing proposals succeed or fail. Examples are hypothetical and the appropriate response depends on the Nation’s priorities and circumstances.
What evidence distinguishes a real resource gap from a design problem?
ISC’s Evaluation of Land Management Sub-Programs found that inadequate funding hindered the Reserve Land and Environment Management Program and identified an appropriately compensated, dedicated land manager as vital. Its mixed-method review covered 2014–15 to 2020–21 and selected later activities. Limited regional engagement and low survey participation constrain generalization.[5] This is a substantive reason to test genuine resource needs; it is not evidence that every service problem can be solved through process changes.
A different warning comes from the House of Commons Public Accounts Committee’s examination of the 2017 CRA call-centre audit. Calls were blocked to help meet a waiting-time standard, while reporting excluded blocked calls from that standard.[6] This historical federal example does not establish staffing requirements in a First Nation. It shows why a favourable activity measure can coexist with poor access.
Arcus’s inference is to test both the resources needed to deliver the service and the operating rules that determine how those resources are used. Neither a staffing increase nor a process redesign should be approved solely on the basis of a headline workload or waiting-time measure.
Define the service problem precisely
Begin with the experience leadership wants to improve. A general statement that a department is overwhelmed does not identify the decision required. Specify which work is delayed, what commitments apply, where consequences arise and what employees are doing to keep the service operating. Include demand that may not appear in the formal workload report.
Distinguish volume from complexity. Two requests recorded under the same heading can require very different amounts of work. A routine inquiry may take a short conversation, while an exceptional case needs coordination, specialist input and several decisions. Counting requests without understanding that variation can produce a misleading account of capacity.
For a hypothetical housing office, a backlog might contain routine maintenance, urgent safety concerns and major capital issues. These should not be treated as interchangeable units. Leadership needs enough information to understand the work and prioritize responsibly, while protecting personal information and avoiding a collection exercise that consumes the capacity it is meant to assess.
Follow work through the service process
Map a representative request from first contact to completion. Identify who receives it, what information is needed, where decisions occur and how the person seeking service is informed. Ask employees where work waits, returns for correction or transfers without clear ownership. A process map should explain the service rather than document every possible exception.
Separate active work from elapsed time. A request may take several weeks to resolve while requiring only a limited amount of staff time, because it waits for information or approval. Another may move promptly through the stages but require sustained specialist effort. Those situations imply different capacity decisions.
If a hypothetical intake employee repeatedly requests missing information from another team, adding a second intake employee may increase the number of requests waiting at the same boundary. A shared information standard or a clearer handoff might be part of the solution. Additional staffing may still be necessary, but leadership should understand what the position will change in the service flow.
Identify the constraint before prescribing the role
A constraint can involve employee time, specialist knowledge, management attention, authority, information or an external dependency. Several may operate together. Review the evidence with the people doing the work and distinguish a recurring pattern from an unusual incident. Do not assume that every delay belongs to the department where it becomes visible.
Consider whether existing priorities are compatible. Employees may be expected to maintain routine services, complete new projects and respond to urgent requests without a clear way to choose between them. That is partly a management decision. A new position cannot create a coherent priority order if leadership continues to treat every commitment as equally immediate.
FMB’s Administrative Governance guidance discusses delegated responsibilities, policies and monitoring within its financial-administration framework.[2] These questions can help identify delays caused by uncertain authority. Confirm what applies locally and preserve necessary controls. The objective is to make decisions dependable, rather than remove review steps without understanding their purpose.
Test competing explanations with different evidence
A sustained qualified-capacity shortage: necessary work exceeds available qualified time even after removing clearly avoidable repetition. Examine demand, complexity, coverage requirements and productive capacity over representative periods. Funded staffing, retention or shared specialist capacity may be necessary. An empty authorized position and an inadequately funded service are different problems.
Repeat work caused by the service arrangement: incomplete inputs, inconsistent answers or failed handoffs generate extra effort. Trace repeat contacts to the underlying request and review their causes. Some follow-up is legitimate support; do not classify it as waste merely because it occurs more than once.
A decision or external dependency: staff can prepare work but lack an authorized decision, specialist input or partner response. Compare active work with waiting and identify the specific dependency. More preparation capacity may increase the queue unless the decision constraint is also addressed.
These explanations can coexist. Use case review and workload evidence together, including complex cases and periods of absence. Avoid selecting only the smoothest cases to justify a low staffing estimate or only the hardest cases to justify a permanent position.
Recognize when additional staffing is justified
Organizational analysis should not become a way to defer a genuine resource need. If essential work exceeds available capacity after reasonable process and priority decisions, leadership should see that gap clearly. Explain the responsibilities involved, the required capability and the consequences of leaving the need unresolved.
Specify the proposed position’s contribution. Will it increase front-line availability, provide specialist judgment, strengthen supervision or reduce dependence on one person? Identify the work that will move and the support the new employee will require. A broad promise to help everyone is harder to evaluate and may leave the role exposed to competing demands.
FMB’s Human Resources guidance connects roles with job descriptions, qualifications and training.[3] Use that relationship to test whether the proposal describes a coherent job. Recruitment, induction, supervision and development are part of the resource decision. A funded vacancy does not provide usable service capacity until the organization can attract, support and integrate the person who fills it.
Examine the whole cost and operating arrangement
Assess ongoing and transition requirements rather than salary alone. Depending on the role, these may include workspace, equipment, systems, training, supervision and coverage. Compare these needs with the resources available and the duration of the service commitment. Do not assume that a temporary funding opportunity can sustain an ongoing function.
Consider alternatives where appropriate: a different allocation of existing work, specialist support, a shared arrangement or a time-limited response to a defined backlog. Compare service access, control, continuity and affordability. An external arrangement should not be treated as inherently preferable to internal capacity, or internal recruitment as the only way to perform every task.
The CCP Handbook connects community priorities with implementation, resources and monitoring.[1] That connection helps place a staffing proposal in context. The question is how the proposed resource supports an authorized priority and what other commitments must change to make it workable. An organizational decision should make those tradeoffs visible to leadership.
Service Capacity Decision Framework
This original framework organizes the staffing decision around five connected questions. It is not a productivity benchmark or a validated diagnostic. Use it to explain the evidence, identify uncertainty and compare practical options before committing to a position or a process change.
Demand: what work must the service perform?
Describe the service commitments, recurring demand, complexity and important variations. Include work that is currently deferred or handled informally. Identify what leadership has authorized and where the organization needs a decision about priorities, eligibility or the intended scope of service.
Flow: where does the work slow or repeat?
Trace information, decisions and handoffs. Distinguish time spent performing the work from time waiting for another contribution. Identify which delays the service can address and which require decisions or cooperation elsewhere. Avoid attributing a shared problem to one employee or team without evidence.
Constraint: what limits reliable delivery?
Assess available time, capability, authority, information and support. Identify the strongest evidence for the limiting condition and record uncertainty. Several constraints may require a combined response; a process improvement should not be presented as sufficient if essential workforce capacity remains missing.
Response: what will the proposed change enable?
Explain what an additional position, revised process or alternative arrangement would do differently. Specify dependencies, resources and implementation responsibilities. Compare options against the same service problem so that leadership can assess their contribution rather than compare unrelated promises.
Evidence: how will leadership know the response works?
Choose a few measures tied to the problem, such as the age of unresolved requests, avoidable rework or access to supervision. Interpret them with service context and information stewardship requirements. FNIGC’s description of OCAP® emphasizes Nation-specific control over information.[4] Decide what may be collected and shared before designing the reporting process.
Arcus can help assess workload, service flow, roles and management responsibilities, distinguishing additional resource needs from problems that require a different operating arrangement.
Examine service capacity before your next staffing decision →
Work through the residual capacity gap
Use a residual capacity calculation alongside the Service Capacity Decision Framework: necessary service effort plus remaining repeat work, less qualified time available. State the period, case mix, coverage assumptions and tasks included. This is an original Arcus planning illustration, not a productivity benchmark.
Suppose a fictional service receives 90 new requests each month requiring an average of two staff hours: 180 hours. Thirty additional one-hour repeat contacts bring total effort to 210 hours. The team has 180 qualified hours available for this service after its other required duties, leaving a 30-hour gap. These assumed averages simplify real variation and do not establish acceptable waiting times.
If a tested process change reduces the repeat contacts from 30 to 10 without restricting access or necessary support, the gap falls to 10 hours; it does not disappear. The process change releases 20 hours of capacity, not an automatic payroll saving. If the remaining gap persists, leadership still needs additional qualified capacity, an explicitly authorized service adjustment or another credible arrangement.
At an invented incremental support rate of $80 per hour, resourcing a verified 10-hour monthly gap would cost $800 per month, or $9,600 over twelve months, before onboarding, supervision, coverage and any minimum contracting commitment. If repetition remains unchanged, the 30-hour gap would require $2,400 monthly at the same assumed rate. These are conditional calculations, not market prices or predicted savings. Compare actual options and procurement terms before deciding.
Repair the process first where evidence identifies avoidable repetition and the change can be introduced without unsafe delay. Add qualified capacity where necessary demand exceeds feasible provision or continuity requires reliable coverage. Combine both where process repair reduces but cannot close the gap. A recurring fractional gap may justify shared capacity; a permanent role may be justified by broader responsibilities, peaks and coverage that this narrow calculation excludes.
Confirm that additional hours can perform the constrained work. Include recruitment time, training, supervisory support and the delay before a new employee becomes independently productive. Assign responsibility for monitoring access, unresolved requests, repeat contacts and staff workload together. A lower queue is not success if residents have simply stopped being able to request service.
Test the proposed response before making it permanent
Where practical, use a defined trial or staged implementation to learn whether the response addresses the constraint. A trial needs an owner, resources, clear boundaries and a review point. It should not become an indefinite temporary arrangement in which employees carry extra responsibilities without a decision about the future.
For a hypothetical referral process, leadership might authorize a clearer intake standard and dedicated coordination time while tracking unresolved handoffs. The trial should examine whether those changes improve completion and what remains constrained. If the evidence shows that volume still exceeds available capacity, the organization has a more precise basis for a staffing proposal.
Avoid promising a specific improvement that the evidence cannot support. State what the response is intended to change and what conditions could limit it. A responsible business case distinguishes expected benefits from guarantees and identifies when leadership will reconsider the arrangement if the assumptions prove inaccurate.
Decide when a broader review is needed
A focused service assessment may resolve a well-defined issue within one team. A broader organizational review becomes useful when delays involve several departments, unclear management responsibilities or incompatible demands across the administration. The scope should follow those connections and preserve services while the work is examined.
The strongest staffing decision explains both the resource need and the operating conditions required for the resource to be useful. That approach supports employees rather than asking them to compensate for unresolved design problems. It also gives governing leaders a clearer basis for choosing where additional investment will make the most meaningful contribution to the Nation’s priorities.
Arcus Advisory
Examine service capacity before your next staffing decision.
Arcus can help diagnose workload, repeat work and decision constraints; compare staffing, process and shared-capacity alternatives; and prepare a defensible service-capacity decision. Deliverables can include a demand and case-mix profile, qualified-capacity estimate, dependency map, residual-gap calculation and recurring-cost comparison.
Implementation support can clarify roles, sequence recruitment and process changes, and establish measures of access, unresolved work and workforce pressure. The review should state evidence gaps and distinguish resources released for other work from genuinely avoidable cash expenditure.
Related research and consulting
When Has a First Nation Outgrown Its Organizational Structure? Seven Warning Signs
Arcus Organization Design consulting · Organizational Design & Change collection · First Nations Knowledge Centre
Sources and further reading
- Indigenous Services Canada. CCP Handbook: Comprehensive Community Planning for First Nations in British Columbia, fourth edition.
- First Nations Financial Management Board. Administrative Governance.
- First Nations Financial Management Board. Human Resources.
- First Nations Information Governance Centre. The First Nations Principles of OCAP®.
- Indigenous Services Canada. Evaluation of Land Management Sub-Programs. Web page modified March 18, 2024; executive summary and methods. Program-specific retrospective findings with regional and survey limitations.
- House of Commons Standing Committee on Public Accounts. Report 41, Canada Revenue Agency call centres. Examination of the 2017 Auditor General findings and November 2017 hearing; historical access and performance-measurement example, not a First Nations staffing standard.
The management analysis, hypothetical illustrations and original framework are practical guidance, not a validated diagnostic or a prescription for every Nation. FMB guidance describes its financial-administration framework; local applicability must be confirmed. OCAP® is a registered trademark of the First Nations Information Governance Centre (FNIGC). Sources reviewed October 2026.