Work plans must settle promises between departments

Attaching a strategic priority number to every activity creates traceability. It does not establish that the activity is affordable, that a partner department has agreed to help or that completion will improve the intended outcome. Alignment becomes useful when it changes decisions about work.

A community vision of easier access to services may involve communications, information systems, program managers, facilities and finance. Assigning the entire priority to one department conceals those contributions. Giving every department the same broad objective can produce overlapping projects without a person responsible for the combined result.

Arcus recommends a two-part translation: identify the service or community outcome, then agree on the specific contribution each department will deliver. Keep one accountable lead for the combined initiative, with named roles for contributing functions. Accountability should come with the authority to coordinate, obtain decisions and escalate unresolved conflicts through the Nation’s management structure.

The work plan is therefore an agreement about deliverable work, not simply a list of aspirations. Its usefulness should be tested at the point where one team depends on another.

Diagnose why an aligned plan is not progressing

The output may be unclear. “Improve member communication” permits many activities but provides no test of completion. A useful first commitment might be a reviewed service directory with an assigned update owner and a process for correcting errors. Whether that improves access remains a separate outcome question.

The dependency may be unacknowledged. Communications cannot publish accurate service information if program managers have not reviewed it. A work plan that assigns all the work to communications may misdiagnose delayed input as poor execution by the lead team.

Essential services may consume the available time. A department can be fully occupied by recurring responsibilities, vacancies and urgent requests. Adding a project without examining that workload creates an unfunded commitment in staff-hours, even when a project budget exists.

Approval may be missing. Staff may have developed a viable option but be waiting for a resource decision or authority to change a process. Additional status reports will not resolve an unmade decision. Identify who must decide, the information required and the latest useful decision date.

The intervention may not address the real barrier. A directory will not solve service-access problems caused mainly by unavailable appointments or transport. Test the proposed contribution against members’ actual experience before scaling it. An output can be completed correctly while the strategic outcome remains unchanged.

Build a commitment record that another team can use

For each significant initiative, record the intended outcome, the department’s contribution, the person accountable, the deliverable, the acceptance criteria, the timing, the resource envelope and the assumptions. Then identify what must arrive from other teams and what this team owes them.

An acceptance criterion should describe useful completion. “Hold a workshop” is an activity. “Agree and record the service referral process, test it with the participating teams and assign an owner for exceptions” explains why the workshop matters. Do not make participation in a meeting the main measure of operational improvement.

Specify dependencies in practical terms: the information, authorization, staff-hours or completed work required; who supplies it; when it is needed; and who confirms receipt. A vague “support from finance” entry cannot be scheduled. A defined costing review with an agreed scope and date can be incorporated into finance’s own workload.

Use the same initiative identifier in the contributing work plans. This makes it possible to see one shared initiative from several departmental perspectives without counting it several times as separate strategic progress. Keep the record proportionate: a small routine improvement may need a few lines, while a major cross-department change needs a fuller brief.

Test capacity before agreeing to the timetable

Start with available time after recurring services, required reporting, leave, vacancies and a realistic allowance for interruptions. Use local operating information rather than treating every paid hour as project capacity. Ask contributing departments to confirm their own estimates; a lead team should not allocate another team’s time unilaterally.

Consider a hypothetical eight-week service-directory pilot. Communications has 48 staff-hours available for improvement work. The pilot needs 32 hours and an already-approved update needs 20, for a total of 52. Program teams must supply another 24 hours of review, and finance needs 8 hours to check cost information. Those 32 contributing hours do not solve communications’ four-hour shortage.

The administration could narrow the pilot, move part of the existing update, extend the schedule or obtain suitable temporary support. Each option has a different consequence for the service, timing and supervision. The correct choice depends on the value and urgency of the competing work, not simply on which manager asks first.

The pilot’s total estimated effort is 64 staff-hours: 32 communications, 24 program review and 8 finance. A time estimate is not a complete cash budget. Add any external services, accessibility work, printing or systems costs, and distinguish incremental spending from the use of existing salaried capacity. Include the ongoing effort to maintain the directory after launch.

These numbers are illustrative, not staffing benchmarks. Their purpose is to expose the difference between an initiative’s total effort and the capacity constraint within a particular function.

Run one reconciliation before approval

Have departments prepare their proposed commitments using a common minimum set of fields. Assemble shared initiatives in one view, then compare demand on scarce functions such as finance, human resources, procurement, information systems and senior management. A plan can appear feasible department by department while overloading the same supporting team.

Use the reconciliation meeting to make decisions. Settle conflicting dates, combine duplicate work, agree on the order of dependencies and remove commitments that lack resources or authority. Record the changes in each affected plan. Avoid treating the meeting as a presentation exercise in which every original request survives unchanged.

Approve a baseline and a simple change process. When urgent new work arrives, ask which existing commitment it affects and who can authorize the change. Preserve an appropriate route for urgent service needs, while making their consequences for the plan visible.

At regular management reviews, focus on exceptions: a missing input, a resource shortfall, a decision approaching its useful deadline, or evidence that the intended benefit is not emerging. Leadership reporting can summarize these issues at the strategic level without taking over routine task supervision.

At the end of a delivery stage, confirm that the output is accepted, maintenance responsibilities are assigned and the team has learned whether the change is useful. Community vision becomes operational when the administration can explain both what it promised and what its combined work made possible.

Evidence and source notes

1. Millbrook First Nation, 2025 Annual Report, available through its reporting page. The report describes departmental work plans aligned with seven strategic priorities. Used as a descriptive planning example, not an evaluation of results.
2. Nipissing First Nation, Strategic Plan 2025–2026, communication objectives and Chief and Council support. The document describes intended initiatives and enabling leadership roles; it does not establish their completed outcomes.

Research reviewed October 18, 2026. The directory pilot and all resource figures are hypothetical. The six tests are original Arcus analysis and should be adapted to the Nation’s governance, administration and service responsibilities.