13.2 marks a big release for the program backlog, we reached out to understand the root of their pain and the core activity it was affecting.
After speaking with our customers during numerous problem interviews, our team honed in on story articulation--giving clarity and distinction to a story--as the activity our users were engaging in with our editor. We then created an activity map to better understand the context of this activity and the actions it involved:
Have a conversation to discover knowledge
Support collaborative story articulation
Invisible part of story articulation process
Provide just enough formatting to support emphasis and clarity
Ongoing changes over finished documentation
We looked back at these principles, which we pinned to our wall, when prioritizing and ranking stories, and to make sure the new editor we were building supported aligned actions. We’d love to hear whether or not you agree, so please let us know how it works for you!
Disclaimer: The statements and opinions expressed in this article are those of the author(s) and do not necessarily reflect the positions of Thoughtworks.