Step-by-step implementation guide — illustrative sample run, sample data only
✅ Verdict
This guide turns strategy into a repeatable operating rhythm — an annual frame, quarterly WSJF rescoring, and a weekly drift check — built on tools you already have. Follow it in order and you'll have a working system running by the end of this quarter, not another roadmap deck nobody opens again.
In this guide
1. Your Strategic Inputs — 2. Annual Strategic Frame — 3. Quarterly Rescoring Worksheet — 4. Weekly Drift Check — 5. Recalibration Trigger Rule — 6. System Summary & End-to-End Cycle
1. Your Strategic Inputs
Everything below was built from these inputs. Confirm they're accurate before reading further — the rest of the guide inherits from this section.
Organization Profile
~3,200 employees. Scope: the Enterprise Applications team, supporting ERP/HRIS across 90 field offices.
Current State
An annual PowerPoint roadmap built once for the board and not revisited. A shared spreadsheet backlog of ~18 competing initiatives with no formal scoring — priority currently goes to whoever escalates loudest.
Strategic Choices Supplied Directly
Winning Aspiration: Be the most reliable, lowest-friction back-office technology stack for a distributed, multi-site workforce — measured by fewer system-driven support tickets and faster new-site onboarding, not feature count.
Where to Play: Concentrate investment on the ERP/HRIS core and the integration layer connecting field offices to it — not on point-solution requests that don't touch the core stack.
How to Win: Win on integration reliability and platform standardization (one system of record per domain), not on fastest feature delivery or lowest cost per seat.
Capabilities Needed: A unified integration/middleware layer, a formal intake-and-scoring process, and cross-functional application-support skills rather than narrow per-system specialists.
Management Systems: Quarterly WSJF rescoring, a weekly drift check, and a single roadmap of record replacing per-department spreadsheets.
🚫 Anti-Pattern
If these hadn't been supplied directly or found in an uploaded strategy deck or board cascade document, this section would contain a structured working-session exercise instead — never invented placeholder language standing in for a leadership team's actual choices.
Tier, Tools & Platform
Tier: Lean — no new software budget approved this fiscal year. Systems already in place: Excel/SharePoint for general tracking; Jira, used only by the applications dev team for ticket-level work, not portfolio prioritization. Platform named for ongoing tracking: monday.com.
Reporting, Scale & Meeting Cadence
Reports to the CIO monthly and the Executive Committee quarterly. ~18 initiatives currently competing for the same delivery capacity (6 shown here as a representative sample). Existing recurring meetings: a monthly IT Steering Committee — no weekly team sync currently exists for the applications team.
2. Annual Strategic Frame
This is the top of the cascade — everything in Sections 3–5 inherits from it.
How to operationalize this
Review this frame once a year with your leadership team, before the first quarterly rescoring cycle of the fiscal year. If any box is contested — someone on the leadership team disagrees with Where to Play or How to Win — resolve it before moving into quarterly execution. A contested strategic frame means every WSJF score built on top of it is scoring against the wrong assumptions.
3. Quarterly Rescoring Worksheet
Cost of Delay (CoD) = Business Value + Time Criticality + Risk Reduction/Opportunity Enablement, each scored 1–10. WSJF = CoD ÷ Job Size (1–10, relative effort). Must-Do overrides rank for hard compliance/contractual/vendor deadlines.
Initiative
Business Value
Time Criticality
Risk Reduction / Opp. Enablement
Job Size
Must-Do
WSJF
Field mobile app performance fix
6
7
3
2
No
8.0
SSO rollout to remaining field systems
6
6
7
4
No
4.8
Legacy reporting tool retirement
4
4
6
3
No
4.7
New-site onboarding integration automation
7
5
4
5
No
3.2
ERP financial module upgrade (vendor end-of-life)
8
9
6
8
Yes
Scheduled
Data warehouse consolidation (BI reporting)
8
3
5
9
No
1.8
How to run this each quarter
Step 1Two weeks before quarter-end, ask every initiative owner to submit or reconfirm their initiative in the shared list. Late submissions roll to the following quarter unless flagged Must-Do.
Step 2One owner (or a small scoring committee) scores each initiative on Business Value, Time Criticality, and Risk Reduction/Opportunity Enablement, and estimates Job Size — against the Annual Strategic Frame, not against who's asking loudest.
Step 3Flag Must-Do for anything with a hard compliance, contractual, or vendor deadline. These get scheduled regardless of WSJF score.
Step 4 — Load into monday.comImport this table as a CSV to create a new board. Must-Do auto-detects as a Status field (Yes/No, under the 9-label threshold). Formula columns can't be set by CSV import — add one manually after import: ({Business Value} + {Time Criticality} + {Risk Reduction or Opp Enablement}) / {Job Size}
⚠️ Watch Out
Column names go in curly braces exactly as titled, case-sensitive, and this requires a Pro or Enterprise monday.com plan. There's no Rank column here on purpose — monday's Formula column can't rank across items the way Excel's RANK() does. Sort the board by WSJF descending instead; it's the live equivalent and updates automatically as scores change.
Step 5Publish the ranked board to stakeholders before the quarter starts, with Must-Do items called out separately so it's clear they're scheduled independent of rank.
4. Weekly Drift Check
How to use this
No weekly sync currently exists for this team — create one: a 15-minute standing "Applications Portfolio Weekly Sync." Attach these five questions directly to the recurring meeting invite or a shared agenda document, sent at least 24 hours ahead, so the leaders backing each top-ranked initiative come prepared to answer rather than getting put on the spot.
Did any of the top 5 ranked initiatives change status this week?
Is any initiative stalled or blocked for 2+ consecutive weekly checks?
Has a new escalation arrived outside the quarterly cycle demanding reprioritization?
Confidence flag (Green/Yellow/Red) for each of the top 5 — Yellow or Red requires one line on why.
Are all Must-Do items still on track for their deadline?
Week-over-week tracking template
A single week's answers don't show drift — a trend does. Log each week in the same grid:
Check item
Week 1
Week 2
Week 3
Week 4
Field mobile app fix — status change?
Green
Green
Yellow — blocked on vendor API access
…
SSO rollout — status change?
Green
Green
Green
…
Any initiative stalled 2+ weeks?
No
No
Watch: mobile app fix
…
New escalation this week?
None
None
None
…
Must-Do items on track?
Yes
Yes
Yes
…
💡 Insight
The #1-ranked initiative — the mobile app fix — is the one that drifts in this sample, going Yellow in Week 3 on a blocked dependency. That's the system working as intended: the highest-priority item is exactly the one you'd want an early warning on.
5. Recalibration Trigger Rule
Add a sixth standing question to the same weekly sync, right after the drift check: "Does anything we just discussed mean we need to recalibrate before next quarter?"
Recalibration procedure
Trigger
Scope
What to do
Who / when
A new Must-Do item appears with a deadline inside the current quarter
Minor
Add it to the Quarterly Rescoring Worksheet, flag Must-Do = Yes, re-sort the board. No change to the Strategic Frame needed.
Worksheet owner, same meeting or immediately after
30%+ of the top-5 ranked initiatives blocked or stalled across 2+ consecutive weekly checks
Investigate first
Discuss root cause in the meeting. Resourcing/execution problem → adjust scores and re-sort (Minor). Flawed strategic assumption → escalate to next row (Major).
Meeting owner + initiative owners, same meeting
An executive sponsor formally changes Where to Play or How to Win
Major
Rerun this brief's Section 2 with the new strategic choices, then re-run the Quarterly Rescoring Worksheet from scratch — every initiative's Business Value assumption may have changed. Regenerate Sections 2–3 and reload the platform.
Executive sponsor + system owner, scheduled follow-up outside the weekly sync
Otherwise: log the observation in the weekly tracker and carry it into the next scheduled quarterly rescoring. Not every yellow flag warrants a recalibration — only these three conditions do.
6. System Summary & End-to-End Cycle
What this guide produced:
Annual Strategic Frame — one-page document, reviewed yearly by leadership.
Quarterly Rescoring Worksheet — WSJF scoring with Must-Do override, loaded into a monday.com board via CSV import, with a live Formula column added post-import.
Weekly Drift Check — five standing questions attached to a new 15-minute weekly sync, plus a week-over-week tracking grid.
Recalibration Trigger Rule — a sixth standing meeting question, backed by a three-row decision procedure distinguishing minor (update the worksheet) from major (rerun the brief) recalibration.