kuan's profile thumbnail
Thank you for sharing!
alicedefault's profile thumbnail
Thanks for sharing @renaobrien! We've actually been trying to shift from a feature-driven roadmap to a problem-driven roadmap in our team these last few weeks. And this puts words on the efforts :) It's been harder than it sounds though. It's so much easier for everyone on the team to default to refer to what we're building as features vs. problems. Usually because features are 2 words ("voice recorder") when problems are a sentence ("Sending a message by text takes way longer than just recording a voice note, and doesn't have the same human touch to it"). Curious if you are doing this on your side as well and if you have any tips on how to implement it successfully? (We are trying to write our marketing copy before building the feature as well and that's working great, when we remember to do it 😬)