Patterns, never people.
We report what the team is feeling, never who said it. Individual answers don't get a face, a name, or a score.
A weekly ritual for teams that are mostly fine.
Most teams aren't on fire. They're mostly fine — until, quietly, they aren't. Murmur is a small, honest way to notice the difference in time to do something about it.
Why we built it.
There's a whole industry of software for watching people — tracking mood, scoring morale, flagging who might leave. It tends to make everyone act a little more guarded, which is the opposite of what you wanted to measure.
We wanted the other thing. A weekly check-in short enough that people actually do it, anonymous enough that they tell the truth, and quiet enough that it never feels like surveillance. A few honest questions. The answers become a team-level signal — not a file on anyone.
The promise is small on purpose. Murmur won't transform your culture. It'll help the team notice the small stuff before it becomes A Thing, and pick one thing to make next week less weird.
What we believe.
Useful beats impressive.
If a feature doesn't help the team notice or fix something, it doesn't ship. No dashboards built to look good in a demo.
Small fixes beat big transformations.
One thing made less weird next week is worth more than a culture roadmap nobody reads.
Privacy isn't a feature.
It's the thing the whole product depends on. The moment people can be singled out, they stop being honest — and then the data is worthless anyway.
What the murmur isn't.
- Not a psychological-safety dashboard.
- Not mood tracking, morale monitoring, or people analytics.
- Not a way to find flight risks. We don't do that.
- Not another tool that emails you a forty-slide quarterly deck.
How privacy works.
Murmur never shows individual answers to Leads. Team summaries appear only once enough people have responded. You can't be singled out.
Start a weekly murmur.
A few honest questions. Nobody has to write an essay. See how the team is actually doing.