When our users clearly state what they want from us, we really have no excuse for not delivering it. By adding a lot of transparency to our workflow, we introduced something new and very powerful: accountability. The team is accountable in the most direct manner We suggest the ideas that we feel most strongly about and let our users tell us what really “clicks” with them. But the opportunity to lay out this vision in front of our users’ eyes, and ask them to show us the easiest path the get there, is invaluable. Of course, we know what we have to build. Your duty is to do the hard work of anticipating the needs, building the best corresponding product, and delivering it as early as possible. From Ford’s quote about his customers asking for faster horses instead of cars, to Steve Jobs’s total disregard for focus groups and market research, a common trope in product development suggests that you should not ask your users what to build next.
And this brings tangible results: people who’ve worked on problems similar to those described in our roadmap have proactively offered their help! 2. That is what is so powerful about transparency. When you let people in on a secret, they feel so involved that they want it to succeed beyond their personal interest. We value transparency because it makes people happy. Front is all about disseminating information to all those who can benefit from it, thus increasing transparency within companies. Why am I so enthusiastic about it? For three reasons: 1. We expect this public roadmap to be the cornerstone of our (non-support related) user feedback.
#ROADMAP APP FOR TRELLO ANDROID#
the native iPhone app was far more urgent than we anticipated, and 4 times more requested than the Android app: we instantly added it to our next product cycle. The public roadmap has already helped us collect valuable feedback - e.g. Cheerings from our users are great, but it’s even better when we can use it to improve our product. The reaction of our users exceeded our expectations. Optional: Enable public comments (tread carefully - we decided not to).
Make it public (Private > Change Visibility > Public)Įnable public vote (Menu > Power-ups > Voting)
We wanted to keep it clean and simple, so we used Trello’s board organization before switching to Product Board. It was a big decision to make and we put a lot of thought into it (see below for the details), but once we opted for it, it literally took us 2 minutes to launch it. When we feel like a feature is important enough to be prioritized, we move it into our product pipeline, where users can follow its progress, from design to development to shipping. More importantly, users can voice their opinion and vote for the features they most urgently want to see implemented. Our “ public roadmap” is a freely accessible page where our users can find what we’ve shipped recently, what we are currently working on, and some ideas of what we should be doing next.
Today, we still have a public roadmap because we continue to value transparency and accountability. This post details how we did that on Trello and why we did it. Our public roadmap is a freely accessible page where our users can find what we’ve shipped, what we are currently working on, and what we should be doing next.īack in the early days of starting Front, we launched a public roadmap on Trello.
0 kommentar(er)
