-
Notifications
You must be signed in to change notification settings - Fork 0
New requests Product & Design question process
After someone has added a 'New Request' into the Inception Pipe, there will be a series of questions or conversations that those with product and design experience are best placed to ask and suggest. These include:
-
These 'issues' or 'requests' by using the template available in GitHub should have 'enough' information for Discovery, Inception and Design to start/progress. However, Product Managers and/or Designers may still be asking questions (to the requester/s) at this stage. This is in order to gather any missing information that the 'requester' may not be aware of.
-
Product and Design, through the pipe process have ideas on 'what is enough design/research' for new features or changes to features. This typically follows an 80/20 benefit process or a 'MVP or MVF' Minimum viable product or Minimum viable feature.
-
What areas of the product or experience are 'touched' by this work/feature that has not been mentioned by the requester? How can this request 'scope creep'?
-
How much (if any) 'new' UI/UX do we want to introduce? Do the current 'building blocks' (UI frameworks) serve our need?
-
Who are the personas/stakeholders to consider?
-
How much time do we want Discovery, Inception, Design round/s to take? When do we want/need to deliver this work?
-
2 weeks of 3 days? deadline is product curation meeting number 25 on the xth october
-
When do we want it to go into delivery pipe?
-
Is there a Discovery, Inception or Design points/Tshirt size estimation?
-
Do we have time and budget?
-
Where can design look for research and/or examples?
-
Does this request require user-research/user-testing? Can customer support/product support with gathering user testers or will?
-
Are the team and/or community in disagreement about the request?
-
Does the request meet inclusion goals around a global OFN strategy? (e.g. Does this impact other countries/cultures in ways we believe could be unequal?)