Having been both a customer and a user of Autodesk products, and later part of the product teams building them, I’ve had the rare chance to see things from both sides. I’ve been the one filing bugs and feature requests, and I’ve been the one deciding which ones make the roadmap.
Over the years, I’ve learned a few things about what really matters when building products that people actually love to use. Whether you’re running a startup or scaling up, these lessons might help you stay focused.
Don’t Be a Feature Factory
When I was a customer, it sometimes felt like every release showed up packed with new features no one asked for. When I joined a product team, I understood how easy it is to fall into that trap, chasing parity, keeping up appearances, or just trying to please everyone.
That’s where the Kano Model helped. It breaks features into:
-
Must-haves: basic expectations. Miss one and customers notice.
-
Performance features: the more you deliver, the happier they get.
-
Delighters: the surprises that make people smile.
At Autodesk, we had something called “F3,” short for Fit, Finish, and Fixes. A sprinkle of those user-delighter details could turn a functional release into one that felt truly polished. The trick was always balance. Keep what matters, drop what doesn’t.
Make Every Feature Earn Its Place
One of my jobs was connecting customer needs to business goals. Every feature request had to pass a simple test: Does it move the needle?
If it didn’t improve retention, create value, or strengthen the product, it didn’t make the cut. Customers can tell when teams build for checklists versus when they build for impact.
Metrics like churn, lifetime value, and engagement tell you a lot, but so does your gut when you’ve been in the field.
Data is a Guide, Not a Governor
Data is powerful, but it’s not everything. Some of the most meaningful product ideas I’ve seen came from intuition and a few “what if” moments.
Use data to validate, not to paralyze. Listen to the stories behind the numbers.
Customer Feedback is Gold, If You Know Where to Look
Not every loud voice speaks for your target user. When I worked on customer programs, we learned to filter feedback through our Ideal Customer Profile, the users who aligned with our strategy and would gain the most from what we built.
It’s not about ignoring feedback, it’s about understanding context.
Ship. Learn. Repeat.
Iteration is how you get better, but it’s easy to get stuck polishing forever. At Autodesk, we set clear goals for each release. When we hit them, we shipped.
As a user, I appreciated that rhythm. Progress over perfection.
Build a Culture of Curiosity
The best teams I’ve worked with were curious. They asked questions, explored trends, and learned from customers every day. That mindset keeps products fresh and people motivated.
Never Underestimate Storytelling
One thing that always stood out to me inside Autodesk was how stories moved people more than features. Customers, partners, even internal teams, everyone connects through a story.
If you can explain not just what you’re building but why it matters, you’ll create more than a product. You’ll create believers.
Startups have the agility to move fast and the freedom to be bold. Focus on real customer value, keep your features purposeful, and tell a story worth following.
Stay curious, stay humble, and keep listening.
