First Nations Management & Leadership · Arcus perspective
Why First Nations Organizational Restructuring Often Fails — and How to Make Change Stick
A new organizational chart can be approved while everyday work remains largely unchanged. Requests still reach the same overloaded executive, staff continue using old approval routes and departments retain their informal boundaries. The organization has changed its description without establishing the conditions needed to operate differently. Leadership then faces a difficult question: was the design wrong, or was it never properly implemented?
The title’s reference to failure describes a management risk, not a measured failure rate among First Nations. There is no claim here that Nations share one pattern of restructuring. The practical issue is how to distinguish weaknesses in design, transition and sustained management. Chiefs, Councillors and senior administrators can use that distinction to make changes more workable within their Nation’s own priorities and governance arrangements.
Diagnose the original problem precisely
A restructuring can lose direction when leadership begins with an organizational answer rather than an observed problem. A new department, senior position or reporting line may be reasonable, but it should be linked to a specific service, decision or capacity requirement. Otherwise, success becomes the completion of the change itself.
Consider a hypothetical program that repeatedly misses internal deadlines. The explanation could be unclear ownership, unrealistic workload, incomplete information or several approvals that do not serve distinct purposes. Moving the program into another department will not necessarily resolve those causes. Review a realistic sample of work before deciding which structural changes are warranted.
Describe the problem in a form leadership can revisit. Record its practical consequences, the evidence supporting the explanation and the improvement expected. Include alternative explanations. This creates a basis for testing the design later and helps avoid the assumption that any continuing difficulty must reflect employee resistance.
Do not confuse agreement with operational readiness
What documented transition evidence supports this distinction?
Indigenous Services Canada’s December 2023 Health Infrastructure Support evaluation combined document and program-data review, interviews and focus groups, a voluntary survey and case studies. Its discussion of First Nations Health Authority transfer lessons identified clear partner responsibilities, time for systems and governance to mature, and sustained resources, including information technology.[5] The evaluation did not formally evaluate the British Columbia tripartite model; that discussion drew on earlier evaluation and other evidence. Health-service transfer is broader than an internal administrative restructuring. These findings support checking dependencies and transition resources, not a claim that a particular structure will work or that restructuring has a measured national failure rate.
Leaders can agree on a structure before the organization is ready to use it. Job descriptions may be incomplete, managers may lack capacity and systems may still route work through the old organization. Approval establishes a direction; it does not automatically resolve the dependencies that direction creates.
Ask what must be ready before each responsibility transfers. A new manager may need authority, staffing, access to records, a budget and a relationship with supporting departments. Distinguish genuine prerequisites from improvements that can follow later. An unnecessarily elaborate readiness standard can stall useful changes, but ignoring essential conditions transfers uncertainty into service delivery.
The CCP Handbook connects implementation with responsibilities, resources, timeframes and monitoring.[1] Apply that discipline to the transition. Each approved recommendation needs a practical owner and completion condition. If implementation depends on resources that have not been secured, leadership should see that condition explicitly rather than encounter it after the announcement.
Change the decision system alongside reporting lines
An employee’s reporting relationship can change while approval policies continue to name the previous role. Managers may receive new accountability without sufficient authority to act. This creates an incentive to keep seeking informal permission, even where leadership expected faster decisions.
FMB’s Administrative Governance guidance discusses delegation, documentation and monitoring within its financial-administration framework.[2] A restructuring should confirm the Nation’s applicable authorities and establish how ordinary decisions and exceptions will be handled. A chart is not a substitute for the approvals required under the Nation’s own laws and policies.
For a hypothetical purchasing process, clarify the department’s request responsibility, the approval authority and any independent control. Explain what changes and what remains reserved. Do not remove useful controls merely to demonstrate speed. The goal is a decision process that is both workable and appropriately accountable, with unnecessary duplication addressed through evidence.
Give managers time to perform the new role
A design may depend on managers leading people, coordinating services and monitoring results while their previous operational workload remains unchanged. The new responsibilities are then added to the old job. Predictable overload can be misinterpreted as an individual capability problem when the role itself was never made feasible.
Examine the manager’s real commitments. Decide which tasks will move, which processes will simplify and what supervision the role requires. Include transition work such as staff discussions, training, records transfer and problem resolution. If these responsibilities have no place in the workload, the organization is relying on additional personal effort rather than a resourced plan.
FMB’s Human Resources guidance addresses charts, job descriptions and training plans.[3] Those tools should reflect actual expectations. A development plan can help someone assume unfamiliar responsibilities, but it should not conceal an unmanageable combination of work. Leadership may need to revise the sequence or scope before expecting the role to succeed.
Treat staff concerns as information
Employees may question a proposal because they see a service dependency that the design team has missed. They may also be concerned about job security, fair treatment, professional responsibility or the credibility of earlier promises. Listening carefully helps distinguish a practical warning from disagreement about the preferred model.
Explain which decisions remain open and how input will be used. Where a decision has already been made, be clear about the scope for shaping implementation. Asking for consultation on a settled question can damage trust if participants reasonably believe they are influencing the outcome. Equally, a clear decision does not remove the need to hear evidence about its implementation risks.
Use appropriate processes and professional advice where changes affect employment or other rights. Do not promise that nobody will be affected unless leadership can support that commitment. A credible communication distinguishes what is known, what is conditional and when further decisions will be made. Uncertainty can be managed more responsibly when it is acknowledged.
Preserve essential relationships and knowledge
The old structure may contain weaknesses while still supporting valuable relationships. Employees know whom to call, which records explain an unusual case and how to coordinate with community institutions. A redesign that removes these connections without replacing their function can make service delivery less dependable during transition.
Map knowledge and handovers as part of implementation. Identify ongoing commitments, unresolved matters and key supporting contacts. Where possible, have the incoming owner confirm readiness rather than treating a file transfer as completion. Preserve continuity arrangements while new working relationships become established.
Information sharing must remain deliberate. FNIGC describes the First Nations principles of OCAP® as supporting First Nations information governance and Nation-specific application.[4] A new shared function does not create blanket authority to access every record. Determine what information the role needs, who authorizes access and how the Nation’s requirements will be maintained.
Design Adoption Results Framework
Use this original framework to identify where a change is struggling. It separates three linked management questions so that leadership can respond to the actual weakness. It is not a numerical diagnostic and does not certify that an organizational model is appropriate.
Design fit
Does the proposed arrangement address the evidenced problem and the Nation’s priorities? Examine mandates, responsibilities, affordability and coordination. If the design relies on assumptions that no longer hold, reconsider the option rather than accelerating implementation of an unsuitable model.
Operational adoption
Can people use the new arrangement in ordinary work? Check authority, capability, workload, records, procedures and service handoffs. Identify which missing conditions explain continued use of old practices. An instruction to comply cannot replace necessary operational support.
Results and adjustment
Is the work improving in the way leadership intended? Compare evidence with the original problem. Decide what to retain, adjust or investigate further. A structure should be open to informed correction rather than defended as complete because its launch date has passed.
Make each transfer decision reviewable
For a material responsibility, record the design assumption, readiness evidence, observed use, expected result and corrective decision. An example assumption might be that an authorized departmental manager can approve a defined class of requests without unnecessary executive escalation. Readiness evidence would include the actual delegation, system access, procedure and available workload. Observed use means checking ordinary requests, including an exception, rather than accepting a training attendance list as proof of adoption.
Use the result to choose the response. If the approved route cannot be used, resolve the missing condition or adjust the transfer date. If it is used but the original problem persists, revisit the causal explanation and design. If results improve while control or service risks worsen, correct those consequences before expanding. This keeps the framework connected to an authorization decision rather than a general statement of readiness.
A worked adoption test: the same delay can require different action
Consider two fictional versions of a purchasing-process change. In the first, a manager has formal authority, but the system still routes approval to the former executive and staff instructions name the old role. Requests continue to wait. The immediate test is whether correcting access and instructions allows the authorized process to operate; replacing the manager or adding another reporting layer would not address the observed mismatch.
In the second version, staff use the new route, approval is timely and the controls function, but services still receive materials late. Trace what follows approval: incomplete specifications, supplier availability, ordering schedules or receiving arrangements may explain the delay. The design promised a service result that faster approval alone could not produce. Leadership should investigate that dependency before expanding the same change elsewhere.
These illustrations are not client cases or proof of either cause in a particular Nation. A short sample can identify a useful next test but may miss seasonal, unusual or high-risk work. Choose review evidence that reflects the actual service cycle and preserve an exception route during the transition.
Build correction into the implementation plan
Early problems should have an owner and a route to resolution. Create a manageable issue log that records the service affected, immediate response, underlying cause and decision required. Avoid collecting concerns without resolving them. Employees need to know which matters can be fixed locally and which require a broader design decision.
Choose review points that fit the transition rather than an arbitrary reporting cycle. A new approval process may reveal problems quickly, while a workforce arrangement may require experience across a seasonal peak. Consider what evidence will be meaningful before declaring success or failure. Keep essential service risks under active oversight in the meantime.
Protect the ability to change direction. A pilot, staged transfer or temporary support arrangement can sometimes reduce exposure while the model is tested. These are options, not universal requirements. Where a change must occur together, leadership should understand the consequences and establish appropriate contingency arrangements rather than assume that gradual implementation is always possible.
Compare the sequence and its full resource requirement
A process pilot suits a responsibility that can be tested within a bounded workflow while essential controls and service continuity remain intact. It can expose hidden dependencies before a wider change. Its limit is representativeness: success with an easy case or unusually well-supported team may not transfer to the full organization.
A staged transfer suits responsibilities that can move in defined groups with clear temporary ownership. It spreads training and handover work, but duplicate processes and ambiguous boundaries can persist. State the end condition for each temporary arrangement and who resolves a request that crosses the old and new structures.
A coordinated cutover may be necessary where authorities, systems or interdependent services must change together. It concentrates preparation and service risk. Require evidence that essential dependencies work, contingency responsibilities are assigned and a fallback is feasible and authorized. Do not presume that a technical reversal can undo employment, legal or service decisions.
Compare options using transition and recurring costs separately. Transition work includes backfill, overlapping operation, training, records and access changes, management attention and resolving early exceptions. Recurring costs include the continuing roles, systems, supervision and service coverage. For each option, estimate locally required hours by capability and period, direct external costs and the approved work displaced. Existing employees’ time is a real capacity constraint even if it does not add a new invoice.
Do not count the same available hours as both ordinary service capacity and transition capacity. If leadership cannot release the required people or fund the necessary overlap, narrow or resequence the change where obligations permit. A lower initial cash outlay can still create a more expensive transition if it prolongs duplicate work or leaves critical responsibilities unowned.
Know when implementation needs independent support
External support can be useful when management lacks capacity to lead the transition, when departments disagree about responsibilities or when leadership needs an independent assessment of competing explanations. The mandate should identify whether the need is design review, implementation management, facilitation or workforce support. These are related but different services.
Ask for capability transfer as well as deliverables. Managers should understand the reasoning behind the model and how to maintain it after the engagement. The Nation should retain practical control over decisions, information and implementation priorities. External coordination should strengthen internal responsibility rather than become the permanent route through which ordinary work is resolved.
A change sticks when people can use it and leadership can see whether it helps. That requires a credible design, operational readiness and disciplined adjustment. If the organization continues working around the new structure, investigate what the workaround reveals before asking employees to abandon it. The evidence may identify the next useful improvement more clearly than another announcement.
Arcus Advisory
Discuss the decision facing your Nation.
An Arcus engagement can be scoped to diagnose whether a stalled change reflects design, operational adoption or an unresolved service dependency. Practical deliverables can include a transition dependency register, decision-rights and handover records, an adoption test using real work, a costed comparison of implementation sequences and a results-review plan. Leadership can use these outputs to decide what is ready to transfer, what requires correction and how to maintain the model after implementation. Scope, information access and responsibilities should be agreed with the Nation.
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. Cluster Evaluation of Health Infrastructure Support for First Nations and Inuit, released December 2023. Scope: fiscal years 2015–16 through 2020–21. Finding 23 discusses transfer lessons; uneven performance information and voluntary participation limit inference. It is not a causal evaluation of internal restructuring.
The management analysis, hypothetical illustrations and original framework are Arcus analytical synthesis and 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.