How might we better set user expectations around incremental MVCs?
Challenge
From @annabeldunstone
I’m working on a very bare-bones MVC and have a question. How much information do we give users to let them know that this new feature is MVC and will only be in this state for ~1 release? I’m basically adding a new page with only a select input on it. The next release it will be fairly long form with additional features.
In a Slack thread about setting user expectations around incremental MVCs there were some tips from @uhlexsis
- Open a feedback issue that gives context on the MVC (you’re great at this)
- Making sure the public roadmap/direction pages show how you’ll iterate here (even just linking to the epic)
- Talking about the future iterations in the release posts and demos as Mike mentioned
How might we make these accessible in the handbook for others who may have similar questions to Annabel?
Solution
Add some documentation to the handbook around how to better set user expectation around incremental MVCs. This ideally will:
- Support teams in optimizing for the long term while still being transparent about future iterations.
- Help users understand the UX improvements that they can expect from future iterations.
- Educate users on the long-term vision to reduce any anxiety they could experience around MVCs in the short term.