Impact-Driven Growth Framework

Why Most Growth Frameworks Fall Short

Task-driven frameworks lead to box-ticking, peer comparisons, and destabilised expectations around promotion and reward. They miss the real point. Impact is what matters.

The root problem: Most growth frameworks treat growth as a checklist, saying "At this level, we expect you to do A, B, C." This is uninspiring and easily gamed. Rewards still go to those who create real impact, but the framework doesn't measure that. The result is destabilised triangulation: people compared against peers, expecting promotion simply for completing similar tasks to those at higher levels.

❌ Task-Driven Growth

→"At this level you must do A, B and C"
→Box-ticking and system-gaming behaviour
→Destabilised triangulation vs. peers
→Extrinsic motivation that fades quickly

✓ Impact-Driven Growth

→"What tangible value have you created?"
→Mastery levels instead of task completion
→Evidence, not memory or manager opinion
→Intrinsic motivation that lasts beyond a quarter

The 7 Pillars of Growth

Click on a pillar to explore more.

The Impact Formula

The engine of the entire framework. Impact breaks down into three controllable components. When these combine, they create impact that can be evidenced and amplified.

Opportunities

Context for impact

Situations where impact can be made. Individuals should have autonomy to seek them, while leaders have a responsibility to find and open up more for their people.

Skills

Craft, tech, domain, strategy

Underpinned by knowledge and awareness. Knowing which skills to grow and utilising them in effective, targeted ways enhances the level of impact you can make.

Actions

Behaviours and attitude

Driven by how you show up, how you collaborate, and the actions you plan and follow through with. Behaviour and attitude directly affect the level of impact you make.

Impact

The cherry on top

Finding the opportunities, utilising the skills, and taking the right actions creates evidence-able impact. Visualising it gives purpose, enables better feedback, and powers meaningful performance conversations.

Two perspectives: The formula can be applied proactively (planning what impact you want to make and mapping the opportunities, skills, and actions to get there) or reflectively (reviewing the impact you made, the skills you used, and the evidence to support it). Both modes are valuable, and which to apply depends on whether you're heading into performance review season or setting new objectives.

🏊 The Swimming Analogy

Why Impact is the Cherry on Top

Imagine you set yourself a bold objective: become the fastest person to swim one length of an Olympic pool. You build an OKR around it. You hire a training team, follow a structured regime, adopt a nutrition plan, and hit every KPI. Then you do it. You break the record.

Most people immediately look for extrinsic rewards: the bonus, the pay rise, the promotion. And if those rewards come, they feel good… briefly. But they don't sustain motivation into the next quarter. And if the reward doesn't come, morale drops. Hard.

"YES! You broke the record! AND… your friends and family feel enormous pride. Your training team gains credibility and reputation. The next generation of children who watched are now inspired to swim. Your competitors are motivated to push harder. And you yourself grow, along with your confidence, your reputation, and your sense of what's possible."

This is the part most people skip. But it's the part that actually fuels long-term motivation, growth, and purpose. OKRs measure the key result. Impact measures the real difference made to people. Impact is the cherry on top. When you understand it, you tap into intrinsic motivation, the kind that lasts beyond a quarter, beyond a KPI, and beyond a bonus cycle.

Mastery Levels & the Growth Table

The shared language of growth. Mastery levels blend Bloom's Taxonomy with the Dreyfus Model of Skill Acquisition to show how skills deepen over time, and remove the ambiguity of "what good looks like" at each career stage.

Why mastery levels instead of tasks: The framework isn't built around "to operate at the next level, you must do A, B, and C." Instead, mastery levels define the level of experience and maturity expected at each stage. This removes destabilised triangulation by eliminating peer comparisons based on tasks or checklists, and refocuses growth on learning, which is the foundation of long-term development.

Level 1

Remember

Level 2

Understand

Level 3

Apply

Level 4

Analyse

Level 5

Evaluate

Level 6

Create

Level 7

Evangelise

Based on Bloom's Taxonomy of Learning × Dreyfus Model of Skill Acquisition

How the Growth Table Works

Roles have various levels aligned to experience and maturity (Junior, Mid-level, Senior, Expert, Principal, etc.). These role levels are contextual to your organisation. Each role has competencies relating to the craft, and relating to personal and leadership traits. Each competency has associated skills, contextual to your company's business and technology domain.

