First Nations Management & Leadership · Arcus perspective
First Nations Organizational Review: What Chief and Council Should Expect
An organizational review should test whether changing the administration will address the problem leadership sees. If its mandate already assumes a new structure is the answer, even a polished report may leave the real constraint untouched.
Arcus’s management proposition is that the most valuable review separates three decisions: what can improve within the existing model, what requires a different allocation of authority or capacity, and what depends on action outside the administration. These distinctions matter because an internal redesign cannot itself alter a funding agreement, create unavailable specialist capacity or settle another institution’s responsibilities.
For Chiefs, Councillors, Band Managers and senior administrators, this means commissioning an explanation and a choice, with evidence that could challenge the preferred answer. The practical expectations below build on Nation-defined priorities and the existing review process. They respect differing governance arrangements, jurisdiction, treaty relationships and circumstances. Hypothetical illustrations are not client cases, and an organizational review is distinct from a financial audit, employment investigation or legal opinion.
Define the question before commissioning the review
A request to review the whole organization can conceal several different decisions. Leadership may be concerned about executive workload, uncertain departmental boundaries, vacancies, service delays or readiness for a new responsibility. These issues can interact, but treating them as interchangeable makes the review difficult to direct and its recommendations difficult to assess.
Write a short problem statement that identifies the observed concern, the effect on the Nation and the decision leadership expects to make. For example, recurring delays in a housing process could justify examining the responsibilities of housing, finance and procurement. It does not automatically establish that departments should be merged or that a new executive position is needed.
Set boundaries without predetermining the answer. Define the services, entities and governance relationships included, the relevant planning horizon and the matters requiring separate advice. Confirm who approves scope changes. A review that expands informally can consume time while leaving the original leadership decision unresolved.
Why an internal chart can be the wrong starting point
The Auditor General’s 2025 follow-up on programs for First Nations examined ISC’s implementation of recommendations from six earlier audits. It reported continuing program and service challenges and identified barriers to implementation. The audited organization was the federal department, not the administrations of First Nations.[5] A Nation commissioning its own review should therefore avoid assuming that every local service problem originates inside its own organization.
Consider a hypothetical housing application delay. It may reflect an unclear handoff between housing and finance, an insufficiently resourced team, or a dependency on external approvals and capital resources. Those causes can coexist, but merging departments addresses only some of them. A review should identify how much of the delay is associated with each constraint and which party has the authority to act.
The CCP Handbook’s published Lytton First Nation example describes building on an existing strategic plan and governance arrangements, then linking priorities to implementation. It also describes organizational-chart changes within that broader planning work.[1] This is an illustrative community account, not comparative proof that a particular structure produces better results. Its relevance is the connection between organizational choices and a Nation’s own planning context.
These sources serve different purposes: the audit identifies problems in federal program implementation; the handbook shares planning experience; neither diagnoses this administration. The local review must supply that evidence. Ask reviewers to state what each source supports, what remains uncertain and how they will test whether an external constraint is being mistaken for an internal design problem.
Make the Nation’s priorities the design criteria
The review should explain how organizational choices will support the Nation’s own priorities. Population, geography, culture, language, treaty relationships, resources and institutional history can all affect the appropriate arrangement. Reviewers should understand the relevant governing bodies and service institutions before applying terminology or importing an external model.
The CCP Handbook emphasizes community-driven planning and connecting priorities with implementation.[1] A review can build on existing plans rather than restart those discussions unnecessarily. Ask what the Nation has already decided, where implementation is constrained and which priorities require new organizational capacity.
Translate these priorities into criteria for comparing options. Examples might include dependable community access, clearer accountability, affordable ongoing costs or stronger local workforce development. Leadership should approve the criteria and recognize tensions between them. A more specialized structure may improve technical support while creating additional management and coordination costs.
Choose the smallest review that can answer the consequential question
A focused process or delegation review
This option is appropriate to test when the concern is concentrated in a defined decision or service pathway. Examine who approves, what information is required, where work waits and whether the agreed procedure is usable. It can be less disruptive than reviewing the entire administration, but its narrow scope may miss a shared capability gap affecting several departments.
A management-capacity and role review
This option examines workload, supervision, decision authority and specialist support across relevant roles. It may be useful where escalation repeatedly reaches the senior administrator or managers cannot support their teams. Compare recruitment with delegation, development, process change and shared support. A larger management team introduces continuing costs; clearer delegation requires competence, information and oversight.
A full organizational and operating-model review
A wider review may be warranted where the mandate has changed, several services share the same constraints, or responsibilities among governing bodies and institutions remain unsettled. It permits a coherent comparison of structures and delivery models. Its costs include leadership attention, staff participation and more complex implementation. Require a clear reason why the broader scope is needed, with boundaries and decision milestones.
These are management choices, not a mandatory sequence or standardized products. A focused review can legitimately reveal a wider issue. Agree how that finding will be tested and who may authorize a scope change. Conversely, if early evidence shows that a narrow remedy is sufficient, the team should be able to recommend it rather than continue towards an unnecessary restructuring.
Expect evidence about how work actually happens
Documents provide a starting point: organizational charts, job descriptions, work plans, budgets, policies and service information. They do not establish how work operates in practice. A chart can be current while a manager’s real responsibilities have changed substantially, and a written approval procedure may differ from the route employees use to meet deadlines.
Ask the review to combine document analysis with interviews and practical process examination. Employees can explain repeated handoffs, unclear decisions and informal workarounds. Leadership can describe the choices that repeatedly reach its agenda. Member perspectives, gathered through a process the Nation considers appropriate, can reveal service gaps invisible within departmental reporting.
Evidence should be traceable without exposing confidential contributions. The final analysis should distinguish observed patterns, reported concerns, confirmed requirements and matters that remain uncertain. An isolated complaint should not become an organizational finding simply because it is strongly expressed. Equally, a recurring problem should not be dismissed because it lacks a convenient numerical measure.
Require the evidence that would disprove the preferred explanation
Ask for an explanation of the mechanism, not simply a collection of opinions. If the proposed cause is excessive escalation, examine a defined sample of decisions: which ones reached leadership, whether they were reserved by policy, and whether the people below leadership had the authority and capability to resolve them. If the proposed cause is workload, examine demand, work complexity, vacancies and the effort required to complete the work.
For each important finding, ask what would change the reviewer’s conclusion. A proposed management position is less convincing if delays occur mainly outside that position’s authority. A process remedy is less convincing if the workload remains beyond available capacity even after rework is removed. A shared-service proposal is less convincing if the participating organizations need incompatible service arrangements and cannot agree who will resolve competing priorities.
Interviews remain important, particularly for understanding trust, informal practice and experiences that records do not capture. They should be interpreted with attention to whose perspective is missing and why different groups might describe the same process differently. Confirm factual patterns without circulating identifiable comments unnecessarily. Where records are incomplete, report the uncertainty rather than manufacture a precise workload estimate.
A useful progress discussion presents an emerging explanation, a credible competing explanation and the evidence needed to distinguish them. Leadership can then correct factual omissions and authorize further inquiry. That discussion should not become an opportunity to remove unwelcome findings; record substantive disagreements and how the final analysis addresses them.
Protect information and participation
Agree on information-governance arrangements before collecting records or interview material. Identify what may be accessed, where it will be held, who may review it, how findings will be reported and what happens to working files when the engagement ends. Clarify the limits of confidentiality rather than making promises the process cannot honour.
FNIGC’s guidance on the First Nations principles of OCAP® recognizes First Nations control over their information and Nation-specific application.[4] The review’s data arrangements should respect that direction alongside applicable privacy and other obligations. Consent to participate in an interview is not blanket permission to reuse someone’s contribution for another purpose.
Explain the review’s purpose to employees and other participants. Separate a structural review from an individual performance investigation unless the mandate explicitly and appropriately includes that work. If concerns arise that require a different process, leadership should address them through the relevant authority and advice, rather than quietly changing the nature of the review.
Require alternatives rather than one unexplained chart
A credible review should identify realistic options and explain their tradeoffs. The current arrangement, with focused improvements, should be considered where it is a genuine alternative. Other options might change delegation, departmental boundaries, management support or shared services. The review should explain which problem each option addresses and which problems remain.
For a hypothetical overloaded senior administrator, options could include clearer delegated authority, strengthened departmental management or a new senior role. These are different investments. Comparing their decision requirements, ongoing cost, supervision and implementation demands gives leadership a stronger basis for choice than treating another position as the inevitable solution.
Ask what would need to be true for the preferred option to work. If the design assumes successful recruitment, better information systems or a funding change, those dependencies should be explicit. Distinguish an attractive future model from a feasible near-term arrangement. A phased design may be appropriate when the Nation cannot safely or affordably implement every recommendation at once.
Examine roles and authority together
An organizational chart shows reporting relationships but cannot carry the entire governance and management system. Recommendations should also clarify mandates, decision rights, escalation and oversight. A position without appropriate authority can become a coordinator of unresolved issues, while authority without information and support can expose the organization to avoidable mistakes.
FMB’s Administrative Governance guidance addresses delegation and monitoring within its financial-administration framework.[2] The review should identify which arrangements apply locally, including decisions reserved to Council or other governing bodies. It should not describe an external framework as a universal legal requirement for every Nation.
Role recommendations also need a workforce perspective. FMB’s Human Resources guidance discusses organizational charts, job descriptions and training plans.[3] Ask how proposed responsibilities relate to employee capability, supervision, development and continuity. Material employment implications should receive appropriate advice and process before implementation commitments are made.
Compare the whole commitment, including the work left behind
Cost each feasible option against the same service expectations and planning horizon. Include implementation effort, recurring positions, supervision, technology, travel and any work retained locally under a shared arrangement. Avoid comparing the full cost of one option with only the visible staff cost of another. Where reliable estimates are not yet available, show the assumptions and the next decision needed to refine them.
Financial affordability and organizational feasibility are separate tests. An approved budget does not establish that the required manager can be recruited, that departments can release staff for implementation or that a partner will provide the assumed support. Test a vacancy and a delay in a critical dependency. Explain which changes can still proceed and what would need to be deferred.
The same discipline applies to the review itself. Agree a proportionate document request, staff participation plan, decision calendar and process for resolving missing information. A comprehensive assessment can be poor value if it consumes the very management capacity required to stabilize services. Internal analysis, peer support or a focused independent assessment may be sufficient for a bounded decision; a broader engagement should earn its scope.
Organizational Review Decision Chain
This original Arcus framework tests the reasoning that connects the review to a leadership decision. Use each card to ask for evidence and identify where a recommendation needs more work. It is a management aid, not a numerical quality score, audit opinion or certification.
Priority to problem
Evidence to request: The observed service or implementation problem and the Nation-defined priority it affects.
Reason to question the recommendation: The report assumes a departmental merger before showing where the constraint occurs.
Evidence to explanation
Evidence to request: The evidence for the proposed cause, the strongest alternative explanation and remaining uncertainty.
Reason to question the recommendation: Repeated interview opinions are presented as proof of a cause without checking workflow or authority.
Options to decision
Evidence to request: Feasible alternatives compared on service impact, authority, full cost, capability and dependencies.
Reason to question the recommendation: The preferred option assumes unavailable staff or partner commitments without an interim arrangement.
Decision to delivery
Evidence to request: An authorized owner, transition resources, completion conditions and a review of the original problem.
Reason to question the recommendation: Approval is requested for a chart without the practical changes required to make it work.
If competing views about structure are preventing a decision, Arcus can help define the review question and compare explanations before developing organizational options.
Expect an implementation plan with the report
The final report should translate recommendations into a manageable sequence. Identify immediate improvements, decisions requiring further work and changes dependent on recruitment, funding or policy approval. Each action needs an accountable owner and a completion condition. Avoid assigning every recommendation to an executive who already lacks capacity to lead the transition.
Include the costs of implementation as well as the ongoing structure. Training, temporary coverage, communications, revised procedures and system changes can require real resources. Leadership needs to see these demands before approving a model. Where estimates remain uncertain, the report should explain the assumptions and the decision that will refine them.
Choose measures that reflect the original problem. Decision turnaround, reliable follow-up, clearer escalation or completion of work plans may be more meaningful than counting how many boxes changed on a chart. Establish a baseline where practical and decide when leadership will revisit the design. Improvement should be demonstrated through the work rather than assumed from the launch.
Accept the recommendation separately from authorizing implementation
Leadership may agree with the diagnosis while requiring further work on a proposed structure, or approve one element while leaving another conditional. Record those distinctions. The final report should identify which recommendations are within existing authority and which require policy decisions, funding, employment advice, partner agreement or further engagement under the Nation’s own arrangements.
Use acceptance criteria agreed at the outset. Can leadership trace the recommendation to evidence? Does it understand what remains uncertain? Are realistic alternatives fairly represented? Is the full commitment visible? Does a capable owner have time and authority to implement the next step? These questions are more useful than accepting the report because its planned interviews and workshops are complete.
After implementation, revisit the original concern. If the chosen arrangement does not improve the decision or service pathway, examine whether the explanation was wrong, implementation was incomplete or conditions changed. A review should leave enough reasoning and practical knowledge within the Nation for leadership to make that assessment without commissioning the same diagnosis again.
Arcus Advisory
Commission a review that can change the decision.
Arcus can help define the organizational question, assess responsibilities and management capacity, and compare feasible design and implementation choices. Depending on the agreed scope, outputs may include an evidence-based diagnosis, options analysis, role and decision-rights recommendations, and a staged implementation plan. Leadership retains the decisions; specialist employment, legal and audit matters require the appropriate expertise.
Related research and consulting
When Has a First Nation Outgrown Its Organizational Structure? Seven Warning Signs
Arcus Organization Design consulting · Arcus consultant directory · Organizational Design & Change collection · First Nations Knowledge Centre
Sources and limits of the evidence
- 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®.
- Office of the Auditor General of Canada. Follow-up on Programs for First Nations. Tabled October 21, 2025. Audit of ISC follow-through on earlier recommendations; not an assessment of an individual Nation’s administration.
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). The CCP Handbook is BC planning guidance with illustrative community accounts, not comparative causal evidence. FMB guidance is institutional guidance, not an impact evaluation; its applicability depends on the Nation’s arrangements. FNIGC principles require Nation-specific application. Research reviewed October 17, 2026. The thesis and expanded decision framework are Arcus management synthesis, not proprietary empirical research.