Team Pulse · illustrative sample

Team Atlas — payments platform

Last six sprints · 11 engineers · 9 of 11 responded to the pulse. All names, tickets and numbers here are invented.
A checkup uses two sources: what the patient says and what the tests show. Team Pulse compares the team’s account with the ticket record, then looks at the gaps.
Delivery predictability
62%
↓ from 84%
Unplanned work
31%
↑ from 12%
Reopen rate vs. org median
3.1×
↑ 6 sprints
Open items per engineer
2.8
↑ from 1.6
Pace felt sustainable
2.4/5
↓ from 3.8

The two sources

The team reports how work feels. The work record shows how it moved. Review both before reaching a conclusion.

The team — what people report9 responses
Do you know what matters most this quarter?
4.1/5
Is the pace sustainable?
2.4/5
Do you have what you need to do your best work?
2.9/5
Are handoffs and ownership clear?
3.3/5
Would you feel comfortable flagging a risk early?
3.9/5
The work record — what the tickets show412 tickets
Points on stated priorities88%
Unplanned work, share of points31%
Cycle time · median → 90th4d → 22d
Ticket age spent blocked38%
Tickets touched by 3+ people41%
Reopened at least once58 of 412

What the ticket text revealed

Jira has no field for these themes. The model groups descriptions, comments, and reopen reasons across 412 tickets. Open a theme to read the source text.

Evidence — what people wrote
PAY-2841“Blocked again — partner sandbox returning 502s since Tuesday. Can't verify the payout path end to end.”
PAY-2903“Waiting on a sandbox refresh from the partner. No ETA given. Parking this.”
PAY-2955“Third time this sprint the test environment dropped our webhook registrations.”
Finding: this is the board’s largest source of blocked time. Current reports miss it because no field records partner-sandbox failures; a delivery dashboard makes the delay look like a slow team.
Evidence — what people wrote
PAY-2877“Is this ours or platform's? Moving to the platform board for now.”
PAY-2881“Moved back — platform says integration owns the mapping layer.”
PAY-2914“Nobody owns the retry contract between us and the connector team. Third time this has come up.”
Finding: the pulse gives ownership clarity 3.3/5, its fourth concern. Ticket text ranks the boundary second by cost. The team is understating a large source of delay.
Evidence — what people wrote
PAY-2790“Reopening — retries still duplicating on 5xx responses.”
PAY-2836“Same as the last two. We keep patching the symptom at the edge.”
Finding: nine tickets across four sprints describe one retry bug. Fix the contract once. This is what reading text adds beyond counting tickets.
Evidence — what the pattern shows
Pattern28% of merged changes pass through one review queue, which is also the slowest step in the 90th-percentile cycle time.
This is a system risk. The process has a single point of failure. Naming a person would turn a system finding into a performance review.

Where the story and the data disagree

Agreement tells us where to stop. Gaps tell us what to examine.

The team said
“We know what matters most this quarter.” — 4.1/5
The tickets show
88% of points map to the stated priorities.
✓ Agreed — priorities are not the problem. Stop looking here.
The team said
“The pace isn't sustainable.” — 2.4/5, down from 3.8
The tickets show
Unplanned work at 31%, open items per engineer up to 2.8.
✓ Agreed — the strain is real and it has a measurable cause.
The team said
Ownership clarity is middling — 3.3/5, their fourth-ranked concern.
The tickets show
Boundary confusion is the second most expensive theme on the board, at roughly 14 days.
⚠ Gap — the team is under-reporting its second-biggest cost. Worth asking why in the next session.

What to do next

Three moves, ordered by what the evidence supports.

1
Escalate the partner sandbox as a dependency, not a bug
This is the largest source of blocked time, and current reports miss it. Assign an owner outside the team and set an SLA in writing.
2
Name one owner for the integration boundary
This requires a decision, not more headcount. One owner could remove roughly 14 days of ping-pong per six sprints.
3
Treat the nine webhook reopens as one design fix
Fix the retry contract once instead of patching the edge a tenth time. Then re-measure reopen rate in two sprints.
Scope: team and system only. No one is named, ranked, or scored. Pulse responses are reported in aggregate. If leaders use this to judge a person, people stop answering honestly and the data stops helping.