@busmark_w_nika Love all of these — especially the part about doing more than what’s expected. That extra 10% really does set people apart, even if it’s not obvious right away.
Also totally agree on movement + travel as a reset. It’s wild how much clarity hits after stepping away from the screen.
Funny enough, the single smallest decision that shifted everything for me was when I chose to launch our no-code accessibility widget solution without waiting for it to feel "perfect." It was messy and had not-a-few rough edges. But we got it live quickly, got reactions (the good, bad, and ugly) from real users with disabilities. We learned about missing features, misunderstood UI patterns, and even legal blind spots we’d never thought about. That rough launch shaped our roadmap, helped us land initial buyers, and gave the team confidence that we were solving a real problem. It reminded me that shipping something that works is always better than waiting for something that’s finished.
@a11yexpert This is gold — shipping before it’s “perfect” is such an underrated unlock. Every time I’ve waited too long to launch, I learned less and felt less momentum. Real feedback beats internal guesses every time. Love that you leaned into imperfect action — that early traction and clarity are worth way more than polish.
I have a simpler situation, when I had a problem at work and I could not solve it with any service. After that I decided to make this product myself and I was supported by the same people who were too multi-tasking and consistent.
While starting my consulting business, I got passionate about building on GenAI and just decided to explore it further and also decided to challenge it with a real world sales problem that I was solving through my consulting service. So, it was kind of accidental as I didn’t think I would get results and it was just for fun. Then one thing led to another and I ended up with a full product when I intended to build none.
@manu_goel2 Love that story — some of the best products start as experiments. It’s wild how solving your own problem just for fun can accidentally snowball into something real. Curious how long it took before you realized, “wait… I think I actually built a product here”?
@dustinheaps it took me a month to realise that but it was an intense month where I was working like 18 hrs everyday — just passionate about exploring and experimenting
@manu_goel2 That kind of deep grind hits different when it's driven by curiosity. Sounds like a wild but rewarding sprint — love hearing how experimentation shaped the insight.
That's interesting, thanks for the topic! I'm with you with this insight, actually: it's way better to do/publish something somewhat raw and start getting insights/feedback/whatever right away, rather than spending tons of time trying to make everything perfect. There's no such thing as 'perfect', and you might end up going down the rabbit hole 🤷🏻♀️
Replies
Thank you, Dustin, for a good topic.
I have more and would like to share them:
Start sooner (even if you do not have it sorted out).
Build a personal brand because not always will your work within the company be recognised.
Do something beyond what is expected – it is a differentiator and you will stand out.
When I need a mental "switch", move the body and travel – after these, I am more inspired.
@busmark_w_nika Love all of these — especially the part about doing more than what’s expected. That extra 10% really does set people apart, even if it’s not obvious right away.
Also totally agree on movement + travel as a reset. It’s wild how much clarity hits after stepping away from the screen.
Appreciate you sharing these 🙌
@dustinheaps I am trying do these more (exception is number 1 – I am still late :D)
Funny enough, the single smallest decision that shifted everything for me was when I chose to launch our no-code accessibility widget solution without waiting for it to feel "perfect." It was messy and had not-a-few rough edges. But we got it live quickly, got reactions (the good, bad, and ugly) from real users with disabilities. We learned about missing features, misunderstood UI patterns, and even legal blind spots we’d never thought about. That rough launch shaped our roadmap, helped us land initial buyers, and gave the team confidence that we were solving a real problem. It reminded me that shipping something that works is always better than waiting for something that’s finished.
@a11yexpert This is gold — shipping before it’s “perfect” is such an underrated unlock. Every time I’ve waited too long to launch, I learned less and felt less momentum. Real feedback beats internal guesses every time. Love that you leaned into imperfect action — that early traction and clarity are worth way more than polish.
IXORD
I have a simpler situation, when I had a problem at work and I could not solve it with any service. After that I decided to make this product myself and I was supported by the same people who were too multi-tasking and consistent.
@ixord Love that — sometimes the best products come from running into a wall yourself.
Props for taking the initiative and building the solution you needed. And having the right people around you makes all the difference
@manu_goel2 Love that story — some of the best products start as experiments. It’s wild how solving your own problem just for fun can accidentally snowball into something real. Curious how long it took before you realized, “wait… I think I actually built a product here”?
@manu_goel2 That kind of deep grind hits different when it's driven by curiosity. Sounds like a wild but rewarding sprint — love hearing how experimentation shaped the insight.
That's interesting, thanks for the topic! I'm with you with this insight, actually: it's way better to do/publish something somewhat raw and start getting insights/feedback/whatever right away, rather than spending tons of time trying to make everything perfect. There's no such thing as 'perfect', and you might end up going down the rabbit hole 🤷🏻♀️