What to do when your weekly pulse goes silent for two weeks running — it's almost never what you think.

Aisha ran ops at a fourteen-person remote company. She had shipped Moodkin in late March; by mid-May, the pulse was humming. Twenty-two answers on Tuesday, twenty on Wednesday, nineteen by Friday. A curve the founder could almost read at a glance.

Then week seven landed. The Tuesday pulse went out at 9am sharp. By 6pm, four responses. By Wednesday morning, six. By Friday end-of-day, nine. The founder opened the dashboard on a Monday morning, looked at the count, and concluded the team had stopped trusting the tool. None of her three hypotheses were right.

We have watched this exact pattern on forty-plus small distributed teams since 2024. In our data, a two-week dip below fifty percent of the previous response baseline almost always traces to one of three causes. The trick is to read which one, because each one wants a different fix.

• *
  Loudest person went quiet.Every team has one or two voices whose vocabulary does the heavy lifting in pulse answers. When one of those stops typing for a week, the founder reads the drop as a system-wide cold-shoulder. It rarely is. The rotating-handle mechanic means a quiet person one week may be a busy person the next, and the absence is already rotating-handed by design. Read the dip as 'person X went quiet,' not as 'the whole team went quiet.'
• *
  The team hit a quiet healthy stretch.Some weeks a team is genuinely fine: post-launch calm, post-holiday warm-up, two quiet weeks after a brutal on-call rotation. Answers arrive short and agreeable ('fine,' 'no blockers,' 'good week'). Founders read those as disengagement; they are often honest rest. Look at the shape of the answers, not the count.
• *
  The cadence slipped.A skipped Tuesday because of a holiday, a pulse that arrived at 11:47pm instead of 9am, two pulses stacked on the same launch week. The team reads missed cadence as 'the founder lost interest' and answers dip before the founder notices the missed slot. A single returned-to-cadence Tuesday usually recovers it.

The pattern is consistent enough that it is worth naming directly. Three forces push the founder toward the failure read, and they compound.

First, the availability heuristic. One vivid week of zero responses pins the whole system as broken in memory, and the credibility of the pulse drops with it. Second, confirmation bias. A founder who has been worrying about trust on the team for three weeks reads the silence as evidence for the worry, not as a separate signal. Third, and worst: a weekly count is not, on its own, a diagnostic. As the cadence argument in why a pulse graduates from signal to checkbox lays out, a single low week is not data; a single low answer is not data. The pattern across weeks is data. The founder has to resist the impulse to over-read.

Once a quiet pulse lands on the Monday readout, run the same three-pass read every time. It is short on purpose. The diagnostic lives in the order, not in the depth.

• *
  Pass 1 — look at who, not just how many.A silent chart is not a silent team. Open the per-handle table. Who answered this week? Who answered last week and not this one? Under the rotating-handle mechanic, a person you cannot identify across weeks is also a person whose absence this week carries less weight than it feels like. Read the count against the handles underneath it. The number almost never tells the story alone.
• *
  Pass 2 — read the vocabulary, not the volume.Pull the free-text column. Group answers by shape. Closed-and-cheerful is honest rest. Closed-and-flat is an early signal. Open and specific is a working team — even at six answers. The pulse is meant to surface shape, not count. Train the eye to read adjectives the way you read a 1:1 face, the way the vocabulary read in what a pulse is actually measuring describes.
• *
  Pass 3 — bring the manager-ready asks into next week's 1:1s.This is the move that closes the loop. Pull the eight questions from the manager-ready weekly ask pattern, and bring two or three of them into the next 1:1 cycle. The dip that looked like a trust problem on Monday almost always dissolves into a vocabulary problem once a manager is asking the right questions out loud.

A quiet pulse, two weeks running, is not a broken system. It is a system doing its job — reading the team, surfacing a shift, asking for a small move from the founder before the loud signal arrives. Act on the who and the how, not the count. That single move is what separates a pulse the team trusts from a dashboard the team forgets.

That is the wire Moodkin is built to deliver: the rotating handle, the Monday readout, the manager-ready ask for next Tuesday. Drop a note and we'll send the install playbook.