Hide / Unhide Explanations
- Megan Brehman (Unlicensed)
- provide explanation/ add tooltip
The section on the right side of the panel displays the list of all the elements in the process and defines the order of these elements in the document. To change the order, click on an element, drag it up or down then drop it.
In this section it is also possible to hide the type of the element in the document by checking the Hide Element Type box, or hide the element section by checking the Hide box. Every time a change is made, the preview section is updated automatically.
PHASE 1: VALIDATION
GOALS
What problem are we trying to solve?
What’s the goal of this feature?
RESEARCH
Review analytics to validate assumptions. Conduct research to understand why we should develop the feature.
What’s the priority for this feature— why is it more important than others?
What does this feature do? (this is applicable only to new features)
Who is this feature for? How many users will benefit?
This feature is meant for ProcessMaker administrators and Architects
How does it improve the product? How does it relate to our overall product strategy?
It improves the
What technical, business or user assumptions are we making?
*** IMPORTANT: Feature must be validated before moving forward ***
PHASE 2: REQUIREMENTS
| # | REQUIREMENT | TYPE | Priority | DESCRIPTION |
|---|---|---|---|---|
| 1 | ||||
| 2 | ||||
| 3 | ||||
| 4 | ||||
| 5 | ||||
| 6 |
USER PERSONAS
Business Users, Architects
USER STORIES
| # | TITLE | USER STORY | PRIORITY | NOTES |
|---|---|---|---|---|
| 1 | ||||
| 2 | ||||
| 3 | ||||
| 4 | ||||
| 5 |
USER FLOWS
PHASE 3: DESIGN + REVIEW
UI SPECIFICATIONS + MOCKUPS
Outline UI specifications and work with designer to create mockups of the feature. Engage copywriter if content is needed. Make sure all requirements above are taken into consideration. Create link to InVision prototypes for product team to review and comment. Make changes as needed.
MOCKUPS | Jira TICKER | (insert mockups) |
|---|---|---|
INVISION PROTOTYPE LINK | ||
REVIEW STATUS | ||
STAKEHOLDER APPROVAL |
RISKS + QUESTIONS
We need to be aware of any significant, known risks that the project faces. I.e. Are there business requirements unrelated to how the software functions? Do the developers need to take any special parameters into consideration? Is the feature going to be formally announced and if so, when should we engage marketing?
| # | QUESTION | REPORTER | RESOLUTION |
|---|---|---|---|
| 1 | |||
| 2 | |||
| 3 | |||
| 4 |
WHAT WE'RE NOT DOING + FUTURE IDEAS
We also want to detail what this feature does NOT do. This helps us make sure we're considering every aspect. Here we can also capture ideas for the future and how the feature might evolve.
METRICS
How do we measure success? What metrics do we need to instrument and track? We need to put proper tracking in place upfront to measure the outcome of our feature. Unless we know exactly what our users are doing, we won't know how to improve.
List 3 main questions. These will also be our key metrics — to help us understand how our feature or improvement is doing.
| # | QUESTION | METRIC | OUTCOME |
|---|---|---|---|
| 1 | |||
| 2 | |||
| 3 |