It’s tedious to keep boards in sync because the data shared between the two is often thought-migration rather than data-migration. The solution for most product teams using Trello public roadmaps is to create an entirely separate board for their public roadmap and a different board (or boards) for their actual roadmaps. Technical details on a public roadmap become a distraction from the things customers do care about. Customers care about how they’ll be impacted by the future of your product. However, customers don’t need the gritty details of how you plan to get from point a to b. #3 Using Trello for a public product roadmap = manually syncing multiple boards □Ī public roadmap lets customers align themselves with your product as it evolves over time - which is especially important for SaaS products. Learn more about his decision to drop UserVoice here. His reason for dropping UserVoice had to with public comments not helping his team or customers achieve desired outcomes. Their reason for discontinuing comments on their roadmap is similar to what we heard from Jonathan Roberts, one of our favorite UX designers from Redgate Software. ![]() To see examples of those challenges just read the comments on Trello’s own public roadmap here. Comments can also create negative perceptions or challenges for product teams. The easiest way (or only way?) to engage with Trello subscribers is via comments.Ĭomments are one way to have transparent conversations, but it’s difficult to have meaningful conversations with Trello users in public comments. There isn’t a way to engage subscribers for more in-depth communication like user interviews, surveys, etc. Subscriber notifications from Trello are high-level updates directly from Trello like when a card is moved to a new column. You can’t subscribe someone on their behalf (like a +1 when you hear feedback similar to something already on your roadmap or backlog) You have to have a Trello account to subscribe The ability to subscribe to a Trello roadmap is awesome for people wanting to stay in the loop. One of the biggest success factors of a product is whether or not you engage with the right users about the right things at the right time. To our next point… #2 It’s not easy to engage stakeholders □ This also makes it impossible to look at subscribers in Trello and use data about your business to separate viable feedback from the noise. You can’t programmatically add subscribers from support tickets or email to understand demand because, unlike most systems of record, Trello uses a username instead of an email address for subscribers. By understanding which stakeholders are interested in roadmap outcomes, you can learn from them, engage them, and ultimately collaborate to create better solutions.Ī Trello roadmap lets people subscribe to a card (which is great!), but what about external people who aren’t using Trello? Stakeholders can also be external people like customers, integration partners, and leads. Stakeholders can be a mix of internal people like developers, support reps, and the CEO. Some roadmaps are useful.- John ✈️ #VMworld □ December 19, 2016 Roadmaps should be inspired by stakeholders.Īll roadmaps are wrong. ![]() One reason why some agile folks don’t find value in roadmaps is because they’re often inspired by the wrong things. :)- Daniel Pasker Novem#1 It’s not easy to add stakeholders □ As products and teams grow, many often struggle to manage feature requests, prioritize a backlog, and communicate their roadmap with Trello is a cluster.
0 Comments
Leave a Reply. |