Document Management System Project Cover

MY ROLE

Senior UX Designer & Strategist - I led research, synthesis, product strategy, information architecture, workflow design, and usability testing, while guiding two junior designers and partnering with product, engineering, and legal and operational stakeholders.

THE TEAM

UX Designer & Strategist (Me)
2 Junior UI/UX Designers
Product Manager
3 Developers
Legal & operational stakeholders

SKILLS

UX Research
UX Design
Design Strategy
Service Design

TIMELINE

6 Months

Designing how 500+ legal professionals find documents, coordinate handoffs, and move 1,000+ cases forward each week.

The brief started as a request for a better document repository. But once I followed how work actually moved through the firm, the problem became bigger: documents, decisions, ownership, and status were scattered across emails, folders, spreadsheets, and individual memory.

I led the research, strategy, and experience design of a connected Document Management System that brought documents, people, and workflows into one place.

60%

reduction in document
retrieval time

3x

faster workflow
coordination & handoffs

80%

improvement in
document discoverability

Estimated impact based on workflow analysis, task benchmarking, usability testing, and stakeholder validation.

01

Research & Discovery

I started by following how a case moved - not where its files lived.

Every legal matter moved through multiple departments before completion, but there was no shared system
supporting that journey.

Documents travelled through email. Progress was tracked manually. Important context stayed buried in inboxes,
and knowing which version was current often depended on individual memory.

Before thinking about features, I wanted to understand one thing:

How did a case actually move through the firm?

Every legal matter moved through multiple departments before completion, but there was no shared system supporting that journey.

Documents travelled through email. Progress was tracked manually. Important context stayed buried in inboxes, and knowing which version was current often depended on individual memory.

Before thinking about features, I wanted to understand one thing:

How did a case actually move through the firm?

Found in Spam: A short story about one case, too many emails, and a missing document
1 New Case Arrives
2 Passed to Filing
3 Here Comes the Manual Work
4 Sent for Review
5 Version 2. Version 3. Version...?
6 One More Handoff
7 One Week Later...
8 The Search Begins
9 Found in Spam
10 But Which Version?
11 The Deadline Doesn't Wait
12 Just Another Day at the Firm

One document told the story.

I created the “Found in Spam” storyboard to follow one case from:

Intake → Filing → Review → Revision → Handoff

to make the fragmented workflow visible.
What looked like a document-storage problem quickly became a question of

“What happens to ownership, context, and status as a case moves between teams?”

I observed how legal teams handled cases day to day.

Rather than beginning with features, I investigated how documents, information, and responsibility
moved across the organization.

06

Stakeholder
Interviews

12

User
Interviews

03

Contextual
Observation Sessions

200+

Observations

03

Rounds of Usability
Testing

I stepped into the day-to-day reality of legal work. I interviewed, observed, and mapped how documents, information, and responsibility moved across teams.

I shadowed employees as they received cases, created documents, searched for files, transferred work between teams, and responded to status requests.

The workarounds revealed what the existing system wasn’t supporting.

Observation showed patterns that interviews alone could not.

Employees repeatedly:

Relied on
memory
to locate files

Re-entered the
same
information
across
documents

Searched email
threads for
context

Followed up
manually to
understand
case
status

Document Management System Observations - Contextual Inquiry Board

Different roles. Same breakdowns.

I synthesized research across eight legal and operational roles into personas and journey maps.

Their responsibilities differed, but the same problems kept appearing:

  • finding documents
  • understanding ownership
  • managing handoffs
  • identifying the latest version
  • knowing current status

That was my first indication that the problem was not tied to one role or department.

It was systemic.

User Personas
Associate Partner
Associate Partner - Rajesh Sharma
Attorney
Attorney - Ibrahim Akhtar
Engineer - Patent Attorney
Engineer - Patent Attorney - John Thomas
Legal Assistant
Legal Assistant - Aashna Khatri
Paralegal
Paralegal - Mukesh Gill
Assistant Manager
Assistant Manager - Sushmita Das
Senior Manager
Senior Manager - Gyanesh Singh
Administrative Personnel
Administrative Personnel - Dhruv Aggarwal
User Journey Maps
User Journey - Research Questions & Context User Journey - Legal Assistant (UJM-04) User Journey - Assistant Manager (UJM-01) User Journey - Associate Partner (UJM-08) User Journey - Senior Manager (UJM-02) User Journey - Attorney (UJM-07) User Journey - Engineer & Patent Attorney (UJM-03) User Journey - Administrative Personnel (UJM-06) User Journey - Paralegal (UJM-05)
02

