Step 2: Cross-reference against your flagged objectives above.
Step 3: Write one objective per chunk — verb + outcome, no targets.
Step 4: Add 2–3 key results per objective — symbol · name · date · target.
Most leadership teams already know what they want to achieve. The challenge is not intent — it is translating that intent into consistent execution. This session builds the operating structure that makes that translation possible.
| Organisation | Session | Date | Your access | |
|---|---|---|---|---|
MB Maple Bridge |
Product division refresh | Apr 22 | Facilitator | |
NC NorthCo Ltd |
Leadership team Q2 | Apr 18 | Invite pending | |
PV PineView Health |
Executive team annual | May 2 | No access |
Most leadership teams already know what they want to achieve. The challenge is not intent — it is translating that intent into consistent execution. This session builds the operating structure that makes that translation possible.
| Organisation | Session | Date | Your access | |
|---|---|---|---|---|
MB Maple Bridge |
Product division refresh | Apr 22 | Facilitator | |
NC NorthCo Ltd |
Leadership team Q2 | Apr 18 | Invite pending | |
PV PineView Health |
Executive team annual | May 2 | No access |
Modules included in this workshop. Additional modules can be unlocked — get in touch with Greg to discuss.
| Session | Access level | Granted | Expires | |
|---|---|---|---|---|
| Product division refresh | Facilitator | Apr 14, 2026 | May 22, 2026 | |
| Engineering team alignment | No access | — | — | |
| Leadership offsite 2025 | No access | — | — |
| Participant | Session | Access | Last active | |
|---|---|---|---|---|
MP Morgan Patel | Product division refresh | Participant | Apr 14 | |
SO Sam Okafor | Product division refresh | Participant | Apr 14 | |
TN Taylor Nguyen Pending | Product division refresh | Participant | — |
Complete with the client leader before the workshop. Work through the agenda, review and agree the draft strategy map, then capture the design decisions that will shape the session.
Map out the sessions, dates and module assignments. Goals describe what you are trying to achieve — outputs are what you will produce. These are different things.
| Session | Date | Duration | Who | Modules | Goal (what we want to achieve) | Output (what we will produce) |
|---|
Present the draft map to the client leader. This was built from their source materials — it is a starting point for conversation, not a final answer. Edit live as changes are agreed.
Work through these together. Structural decisions are wired into the platform — they will change how the workshop runs. Informational decisions are recorded for reference.
Configure before the workshop begins. Module selection and session type are locked for facilitators — changes can only be made here.
Select the type of workshop you are running. This configures the navigation and available modules.
Strategy map and workshop output are always included. Select additional modules for this session.
Name and what they represent — feeds into contribution matrix and OKR writing.
Present the draft map to the group. Edit live as changes are agreed. Focus points come in the next step.
Click any objective to edit. Arrows show the upward causal flow — Enablers → Internal → Customer → Financial.
A distribution of priority of effort — not a ranking of importance. Distribute 100% of focus across the map in three stages.
Agree the metric that signals early whether each objective is on track. Symbol, name, target, date. Highest-focus objectives first.
For each objective, define 5–7 success factors and score each one out of 10 as a group. The aggregate score determines the objective's current status.
These apply to all objectives. A score of 10 on every factor = 100%. Adjust the thresholds to match your organisation's expectations.
Score each participant's impact on each objective (0–5). Black means this person should write an OKR here.
Learn the framework, practise with a group example, then write individual OKRs.
Pick a volunteer. Their flagged objectives appear automatically — this becomes their first real OKR.
Select a participant to open their writing workspace.
All OKRs written this session. Share and discuss as a group.
Objectives flagged for each participant based on their contribution scores and focus weights.
Group performance scores against each objective — gap = focus weight × (5 − process capability score).
Capture the key initiatives that will move your strategy forward. Link each one to the objectives it supports — this becomes part of your dashboard.
Work through the What / So what / Now what framework as a group. Start with the example, then practise with a real objective. Add rounds until the format feels natural.
Each person selects one of their objectives and writes their What / So what / Now what. This becomes the agenda for your first practice meeting.
Build the agenda for your first practice meeting using the What / So what / Now what entries written by the group. Assign roles, select items, set the time — then run it.
Assign roles before the meeting starts. Decision authority must be clear before any discussion begins.
Choose which participants bring items to this practice meeting. Not everyone needs airtime — this is how a real performance meeting works. Selected items get time allocated; others are noted as reviewed.
No actions yet — add during the meeting.
No parking lot items yet.
Capture the commitments made in the room. These go on the performance meeting charter.
What makes something worth including in selected performance items? Agree the rules now so the facilitator can prepare the agenda each month without a separate conversation.
Participants carry over from session setup. Adjust if needed for this exercise — for example, bringing in someone closer to the work to score specific areas. Changes here do not affect the original session.
Name and what they represent — each person scores the performance of processes within their domain.
Read-only. Return to session setup if a change to the strategy map is needed.
The resource score (1–10) is relative — a project scoring 10 requires roughly twice the resources of one scoring 5.
Score how well each participant's domain processes are currently performing against each objective (0–5). Leave blank where there is no meaningful relationship. The contribution score from the previous matrix is shown above each input — high contribution, low performance, high weight = strategic risk.
Score each project's impact on each objective (0–5). Leave blank where there is no meaningful relationship. Return on resources is calculated automatically — total weighted impact divided by the resource score.
A quarterly signal tool — identify where the strategy is under-resourced, which projects deliver the most return, and where to focus.
A quick group assessment of whether your current processes are strong enough to deliver each strategic objective. Score as a group — the conversation matters as much as the number. The gap chart updates as you score.