Manager view

Team communication overview

An example of what a people manager would see: patterns across the team, not individual answers. All figures below are illustrative sample data for a fictional team of eight.

Pace · Understand

A team view shows patterns, never people.

Use it to decide where team habits could change, then let each person choose their own focus.

01 · What managers see

Aggregated trends only

Illustrative anonymised sample data. Managers see aggregated trends only — never an individual's responses, scores or free-text reflections. Individual results stay with the employee.

02 · What matters now

The team at a glance

Team size

8

Team average

65/100

Building

Team strength

Listening

74/100 average

Team gap

Challenge

56/100 average

03 · What to do next

Recommended team actions

The largest team gap is challenge. These actions are designed to build shared habits rather than assess individuals.

Make challenge safe

Constructive challenge is the lowest team average. Open the next three team meetings by explicitly inviting a counter-view, and thank the first person who gives one.

Standardise handovers

Agree a three-line handover format (what, owner, date) for cross-functional work to lift audience awareness and clarity together.

Feedback in the flow

Add a two-minute 'one thing that helped, one thing to adjust' close to weekly rituals so feedback stops being an annual event.

Pair the range

The team spans Emerging to Amplifying. Pair the strongest listeners with those building the habit for a month of shadowing.

04 · Supporting detail

Patterns across the team

Team averages by dimension

Distribution by stage

  • Emerging1 person
  • Building4 people
  • Effective3 people
  • Amplifying0 people

05 · Trust

Privacy by design

Aggregated views would only appear for teams of five or more, individual responses are never surfaced to managers, and participation would be voluntary and developmental.