- Participatory roadmap on Figma: https://www.figma.com/board/dPjd7qeD5Za3euRISrqjIY/Participatory-Roadmap?t=OFuaVPpuTLypvHwQ-1
- Drive with session deck and prototype link: https://drive.google.com/drive/folders/1d_76Sm4YcCaIgI7TWsTe7VYAlf7FFKrB?usp=sharing
This week, our team did participatory roadmap testing to get a better idea of what people would actually want from Pip. We had participants sort different features into three categories: Build Soon, Build Later, and Build Much Later.
What We Learned
Looking at all 12 roadmaps, we noticed that a lot of people cared about the same things. Most wanted Pip to be good at summarizing meetings, keeping track of action items, and making sure tasks were assigned to the right people. Something else that came up was wanting to double-check or edit what Pip generates before it does anything, which makes sense because nobody wants an incorrect task or email sent out for them.
There were some differences in what people wanted next. Some thought integrations with Google Calendar and Slack should be a priority, while others felt those could wait. Things like customizing Pip’s appearance, adding more animations, or having detailed analytics were usually pushed to much later.
What’s Next?
Going forward, we want to focus on improving the features Pip already has before trying to add a bunch of new ones. The roadmaps helped us see that even though we have a lot of ideas for what Pip could eventually do, people mostly just want something that works well and makes their meetings less of a hassle.
