Build the Right Product, Build the Product Right.
- Mark
- Jun 11
- 2 min read
Updated: Jul 4

It's funny how a new job can completely change how you see things. After years at big companies like IBM and HP, where following strict rules was everything and knowing how to build was the main focus, joining Mavericks Consulting felt like a breath of fresh air - or maybe a splash of cold water.
In my old roles, we were masters of getting things done. We had detailed rules, strict methods, and we knew exactly how to make a product perfectly. Our plans were flawless, our code clean, and our testing thorough. We were great at building products right. But I've come to realize we spent less time asking if we were building the right product in the first place.
Our talks rarely focused on what users actually needed, the real market problem, or the actual value we were bringing. Instead, they were about technical setups, following rules, and getting the product out the door. We just assumed someone higher up had already figured out what to build, and our job was just to deliver the how. It was efficient, yes, and we produced polished results. But looking back, I can't help but wonder how many of those perfectly built products just sat unused, or were eventually replaced by something simpler that users actually wanted.
The Mavericks Difference
Then came Mavericks Consulting. From day one, the motto,"Build the Right Product, Build the Product Right," really stuck with me. It's not just a catchy phrase, it's how we actually work. Here, our first conversations aren't about the tech we'll use or how long it'll take. They're about the problem. We spend a lot of time upfront, really understanding the client's business, their users, and their key challenges. We question assumptions, explore different ideas, and refine our thinking before we write any code.
This shift has been both tough and incredibly rewarding. My old habits often make me want to jump straight into solving things, but the culture at Mavericks encourages or even demands a pause. We do a lot of research/spikes, talk to stakeholders, and constantly get feedback. It's an agile way of thinking that goes beyond just software. It's about being flexible in business, quickly adapting if we find our first idea for the 'right product' wasn't quite perfect.
Learning New Ways
It's been a steep learning curve, especially letting go of some old corporate habits. It demands a different kind of focus now - being curious, understanding people, and being willing to challenge how things are usually done. When we do start building, we do it with a much clearer purpose and confidence, knowing we're not just following a plan, but solving a real problem for real people.
I'm still committed to building products right. My years at IBM and HP taught me that, and it's still crucial. But now, at Mavericks Consulting, I'm just as, if not more, focused on making sure we're building the right product. And honestly, that has changed everything for me. It's more than just a job - it's a constant effort to create genuine value, and it's incredibly fulfilling to be part of a team that believes in that every single day.
Comments