This is great! I love how easy it is to move planning and brainstorming into Trello now. No more hours wasted re-writing everything as Trello cards. Love it!
I believe the user stories here are used incorrectly. You haven't actually defined the user stories as things a user would value. You've only specified what a user expects to do which leaves little room for creativity of solutions. Maybe the best solution isn't that the user pays at the end of the drive, maybe instead at the beginning, or as a subscription service. I would love to hear other's thoughts
You have some very valid points @DavLin . We agree with you. User stories should not be specifications, but the starting point for a conversation with developers and designers. Will keep this in mind in our upcoming videos.
@@thoughtflow4846 thanks. I appreciate your response. Must a say that your way of helping reasoning about roles through this mind map exercise is really good
this is another good take on how to explain story mapping, glad i have watched this
This is great! I love how easy it is to move planning and brainstorming into Trello now. No more hours wasted re-writing everything as Trello cards. Love it!
just realised trello can do with this workflow
Clear, lucid and apt. Thank you!
Thank you jimi. Glad you found it useful.
User story mapping disguised as mind mapping is powerful. Great product thinking.
Thanks . Great Catch :)
Which software you are using
What software are you using?
Really enjoy the explanations given - by far the most useful explanation I've seen for the different components of a user story map. Thank you!
Glad it was helpful!
Wow...Insightful and creative product
Thank you!
Really amazing ! Many thx
Glad you like it!
Great demo!
Very helpful.
Glad to hear!
I cannot the mindmapping function on thoughtflow
Hi.. please write to contact@thoughtflow.io . Will schedule a demo for you.
I believe the user stories here are used incorrectly. You haven't actually defined the user stories as things a user would value. You've only specified what a user expects to do which leaves little room for creativity of solutions. Maybe the best solution isn't that the user pays at the end of the drive, maybe instead at the beginning, or as a subscription service. I would love to hear other's thoughts
You have some very valid points @DavLin . We agree with you. User stories should not be specifications, but the starting point for a conversation with developers and designers. Will keep this in mind in our upcoming videos.
@@thoughtflow4846 thanks. I appreciate your response. Must a say that your way of helping reasoning about roles through this mind map exercise is really good