Users could find the sign-off action, but they weren’t sure it worked.

I used usage data to identify our most frequent users and interviewed 15 of them about how they work. Seven raised unprompted that they doubted their sign-off had registered, especially when acting from the list view, where they expected the row to disappear. Combined with the in-app feedback, this pointed to a missing feedback loop, not a findability problem.

The only confirmation was a status change on a panel users were about to leave. This challened their trust in the new system

I added a success toast so confirmation appears where users’ attention already is.

‍Honest content design: The toast says “Sign off received. Your Key Deliverable will update once SAP confirms.” I chose “received” over “complete” because SAP confirms asynchronously, and I didn’t want to promise something the system hadn’t done yet.

‍Not color alone: A green treatment with a check icon, and a 15-second duration so slower readers aren’t rushed.

‍A pattern, not a patch: This lead to implementation of other successful actions getting a toast. Errors are treated differently. The remain inline, where they occurred, with guidance to resolve them. Bulk sign-offs produce a single toast to avoid stacking.

‍Built on the design system: I reused the existing toast for consistency and speed, and designed undo as an inline link since the component has no action slot.

‍Scoped deliberately: Developers proposed a page refresh to remove the signed-off row, but I pushed back because a silent reload is jarring and doesn’t explain what happened. The toast shipped first, and row removal and undo are planned for the next iteration.