Analysis & Synthesis

200+ observations. Five patterns kept repeating.

After each interview and observation session, I captured behaviors, breakdowns, workarounds, questions,
and opportunities.

Across the research, this produced more than 200 observations.

I synthesized them through affinity mapping and thematic clustering to separate
isolated frustrations from recurring patterns.

Octalysis Whiteboard Mapping Sprint Goals and Team Discussion Affinity and Observation Sticky Notes Customer Journey Wireframe Sketches
Competitive Analysis
iManage Work Competitive Analysis
Box Evaluation Box Highlights and Office 365
Office 365 Summary Features and Highlights
DMS Affinity Mapping Clustering

Five themes emerged :

Information access

Finding the correct document depended on knowing where someone had stored or shared it.

Manual processes

Repeated data entry slowed employees down and introduced avoidable errors.

Version management

Employees lacked confidence that they were viewing or editing the most current file.

Workflow visibility

Once work moved to another department, its status and ownership became difficult to trace.

Collaboration

Important decisions and context were distributed across emails, conversations, and individual tracking methods.

These themes shifted the project from features thinking to systems thinking.

Five Key insights that changed the product

01

Finding information was harder than creating it

Design Response: Contextual search.

02

Administrative tasks were consuming valuable legal time.

Design Response: Reusable templates.

03

Version ambiguity created operational risk.

Design Response: Version history and audit trails.

04

Ownership became invisible during cross-team handoffs.

Design Response: Assignment management and workflow tracking.

05

Teams needed one shared operational source of truth.

Design Response: Centralized workflow ecosystem.
03

The Reframe

Leadership initially believed the firm needed a better document repository.

Research revealed that storage alone would not solve unclear ownership, broken handoffs, missing content, repeated followups, or uncertainty around document versions.

Transition from document chaos to structured digital workflow
The brief changed
Document Repository

Document Repository

A place to store files.

Connected Documents Workflow Ecosystem

Connected DocumentsWorkflow Ecosystem

A unified system to connect documents, people, and workflows.

Because the real problem was bigger.

Unclear ownership icon Unclear ownership across teams
Repeated follow-ups icon Repeated follow-ups to check status
Broken handoffs icon Broken handoffs between departments
Document versions icon Uncertainty around document versions
Missing context icon Missing context in emails, folders and chats
Limited visibility icon Limited visibility into case progress.
04

Ideation & Strategy

We had more opportunities than we could responsibly put into V1.

Research surfaced opportunities across document retrieval,
collaboration, workflow visibility, document governance,
templates, automation, analytics, and knowledge management.

The challenge was no longer generating ideas.

It was deciding what mattered most now.

I prioritized opportunities around: Frequency × User Impact × Operational Risk × Technical Effort × MVP Feasibility

MVP
Contextual Search Contextual
Search
Central Repository Central
Repository
Workflow Tracking Workflow
Tracking
Assignment Management Assignment
Management
Reusable Templates Reusable
Templates
Version Control Version
Control
Future
AI-Assisted Retrieval AI-Assisted
Retrieval
Knowledge Management Layer Knowledge
Management Layer
Workflow Analytics Workflow
Analytics

Scenario Mapping

Scenario Mapping Specifications
Opportunity Matrix - Impact vs Effort Prioritization

From research opportunities to user flows

I mapped key scenarios to understand how the primary features would come
together to support end-to-end workflows

Search Search a document
Login Home Search Results Open
Manage Manage a document
Open Edit Version Audit
Templates Create from a template
Login Home Templates Edit Save
Assign Assign work
Open Assign Add Context Update Status Handoff

Strategic Decisions - from constraints to direction

Workflow Ecosystem

Repository →
Workflow Ecosystem

Storage alone would not solve unclear ownership, handoffs, or status.

Folder-First

Folder-First →
Search + Familiar Structure

Users remembered clients, cases, matter IDs, and keywords more reliably than folder paths.

Reusable Templates

Full Automation →
Reusable Templates

