How to use the IMPACT Framework.
The IMPACT Framework defines six stages that connect intention to outcome: Identify, Motivate, Plan, Act, Check, Transform. The framework page explains what each stage is. This guide explains how to apply it — with practical steps, common mistakes, and worked examples at the individual, team, and organisational level.
Whether you’re using IMPACT to structure a personal quarterly goal or to cascade company strategy through a 500-person organisation, the mechanics are the same. The depth changes, the scope changes, but the sequence is constant. Start here if you want to move from understanding the framework to using it.
I — Identify
Identify: define the outcome that matters
What it means. Identify is the act of selecting the one outcome that will create the most meaningful progress. Not a list of everything you want to achieve. Not a backlog of projects. A single, specific outcome that, if accomplished, would represent genuine strategic advancement. At the individual level, this might be a career milestone or a performance outcome. At the organisational level, it’s the strategic objective that drives the most enterprise value.
How to do it.
1. Start with the question: “If I could only accomplish one thing this quarter, what would move the needle most?”
2. Force a constraint — no more than three objectives at any level. Two is better. One is ideal.
3. State the outcome in terms of a result, not an activity. “Increase retention to 92 %” not “Improve the onboarding programme.”
4. Test it: does this outcome connect to the objective above it in the cascade? If there is no visible connection, you are optimising locally.
Common mistakes. The most frequent error is identifying too many goals simultaneously. Breadth feels productive but produces dilution. The second mistake is stating activities instead of outcomes — “launch the new product” is an activity; “achieve £500k ARR from the new product” is an outcome. The third is choosing goals that are comfortable rather than consequential. If the goal can be achieved without changing any current behaviour, it is not strategic.
Worked example. Individual: A marketing manager identifies “generate 200 qualified leads per month from content by end of Q2” — specific, outcome-oriented, and connected to the company’s growth objective. Organisation: An enterprise SaaS company identifies “reduce net revenue churn to below 5 % annually” as their single most consequential objective, cascading from the board’s mandate to protect recurring revenue.
M — Motivate
Motivate: connect the goal to personal and collective meaning
What it means. Motivate is the stage where the goal acquires emotional and intellectual significance. A goal that is strategically correct but personally meaningless will be deprioritised the moment competing demands arise. This stage asks: why does this goal matter to the person or team who must deliver it? The answer must resonate at a level deeper than “because leadership said so.”
How to do it.
1. Articulate the personal benefit of achieving the goal — skill development, career progression, recognition, or intrinsic satisfaction.
2. Make the strategic connection visible: show how the individual or team goal feeds the company objective above it in the cascade.
3. Name the cost of not achieving the goal. Loss aversion is a powerful motivator — what is at risk if this goal is missed?
4. Share the goal publicly within the team. Social commitment creates accountability that private intention does not.
Common mistakes. Skipping this stage entirely is the most common error. Organisations set goals and move straight to planning, assuming motivation is implicit. It is not. The second mistake is relying on extrinsic incentives (bonuses, targets) without connecting the goal to intrinsic meaning. Extrinsic motivation produces compliance. Intrinsic motivation produces discretionary effort.
Worked example. Individual: The marketing manager connects the 200-lead target to their ambition to be promoted to Head of Content by year-end — demonstrating measurable commercial impact is the missing evidence in their promotion case. Organisation: The churn reduction goal is framed not as a financial metric but as a customer success mission: “Every renewal represents a customer whose work is better because of us.”
P — Plan
Plan: decompose the goal into milestones and daily actions
What it means. Plan is where the goal is broken into a sequenced series of milestones, and each milestone is decomposed into the specific daily actions required to achieve it. This is the structural bridge between a quarterly ambition and a Tuesday morning. Without this decomposition, the goal exists at a level of abstraction too high for daily execution.
How to do it.
1. Break the goal into 3–5 milestones, each representing a meaningful checkpoint. Milestones should be binary: achieved or not achieved.
2. For each milestone, identify the 5–10 specific actions required to reach it.
3. Sequence the actions by dependency and priority. What must happen first? What can be parallelised?
4. Assign time estimates. If a single action takes more than two hours, decompose it further.
5. Connect each day’s plan to the next milestone. The daily planning ritual should surface the most impactful actions for today based on the current milestone’s requirements.
Common mistakes. Planning at the wrong altitude: milestones that are too vague (“make progress on content”) or actions that are too granular (“open Google Docs”). The plan should sit at the level of meaningful, completable work units — tasks a professional can accomplish in a focused session. The second mistake is building a static plan. Plans must adapt as context changes. A plan that was created in January and never revised by March is a historical artefact, not a guide for action.
Worked example. Individual: The marketing manager decomposes the 200-lead target into three milestones: (1) publish 12 SEO-optimised articles by end of month 1, (2) build a lead magnet with a 15 % conversion rate by end of month 2, (3) scale paid distribution to achieve steady-state volume by end of month 3. Each milestone has sequenced daily actions. Organisation: The churn reduction goal is decomposed into milestones across teams: Customer Success owns onboarding NPS, Product owns feature adoption metrics, Support owns time-to-resolution targets.
A — Act
Act: execute daily through micro-commitments
What it means. Act is the daily execution stage — where the plan meets reality. This is not simply “do the work.” It is the deliberate practice of starting each day by committing to specific, goal-aligned actions and completing them. The difference between Act and unstructured work is intentionality: each action is consciously connected to a milestone, which is connected to the goal, which is connected to the strategy.
How to do it.
1. Begin each day with a planning ritual: review your active milestone, select 2–3 actions to complete today, and commit to them explicitly.
2. Keep actions small enough to complete in a single session. Micro-commitments sustain momentum; large tasks create procrastination.
3. Track completion. The act of marking an action as done provides immediate reward and sustains the habit loop.
4. Protect execution time. Block calendar time for goal-aligned work — it will not survive if it competes with reactive tasks on equal footing.
Common mistakes. Letting the day run you instead of running the day. Without an explicit morning planning ritual, the first email or Slack message determines the day’s priorities. The second mistake is action inflation — committing to ten actions per day and completing three. Under-commitment and over-delivery is always better than the reverse. The third mistake is disconnecting actions from their goal context. If you cannot articulate which milestone a given action serves, the action may not be worth doing.
Worked example. Individual: The marketing manager’s Tuesday morning plan: (1) draft the keyword brief for article 7, (2) review the first draft of article 5 from the freelancer, (3) analyse last week’s lead magnet conversion data. Three actions, each connected to milestone 1 or 2. Organisation: Across the enterprise, every individual’s daily plan is visible to their team — creating a real-time picture of whether the organisation’s strategic goals are being executed or merely documented.
C — Check
Check: reflect, measure, and adjust
What it means. Check is the reflective stage — the structured pause where progress is measured against the plan, and the plan is adjusted based on what’s actually happening. This is not a performance review. It is a learning loop: what worked, what didn’t, what needs to change. The Check stage prevents the plan from becoming outdated and prevents effort from continuing in an unproductive direction.
How to do it.
1. Conduct a weekly reflection: review the past week’s actions, completion rate, and milestone progress.
2. Ask three questions: What moved the needle? What was wasted effort? What do I need to change next week?
3. Update the plan. If a milestone is ahead of schedule, accelerate the next. If it’s behind, diagnose whether the problem is effort (not enough actions) or approach (wrong actions).
4. At the team level, surface patterns: are certain goals consistently deprioritised? Is the team’s collective effort aligned with the highest-priority objectives?
5. Share reflections. Individual learning becomes organisational learning only when it is communicated.
Common mistakes. Treating Check as a reporting exercise rather than a learning exercise. If the reflection is a status update written for a manager, it optimises for perception. If it is a private learning moment, it optimises for performance. The second mistake is checking too infrequently — a quarterly review cannot course-correct a daily execution problem. Weekly is the minimum cadence; daily check-ins on action completion provide even tighter feedback.
Worked example. Individual: At the end of week 4, the marketing manager reflects: articles are on track (7 of 12 published), but lead magnet conversion is at 8 %, well below the 15 % target. The plan is adjusted: week 5 will focus on A/B testing the lead magnet landing page rather than continuing to publish articles at the current pace. Organisation: The weekly leadership check-in reveals that Customer Success has strong onboarding NPS but Product’s feature adoption metric is flat. Resource is reallocated to a guided onboarding flow that the Check stage surfaced as missing.
T — Transform
Transform: convert outcomes into lasting capability
What it means. Transform is the stage most frameworks omit. It asks: now that you’ve achieved (or partially achieved) the goal, what has permanently changed? What capability, habit, or structural improvement persists beyond the goal’s completion? Without the Transform stage, goal achievement is episodic — each cycle starts from scratch. With it, each cycle builds on the last, creating compounding organisational capability.
How to do it.
1. Identify what the goal cycle taught you that you did not know before. Codify it — a process improvement, a new skill, a structural change to how the team works.
2. Ask: what habit or ritual was formed during this cycle that should persist? Not every goal produces a lasting habit, but the best ones do.
3. Share the transformation. What one team learned should be available to every team. Document the insight, present it, add it to the organisational playbook.
4. Set the next goal based on the new capability. The Transform stage is the bridge between cycles — the outcome of one cycle informs the Identify stage of the next.
Common mistakes. Finishing a goal and immediately moving to the next without pausing to extract the learning. The urgency to move on is understandable but costly: the organisation fails to capture the capability improvement that the effort produced. The second mistake is treating transformation as an individual responsibility. The most valuable transformations are structural — a new process, a new ritual, a new way of working that benefits everyone, not just the person who discovered it.
Worked example. Individual: The marketing manager achieved 180 of the 200-lead target. The Transform insight: long-form SEO content outperformed short-form by 4× on lead generation. This insight reshapes next quarter’s content strategy permanently — it is not a one-cycle finding but a lasting capability shift. Organisation: The churn reduction initiative achieved a drop from 8 % to 5.5 %. The Transform output is a structured onboarding process, a health-score dashboard, and a weekly customer review ritual that persists beyond the goal’s completion. The company is structurally different from when the cycle began.
Individual level
Applying IMPACT at the individual level
At the individual level, IMPACT functions as a personal operating system for goal execution. The full cycle for a single person might look like this:
A product designer wants to transition into a design leadership role within 12 months. Identify: lead the design for the company’s highest-revenue product redesign. Motivate: this project is the most visible design initiative in the company; leading it demonstrates exactly the capability the promotion requires. Plan: three milestones — complete the design audit by end of month 1, deliver the prototype by end of month 2, ship v1 by end of month 3. Each milestone decomposes into daily actions: user interviews, wireframes, design reviews. Act: every morning, the designer commits to 2–3 specific actions connected to the current milestone. Check: weekly reflection — the prototype milestone is behind schedule because stakeholder feedback is taking longer than expected. The plan is adjusted: stakeholder reviews are moved from async to synchronous, with a 48-hour response deadline. Transform: the product ships, the designer is promoted, and the structured stakeholder review process they created becomes the department’s standard.
Notice the cycle’s hallmark: the individual finishes with more capability than they started with. The Transform stage ensures that the next IMPACT cycle begins from a higher baseline.
Team level
Applying IMPACT at the team level
At the team level, IMPACT coordinates collective effort around a shared objective. The team’s IMPACT cycle cascades from the organisational level and creates the context for each individual’s cycle.
A customer success team of twelve is asked to reduce time-to-value for new customers from 45 days to 20 days. Identify: the single outcome is clear — halve time-to-value. Motivate: the team lead frames the goal around customer impact: the faster customers reach value, the more successful they are, and the more rewarding the work becomes. The team also connects it to the company’s churn-reduction goal, making their contribution to the wider strategy visible. Plan: three milestones across the team — (1) redesign the onboarding playbook, (2) implement automated health scoring, (3) launch proactive intervention triggers. Individual team members own specific milestones. Act: every morning, each team member commits to goal-linked actions. The team’s plan is visible to all members, creating collective awareness of who is working on what. Check: a weekly team reflection surfaces that automated health scoring is ahead of schedule but the onboarding playbook rewrite is stalled because no one owns the content review step. The plan is adjusted: a specific owner is assigned, and the deadline is extended by one week. Transform: time-to-value drops to 22 days. The lasting transformation: the team now operates with a structured onboarding playbook, automated health scores, and a weekly review ritual that did not exist before the cycle began.
Organisation level
Applying IMPACT at the organisation level
At the organisational level, IMPACT provides the cascade architecture that connects board-level strategy to individual daily execution. The organisation’s IMPACT cycle sets the context for every team and individual below.
A 300-person technology company sets a goal to achieve £20M ARR by year-end. Identify: one number, one year. Motivate: the CEO frames the goal as the milestone that unlocks Series B funding, enabling the company to hire into three new markets and giving every employee equity appreciation. The motivation is both collective (company growth) and personal (equity value). Plan: the target decomposes across departments — Sales owns £12M in new revenue, Customer Success owns £8M in renewals, Product owns the feature set required to win in the target segments. Each department decomposes further into team and individual milestones. Act: across 300 people, daily planning generates thousands of goal-aligned actions per week. The AI engine personalises each individual’s daily plan while maintaining visibility at every layer of the cascade. Check: at the monthly executive review, the Check stage reveals that Sales is ahead but renewals are tracking 10 % below plan. Resource is shifted: two senior Customer Success hires are accelerated, and Product reprioritises a retention feature. Transform: the company hits £18.5M — short of target but fundamentally transformed. The cascade architecture, the daily planning ritual, the weekly Check cadence, and the cross-functional reallocation process all persist as permanent organisational capability.
The power of IMPACT at the organisational level is the cascade: every individual’s Tuesday morning actions connect, through milestones and goals, to the board’s strategic objective. The framework does not just set goals. It builds the execution system that delivers them.
With OKRs
IMPACT and OKRs — how they work together
OKRs (Objectives and Key Results) and the IMPACT Framework are not competing models. OKRs define what to achieve and how to measure whether you’ve achieved it. IMPACT defines how to execute. They are complementary layers of the same system.
In practice, OKRs map onto the first two stages of IMPACT. The Objective is the output of Identify. The Key Results are the measurable milestones generated during Plan. What OKRs typically lack is the execution methodology: how are Key Results achieved day-to-day? IMPACT fills this gap with the Act, Check, and Transform stages — the daily planning rituals, weekly reflections, and learning loops that turn Key Results from static metrics into actively pursued outcomes.
OKRs define the what and the measure. IMPACT defines the how. Organisations that use both get the structured goal definition of OKRs with the daily execution engine of IMPACT.
If your organisation already uses OKRs, IMPACT wraps around them rather than replacing them. The Objective becomes the Identify stage. Motivation is layered on top (most OKR implementations skip this). Key Results decompose into milestones during Plan. Act, Check, and Transform provide the execution engine that OKRs, by design, leave to the team’s discretion. The result is a more complete system than OKRs or SMART goals alone — one that includes not just goal definition but goal execution.
FAQ
Frequently asked questions
Put IMPACT into practice.
Book a 30-minute demo. We’ll show you how Goalite operationalises the IMPACT Framework — daily planning, milestone tracking, AI coaching, and the Transform stage that compounds learning across cycles.