The mastery levels are mapped across each role level, per competency, making expectations transparent and scalable. People in the role understand where they need to be in terms of mastery, not what tasks they must complete, but what level of experience and capability is expected at each stage.

Key effect: This structure enables stabilised triangulation, creating space for targeted, meaningful, actionable feedback conversations, rather than "she did the same thing as someone at the next level, so why isn't she promoted?"

Skills Mapping

The diagnostic layer. Skills mapping helps people understand where they currently sit in terms of capability, confidence, and mastery, highlighting the gaps between where they are and where they want to be.

The Tina the Tester model: A single role is made up of multiple layers, including role, team, product, platform, department, and organisation. Each with their own skill clusters: craft skills, tech skills, domain knowledge, system knowledge, strategy and tactical skills, tools and frameworks, environments. Tina may be strong in exploratory testing and risk analysis, but still developing in system-level thinking or domain knowledge. Skills mapping makes this intentionally visible.

Craft Skills

The technical and methodological skills of your discipline, including testing, coding, product thinking, design, data analysis, etc.

Domain Knowledge

Business domain, product context, market, users, regulatory environment. The "why" beneath the "what."

Leadership Skills

Collaboration, communication, decision-making, change agency, driving results. Often what determines readiness for the next level even when craft is strong.

System & Strategy

Organisational systems, strategic context, cross-functional dynamics. The level at which your influence operates and expands.

Growth isn't linear: Someone can be at "Practice" in one skill, "Grow" in another, and "Understand" in a third. Skills mapping helps people avoid the trap of assuming they must be uniformly strong across every competency to progress. It also reveals when you're consistently performing above or below your role level, which informs whether a promotion conversation is grounded in reality.

Impact Planning

The proactive mode of growth. Plan the impact you want to create before you create it, so that when you do, you can evidence it, map it, and request feedback on it with precision.

The shift: This moves growth from reactive "what happened this quarter" thinking to intentional, strategic action. Personal ambition meets organisational value. Instead of waiting for growth to happen, you architect it.

The Impact Planning Canvas

The planned impact canvas is a visual planning tool designed to make intended impact strategically visible. Impact topics are structured into two distinct zones:

Role-Level Impact

Impact directly related to your role responsibilities and core deliverables, your primary domain of contribution.

Org-Level Impact

Impact tied to broader organisational efforts beyond your role. Cross-functional contributions that are equally valid and valuable.

Each impact topic is templated around three dimensions:

What

The impact itself

Who

Who is impacted

How

Through what actions

Tip: If impact feels hard to articulate, start with the task or action you're doing (that's what most people naturally think about), then ask: who am I doing this for? Then: what difference does it make to them? Working through those three questions in order turns a task description into an impact story.

Impact Mapping

A visual map turns abstract contributions into a pattern you can actually see. Instead of a scattered list of achievements, you get a structured picture of where your energy goes, where your strengths cluster, and where your influence is growing.

Once you've chosen the quadrant, choose the ring that reflects the scale of impact, and how far your influence reached. Place each impact item at the intersection of its quadrant segment and its ring. Over time, you'll see patterns: where your strengths cluster, whether your influence is expanding outward, and where you want to stretch next.

Knowledge Value

Contextual to each role. For engineers and testers: Development & Tech, DevOps, Testing & Quality, and Agility & Flow. For Product Managers: Product Strategy, Planning, Experimentation, etc. The segments are shaped by your craft and your organisation.

Business Value

Direct contributions to business outcomes, impacting revenue, client satisfaction, user experience, or commercial success. Contextual to the organisation: different business domains or client engagements may have their own segments here.

Giving Back

Impact through supporting others, including mentoring, coaching, teaching, and community involvement. Split between internal communities (within the organisation) and external communities (industry, open source, conferences, etc.).

Avoiding Waste

Impact relating to efficiency, whether proactively avoiding waste or reactively reducing it. Catching issues early, removing blockers, preventing duplication. This quadrant surfaces the "invisible" impact that rarely makes it into traditional performance conversations.

Evidencing Impact

Turning work into a clear, traceable story about value. Evidence captures what was done, how it was done, who it affected, and what changed as a result. Without deliberate evidence capture, impact disappears into the noise of delivery.

Evidence turns a claim into a fact. When you evidence your impact, you create a defensible, compelling narrative of your value. You're no longer relying on memory, luck, or someone else noticing your work. You're building a body of proof that shows how you think, how you operate, and how you create change.

Field	What to capture	Why it matters
1. The Impact	What was the change you created? Short, specific, outcome-focused. This is your post-it note from the Impact Planning canvas with added clarity.	The headline. Everything else supports this statement.
2. Competencies & Skills Used	Map the impact to the mastery levels and competencies you demonstrated, both craft and leadership/personal.	Connects impact to development. Shows how you operated, not just what you did.
3. Your Role	Were you the Instigator (originated the idea), Owner (drove it end-to-end), or Collaborator (meaningful contributor)?	Prevents over- or under-claiming. Critical in cross-functional work.
4. Who Was Impacted	The specific people affected by your work. These are your targets for 3rd-order feedback requests.	Turns generic requests into specific, high-value feedback conversations.
5. Scale of Impact	Which ring from the impact map? Personal, Team, Group, Company, or Industry?	Ties directly to seniority expectations. Shows how your influence is growing over time.
6. Supporting Links	Code repos, PRs, release notes, dashboards, tickets, presentations, feedback messages, and before/after snapshots. Anything that shows what you did.	The grounding layer. Gives others something concrete to point to and verify.

Feedback on Impact

Not generic feedback. Not feedback on tasks. Feedback targeted at the specific, concrete impact you made on real people, which is a fundamentally different and more valuable signal for growth.

1st Order Feedback

The Person

Focuses on: You

"Dan is a great communicator and really easy to work with."

Warm but vague. Hard to act on. Doesn't tell you what to grow.

2nd Order Feedback

The Task

Focuses on: What you did

"The testing strategy Dan ran was thorough and caught issues early."

Better. Describes the work. Still doesn't connect to real-world value.

3rd Order Feedback

The Impact

Focuses on: What you accomplished

"Because of the testing strategy Dan ran, we shipped without a critical defect for the first time in three releases, which restored client confidence and unblocked the contract renewal."

This is the signal that fuels growth, validates evidence, and powers performance conversations.

The feedback loop: Plan impact → Make impact → Evidence it → Request 3rd-order feedback from those you impacted → Use that feedback to validate, deepen, and amplify. Over time, this creates a powerful rhythm where the people affected by your work help you articulate its value, and where feedback becomes transformative rather than performative.

The Growth Runbook

Eight steps to put the framework into practice. Run the full cycle each quarter. Use individual steps between cycles as needed, particularly the evidence and feedback steps, which benefit from more frequent practice.

Clarify

Define What Impact Means in Your Context

Before planning or evidencing impact, you need a shared understanding of what it means in your role, at your organisation. Impact for a software engineer looks different from impact for a product manager or a team lead, and it should.

Review your organisation's OKRs or KPIs. These are the frame within which your impact should sit
Talk to your manager: "What impact are you hoping I have this quarter?" Their answer is the starting point.
Identify 3-5 areas where you have the greatest potential to create value, by role, by project, and by personal aspiration
Distinguish between role-level impact (your core responsibilities) and org-level impact (broader contributions)
Output: a shared, aligned definition of the impact you're aiming to create this quarter

Baseline

Map Your Current Skills Against the Growth Table

Run an honest skills mapping session. The goal is to get a clear, accurate view of where you are so you can be intentional about where to invest, not to paint a flattering picture.

Access your organisation's growth table (or role expectations document)
Rate yourself against each competency using the mastery levels (Remember → Evangelise)
Note where you're at your role level, above it, or below it
Pay special attention to leadership and personal competencies, as these are often the hidden readiness signals for progression
Share your self-assessment with your manager and invite their perspective. The gaps between your view and theirs are especially informative.
Output: a completed skills map showing current mastery levels across craft and leadership competencies

Plan

Build Your Impact Planning Canvas

Populate your impact planning canvas with the specific impact topics you intend to work on this quarter. For each one, define what the impact is, who will be affected, and what actions will create it.

