Organizational Impact: what it is and how to measure it

Every organisation has at least one team that is busy, competent, well liked by its members and, if it vanished tomorrow, would not be missed for a quarter. Its sprints close. Its reports are on time. Nobody reads them. This is the failure mode the Organizational Impact KPI exists to catch, and it is invisible to every metric the team keeps about itself.

What Organizational Impact means

PEAKTEAMS defines Organizational Impact as the value a team creates beyond its boundaries: its alignment with organisational strategy, its collaboration with other teams, and its contribution to the broader success of the organisation. It is the second of the two Output KPIs. Where Team Output asks whether the team delivers what it set out to deliver, Organizational Impact asks whether that delivery changes anything for anyone outside the room.

The distinction is the one Hackman (2002) built into his first criterion of team effectiveness: output that is acceptable to those who receive it. Not to the team, to the recipients. A team is the wrong judge of its own relevance, which is why this KPI asks about visible effects, recognition, influence and other teams' success rather than about effort.

Why it matters

The clearest evidence comes from research on what teams do at their edges. Deborah Ancona and David Caldwell (1992) followed product development teams and found that the teams' external activity, which they sorted into ambassador work (managing upward, securing support), task-coordinator work (aligning with other groups) and scouting (gathering information), was related to how the teams were rated by managers; teams that focused only inward did worse on the ratings that mattered to the organisation. Internal cohesion was not enough. The teams had to work the boundary.

The second strand concerns motivation. Adam Grant's 2007 work on relational job design argues, with supporting studies, that contact with the people who benefit from one's work and awareness of that impact increase effort and persistence. Teams that can see their effect on others work differently from teams that ship into a void. And the IMOI model of Ilgen and colleagues (2005) closes the loop: a team's outputs become inputs to the next cycle, including the organisation's willingness to fund, staff and listen to it. Impact is how a team earns its next set of inputs.

What high and low look like in a real team

Impact is easiest to recognise by what other people do. Signs that a team scores high on this KPI:

• Other teams ask for its input before making decisions that touch its area, rather than informing it afterwards.
• Members can name, without looking it up, which organisational objective their current work serves and how it will show.
• When the team changes something, someone outside it notices and says so, whether in thanks or in complaint.
• The team has at least one standing relationship with each team it depends on or that depends on it, not just a ticket queue.
• Its work gets reused: a tool, a template, a dataset or a practice it built turns up somewhere it did not plan for.
• Leadership references the team's results in forums the team does not attend.

A low-scoring team shows the inverse. It learns about strategy changes from the all-hands. Its requests to other teams go to the bottom of their lists, and its own backlog contains items nobody outside the team has asked about in months. Members describe their work in terms of tasks ("we maintain the integration layer") rather than effects ("we are why the finance close takes two days instead of five"). When budgets are cut, it is surprised to be on the list.

How PEAKTEAMS measures it

Organizational Impact sits in the Output pillar of the Team P&L. The Snapshot survey (about 12 minutes per member, all 18 KPIs) asks two statements for it, both answered on a five-point agreement scale.

The Deep-Dive survey asks thirteen items for this KPI. Twelve are positively worded and map onto Ancona and Caldwell's boundary roles without naming them: being valued by the organisation, contributing to strategic goals, collaborating with other teams, visible and recognised impact, alignment with priorities, helping other teams succeed, reputation, influence beyond the team, lasting value, work that scales, building on organisational capabilities, and acting as a good citizen of the organisation. The thirteenth is reverse-scored, "Much of our work has little visible effect outside the team", and it is there so that a team in the habit of agreeing cannot score high by reflex.

Results appear only once at least five team members have answered; the owner's own answer does not count. The Consensus Matrix then plots each item's average against the team's agreement on it, so read this KPI's items together. One caution specific to this KPI: it measures the team's perception of its impact, not the organisation's. A high score with high agreement tells you the team believes it matters. Whether it is right is a question for its stakeholders, and the fastest way to answer it is to ask three of them the two Snapshot items about the team and compare.

How to improve it

Ancona and Caldwell's three roles make a useful to-do list, because most teams have one covered and two empty.

• Appoint an ambassador. One person whose explicit job includes keeping two levels of leadership informed of what the team is doing and why; impact that nobody above the team knows about does not count when resources are allocated.
• Hold a standing coordination slot with each neighbouring team. Fifteen minutes a fortnight with the teams you depend on removes most of the surprises that make a team look unreliable from outside.
• Send a scout. Someone who reads the strategy documents, attends the other departments' reviews and brings back what is changing, so the team hears about priority shifts before they land as reprioritisation.
• Rewrite the backlog in terms of beneficiaries. Each item should say who outside the team is better off when it ships; items with no answer are candidates for deletion, which is itself an impact improvement.
• Publish outcomes, not activity. A quarterly one-pager that says what changed for whom, rather than what was done, is what makes impact visible and recognised, two of the Deep-Dive items.
• Lend people out. A week of helping another team through its crunch builds the reputation and influence items faster than any amount of internal excellence.

Related KPIs

Team Output is the twin Output KPI: it measures whether the team delivers; this one measures whether the delivery lands. The direction a team's impact points in is set by two Input KPIs, Purpose & Objectives, which covers awareness of stakeholder expectations, and Values & Vision, which covers alignment with the organisation's longer-term direction.