Templates delivered immediate value while keeping the MVP technically realistic.

Generic DMS

Generic DMS →
Workflow-Specific Experience

The platform was structured around the firm's operating model rather than forcing users into a generic hierarchy.

Experience Principles - guiding the design

Find without relying on memory

Find without relying on memory

Make ownership visible

Make ownership visible

Reduce repetitive work

Reduce repetitive work

Preserve document integrity

Preserve document integrity

Keep work connected

Keep work connected

Information Architecture

Legal professionals think about work through clients, matters,
cases, owners, statuses, and tasks. The IA supports
multiple routes to the same information.

DMS Home Search Matters Documents Workflow Templates Settings / Admin My work Recent matters Recent documents Pending approvals Favorites All Documents Matters Clients People Matter Detail Overview Documents People Tasks / Workflow History Permissions All Documents Recent Shared With Me Favorites Document Detail Content / Preview Metadata Workflow Versions Audit Activity Share & Access Assigned to Me Assigned by Me Team Queue Completed Template Library Template Detail Create From Template Users & Roles Permissions Metadata / Taxonomy Template Management Search what you remember Create from approved templates Control access and permissions Track task progress View, manage and share documents
Information Architecture Site Map
05

Formulation & Application

Designing for speed and context.

I translated the research findings into a product structure that helped legal teams find, act, and collaborate without losing the case context.

“

Legal teams didn’t just need to find documents faster. They needed to see the full context around the work so they could act with confidence.

— Legal Associate

From the reframe to the system

The research revealed that the problem was not just document storage, it was the effort of finding the right information, understanding the full context, and coordinating next steps. I translated this into three core product requirements.

01

Flexible retrieval

Make it easy to find the right information without relying on memory or folder paths.

02

Connected case context

Keep documents, matter details, people, and history together in one place.

03

Visible ownership and handoffs

Show who owns what, where it is in the workflow, and what happens next.

From structure to core flows

I mapped the key end-to-end flows to validate that the structure supported real user tasks.

01

Find a document

Search → refine → results → open
Search by keyword, client, matter ID
1 Search by keyword, client, matter ID
Refine with filters
2 Refine with filters
Open in context
4 Open in context
See relevant results
3 See relevant results
02

Create from a template

Templates → select → retrieve case data → populate
Browse templates
1 Browse templates
Select template and add case info (e.g. IRN)
2 Select template and add case info (e.g. IRN)
Pre-filled content in a new document
3 Pre-filled content in a new document
03

Coordinate a handoff

Workflow → stage/status → assign → next step
View workflow and status
1 View workflow and status
Assign to owner with message
2 Assign to owner with message
Next owner sees the task
3 Next owner sees the task
WHAT THIS UNLOCKED
→

The structure was now clear.

Next, I designed the final experience around the recurring needs uncovered in research.

Retrieval, context, and ownership stay connected, helping legal teams move faster, with less manual effort.

06

The Final Experience

A workflow ecosystem for everyday legal processes

Rather than organizing the solution by screens, I designed around five recurring employee needs.

01 Find
02 Context
03 Ownership
04 Templates
05 Trust
01

Find it without remembering where it lives.

CONTEXTUAL SEARCH
RESEARCH SIGNAL

Retrieval often depended on memory or knowing an exact folder path.

PRODUCT RESPONSE

Search by client, matter ID, case number, keywords, document type, owner, or status with combinable filters.

Client Matter ID Case Number Status Keywords Document Type Owner
Multiple routes to
the right document.
DMS
AT
Alex Thompson

Search

