Product Feature UX plan

Product Feature UX plan

What’s the UX plan for?
The UX plan aims to help us designers guide through each single step of designing and documenting product features in a thought out and mindful way. This plan supports us designers and developers and helps everyone to stay in the loop but is open to change and adapt our workflows. It also helps to know the status of a feature. (e.g. in progress/done, document changes, see who’s responsible and if it’s ready for implementation).

Example doc that follow this structure:

First up:
  • Import the checklist into your Todoist
  • Invite collaborators (Designers, UX writers you want to work with, at least 2 collaborators)


  • Create new doc on with your account
  • Add to folder: “Todoist” or “Twist”
  • Edit title of doc to feature name with briefing: problem description, purpose and goals (e.g. Twist: Archiving Channels)
  • Create Dropbox folder with feature name including link to doc and sketch file (In Doist > Todoist / Twist)

Documenting and designing:
  • Add your name to the top as “Creator: Your Name”
  • List supported platforms
  • List user types and states
  • Research and brainstorm UX/UI
  • Write down web/mac user flows and copy
  • Write down iOS user flows and copy
  • Make sure it also works on iPad
  • Test on iPad split screen
  • Write down Android user flows and copy
  • Make sure it also works on Android Tablet
  • Share document with a small group of designers to check if nothing big is missing
  • Document hover states, click areas and useful tooltips
  • Document all possible edge cases and include them
  • Document UI decisions based on localization if needed (eg used icon instead of label) 
  • Document error and time out handling
  • Document dark mode designs

Prototyping helps to avoid any UX flaws and document better.
On Marvel:
  • Start a prototype by naming it [Product Platform – Feature name v1].
  • Share it with the design team by clicking +Add People > Doist team
  • Web/Mac Prototype (optional but preferred)
  • iOS Prototype (optional but preferred)
  • Android Prototype (optional but preferred)
  • Resolve as many comments as possible
  • Document animations, transitions (if needed)
  • Review UX copy by yourself: Take localization into account

Ready for team discussion: