The Latest In The Content Marketing World

Follow our blog for expert takes, insider tips, and up-to-date news about the dynamic content marketing industry.

The Impact Stack. 5 Layers That Turn “Good Work” Into Credible, Shareable, Measurable Change

by | Feb 13, 2026 | blog

For CSR teams, foundations, and impact-driven organisations, “impact” is not just an intention; it is a claim you must substantiate.

And in 2026, claims get challenged. By employees, boards, partners, communities, customers, and the public. This isn’t because people don’t want to believe in good work, but because they’ve seen too many stories that are either:

  1. Inspiration without evidence (it reads like a campaign), or
  2. Evidence without narrative (it reads like a report nobody finishes).

I’ve reflected on this a lot while working on Microsoft’s Code; Without Barriers over the last couple of years, supporting the programme’s communications, developing content, and leading mentoring circles.

I was honoured to collaborate with Microsoft on their Code; Without Barriers initiative.

Crafting impact stories in this space has reinforced a belief I now hold strongly: Impact storytelling is not a comms add-on. It’s a cross-functional discipline. Programmes + measurement + community voice + narrative craft.

Here’s a framework I use to help CSR teams, Foundations, and impact organisations tell credible, compelling stories. I call it the Impact Stack: five layers that must exist simultaneously. Missing one makes the story fluffy, fragile, or forgettable.

Let’s go!

Layer 1. Point of view. Think purpose, boundaries and who it’s for

Most impact narratives start with values: “We care about inclusion.” That’s nice. But it’s not enough.

A strong point of view answers:

  • What gap are you addressing? (name the problem plainly)
  • Who is it for? (be specific about the community)
  • Where are your boundaries? (what you won’t claim, or won’t do)

For Code; Without Barriers, the gap is explicit: closing the gender gap in tech. The audience is clear: women coders, developers, and technical talent. That clarity matters; it prevents the story from becoming “we’re for everyone”, which usually becomes “you’re for no one in particular”.

For Foundations, this layer is just as important: it protects you from becoming a catalogue of grants and instead positions you as an organisation with a clear thesis and a distinct role in the ecosystem.

Side note: Some teams often avoid a point of view because it can feel political. But neutrality is also a stance, and it often reads as vague.

Layer 2. Strategy. The mechanism of how change happens

Once the “why” is clear, the story must make the “how” legible.

Strategy is not your list of activities. It’s your logic of change; the mechanism you believe will move the needle. For CSR leaders, programme teams, and Foundation execs, this layer aligns internal stakeholders (and prevents comms from having to “interpret” the programme after the fact).

A good strategy layer articulates:

  • The mechanism in plain language (e.g., skills, confidence, networks and opportunity)
  • The choices (why this approach, not another)
  • The assumptions (so they can be tested, not hidden)

With CWB, what stood out is how the program blends levers: capability-building, community, visibility, and opportunity. It does this rather than assuming a single intervention can do it all.

This is where Foundations can create clarity: naming how you believe change happens makes it easier to choose partners, explain decisions, and communicate priorities without lengthy explanations.

Side note: If you can’t explain your mechanism in one minute, your programme isn’t too complex; your narrative is.

Layer 3. Proof of work (outputs, delivered with pride)

Outputs get treated like the “less important” part of impact. But it’s the outputs that make your story real.

This is where you can confidently say, “Here’s what we shipped”, “Here’s what we delivered”, “Here’s what happened because we showed up”.

Best practices for the proof-of-work layer:

  • Make outputs sharp and contextual (not a dumping ground for everything you did)
  • Tie outputs to why they matter (bridge to outcomes)
  • Prioritise consistency over splash

When I shared on LinkedIn that our first Code; Without Barriers impact story was out and that it was only the beginning, it wasn’t just an update. It signalled a system: a series, a cadence, and a commitment to amplify journeys and outcomes over time.

Similarly, completing mentoring circles more than once isn’t vanity. It shows sustained engagement and a learning loop. Mentoring, taken seriously, is more than giving back; it’s building capability and networks in action.

Layer 4: Outcomes and attribution. What changed, and what you can honestly claim

This is where trust is either earned or lost.

Outcomes should answer: what changed for people, communities, or systems as a result of the work (and over what timeframe)? Attribution answers: what part can we responsibly claim, versus what we contributed to alongside many other factors?

Best practices:

  • Use a mix of evidence (quantitative and qualitative)
  • Separate signal vs noise (what changed vs what happened)
  • Be explicit about contribution vs attribution

Done well, impact stories go beyond inspiration. They amplify voices, highlight journeys, and link lived experience to credible change. Shared across communities, these stories can spark conversations and open doors for others—but you must track them (even lightly) to make such claims.

A simple “lightweight” evidence set could include:

  • Participation and progression indicators
  • Qualitative themes and quotes gathered consistently
  • Referral pathways (introductions, applications, opportunities created)
  • Partner engagement (repeat participation, community growth, downstream action)

A quick “measurement theatre” checklist to avoid could look like:

  • Vanity impressions with no downstream action
  • “Lives touched” with no definition
  • Outcomes with no baseline, timeframe, or method

Side note: CSR/impact comms fails the moment it tries to claim the hero role. Your job is to be credible, not cinematic.

Layer 5: Learning & evolution. What you changed because you listened

This is the layer most organisations skip, and it’s the one that signals maturity.

Learning answers:

  • What surprised us?
  • What didn’t work as expected?
  • What are we changing next?

Mentoring circles taught me that two-way learning isn’t a luxury. It’s crucial. In impact work, legitimacy comes from listening, adapting quickly, and making sure those affected see themselves in your story.

 

Remember that the most credible impact teams don’t just report outcomes; they report decisions. So publishing learnings strengthens your story. It shows you’re accountable to reality, not just optics.

People mistrust CSR and impact organisations not from dislike, but because stories don’t match substance, or the substance isn’t clear.

The Impact Stack makes impact work easier to understand, share, and believe. From Code; Without Barriers and other initiatives, I have realised that the organisations that excel aren’t louder; they’re clearer.

If you lead a foundation, a CSR portfolio, or an impact initiative and want to strengthen your storytelling system, your narrative, your impact stories, your messaging architecture, and the comms that connect programmes to proof, I’d love to help.

If you’re in CSR, partnerships, comms, or impact measurement, which layer is hardest in your work right now: point of view, evidence, or learning? If you’d like to learn how to practically apply the Impact Stack to your existing reporting processes, PM me!