These are illustrative scenarios showing how the products are used, not customer case studies.
The same sequence, twice
Today
- Work happens in your app
- Approval in another tool
- A second login
- Adoption stalls
With SynaptaGrid
- Work happens in your app
- Inbox embedded beside it
- Decide without leaving
- Timeline sits on the record
The situation
Sending users somewhere else to approve their own work is where adoption stops. Building the inbox, the decision panel and the run timeline inside the product instead means owning three more screens and all of their states indefinitely.
How it is approached
The task inbox, the decision panel, the run timeline, a state badge, a follow toggle and a start button are ready-made components dropped into the existing interface. The record shows which workflow state it is in and its run history, and a run can be started from the record. Claims are leased, so a task someone opened and abandoned returns to the queue on its own.
What changes
People approve where they already work, with no second login to explain. The process behind the approval can be rebuilt without touching the product it renders inside.