Some Thoughts On Input Velocity
6 May 2026
We launched HappyHQ last week. Which is both exciting and terrifying.
Now comes the part few people talk about as much: figuring out whether what we built actually maps to how real people and real teams work. Not in theory. Not in a demo. In the actual, messy, Monday-morning reality of getting things done.
We already know we have built something that folks seem to want. We’ve got people actively using HappyHQ to help them with their work. We use it ourselves. But we want and need more information, more validation, more use cases.
One of the ideas I keep coming back to is something I call Input Velocity, and I want to share how we’re thinking about it, openly, because it’s still forming.
The basic idea
Every team is constantly surrounded by information. Customer frustrations. Market signals. Ideas from various people. Things that, if they made it into our orbit, would likely change a priority or a decision.
We think of Input Velocity as a way of asking: how much new customer insight is actually getting in and how good is it?
This first question is about rate and quality, not volume, because, let’s face it, nobody needs more noise. This is about novel, insightful signals.
This is the kind of information that genuinely updates our understanding of the problem we’re solving. A customer describing their workaround in a way we didn’t expect. A team member flagging something that doesn’t fit the current model.
That’s the primary phase: how can we discover new, meaningful information?
The second question is speed. Once something insightful does enter, how quickly does it get captured? How quickly does it become a shared understanding, a decision, an action, a change? That gap matters. But it’s downstream.
A team can have excellent processes for acting on information and still be flying blind, because the information coming in was never that interesting to begin with. I have seen and experienced this problem so, so many times!
What we think might be worth tracking
We’re still figuring this out, honestly. But one signal feels more meaningful than the rest right now:
Input novelty rate: the percentage of conversations that surface a problem we haven’t heard before.
That’s it. That’s the number we care most about at this stage.
Not how many signups. Not activation rate. Not time-in-app. Those will matter eventually. Right now, if we’re talking to early adopters and every conversation is confirming the same three things we already believed, something is wrong. Either we’re asking the wrong questions, or we’re talking to the wrong people, or, even worse, we’ve already started hearing what we want to hear.
A high input novelty rate means we’re still in discovery. That the map doesn’t match the territory yet. That’s uncomfortable, but it’s the only honest place to build from.
We do have related signals we’re watching alongside input novelty rate:
Problem recurrence: When the same pain does show up across conversations, how precisely do people describe it? The language shifts as understanding sharpens.
Surprise rate: How often does someone say something that makes us want to change a roadmap decision?
Conversation-to-insight ratio: How many calls before a new, actionable pattern emerges?
These aren’t vanity metrics. They’re a check on our own assumptions.
Why it matters
Slow input velocity is usually invisible. Teams don’t feel it as a discrete problem. They feel it as vague stress. A sense that things fall through the cracks. That decisions take forever. That nobody’s quite on the same page even though everyone has been in the same meetings. The tools that were supposed to help often make it worse: more channels, more notifications, more places where information lives and dies without ever becoming action.
We built HappyHQ because we believe the answer isn’t more software. It’s less friction. Fewer places to look. A working environment that stays close to how you actually think, not how someone assumed you’d think. But we also know we don’t have the full picture yet.
This is where you come in
We’re doing concierge onboarding right now, which is a fancy way of saying: we want to get on a call with you and just listen. Not a demo. Not a sales conversation. We want to hear how your team works. Where information gets stuck. What you’ve tried. What’s helped. What hasn’t. We want to set you up (for free!) on HappyHQ and hear what works or doesn’t.
We think Input Velocity matters, but we might be wrong about what to measure, or how, or for whom. The only way to find out is to talk to people doing real work.
If you’re an early adopter, or even just curious, we’d love to hear from you. You can join our waitlist, and we’ll set up a time to listen and get you started with HappyHQ. You can also reach us at hello@happyhq.com. No agenda. No growth hacking. Just conversation.
That’s how we want to build this.