Problem
There was inconsistency across the UI flows or different transactions/tasks in the application. Our goal was present a consistent, predictable pattern for completing all transactions.
Solution highlights
Clear indication of a task name and the selected entity (to perform the task)
Number or steps involved in the task shown with labels
Indication of completed, current and pending steps
Ability to review/confirm (key details) before submitting
Ability to enter email to receive confirmation
Clear indication of the transaction result, wether success or failure
Indication of when it would come into effect/applied
Ability to export PDF of the confirmation screen
Ability to repeat the same transaction on other eligible entities within the application
Design principles
Focus and present only on the relevant information to the task.
Avoid distraction inform of other navigational elements.
User should be in control of navigation (to proceed, go back, or abort the task/transaction).
Pre-fill information wherever possible, avoid redundant data entry.
User research
The task confirmation email usually goes to the registered email ID on the account. Most of the time our users are bookkeepers, office managers. They need a copy for filing their records. Thus we added the function to add an email ID (in addition to the registered) to receive confirmation. We also added ability to export PDF of the confirmation screen.
Transaction pattern screens
.png)