All content
Acme Technologies Ltd.
MAT-00427
Agreement
Approved
42 results
Sort by: Relevance ⌄
Name ⇅ Type Matter Client Owner Modified ⇵ Status
Mutual Non-Disclosure Agreement.docx Contracts › NDA
Contract
MAT-00427 Acme Technologies Ltd.
Acme Technologies Ltd.
AT
Alex Thompson
12 May 2024, 10:24 Approved
NDA - Acme Technologies.pdf Contracts › NDA
Contract
MAT-00427 Acme Technologies Ltd.
Acme Technologies Ltd.
SC
Sarah Chen
10 May 2024, 14:11 Approved
Vendor Agreement - Beta Innovations.xlsx Contracts › Vendor Agreements
Contract
MAT-01562 Beta Innovations Inc.
Beta Innovations Inc.
RB
Robert Brown
8 May 2024, 16:03 In Review
Service Agreement - Global Solutions Contracts › Service Agreements
Contract
MAT-00918 Global Solutions
Global Solutions
JD
Jane Doe
29 Apr 2024, 11:08 Approved
Mutual NDA - Draft.docx Contracts › NDA
Contract
MAT-00427 Acme Technologies Ltd.
Acme Technologies Ltd.
EM
Emily Martinez
22 Apr 2024, 13:42 Pending
Client Service Terms.pdf Contracts › Client Agreements
Contract
MAT-02110 SupplyCo
SupplyCo
AT
Alex Thompson
18 Apr 2024, 09:30 Approved
Power of Attorney.docx Legal › Power of Attorney
Legal
MAT-00391 Wayne Enterprises
Wayne Enterprises
SC
Sarah Chen
15 Apr 2024, 14:20 Archived
Employment Agreement.pdf HR › Employment Agreements
HR
MAT-01745 Internal
Internal
RB
Robert Brown
10 Apr 2024, 11:16 Approved
Showing 1-8 of 42 results
02

See the whole matter in one place.

CONNECTED MATTER WORKSPACE
RESEARCH SIGNAL

Context was split across emails, folders, people, and individual trackers.

PRODUCT RESPONSE

Bring documents, matter information, ownership, people, status, history, and related tasks into one shared environment.

Context stays
with the matter.
DMS
AT
Alex Thompson

Welcome back, Alex

Upload document
Create new matter
Generate from template
Create task / workflow

Recent matters

View all →
MAT-00427
Commercial Partnership Agreement
Acme Technologies Ltd.
Active
MAT-00918
Master Services Agreement
Global Solutions Inc.
In Review
MAT-01562
Vendor Agreement
Beta Innovations
Active
MAT-02110
Client Engagement Agreement
SupplyCo
Pending

Recent documents

View all →
Name Matter Type Modified ↕ Owner Status
W
Mutual Non-Disclosure Agreement.docx Agreement
MAT-00427 Agreement 12 May 2024
10:24 AM
AT
Alex Thompson
Approved
人
Commercial Partnership Agreement.pdf Contracts
MAT-00427 Agreement 10 May 2024
02:11 PM
SC
Sarah Chen
In Review
X
Pricing & Terms Schedule.xlsx Financials
MAT-00427 Spreadsheet 8 May 2024
04:03 PM
RB
Robert Brown
Approved
W
Counterparty Redline.docx Drafts
MAT-00427 Agreement 6 May 2024
11:20 AM
EM
Emily Martinez
Draft
人
Board Approval Memo.pdf Internal
MAT-00427 Report 2 May 2024
03:14 PM
AT
Alex Thompson
Approved

Commercial Partnership Agreement

• Active
MAT-00427 | Acme Technologies Ltd.
Practice area Commercial
Matter owner
AT
Alex Thompson
Current stage Agreement Review
Next deadline
24 May 2024
12 Documents
3 Open tasks
4 People involved
24 May 2024 Next deadline

Recent documents

Name Type Version Modified ↓ Owner Status
W
Commercial Partnership Agreement.docx Agreements
Agreement v2.1 12 May 2024
10:24 AM
AT
Alex Thompson
Approved
人
Client Service Terms.pdf Client Documents
Contract v1.4 10 May 2024
02:11 PM
SC
Sarah Chen
Approved
X
Vendor Evaluation Matrix.xlsx Supporting Documents
Workbook v1.0 8 May 2024
04:03 PM
RB
Robert Brown
In Review
W
Draft Agreement.docx Drafts
Agreement v0.9 6 May 2024
11:20 AM
EM
Emily Martinez
Draft
人
Due Diligence Report.pdf Research & Analysis
Report v1.2 2 May 2024
03:14 PM
AT
Alex Thompson
Approved
Showing 1–5 of 12 documents
03

Know who owns it and what happens next.

WORKFLOW + ASSIGNMENT MANAGEMENT
RESEARCH SIGNAL

Ownership became unclear during cross-team handoffs.

PRODUCT RESPONSE

Make current owner, workflow stage, status, pending action, and next step visible.

