Written by Samuel Valente
You’ve started making decisions based on a signal that was never designed to guide you.
Look at your last ten decisions, which content to double down on, which offer to push, which feedback to act on, which hire to keep. Now ask honestly: how many of those were made because the data told you to, and how many were made because someone reacted well, or badly, and you adjusted?
If you’re like most operators at your stage, more of those decisions were driven by reaction than you’d like to admit. Not because you’re weak. Because approval is the easiest signal to read and the hardest one to ignore. It arrives instantly. It feels like information. It isn’t.
This post is about separating the two signals you’re currently treating as one ( what people think of your move, and whether your move is actually right ) and building a filter that lets you stop confusing them.
Every founder who builds anything visible runs into this exact failure mode. A post performs well, so you make more like it, even if it drifted from the thing you actually set out to build. A customer complains loudly, so you patch the offer around their objection, even if that customer was never who you were building for. A competitor mocks your pricing publicly, so you second-guess a number you’d already tested and confirmed.
None of these are strategy. They’re flinches. And flinches, repeated enough times, become your roadmap, a roadmap written by whoever reacted loudest that week, not by you.
The mistake
The mistake isn’t caring what people think. It’s treating their reaction as if it were evidence about your decision, when it’s almost always evidence about them.
Applause tells you what someone prefers. It doesn’t tell you what’s true, and it definitely doesn’t tell you what’s aligned with what you’re building. Criticism works the same way, just with the sign flipped.
When someone reacts sharply to a price, a position, or a piece of content, the sharpest thing to ask isn’t “am I wrong”; it’s “what does my move contradict about how they think this should be done.” Most criticism is someone else’s discomfort with a choice they wouldn’t have made, routed through you.
That reframe changes nothing about the criticism itself. It changes everything about what you do with it.
The filter
Here’s the structural fix. Before reacting to any signal ( praise, backlash, a spike in engagement, a churn spike) run it through three questions, in order:
What is this signal actually measuring? Preference, or performance. A like measures preference. A refund measures performance. Don’t let the first one borrow the authority of the second.
Does it touch something you’ve already defined as a value, or just a preference someone else holds? If a customer says your onboarding is too intense, and rigor is a stated value of your business, that’s not feedback to absorb, that’s confirmation you’re filtering correctly. If they say your emails feel too infrequent and frequency was never a value you set, that’s just their preference meeting your absence of a decision.
If you acted on it, would you be building the thing you set out to build, or the thing that avoids the loudest objection this week?
This is the decision rule: treat every reaction (good or bad ) as data about the person reacting, and only act on it if it also passes your own stated values. Otherwise, it’s noise wearing the costume of feedback.
Notice the requirement buried in that rule: you need stated values before this filter works at all. Most founders skip that step. They discover what they value in the moment a customer or a critic challenges them, which means the “value” they defend is really just whatever they felt like defending that day. That’s not a filter. That’s improvisation dressed up as conviction.
Practical application
Do this before your next content cycle, pricing decision, or product change:
Write down three non-negotiables for how you operate, not aspirational values, operational ones. Things like “we price for the outcome, not the hours,” or “we say no to clients who aren’t ready,” or “we publish the uncomfortable take, not the safe one.” Three is enough. More than five and you’ll bend at least one under pressure.
Then, the next time a comment, a customer, or a competitor gets a reaction out of you, stop before you respond. Run it through the three questions above. If it doesn’t touch one of your three non-negotiables, you’re allowed to notice it and do nothing. That’s not avoidance, that’s the entire point of having values instead of vibes.
Track this for two weeks. You’ll notice the volume of things demanding your attention drops sharply, not because fewer things are happening, but because you finally have a reason to ignore most of them.
The principle
You were never going to escape being judged. That was never the goal, and chasing it wastes energy you don’t have.
The goal is building something solid enough that judgment stops being able to move you.
Applause doesn’t confirm you’re right. Criticism doesn’t confirm you’re wrong. The only verdict that should change your next move is your own, measured against values you chose before the reaction happened, not values you invent in the moment to justify how you already feel.
Decide what you stand for once. Let it decide everything after.
Acquisition Notes turns Hormozi frameworks into clear, actionable execution, so you always know the next move to grow your business. No noise. No theory. Just decisions.
Context
Acquisition Notesis independently written and operated by Samuel Valente.
It is not affiliated with, endorsed by, or produced by Alex Hormozi, Leila Hormozi, or Acquisition.com.All content is original analysis and interpretation, created for educational purposes.
A refund tells you something real. A backlash on a post mostly tells you who was already primed to be annoyed.
Mixing those two up is how a lot of good decisions get reversed for bad reasons.