First Nations Management & Leadership · Arcus perspective
How to Build an Effective Senior Management Team in a First Nation
A management team needs work that belongs to the team
Putting department heads in a weekly meeting does not necessarily create a senior management team. If each person reports progress to the executive and then returns to an unchanged departmental plan, the group may be a useful information forum. It has not yet demonstrated a collective management function.
The strongest reason to establish a senior management team is to resolve interdependent work: competing resource demands, services crossing departmental boundaries, shared risks and implementation choices requiring several managers. Its value comes from decisions and coordination that individual departments cannot accomplish alone.
Begin by identifying that shared work. Do not assume that every management issue needs group consideration. Routine supervision, confidential individual matters and decisions reserved to governing leadership need their appropriate routes. The team’s mandate must fit the Nation’s actual authorities and information requirements.
Use the evidence with attention to context
AFOA Canada’s CAPA course descriptions include leading effective teams, financial oversight, communication and knowledge of the local governance context. This supports a broad capability perspective: technical knowledge and working relationships both matter. The curriculum is professional guidance, not an evaluation showing that any particular meeting model improves results.1
Amy Edmondson’s 1999 study examined 51 teams in a manufacturing company and found an association between team psychological safety and learning behaviour. The study is relevant to asking whether managers can raise uncertainty and discuss mistakes. It is not First Nations research, and it does not establish that importing a workplace intervention will produce the same results in a Nation’s government.2
Arcus uses these sources to frame questions for local testing, rather than prescribe a universal team culture. The Nation determines the appropriate ways to deliberate, respect relationships and exercise authority. A useful design enables candid discussion while preserving clear responsibility for the decision.
Distinguish four explanations for a weak team
A group may appear uncooperative because it lacks shared work, lacks authority, lacks capability or lacks trust. These are different problems. A team-building session may help relationships but cannot authorize a resource decision. A new mandate may clarify authority but cannot supply missing financial analysis.
Review several recent matters that crossed departments. Identify what information was missing, what choice remained unresolved and who had authority to act. Ask whether the issue belonged in the group at all. If managers could have resolved it directly, the meeting may be adding delay.
Consider a hypothetical community event requiring facilities, transportation and program staff. Repeated disagreement might reflect competing schedules, an unfunded commitment or uncertainty about who approves overtime. Calling this a personality problem before examining those constraints risks choosing the wrong intervention.
Where distrust is the central issue, establish whether managers experience consequences for raising problems early or challenging assumptions. A meeting cannot become candid simply because its chair asks people to speak openly. Leaders need to respond consistently when the information is inconvenient.
Choose the forum that the work requires
A coordination forum is appropriate when managers mainly need to exchange information and align schedules. Keep it brief and retain decision ownership in the responsible roles. It should not imply collective approval of every departmental action.
A standing senior management team is appropriate when recurring choices require trade-offs across services and functions. Define its membership, decision process, boundaries and escalation route. The executive remains responsible for decisions within the executive mandate; a team discussion does not automatically create collective authority.
A temporary cross-functional group fits a defined initiative or recurring service problem with a clear endpoint. Include the people who understand the work, even if they are not the most senior. Establish the sponsor, deliverables and route for decisions beyond the group’s authority. Close or redesign the group when its purpose ends.
An organization may need all three forms, but each should have a distinct purpose. Avoid requiring the same people to repeat the same discussion in several forums. Map the decision path before adding another committee.
Design membership around contribution and decision needs
The team needs managers who can explain operational consequences and the functions that reveal important constraints. Finance, people management and service operations often provide different perspectives on the same proposal. Membership should reflect the Nation’s scale and responsibilities rather than a borrowed organization chart.
Distinguish standing members from invited contributors. A specialist may be needed for one decision without attending every routine discussion. A frontline perspective can reveal a practical problem that a senior team misses, but participation should be purposeful and supported rather than symbolic.
Clarify the role each person plays. Are they authorized to commit departmental resources, provide advice or take a recommendation back for approval? Without that distinction, apparent agreement may dissolve when implementation begins. Record any conditions attached to a commitment.
Make challenge part of the decision process
For a consequential proposal, ask one participant to explain the strongest alternative and another to identify implementation assumptions. Invite managers closest to the affected work to speak before the executive states a preference. These are practical options for testing, not requirements for every Nation’s deliberation style.
Separate challenging a proposal from criticizing a person. The group should be able to examine whether staffing, timing or cost assumptions are credible. It should also distinguish evidence from preference and identify what additional information would change the recommendation.
Do not confuse psychological safety with guaranteed agreement or freedom from accountability. Managers need to raise concerns, and they remain responsible for the work they have accepted. Equally, accountability should not discourage early disclosure of a problem that can still be corrected.
After the authorized decision, document the action, owner, dependencies and review date. Record significant unresolved reservations when they affect implementation or risk. A statement that everyone agreed is less useful than an accurate record of what was decided and what remains uncertain.
Calculate the cost of collective management
The cost of a meeting includes participants’ preparation, attendance, follow-up and the service work displaced. For planning, estimate the total hours across all participants over a year, including the person who prepares the evidence. This can reveal that a seemingly modest recurring meeting consumes substantial management capacity.
Balance that cost against specific work avoided: repeated bilateral negotiations, unresolved dependencies, rework caused by late information or decisions that otherwise wait for the executive. These benefits should be observed locally; they should not be assumed from the existence of a team.
A shared decision log or concise pre-read may be sufficient at first. A new software platform introduces configuration, training, access management and ongoing administration. Invest in technology when the workflow is understood and the scale justifies it. Do not automate an unclear decision process.
Budget development effort as well. Managers may need coaching in financial interpretation, briefing notes, conflict resolution or supervising staff. Protect time to apply new skills to actual work. A course without changes to expectations or opportunity to practise may leave the operating problem unchanged.
Use a practical agenda and decision record
A useful agenda separates information, coordination, decisions and escalations. For each decision item, state the question, authority, available options, resource implications and affected services. Ask whether the group has enough information to decide or whether it is only ready to define the next inquiry.
Review outstanding commitments by exception: what has changed, what is blocked and what support or decision is needed. Avoid using the meeting to read every task aloud. Preserve enough underlying information for participants to challenge a summary when necessary.
Keep private case details in the appropriate process. The senior team may need to understand a staffing risk without receiving unnecessary personal information. The Nation’s information rules determine what can be shared, and general team membership does not establish unlimited access.
Close each consequential item by confirming the decision or next step. Name the owner and the date for review. Where the group is advisory, identify the person or body that will make the decision and what must be presented to them.
Pilot the team on a real dependency
Select one recurring cross-department problem, such as coordinating facility readiness with staffing and program launch. Establish the team’s authority and the evidence needed. Map the dependencies and agree which decisions can be made in the team and which must be escalated.
Over several meeting cycles, track unresolved dependencies, decisions reopened because key information was missing and overdue shared commitments. Also record the effort required to operate the process. These measures are diagnostic, not a validated score or a substitute for service outcomes.
At review, ask whether managers can resolve shared work more reliably, whether concerns surface earlier and whether the executive receives better recommendations. Consider changes in staffing or demand before attributing improvement to the new team. Retain the useful practices and remove steps that add discussion without improving coordination.
The Arcus shared-management framework
This original Arcus decision framework is a management aid for local adaptation. It is not a validated assessment instrument or a substitute for the Nation’s authority and relevant professional requirements.
Shared work
Question: Which issue genuinely needs several managers?
Decision evidence: Identify dependencies, competing resources or risks that cannot be handled effectively within one role.
Authority
Question: What may the team decide or recommend?
Decision evidence: State the decision owner, limits and escalation route before seeking agreement.
Challenge
Question: Can the group test assumptions and alternatives?
Decision evidence: Make space for operational evidence, uncertainty and reasoned disagreement.
Commitment
Question: Who will do what after the discussion?
Decision evidence: Record owners, resources, dependencies and review dates in a usable form.
Value
Question: Does the team improve work enough to justify its cost?
Decision evidence: Compare decision quality, unresolved dependencies and total management effort over a defined pilot.
Turn the design into an operating commitment
Begin with one piece of shared work and a clear decision route. A management team should earn its place through better coordination and follow-through, rather than through the seniority of the people attending.
Arcus can support the assessment of cross-department work, design of team mandates and decision routines, and development of practical management capabilities. The Nation determines the authority and cultural context in which those routines operate.
A useful first result is a decision that departments can implement together with fewer unresolved assumptions. Build the broader team around repeated evidence of that value.
Sources and limits of the evidence
- AFOA Canada — CAPA Online Courses. Professional course descriptions identify team, communication, financial and governance capabilities. They do not provide causal evidence about a specific team design.
- Edmondson, A. (1999), Psychological Safety and Learning Behavior in Work Teams. Research summary and abstract in Harvard’s repository, Administrative Science Quarterly 44(2). Study of 51 manufacturing teams; association and context limits are retained. No First Nations-specific effect is claimed.
Research reviewed October 18, 2026. Decision frameworks, options and hypothetical illustrations are Arcus management synthesis. No client outcomes or universal savings or impact benchmarks are claimed.
Governance & Leadership collection · The executive’s role in reconciling commitments · Organization design services · Arcus consultant directory