From Strategic Plan to Monday Morning

Most organizations have a strategic plan. Far fewer have a way for that plan to show up in what a department does on a Monday morning. The gap between the two is where strategy quietly dies.

Two Plans, Two Different Jobs

A strategic plan and a tactical plan are not the same document at different levels of detail. They answer different questions, for different audiences, over different time frames.

The strategic plan aligns the board, the executive team, and staff around one north star. The tactical plan is the bridge: it turns each pillar into bite-sized work that a manager can assign and a team can finish.

One page, two views, for every department

The format that works best is deliberately simple: one page per department, with two views of the same year.

• The production viewDepartment goals by quarter, each with the KPI it moves and the strategic pillar it serves.
• The project viewProjects on deck by quarter, how much capacity the team actually has, requests from the executive team, and the cross-functional help each project needs.

Keeping both views on the same template matters. Production goals show what the team is accountable for. The project view shows whether the team has the capacity to do it. A plan with seven projects on deck and no spare capacity is telling you something before the year starts.

Tag every goal to a pillar

Give each strategic pillar a short code, and require every goal and project to carry one. It sounds administrative, but it does three things at once. It makes the plans comparable across departments. It shows instantly which pillars have plenty of work behind them and which have almost none. And it forces a useful conversation: if a goal can’t be tagged to any pillar, why is it in the plan?

I also separate work that runs the business from work that changes it. Both matter, but they compete for the same people, and leadership should see the split.

Then read the plans together

Most organizations collect department plans and file them. The real value comes from reading them side by side. When I do this, I look for four things:

1. Coverage. For each enterprise KPI, which departments set a target for it, and which ones influence it without saying so? A support team that moves a KPI should show up with a number.
2. Asks made versus asks received. When one department lists another as a partner, does the other team list it back? One-way dependencies are where projects stall.
3. Dates. Do the tactical plans agree with the enterprise roadmap? A project the roadmap expects in Q2 and the plans launch in Q3 is a decision waiting to happen.
4. Sizing. Does every efficiency project put a value on the hours or dollars it saves? If not, nobody can see the savings add up.

Deploy it with a rhythm

A tactical plan nobody reviews is a wish list. Four habits keep it alive:

• Cascade itTranslate the plan so every frontline employee can see how their daily work contributes.
• Cross functional linesPair departments on shared initiatives instead of handing work across a wall.
• Set a rhythm of accountabilityExecutives review enterprise KPIs monthly or quarterly; managers track tactical milestones in between.
• Make it visibleOne dashboard everyone reads, so progress is a fact rather than a status update.

A quick plan-hygiene check

Before the year starts, check that every plan uses the same year and quarter labels, that no production goal is left as “to be determined,” that every goal carries a pillar code and a KPI, and that cross-team asks have an owner and a date. It takes an afternoon and saves a quarter.