Overview

My role

Context

How I got there

What did we ship and what impact did it have?

Learnings

https://embed.notionlytics.com/wt/ZXlKd1lXZGxTV1FpT2lJd05ERTVNR1ZrTURGak56WTBNVEV4T0dNeVltWmlZekV3WXpaaU1EZGtPQ0lzSW5kdmNtdHpjR0ZqWlZSeVlXTnJaWEpKWkNJNklrWlpTMHBYVWsxM1VteERUWEk1YlhobFNrUklJbjA9

Overview

The project aimed to build a system that allows users to know when others are editing the document and de-risk the issue of versions missing changes. I also designed an interface, powered by a technology that would automatically merge changes from different versions. This would reduce the number of versions created, streamline collaborative editing, and increase productivity and efficiency.

My role

I led the discovery and design efforts for this project from July 2022 - Feb 2023. In addition, I worked alongside an acting Product Manager and an acting Engineering Lead from July - Oct 2022. A dedicated Product Manager and Engineer Manager were not assigned to this project until late Oct 2022, so I was also responsible for the initial product strategy and planning.

Context

What is Ironclad?

Ironclad is a digital platform that connects business and legal teams, manages every aspect of the contract lifecycle, and provides an in-app document Editor for collaboration with their colleagues.

Ironclad terminology

Workflow. An agreement; a contract template (i.e., a document), and the business process connected to it.

Document. The atom of an agreement. Without a contract document, there is no agreement.

Version. Every time the document is updated, either internally or when it’s received from the counterparty and uploaded into the system, a new document version is created.

Challenges

<aside> 😢 Users did not trust the Ironclad Editor because document versions would overwrite each other.

</aside>