Do your solution solve a customer problem?

🚀 You know that feeling when the product team is super excited to develop an awesome solution, only to find out that it doesn’t actually solve the customer’s problem or need? 😱

Unfortunately, it often happens once the solution has been fully developed and released to production. It takes one to know one—so of course, I’ve been part of that many times myself. 🫣

I’ve seen SO many teams get caught up in that rush, and I’d even go so far as to say I don’t know a single team that hasn’t experienced it. It comes in many forms: sometimes it’s tech bling bling, sometimes it’s feature creep, sometimes it’s gold plating. 🤠

It’s so costly, not just in 💰, but also in terms of demotivation and wasted mental energy.

I believe it can easily be prevented by continuously refining your backlog. But if it’s that easy, why does it still happen? I think it’s the lack of focus on co-creation of user stories—ensuring everyone is aligned on the Why, the What, the How, and the Size. That’s why I created Mojn.Dev, a tool where teams can collaboratively refine their backlog online. 💡