This is the coordination
problem made visible.
DMS
AT
Alex Thompson

Workflow

Track and manage tasks across matters, from review to execution.

Matter ↑ Task Stage Status Assignee Due date Priority
MAT-00427 Commercial Partnership... Review final draft Agreement Review In Progress
AT Alex Thompson
18 May 2024 High
MAT-00427 Commercial Partnership... Send to client Client Review Not Started
SC Sarah Chen
20 May 2024 Medium
MAT-00427 Commercial Partnership... Prepare signature package Execution Not Started
EM Emily Martinez
24 May 2024 High
MAT-01562 Vendor Agreement Update commercial terms Legal Review In Progress
RB Robert Brown
28 May 2024 Medium
MAT-00918 Client Engagement... Submit for regulatory filing Regulatory In Review
AW Andrew Wilson
3 Jun 2024 Medium
MAT-00391 Master Services... Follow up on diligence questions Due Diligence Blocked
AC Alex Chen
25 Apr 2024 High
MAT-00356 Vendor Agreement Prepare final agreement Execution Not Started
JP Jamie Park
2 May 2024 Medium
MAT-00312 Client Engagement... Confirm client details Intake In Progress
ML Morgan Lee
28 Apr 2024 Low

Task details

Review final draft In Progress
Matter
MAT-00427 Commercial Partnership Agreement
Stage Agreement Review
Status In Progress
Assignee
AT Alex Thompson
Due date
18 May 2024
Priority
High
Description

Review the final draft of the Commercial Partnership Agreement and incorporate internal and client feedback.

Upcoming deadlines

View all →
24 MAY
Signature package MAT-00427
High
28 MAY
Client review MAT-01562
Medium
03 JUN
Regulatory filing MAT-00918
Medium
04

Reduce Repetitive Work

APPROVED TEMPLATES FOR CONSISTENCY

Pre-approved templates helped legal teams create documents faster and with fewer errors, reducing repeated data entry and improving consistency.

  • Template library by document type
  • Pre-filled fields and guidance
  • Maintain version control and approvals
Start from an
approved template.
DMS
AT
Alex Thompson
Templates

Start from approved templates and generate documents faster.

Contracts ×
Approved ×
United States ×
Clear all
Mutual Non-Disclosure Agreement
Contracts

Standard mutual non-disclosure agreement with customizable terms for commercial engagements.

● Approved v3.2
Service Agreement
Contracts

Service agreement for professional services with standard terms and conditions.

● Approved v2.1
Vendor Agreement
Contracts

Vendor agreement for goods and services with commercial and compliance terms.

● Approved v1.4
Employment Agreement
Employment

Employment agreement with standard terms, compensation and confidentiality provisions.

● Approved v2.0
Legal Notice
Corporate

Template for legal notices and formal communications.

● Approved v1.1
Power of Attorney
Corporate

General power of attorney with customizable scope and jurisdiction clauses.

● Approved v1.3
Selected template
Mutual Non-Disclosure Agreement
● Approved
Category Contracts
Version v3.2
Maintained by Legal Operations
Jurisdiction United States
Last reviewed 5 Mar 2024
Create a document from this template
1
Select matter Choose the matter to generate a document for.
MAT-00427
Acme Technologies Ltd.
2
Review pre-filled fields The following fields will be pre-filled from the matter.
Client name Acme Technologies Ltd.
Matter ID MAT-00427
Effective date 12 May 2024
Jurisdiction United States
3
Generate document Review the document and make any final changes before creating it in the matter.
Templates › NDA Template › Create Document
1 Fill details
2 Review & edit
3 Finalize
Create from Template

Fill in the key details and generate a customized document.

NDA Template
Standard non-disclosure agreement with key clauses and guidance.
Basic information
📁 MAT-00427 - Commercial Partnership Agreement
🏢 Acme Technologies Ltd.
Mutual NDA
📅 10 May 2024
United States
Additional details
All business, technical, and financial information shared between the parties for the purpose of exploring a commercial partnership.
3 years
MUTUAL NON-DISCLOSURE AGREEMENT

This Mutual Non-Disclosure Agreement (“Agreement”) is entered into on 10 May 2024 by and between Acme Technologies Ltd. (“Disclosing Party”) and Global Solutions Inc. (“Receiving Party”), each a “Party” and together the “Parties”.

