From an idea to a signed agreement.

Define the agreement journey

Before there was a product to refine, there was a job to understand: helping business teams prepare an agreement, send it to the right people and know what happened next.

I worked on market research, jobs to be done, journeys and flows. Experience mapping helped frame practical questions: how someone uploads a document, how they learn the preparation tools, and what the signer will see on the other side.

Make preparation a clear sequence

The core flow moves through upload, signers, document preparation and review before sending. Each step gives a distinct decision its own space.

Preparing a document brings together the agreement, its fields and the people responsible for completing them. Keeping that relationship visible matters as soon as a document has more than one signer.

Document preparation: signers, fields and the agreement in one workspace.

Document status gives the sender a view of what needs attention.

Account for the exceptions

The happy path is only part of sending an agreement. The design work also considered self-signing, switching between signers and reassigning a signature request.

Reassignment introduces a responsibility question: who can request a change, and who confirms it? The mapped flow includes the replacement signatory, creator notification and a review step before sending again.

Continue after launch

I stayed involved for roughly a year of post-launch iteration. Handoff work includes clearer self-signing steps, signer switching, templates, reminders and document-status controls.

Those refinements build on the original product foundation. They show the smaller interaction decisions that follow an MVP, alongside the larger work of defining it.

Mobile signing and signature-entry states from the original project artwork.