F.Doc — Enterprise-Grade E-Signature Flows
Role on project
Key Product Designer • Design System • Mobile App • IA
Date
2021-2022
Project Overview
F.Doc is an enterprise platform for electronic document workflows and e-signatures.
The product supports legally binding operations across banking and corporate processes, including complex signing scenarios with multiple roles, multi-stage document states, cancellation of already signed documents, and asynchronous collaboration between participants.
It is a large-scale system with numerous workflows where the cost of user error is particularly high. The interface therefore needs to provide clarity, predictability, and control at every stage of the document lifecycle.
The product supports legally binding operations across banking and corporate processes, including complex signing scenarios with multiple roles, multi-stage document states, cancellation of already signed documents, and asynchronous collaboration between participants.
It is a large-scale system with numerous workflows where the cost of user error is particularly high. The interface therefore needs to provide clarity, predictability, and control at every stage of the document lifecycle.
My Role & Scope
On F.Doc, I was one of the key product designers responsible for user interface design and the evolution of the product’s design system.
My responsibilities included:
My responsibilities included:
- Contributing to the creation and evolution of the F.Doc design system
- Designing core product interfaces and workflows
- Developing scalable UI patterns for complex enterprise scenarios
- Designing around enterprise constraints and legally significant user actions
Product Complexity
Key sources of product complexity included:
- Multiple user roles with different permissions and available actions
- Multi-stage document signing workflows
- Asynchronous processes involving signatures from multiple participants
- Legally significant and potentially irreversible actions
- Dedicated flows for errors, cancellations, resubmissions, and confirmations
Scenario 1 — Document Search & Status-Driven Lists
F.Doc operators work with large volumes of documents simultaneously, making search, filtering, and list navigation part of their everyday workflow.
The document list was designed as a status-driven workspace, where users primarily navigate by the current state of a document and the actions available to them rather than by filename alone.
Search and filtering help users quickly narrow down large document sets while preserving context and reducing the risk of mistakes when working with legally significant data.
The document list was designed as a status-driven workspace, where users primarily navigate by the current state of a document and the actions available to them rather than by filename alone.
Search and filtering help users quickly narrow down large document sets while preserving context and reducing the risk of mistakes when working with legally significant data.
Key UX Principles
- Document statuses are always visible and easy to scan
- Active filters are clearly exposed
- Unavailable filters explain why they cannot be used
- Empty states communicate the reason, not just the absence of results
Scenario 2 — Multiple Signers Flow
In many business scenarios, documents in F.Doc require signatures from multiple participants.
These can include both company employees and external clients, with each participant playing a different role in the overall signing process.
These can include both company employees and external clients, with each participant playing a different role in the overall signing process.
The interface needed to support a transparent and secure multi-party signing experience, ensuring that users always understand:
- Who has already signed the document
- Who is expected to sign next
- What stage the signing process is currently in
- Which actions are available in the current state
Scenario 3 — Cancellation of Signed Documents
F.Doc includes a dedicated workflow for cancelling documents that have already been signed.
From a product perspective, this was one of the most sensitive UX scenarios because it involves legally significant actions and potentially irreversible consequences.
Cancellation was therefore designed as a dedicated process rather than a simple interface action. Users move through a sequence of deliberate steps that make the consequences clear and reduce the risk of accidental or incorrect decisions.
From a product perspective, this was one of the most sensitive UX scenarios because it involves legally significant actions and potentially irreversible consequences.
Cancellation was therefore designed as a dedicated process rather than a simple interface action. Users move through a sequence of deliberate steps that make the consequences clear and reduce the risk of accidental or incorrect decisions.
Operator Experience
Client Side — Mobile App
Design Approach & Learnings
Working on F.Doc reinforced a key principle of enterprise product design: the user experience is shaped less by visual effects and more by state management, process transparency, and error prevention.
Every meaningful action in the product can carry legal consequences. Designing for this environment means making system states, consequences, and available actions exceptionally clear and predictable while protecting users from accidental decisions.
Every meaningful action in the product can carry legal consequences. Designing for this environment means making system states, consequences, and available actions exceptionally clear and predictable while protecting users from accidental decisions.
Next projects
AI-powered platform that automates the entire visa application process — from eligibility assessment and document preparation to interview booking and submission.
Redesigned and launched a federal payment platform for utilities, taxes, fines, and financial services, transforming a legacy portal into a searchable, mobile-first service marketplace.