1. Purpose

The purpose of this Agreement is to enable the Parties to explore a potential commercial partnership and share certain confidential information in connection with such discussions.

2. Confidential Information

“Confidential Information” means all business, technical, and financial information shared between the parties for the purpose of exploring a commercial partnership, whether written, oral, or in any other form.

3. Term

This Agreement shall commence on 10 May 2024 and shall remain in effect for a period of 3 years, unless earlier terminated in accordance with Section 8.

4. Governing Law

This Agreement shall be governed by and construed in accordance with the laws of the United States.

05

Maintain Trust

VERSION HISTORY & AUDIT TRAILS

Employees could verify the latest version, review activity, understand ownership, and restore previous versions without leaving the document.

  • Granular version timeline & audit trails
  • Clear attribution by author and timestamp
  • One-click restore without leaving the doc
See history.
Know who changed
what. Restore
if needed.
DMS
AT
Alex Thompson
Home › Document Center › MAT-00427
Commercial Partnership Agreement.docx
Approved
MAT-00427 | Acme Technologies Ltd.
1 / 12
100%

COMMERCIAL PARTNERSHIP AGREEMENT

This Commercial Partnership Agreement (the “Agreement”) is entered into on 12 May 2024 (the “Effective Date”) by and between Acme Technologies Ltd., a company incorporated under the laws of the United States (the “Company”), and Beta Innovations Inc., a company incorporated under the laws of the United States (the “Partner”), collectively referred to as the “Parties”.

1. Purpose

The purpose of this Agreement is to establish a strategic partnership between the Parties to collaborate on the development, marketing, and distribution of certain products and services in accordance with the terms and conditions set forth herein.

2. Scope of Collaboration
2.1

The Parties agree to work together to identify and pursue mutually beneficial business opportunities in the markets specified in Exhibit A.

2.2

Each Party shall contribute its respective resources, expertise, and personnel as agreed in writing from time to time.

Version history
W
v2.1 12 May 2024, 10:24 AM
AT Alex Thompson
Current

Updated commercial terms and signature blocks.

W
v2.0 10 May 2024, 02:11 PM
SC Sarah Chen

Client revisions incorporated.

W
v1.3 8 May 2024, 04:03 PM
RB Robert Brown

Internal legal review edits.

W
v1.0 5 May 2024, 11:20 AM
EM Emily Martinez

Generated from approved template.

Version activity
View all →
Version 2.1 approved 12 May 2024
10:24 AM
Document approved and published.
Version 2.1 edited 12 May 2024
09:15 AM
Alex Thompson made changes to commercial terms and signature blocks.
Version 2.0 uploaded 10 May 2024
02:11 PM
Sarah Chen uploaded a new version.
07

Validation & Iteration

Testing with users to refine and strengthen.

I conducted 3 rounds of moderated usability testing with 6 legal professionals, focusing each round on a critical product risk. Each iteration reduced ambiguity, improved task success, and increased confidence before implementation.

“It finally feels intuitive.
I can find what I need and
understand who owns it
without asking around.”

— Legal Professional
01

Round 1 — Ownership

TASK: IDENTIFY AND MANAGE ASSIGNED DOCUMENTS
Before: My Tasks navigation menu
After: Assigned tasks with status indicators
Before
After
Finding icon Finding

“Assigned to me” and “assigned by me” were difficult to distinguish.

Change icon Change

Clearer task states, ownership labels, avatars, and status indicators.

02

Round 2 — Retrieval

TASK: FIND A SPECIFIC DOCUMENT USING FILTERS
Before: Basic document search list
After: Filtered search with active filter chips
Before
After
Finding icon Finding

Users expected filters to work together but were unsure which filters were active.

Change icon Change

Persistent multi-filter search with visible active filters and easy filter removal.

03

Round 3 — Version Trust

TASK: CHECK DOCUMENT HISTORY WITHOUT LEAVING
Before: Document action menu
After: Embedded version history sidebar
Before
After
Finding icon Finding

Users wanted to see version history and key changes without leaving the document.

Change icon Change

Embedded version history with quick-access audit information.

Other usability learnings