Start with the top 3-5 impact areas you identified in Step 1
For each, write: "I want to impact [who] by [doing what], resulting in [what change]"
Identify the skills you'll need to draw on or develop to create each impact
Check that your planned impacts connect to organisational OKRs or strategic priorities
Flag which impacts will be role-level (your direct responsibilities) and which are org-level (cross-functional or community contributions)
Output: a populated impact planning canvas with at least 3 specific impact topics, each with a who, what, and how

Execute

Make the Impact, Deliberately

This is the doing. But it's intentional doing, guided by your plan, with awareness of the skills you're applying and the people you're affecting. The difference between reactive delivery and impact-driven execution is the level of intentionality.

Keep your impact planning canvas visible. Review it weekly, not just quarterly.
As you work, notice when you're operating on a planned impact topic and make a note
Be conscious of which mastery level you're operating at, and when you're stretching beyond it
Look for opportunities beyond your immediate role: mentoring moments, cross-team problems, community contributions
When you complete something that created real impact, capture a rough note immediately, before the details fade
Output: real impact created, with rough notes ready to be formalised into evidence entries

Map

Place Your Impact on the Map

For each impact you've created, place it on your impact map, choosing the right quadrant (Knowledge Value, Business Value, Giving Back, Avoiding Waste) and the right ring (Personal, Team, Group, Company, Industry).

Review your rough notes from Step 4 and formally place each item on the impact map
Look for patterns: are you clustering in one quadrant? At one ring level? These are your strengths and your blind spots.
Identify any quadrants or rings you haven't reached yet. These are your next stretch opportunities.
If your influence is consistently Team-level and you want to progress, look for Group or Company-level contributions to target next quarter
Output: a populated impact map that visually tells the story of your contributions this quarter

Evidence

Document Each Impact Using the Six Fields

For each item on your impact map, complete an evidence entry using the six-field structure. This is the foundation of any meaningful performance conversation, promotion case, or interview answer.

For each impact item: write what the change was, which competencies you used, your role (instigator/owner/collaborator), who was impacted, the scale, and supporting links
Be specific and concrete. "Improved delivery speed" is not evidence; "reduced deployment cycle time from 3 days to 4 hours through introducing automated release gates" is
Store your evidence somewhere durable and accessible, such as a personal doc, Notion page, or dedicated tool
Review your evidence entries before performance reviews, not during them. You should never be scrambling for examples under pressure.
Output: a structured evidence table with at least one complete entry per planned impact topic

Feedback

Request 3rd-Order Feedback on Specific Impact

Don't ask generically. Use your evidence entries to target feedback requests at the specific people your work impacted, and ask them about the impact they felt, not about you as a person or about the tasks you did.

Identify the people listed in field 4 (who was impacted) of each evidence entry
Reach out with a specific, framed request: "I worked on [X] and I think it affected [you/your team] in [these ways]. I'd really value your perspective on the difference it made."
Collect feedback through whatever channel is natural, whether Slack, email, 1:1, or an HR tool
Store feedback directly alongside the evidence it relates to. The connection between evidence and feedback is the most powerful part of this system
Output: at least one piece of 3rd-order feedback per major impact item, stored alongside the evidence entry

Review

Quarterly Reset: Plan the Next Impact

Close the loop. Review what you planned, what you made happen, what you evidenced, and what feedback you received. Then set your intentions for the next quarter, with the benefit of a clear picture of where your impact has been.

Review your impact planning canvas: what did you complete, what didn't move, and why?
Review your impact map: what patterns are emerging? Are you stretching into new quadrants or rings?
Re-run your skills mapping. What has changed since last quarter? What mastery levels have shifted?
Prepare your evidence and feedback for any upcoming performance reviews
Set new impact planning topics for the next quarter, informed by your company's updated OKRs and your personal growth priorities
Output: a fresh impact planning canvas, updated skills map, and a clear sense of where to focus next

Growth Readiness Self-Assessment

How actively are you practising each component of the framework? Rate yourself honestly. This isn't about where you want to be, it's about where you are today. Track the composite score quarterly; a rising trend is the signal that matters.

Growth Readiness Check

Impact Formula

In progress

Mastery Levels

In progress

Skills Mapping

In progress

Impact Planning

In progress

Impact Mapping

In progress

Evidencing

In progress

Feedback

In progress

3.0

UNAWAREAWAREPRACTISINGCONSISTENTFLUENT

Unaware

