An impact map is a plan, not a poster
Impact mapping is the practice of writing down four things about your business: the activities you actually do, the outputs those activities produce, the outcomes that follow, and the goal they all ladder up to. Four layers. One page. That is the whole method.
Most purpose-led consultants can describe the change they want to see in the world. Far fewer can draw a line from Tuesday's client call to that change. The gap between those two things is where good intentions go to die — usually dressed up as a values statement on a website nobody reads.
An impact map closes the gap. It also does something less obvious and more useful: it tells you what to stop doing.
The four layers, in plain language
Get these definitions straight before you start, because most maps fail on layer confusion.
Activities are what you do. Delivered a strategy sprint. Ran a workshop. Wrote a report. Mentored someone. Paid a supplier. Activities are verbs, and you control them completely.
Outputs are what those activities produce, counted. Six workshops. Forty participants. One board-ready plan. Twelve hours of pro bono advice. Outputs are numbers, and you still control them almost completely.
Outcomes are what changed for someone else because of those outputs. A board that can now make a decision it was stuck on. A small charity that stopped losing two days a month to manual reconciliation. A first-time founder who charged properly for the first time. Outcomes are changes in behaviour, capability or condition — and you influence them, you don't control them.
Goal is the larger thing those outcomes contribute to. Not "making a difference". Something specific enough to argue with. For a lot of our members that means naming a UN Sustainable Development Goal and a target underneath it, because it gives you shared language with clients, funders and collaborators who are already using that frame.
The discipline is refusing to let a layer masquerade as the one above it. "Ran twelve workshops" is not impact. It is an output. Twelve workshops that nobody applied is twelve workshops.
How to start impact mapping your business
Work backwards. Always backwards. If you start from activities you will simply describe your current calendar and then reverse-engineer a noble reason for it.
1. Write the goal first. One sentence. Who is better off, in what way, and how would a sceptic know? Then map it to an SDG if that is useful to you. Most service businesses land somewhere in SDG 8 (decent work and economic growth), SDG 4 (quality education), SDG 5 (gender equality), SDG 12 (responsible consumption and production) or SDG 17 (partnerships). We pay particular attention to SDG 17, because for a company of one, partnership is the only realistic path to scale.
2. Name three to five outcomes that would make the goal more likely. Be honest about your reach. You are not going to reform an industry. You might make eleven organisations in that industry measurably better run. That is a real outcome and it is enough.
3. Work out which outputs produce those outcomes. This is where it gets uncomfortable, because you will find outputs you are proud of that produce nothing. Keep going.
4. List the activities that create those outputs. Now compare that list to your actual week.
5. Circle the mismatches. Every activity on your calendar that does not appear on the map is either admin you can't avoid, revenue you need, or something you should stop. Be clear which is which. Revenue is a legitimate answer. This is a business, not a hobby, and an impact map that quietly assumes you'll work for free is a map for a business that closes in eighteen months.
The whole exercise takes about ninety minutes the first time. It takes considerably longer if you do it alone with no one to challenge your outcome statements, which is a reason to do it with peers rather than on a Sunday afternoon with a notebook.
A worked example: a two-person operations advisory
Say you run a small operations advisory. Two people, working with not-for-profits and social enterprises on finance and systems. You want to work three days a week and still earn properly. Here is what the map might look like.
Goal. Small purpose-driven organisations in Australia run on systems that don't depend on one exhausted person's memory. Laddered to SDG 8, target 8.2 — higher productivity through diversification and upgrading.
Outcomes.
- Client organisations reduce monthly finance admin time and redirect those hours to programme delivery.
- Client staff can run the system without you after the engagement ends.
- Client boards receive reporting they can actually make decisions from.
- Other advisers in the sector use your documentation approach with their own clients.
Outputs.
- Eight full implementation engagements a year.
- One documented, handover-ready system per engagement.
- One staff training session per engagement, recorded and left with the client.
- A public template library, updated quarterly.
- Four ninety-minute diagnostic sessions a year offered at no cost to organisations under a certain size.
Activities.
- Discovery, build, handover — the core delivery cycle.
- Writing documentation as you go rather than at the end.
- Recording training instead of delivering it live twice.
- Maintaining the template library.
- Paying your own contractors within seven days.
Notice three things about that map.
First, the fourth outcome — other advisers using your approach — is a partnership outcome, and it is the only one with any leverage beyond your own delivery hours. It costs you a template library and some generosity. It reaches organisations you will never invoice. That is what SDG 17 looks like on a small business's map.
Second, "paying contractors within seven days" sits in activities. It produces no client-facing output. It stays on the map anyway, because how you run the business is part of the impact of the business. Operational practice belongs on the map. Procurement, employment, payment terms, energy, who you say no to.
Third, the no-cost diagnostic sessions are capped at four. Not "as many as we can fit in". Four. A number you can hold. Unbounded generosity is the most common way purpose-led consultants quietly go broke, and the map is where you set the boundary before the guilt sets in.
Choosing what to measure without drowning
You do not need an evaluation framework. You need two or three honest numbers you will actually collect.
Pick one measure per outcome, maximum. For the operations advisory above, that might be: hours of monthly admin before and after, self-reported by the client at six months; whether the system is still in use at twelve months, asked in a two-question email; and number of advisers who request the template pack.
That's it. Three data points. Collected with an email. Reviewed twice a year.
The temptation is to build something more impressive. Resist it. A measurement system you abandon in March tells you less than one crude number you have collected every year for four years. And be honest when the number is bad — a map you only update when it flatters you is marketing, not measurement.
If you want the longer view of how we think about honest measurement and the SDGs, that sits in our approach to impact at The IC.
Three ways impact maps fail
The map describes an aspiration, not a business. If nothing on the activities row appears in your calendar this month, you have written a mission statement with extra steps. Rewrite it around what you actually sell.
Every client fits. If your map accommodates every enquiry that comes through the door, it isn't doing any work. A useful map makes some enquiries obviously wrong for you, and gives you language to decline them that isn't "we're at capacity".
Impact is the whole story. Impact is one of the five pillars in the Impact Architect Framework™ — alongside Product Design, Visibility, Systems and Wellbeing — and it is the one people most often try to solve in isolation. A beautiful impact map attached to underpriced offers and no pipeline is a plan for burning out virtuously. Members rate all five pillars 1–10 during onboarding for exactly this reason: the weakest pillar sets the ceiling.
Revisit it twice a year
Six-monthly is about right. Long enough that something has genuinely changed, short enough that you catch drift before it costs you a year.
Three questions each time. Did the outcomes happen? Which activities produced nothing? What is on the calendar that isn't on the map?
The answer to that last question is usually the most valuable thing the exercise gives you.
Do this with people who will push back
Impact maps get sharper with challenge and softer in isolation. Your own outcome statements will sound persuasive to you at the moment you write them. They need someone to ask what would have happened anyway.
That's the work we do in Foundation Pods and, more pointedly, in Expert Pods — three or four members and an expert guide, small enough that nobody's vague outcome statement survives the hour. The IC isn't where you summit. It's the base camp: the place you get resupplied, checked over and honestly briefed before you go back up.
We cap membership at 150 so those rooms stay small. If you want in, join the Community Waitlist.