Greg is vibrating. It’s a literal, physical hum of anxiety that usually precedes a catastrophic decision involving the product roadmap. He’s currently holding a dry-erase marker like a weapon, hovering over the ‘Q3 Deliverables’ column, ready to smudge out 77 days of engineering labor to make room for a ‘Custom Export Dashboard.’ Why? Because a single client in the Midwest, who represents roughly 0.07% of our annual recurring revenue, threatened to walk away if they couldn’t export their data into a specific, obsolete format from 1997. We all know it’s a mistake. The lead architect is staring at the ceiling, probably calculating how many job applications he can send out before lunch. I’m just sitting here, my eyes stinging because I tried to go to bed early and instead spent four hours staring at the ceiling, thinking about how we keep trading our future for a few moments of quiet in the present.
[The whiteboard is a graveyard of good intentions.]
The Lazy Virtue of Customer Obedience
There is a peculiar, almost religious devotion to the phrase ‘the customer is always right.’ It’s the kind of mantra that sounds noble in a boardroom but feels like a slow-motion car crash when you’re actually building a product. We’ve been conditioned to believe that listening to the customer is the ultimate virtue, but we forget that there is a massive difference between hearing a problem and obeying a suggestion. When we obey, we aren’t being customer-centric; we’re being lazy. We’re outsourcing our strategy to someone who hasn’t spent 47 minutes thinking about the long-term scalability of our database. They just want their button. They want the button because it solves a local itch, oblivious to the fact that the button might set the entire house on fire.
The Sky M. Analogy: Discomfort vs. Cure
I think about Sky M. in moments like this. Sky is a professional mattress firmness tester… Sky once told me that if you ask a person what kind of mattress they want, 87% of them will describe something that feels like a marshmallow… But if Sky actually built what they asked for, those same people would wake up in 17 days with back pain so severe they’d sue the manufacturer. Sky’s job isn’t to give them the marshmallow; it’s to give them the support they don’t know they need while making them think they’re getting the comfort they want. He’s an advisor, not a servant. He understands that the customer is ‘right’ about their discomfort, but ‘wrong’ about the cure.
The Swiss Army Knife Product
We’ve lost that distinction in software. We’ve become order-takers at a digital fast-food window. When a loud customer screams for a niche feature, we don’t ask why. We don’t dig into the workflow. We just add it to the backlog and call it ‘responsiveness.’ The result is a product that looks like a Swiss Army knife designed by a committee of people who have never seen a tree. It’s got 27 blades, 7 of which are serrated, and a toothpick that breaks the first time you use it. Nobody can actually cut anything with it because it’s too heavy to lift. By trying to be everything to one person, we’ve become nothing to everyone else.
(For a 47-minute training session)
I once spent 7 days trying to find the perfect ergonomic chair, only to realize the problem wasn’t the chair but the fact that I was sitting for 17 hours straight. Sometimes the solution isn’t a new product; it’s a new habit. We do this in tech all the time. We build a feature to fix a user’s bad habit, effectively subsidizing their inefficiency. We spent $77,007 on a reporting engine last year because a VP at a legacy firm didn’t know how to use a filter. We could have trained him in 47 minutes. Instead, we permanently cluttered the UI for 10,007 other users.
The Backbone of the Advisor Model
This is where the ‘Advisor’ model becomes a life-raft. An advisor doesn’t just say yes. An advisor has the backbone to say, ‘I hear what you’re asking for, and if I gave it to you, I’d be doing you a disservice.’ It’s a terrifying thing to say to a person holding a checkbook, but it’s the only way to build trust. When you’re dealing with something as complex as environmental control-like looking for specialized units at
minisplitsforless-you don’t want someone who just nods. You want the person who tells you that the unit you’re eyeing is actually overkill for your square footage and will lead to short-cycling and a $237 repair bill in six months. That’s the person you trust. You trust them because they care more about the outcome than the transaction.
Trust vs. Transaction: The Core Difference
Focus on the immediate deal.
Focus on the long-term outcome.
But staying in that advisor lane is exhausting. It requires a level of strategic conviction that most companies simply don’t have. It’s much easier to blame the customer. ‘Well, we only built it because they asked for it!’ is the ultimate shield for a weak product manager. It’s a way of avoiding the responsibility of having a vision. If you have a vision, you have to defend it. If you’re just a mirror, you can blame the reflection for being ugly. I’ve been guilty of this 37 times in the last year alone. I’ve taken the path of least resistance because I didn’t want the 7-hour meeting required to explain why a feature was a bad idea.
‘Well, we only built it because they asked for it!’ is the ultimate shield for a weak product manager. It’s a way of avoiding the responsibility of having a vision.
The Interest Rate of Technical Debt
The cost of this cowardice is technical debt. Every time we build a ‘one-off’ for a ‘strategic’ client, we’re taking out a high-interest loan. We think we’ll pay it back later, but we never do. We just keep paying the interest in the form of slower deployments, more bugs, and a team that is 77% less motivated because they know they’re building junk. I’ve seen developers quit over this. They don’t quit because the work is hard; they quit because the work is meaningless. They quit because they’re tired of being told that the roadmap is a sacred document on Monday and a suggestion box on Tuesday.
Unpaid Technical Debt Interest
Debt Trajectory
There’s a 7-step process for regaining control, but it starts with a simple, painful realization: you cannot please everyone and build something great. Excellence requires exclusion. It requires looking at a potential $127,007 contract and saying, ‘We aren’t the right fit for you if you need that specific functionality.’ It feels like jumping out of a plane without a parachute, but in reality, it’s the only way to stay airborne. When you stop chasing the wrong customers, you finally have the space to serve the right ones.
Regaining Control: The Path Forward
Realization (7 Steps)
Excellence demands exclusion.
Defense of Roadmap
Saying ‘No’ builds necessary trust.
Greg is still standing at the whiteboard. He’s just drawn a jagged line through the ‘User Experience Audit’ task. He’s replacing it with ‘Legacy SQL Integration.’ I can feel the tension in my shoulders, that familiar tightness that comes from knowing we’re about to spend the next 7 weeks digging a hole just so we can fill it back in. I should speak up. I should tell him about Sky M. and the marshmallow mattresses. I should remind him that our 7 best engineers are already at their breaking point.
Instead, I find myself thinking about the time I tried to bake a cake with 7 different types of flour because I wanted to be inclusive to every dietary trend I’d read about that morning. It was a disaster. It was heavy, grey, and tasted like damp cardboard. I threw it in the trash and went to buy a simple, well-made loaf of bread from the guy down the street who only makes three things. He’s been in business for 27 years. He doesn’t take requests. He doesn’t care if you want raisins in your sourdough. He knows what he’s good at, and he knows that if you don’t like it, you can go to the supermarket. There is a profound dignity in that kind of refusal.
– The Dignity of Refusal
We need more of that in the boardroom. We need more people who are willing to be ‘wrong’ in the eyes of a single customer so they can be ‘right’ in the eyes of the market. We need to stop treating the roadmap as a menu and start treating it as a manifesto. Because at the end of the day, a product that tries to be everything to everyone eventually becomes nothing to anyone. It becomes a ghost, a collection of buttons and toggles that haunts the users who were actually looking for a solution.
The Smallest Victory
I stand up. My chair makes a loud, 7-decibel screech on the linoleum. Greg looks over.
‘Greg,’ I say, and my voice is steadier than I expected, despite the lack of sleep. ‘If we build that, we’re going to regret it in 7 months. And more importantly, the customer is going to regret it too. They don’t need a custom export; they need a better way to visualize their data in the platform. Let’s build the solution, not the request.’
There’s a silence in the room that feels like it lasts for 7 minutes, though it’s probably only 7 seconds. Greg looks at the whiteboard, then at me. He doesn’t put the marker down, but he doesn’t draw the line either. It’s a small victory, the kind that doesn’t show up on a spreadsheet but keeps the soul of the product alive for one more day.
[The best way to respect a customer is to protect them from their own bad ideas.]
We are advisors. We are experts. We are the ones who have seen the 107 ways this can go wrong. If we don’t lead, we shouldn’t be surprised when we end up lost. And being lost is a lot more expensive than losing a single contract.