1.0–1.9. Framework not yet in use. Start with the Impact Formula and one evidence entry.

Aware

2.0–2.9. You understand the framework but aren't consistently applying it. Pick one component and practise it daily.

Practising

3.0–3.9. Some components are active. Build consistency. The runbook is your guide.

Consistent

4.0–4.4. All seven components are in active use. You're generating a compounding picture of your impact.

Fluent

4.5–5.0. Impact-driven growth is your natural mode. You plan, map, evidence, and get feedback without prompting.

Growth Readiness Formula

Score = (Formula + Mastery + Skills + Planning + Mapping + Evidence + Feedback) ÷ 7

Each component rated 1–5. Track quarterly. A rising score reflects increasing intentionality, which is itself the most reliable predictor of sustained growth.

Quick Wins to Start Today

Before you run the full runbook, build momentum. Each of these takes minutes to an hour and starts a habit that the framework can then build on.

Write down one thing you did this week and who it impacted

Not the task. The change. "I did X" vs "I helped Y achieve Z." That shift in framing is the beginning of impact thinking.

Ask your manager: "What impact are you hoping I have this quarter?"

Their answer is your starting point for impact planning. If they can't answer it, that's equally important information and a good conversation to have.

Pick one skill and deliberately apply it today

Not to practise it in the abstract, but to create a specific impact with it. Notice who benefits and how. That's your first evidence note.

Find one opportunity to make impact beyond your immediate team

A cross-team problem you could help with, a community post you could write, a colleague you could mentor. Org-level impact often starts with noticing it's possible.

Write your first evidence entry, even a rough draft

Six fields: the impact, the competencies, your role, who was affected, the scale, and a link. Five minutes now is worth an hour of scrambling before your next performance review.

Ask someone for 3rd-order feedback on a specific impact

"I worked on X and I think it helped you in Y way. Did it? What was the difference it made?" That question will get you better feedback than any generic end-of-year request.

Sketch your impact map, even rough

Draw four quadrants and place three things you've done this month. You'll immediately see patterns that you can't see in a list. It doesn't have to be perfect, it just has to be visible.

Identify one area where you're consistently operating above your role level

Name it. That's evidence of progression. Now decide: should you be seeking a growth conversation about it, or first collect more evidence and feedback to make the case?

The Golden Rule

Don't wait for growth to happen. Architect it.

When you understand the landscape of your impact, you can choose where to invest your energy. You can plan the kind of impact you want to make, seek out the opportunities that align with it, and deliberately build the skills that will get you there. Instead of drifting through tasks and waiting to be noticed, you become intentional, directional, and empowered, shaping a career defined by the impact you choose to create. Impact is what gives your work meaning. Impact is what connects your effort to something bigger. Impact is the cherry on top.

00 Why Most Growth Frameworks Fall Short

01 The 7 Pillars of Growth

The Impact Formula

Mastery Levels & the Growth Table

How the Growth Table Works

Skills Mapping

Impact Planning

The Impact Planning Canvas

Impact Mapping

Knowledge Value

Business Value

Giving Back

Avoiding Waste

Evidencing Impact

Feedback on Impact

02 The Growth Runbook

Clarify

Define What Impact Means in Your Context

Baseline

Map Your Current Skills Against the Growth Table

Plan

Build Your Impact Planning Canvas

Execute

Make the Impact, Deliberately

Map

Place Your Impact on the Map

Evidence

Document Each Impact Using the Six Fields

Feedback

Request 3rd-Order Feedback on Specific Impact

Review

Quarterly Reset: Plan the Next Impact

03 Growth Readiness Self-Assessment

Growth Readiness Check

04 Quick Wins to Start Today

Write down one thing you did this week and who it impacted

Ask your manager: "What impact are you hoping I have this quarter?"

Pick one skill and deliberately apply it today

Find one opportunity to make impact beyond your immediate team

Write your first evidence entry, even a rough draft

Ask someone for 3rd-order feedback on a specific impact

Sketch your impact map, even rough

Identify one area where you're consistently operating above your role level

∞ The Golden Rule

Why Most Growth Frameworks Fall Short

The 7 Pillars of Growth

The Growth Runbook

Growth Readiness Self-Assessment

Quick Wins to Start Today

The Golden Rule