Imagine running your marketing team on website traffic data from three months ago. The campaigns you're evaluating launched in spring. It's now summer. You're making decisions about what to fund next based on what the audience was doing before half the things that have since happened actually happened.
That sounds absurd when you say it about traffic data. It's exactly what most organisations accept for people data.
A quarterly feedback cycle means your most recent read on team sentiment is at least three months old, and often older. By the time the survey closes, gets analysed, gets presented to leadership, and lands in an action plan, you're typically five or six months removed from the moment people were actually asked. In that window: a new manager might have started, a key person might have left, a restructure might have been announced, a particularly brutal quarter might have ground through the team. None of this is in the data. The data predates all of it.
What makes this worse is that the decisions made from that data affect people's present experience. You run a pulse check in Q1. Results suggest collaboration is strong. You deprioritise team-building budget in Q2. In reality, collaboration broke down in March after a difficult reorg, and the Q1 data doesn't know that. By Q3, when the next check lands, you're dealing with the consequences of a decision made from wrong information.
People operations isn't a slow-moving function. Teams change fast. Sentiment shifts faster than most leaders expect - a single bad month, a leadership change, a credible rumour about redundancies: any of these can move sentiment materially in a matter of weeks. A quarterly cycle can miss all of it.
The operational case for more frequent signal isn't complicated. It's the same case you'd make for any business function: if the data you're acting on is wrong, your actions will be wrong. The lag in people data isn't a design choice - it's a constraint that used to be unavoidable. Surveying large teams took time and resource. That's no longer true.
A weekly check-in takes less than a minute to complete and produces a trend rather than a snapshot. You can see when something changed, not just where things currently stand. You can respond in the same week you learn about a problem, not in the quarter after next.
The argument for staying with quarterly or annual cycles is usually cost, effort, or precedent: this is how we've always done it, it's what fits the annual review process, it's what the board wants to see. These are process arguments. They don't address the fundamental question of whether the data is timely enough to be useful.
Relay gives you a read on your team every week. Not a replacement for deeper, less frequent analysis - a complement to it. So that by the time you sit down for the quarterly review, you're not catching up. You already know what's been happening.