Confirmed users
365
edits
Support/Kitsune/Features/AAQ-Process: Difference between revisions
→Open issues/risks
| Line 13: | Line 13: | ||
* Do we need a builder to manipulate the process without code pushes? | * Do we need a builder to manipulate the process without code pushes? | ||
* Are process wizards part of this work? | * Are process wizards part of this work? | ||
* How can users view articles and return to the flow if it's not the right one? | |||
* What's the experience of a new user compared to a returning user? | |||
* How can we increase the visibility of known and trending issues (i.e. java vulnerability) so they don't highjack all the questions in the forum? | |||
* How can we manage the expectations of a user so they know when to expect an answer? And what type of answer they will receive based on their question? | |||
* How do we ensure that users understand all the steps of the process and don't drop out involuntarily? | |||
* How do we measure the success of the flow as a whole and each step individually? | |||
* How can we maximize our visual assets? Can we make the flow visually heavy instead of text heavy? | |||
* How can we capture the maximum relevant information from the user? Can we do anything else on top of the Support API? Can we customize forms per topic? | |||
==Definition== | ==Definition== | ||