...
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Takeaways and itteration iteration will be only conducted for construction permit application flow only due to project scope of the demo application. If the project scope increase to registration new iteration and takeaway will be created. |
From User Testing:
In general user testing was a success. Participants found the wireframes and flow quite efficient and they easily interacted with the prototype without having any major problems.
- Clearly inform the user regarding the payment fee (possible estimated amount and automatic calculation process)
- Identification person/entity
- Simultaneous application. (cancel application part)
- Task flow pages needs iteration ( Some users found confusing - Similar language is needed)
- Add progress bar or steppers or mix
- Add similar design element on task page within the task
- Change task overview to Application Overview
- Create different versions of the flow and share with the team
- Change the review page similar to task overview page
- Information in the Parcel ID page should communicate with the user regarding automatically filling it.
- The map option can be shown more prominently.
- Wording in general.
- Wording for digital signature and task overview page was where most confusion happened (need to be revisited)
- Digital signature service will affect the uploading documents page. Scope in this regard needs to be decided. this not only will affect the flow and UI but also will affect which device our users are using (For example: Estonian version of digital signature drives users to use desktop)
- Add to calendar option should be added during tracking scheduled field visit.
- Application number should be added when application was started and additional related locations.
- add debit/credit card
- Add additional download invoice option/payment proof
- Toast messages (or alternative for notifications and error can be added to scope (Artun Gürkan design Jonas Bergmeier Priit Puru Feedback) / this may also allow us to replace disabled buttons with error notifications through toast.
- Change burger menu, allow users to track application via burger menu/ notification page can be added as a separate wireframes.
...
- Progress bar will be added
- Payment flow feedback needs more explanation during the meeting 21/09/2023
- Approval time/process time should be more clear
- The feedback page needs to be discussed with stakeholders. The feedback page was clear for users but we received feedback to use net promoter ( Artun Gürkan Check https://link.springer.com/article/10.1007/s12208-021-00280-9) For demo purpose this might not be relevant and can be highly depending on the country.
- If the user edit existing information we should notify them these changes will be reflected in the source registry as well.
- More explanation is needed regarding end of the service
...