Team harmony for engineering and product orgs

The three ratings that match how eng work fails

1. Skills — staffing, depth, tooling
2. Collaboration — productive vs a tax on delivery
3. Impact — shipping, customer value, clear outcomes

Intentional shape: fixed three metrics · monthly · small-team digest — not a general anonymous poll suite.

The loop

1. 1

   Connect Slack

   The roster syncs from the workspace. People do not need a Wolfloyee account to answer.

2. 2

   Three questions, one minute

   Each person gets a private DM and email. Skills, collaboration, and impact.

3. 3

   Read the harmony score

   The score is hidden until at least three people answer.

Why eng leads use a pulse (not a 40-question suite)

Velocity on the board can look healthy while reviews stall, standups go quiet, and a strong IC starts taking recruiter calls. Annual engagement surveys arrive after the damage is already in the sprint. Channel polls are social — people perform for the room. Enterprise suites often sit behind a ~$4k+/year floor and a 40-question program nobody wants to fill out twice.

A monthly pulse is the opposite shape. Same three ratings every month. Private Slack DMs. One harmony score you can compare to last month. Wolfloyee is free during beta for that signal — not another HR platform to roll out.

Spotting delivery friction before it hits the board

Engineering managers usually feel friction first in the work, not in an HR dashboard. Pull requests sit. Design reviews slip. The same two people carry the on-call load. Standups get shorter because nobody wants to say that collaboration has become a tax. Then a 1:1 turns into an exit conversation you cannot unwind.

A pulse does not replace your incident review or your staffing plan. It asks the team, privately, whether skills, collaboration, and impact still hold. When those three ratings drift, you get a number you can bring to planning — while you can still change scope, pairing, or how the team ships.

Product managers see the same pattern from the other side of the ticket: busy sprints, unclear outcomes, and impact that does not land. The impact rating is there for that. If the score drops while the roadmap still looks full, the friction is already in the system — not waiting for the next performance cycle.

Pulse vs retro

A retro is a conversation in the room. It is useful, and it is also social. The loudest story wins; the person already interviewing may stay quiet. A pulse is a private, repeatable check — three ratings, once a month — that does not wait for the sprint ceremony.

Use both. The retro still owns what happened this sprint. The pulse owns whether the pack still works as a unit. When the harmony score and the retro notes disagree, that gap is the signal. You do not need a 40-question engagement survey to see it.

A Slack-native workflow

The team already lives in Slack. Connecting the workspace syncs the roster. People do not need a Wolfloyee account. Each month they get a private DM and a personal email link, not a channel blast. Answers stay anonymous. The score stays hidden until at least three people respond.

That is the whole loop: create the company, connect Slack, send the pulse, read the score. No extra survey portal to nag people into, and no long form that burns the team's goodwill. For engineering and product orgs that want a monthly signal without standing up an HR suite, the workflow is the product.