Users preferred search over deep folder navigation
Clearer naming conventions reduced errors
Status labels needed consistent language across departments
Templates saved significant time for recurring documents
Visual workflow stages increased accountability
Context and metadata were as important as the document itself
Iterative testing helped us solve real user challenges before development.
08

Impact

What changed and what the system made possible.

A connected system reduced time spent searching for documents, improved cross-team coordination,
and created greater visibility, accountability, and confidence across everyday legal workflows.

60%
estimated reduction in document-retrieval time
3×
estimated faster workflow coordination and handoffs
01

Employee Impact

  • Less time spent searching for documents.
  • Less repetitive administrative entry.
  • Greater visibility into case status and ownership.
  • More confidence around document versions.
02

Team Impact

  • Clearer cross-team handoffs.
  • Less reliance on email for status updates.
  • Shared visibility into case progress.
03

Organizational Impact

  • A centralized source of information.
  • Greater accountability across workflows.
  • A foundation for future automation and analytics.
“We went from chasing updates across emails and folders to having a single place where everyone can see the latest status, ownership, and documents. It has made our work significantly faster and more transparent.”

— Legal Operations Stakeholder

09

Reflection

This project changed what I thought
I was designing.

I started with a document-management problem.
I ended up redesigning how information, ownership, decisions, and case progress
moved through an organization.

The project pushed me beyond interface design into research, systems thinking,
workflow strategy, product prioritization, and stakeholder alignment.

01

Research changed the
brief.

Following cases across departments revealed a broader challenge than the original repository request.

02

Constraints sharpened
the product.

Prioritization forced us to address recurring, consequential problems before expanding the feature set.

03

Visibility became part of
the experience.

Some of the most important improvements were making ownership, context, status, and next steps visible when employees needed them.

DMS
AT
Alex Thompson

Welcome back, Alex

Upload document
Create new matter
Generate from template
Create task / workflow

Recent matters

View all →
MAT-00427
Commercial Partnership Agreement
Acme Technologies Ltd.
Active
MAT-00918
Master Services Agreement
Global Solutions Inc.
In Review
MAT-01562
Vendor Agreement
Beta Innovations
Active
MAT-02110
Client Engagement Agreement
SupplyCo
Pending

Recent documents

View all →
Name Matter Type Modified ↕ Owner Status
W
Mutual Non-Disclosure Agreement.docx Agreement
MAT-00427 Agreement 12 May 2024
10:24 AM
AT
Alex Thompson
Approved
人
Commercial Partnership Agreement.pdf Contracts
MAT-00427 Agreement 10 May 2024
02:11 PM
SC
Sarah Chen
In Review
X
Pricing & Terms Schedule.xlsx Financials
MAT-00427 Spreadsheet 8 May 2024
04:03 PM
RB
Robert Brown
Approved
W
Counterparty Redline.docx Drafts
MAT-00427 Agreement 6 May 2024
11:20 AM
EM
Emily Martinez
Draft
人
Board Approval Memo.pdf Internal
MAT-00427 Report 2 May 2024
03:14 PM
AT
Alex Thompson
Approved

Commercial Partnership Agreement

• Active
MAT-00427 | Acme Technologies Ltd.
Practice area Commercial
Matter owner
AT
Alex Thompson
Current stage Agreement Review
Next deadline
24 May 2024
12 Documents
3 Open tasks
4 People involved
24 May 2024 Next deadline

Recent documents

Name Type Version Modified ↓ Owner Status
W
Commercial Partnership Agreement.docx Agreements
Agreement v2.1 12 May 2024
10:24 AM
AT
Alex Thompson
Approved
人
Client Service Terms.pdf Client Documents
Contract v1.4 10 May 2024
02:11 PM
SC
Sarah Chen
Approved
X
Vendor Evaluation Matrix.xlsx Supporting Documents
Workbook v1.0 8 May 2024
04:03 PM
RB
Robert Brown
In Review
W
Draft Agreement.docx Drafts
Agreement v0.9 6 May 2024
11:20 AM
EM
Emily Martinez
Draft
人
Due Diligence Report.pdf Research & Analysis
Report v1.2 2 May 2024
03:14 PM
AT
Alex Thompson
Approved
Showing 1–5 of 12 documents

The strongest enterprise
products don’t simply
improve screens.

They improve how
people work together.

Research strategy system.