Closed Erioldoesdesign closed 3 years ago
Here's a comment from design about an idea or comment
product disscussion etc
Now this issue has 'enough' information for design to start. but designers are still potentially asking questions at this stage.
Ideas on 'what is enough design' for features or changes to features
(Mandatory)What areas of the product or experience are 'touched' by this work/feature?
(Mandatory) Who are the personas/stakeholders to consider?
(Nice to have) How much time do we want design round 1 to take?
(Nice to have) Where can design look for research and/or examples?
(Nice to have) This feature require research/testing?
Papercuts process
Decide as a product and design circle -> Do papecuts get up to Xhr's of design 'thinking' as part of the papercut process.
What are the implications of this papercut for users? is it a 'no-brainer' it will only improve user experience.
If 'complicated' then probably not papercut and needs inception even if its 'light' inception
If 'no brainer' then goes very quickly past design or straight to dev.
e.g. a logo file is rendering pixely and a new logo needs uploading - design might need to prep the file but no further complicated differences
@Erioldoesdesign I closed this issue as it was an example during setting up the process but pinging you because this is where the design ready draft sits
Stage 1 - Ready for inception: Title & assigned to a product person & product curation has been prioritised and will have resource allocated.
Stage 2 - In Inception: Product team have discussed and refined the acceptance criteria. Can be assigned or labelled 'needs design input' or 'needs tech input'