Client work
Contract workflows
Show what changed, and why, before anyone signs.
In one paragraph
Legal teams edit contract workflows every day without being engineers. When a version changed, nobody could see what changed or why, so every audit meant reading two versions side by side. I designed a way to see the difference.
The distance
A contract workflow is structured legal content, run daily by people who aren’t engineers. The system stored every version. People couldn’t see what had changed between two of them, or why. So audits meant reading two flowcharts side by side, box by box.
The working
The change log had to speak in intent, not in edits. “Approval now needs Legal before Finance” instead of “node 14 moved”.
- A visual diff on an infinite canvas. Two versions overlaid, with changed steps marked, like tracing paper over a drawing.
- Changelog cards in plain words. Each card says what changed and why, and links to the step.
- Presence for 10 or more editors at once,Receipt10+ editorsConcurrent presenceMethodReal-time presence designed for ten or more people editing one workflow.SourceEnterprise workflow designer case study (design.izaias.xyz)Checked so people see who else is in the workflow before they collide.
Alongside the product, I grew the design team from 2 to 10Receipt2 to 10Design team grownMethodHeadcount of the design team at start and end of the role.SourceRésumé fact baseChecked and set up a Storybook library with contribution standards, so the team could ship the same components the engineers used.
Receipts
- Audits 70% faster, from days to hours.Receipt70% fasterAudit cycle timeMethodAudits went from days to hours after the visual diff shipped.SourceRésumé fact baseChecked
- Workflow Designer usage up 300% in six months.Receipt+300%Workflow Designer usage in 6 monthsMethodUsage change after the redesign shipped, as recorded in the résumé fact base.SourceRésumé fact baseChecked
- Design team grown from 2 to 10.Receipt2 to 10Design team grownMethodHeadcount of the design team at start and end of the role.SourceRésumé fact baseChecked
Lessons paid for twice
- A diff people can’t read is the same as no diff.
- Describe a change by what it means, then by what moved.
- Shared components are a team’s memory. Write the contribution rules early.