Environment & Resources: what it is and how to measure it

Of the 18 KPIs in the PEAKTEAMS survey, Environment & Resources is the one team leads most often want to wave away. "We cannot change the budget, so why ask." It is also the KPI whose low score most reliably explains low scores elsewhere. A team that is short of people, waiting on the organisation for every decision and reshuffled every quarter will score poorly on delivery, focus and cohesion, and no amount of work on those process KPIs will fix an input problem.

The KPI measures whether the team has what it needs to do the job: enough time and people, tools and workspace that help rather than hinder, support from the wider organisation when it is asked for, and enough stability in its membership to have learned how to work together.

Four things in one score

• Capacity. Enough people and enough hours for the goals the team has actually been given, not the goals on the original plan.
• Organisational support. When the team needs a decision, a budget line, a contract signed or a dependency unblocked, does it get it, and how long does it take.
• Tools and environment. Software, equipment, workspace and the physical or virtual setup for collaboration.
• Stability. Whether the team's composition has held still long enough for people to learn each other's strengths. This item sits in Environment & Resources deliberately: churn is a condition the team works under, not a process it controls.

The evidence that context matters

Hackman (2002) names a supportive organisational context as one of his conditions for team effectiveness, and breaks it into the reward system, the information system, the education system and the material resources available. His point is uncomfortable for a team-level survey: a lot of what makes a team effective is decided above it. Measuring it anyway is the only way to make the case upwards.

The job demands-resources model (Bakker and Demerouti, 2007) describes strain as the result of demands outstripping the resources available to meet them, where resources include everything from tools and autonomy to support from colleagues and managers. The same workload is sustainable with the right support and corrosive without it, which is why "our workload is manageable" and "management provides the support we need" sit in the same KPI.

Maslach and Leiter (2016) list workload first among the six areas of work life that drive burnout, alongside control, reward, community, fairness and values. Chronic under-resourcing is not a motivation problem to be solved with better goals; it is a capacity problem that eventually shows up as exhaustion.

On stability specifically, Huckman, Staats and Upton (2009) studied software project teams and found that team familiarity, the prior experience members had of working together, was associated with better performance. Teams that are rebuilt every quarter keep paying the cost of learning each other again.

Signs of a low score

You will usually see a low Environment & Resources score before the survey tells you about it. The free-text answers in the Snapshot tend to name it directly, but the behaviours are visible earlier:

• The team has a standing list of things it is "waiting on" from outside, and the list does not get shorter.
• Workarounds have become the process: people export to spreadsheets because the tool cannot do the thing.
• Estimates are padded for interruptions, and the padding is now most of the estimate.
• Nobody has had a full day of uninterrupted work in the last month.
• The team has lost or gained a member in each of the last three quarters.
• Requests for training are approved in principle and never scheduled.

A high score looks unremarkable from the outside, which is the point. Tools get bought when they are needed, escalations get answered within days, the team has the same core members it had a year ago and can say so with mild surprise that you asked.

How PEAKTEAMS measures it

The Snapshot survey (about 12 minutes per member, all 18 KPIs) asks three statements for this KPI, one more than most, because the stability item was moved here from the Friction pillar.

The Deep-Dive adds twelve more that separate the components: tools, budget, headcount, workspace, training, technology, management support, help from other teams, workload, time for deep work, administrative support and whether the environment enables collaboration. There is no reverse-keyed item for this KPI.

This KPI is unusual in that disagreement within the team is itself informative. The Consensus Matrix plots each item's average against agreement, and a wide spread on the Environment & Resources items usually means the shortage is concentrated: one role is overloaded, one sub-team is waiting on a vendor, one person is on the hardware nobody else has. Results appear only once at least five team members have answered; the owner's own answer does not count.

How to improve it

The honest answer is that some of this is above the team's pay grade. But less of it than leads assume.

• Make the waiting visible. A list of open requests to the organisation, with dates, turns "we never get support" into a conversation about specific items and specific delays.
• Match the goals to the capacity, not the other way round. If headcount is fixed, the lever is scope; a team that is asked to do less and does it is scoring higher on this KPI than one that is asked to do everything.
• Protect blocks of focused time. Two meeting-free half days a week cost nothing and address the deep-work item directly.
• Treat stability as a request, not a fact of life. Leads can ask for a membership freeze for two quarters; many never ask.
• Fix the tool that generates the most workarounds first. Ask the team which one it is; they know.
• Take the score upwards. An anonymous team-level number on "we get support when we ask" is a stronger argument to a sponsor than any single complaint.

Related KPIs

Team Organization is the sibling Input KPI about whether the people the team has are in the right roles with a fair workload; Environment & Resources asks whether there are enough of them at all. Friction & Consumption measures energy lost to bureaucracy and unproductive meetings, which is often the same organisational drag seen from the other side. Delivery Methodology is where tool problems usually surface first.