Fabian Delven Fabian Delven
Case study · 2026
AI & design workflow

AI Email & Docs Specialist

An AI-assisted workspace that turns communication and documents into organized, actionable work — without taking control away from the person doing it.

Role
Product & interaction design
Type
AI workflow concept
Focus
Knowledge work · clarity
Context

Knowledge workers spend their days reading messages, finding documents, summarizing, drafting, and tracking follow-ups.

This project began as a study of that daily load. The goal was never to automate communication completely — it was to reduce the effort required to understand what actually needs attention.

The problem

Everything competes for attention at once.

Important requests are buried among low-priority messages.

Deadlines hide inside long conversation threads.

Documents are difficult to locate when they are needed.

Responsibilities are not clearly assigned.

People summarize the same information over and over.

Follow-up actions are easy to forget.

User & operational needs

What the work actually requires.

See

Know at a glance what needs a response today versus what can wait.

Understand

Grasp the ask without re-reading an entire thread each time.

Find

Reach the right document in context, not through a separate search.

Act

Turn a message into a reply or a tracked task in one step.

Trust

Stay confident that nothing is sent or filed without a person's say-so.

Not repeat

Avoid re-summarizing the same conversation for different people.

Workflow before the solution

A loop of scanning and switching.

Scan inbox
Read everything to decide what matters.
Hunt for files
Switch apps to find the related document.
Re-summarize
Rebuild context that was already understood.
Draft & track
Write a reply, then try to remember the follow-up.

Every step lives in a different tool, and the context resets each time. The effort goes into re-orienting, not deciding.

Design principles

Clarity over feature quantity.

Attention first

Show what needs a decision before anything else.

Context in place

Bring the thread and files to the decision, not the reverse.

Always a proposal

AI suggests; the person decides. Nothing is automatic.

Remove before adding

Every element earns its place or it is cut.

Proposed system

A single, calm sequence.

The experience organizes work into five steps that always end with the person in control.

  1. 01

    Identify what needs attention

    Surface the messages and documents that genuinely require a decision.

  2. 02

    Explain why it matters

    Give the reasoning — the deadline, the request, the stakes — in one line.

  3. 03

    Connect the relevant messages and documents

    Pull the related thread and files into one place, automatically.

  4. 04

    Suggest the next action

    Propose a reply, a task, or a follow-up — never assume it is final.

  5. 05

    Let the user review and confirm

    The person stays in control of everything before it is sent or finalized.

Role of AI

Assist the thinking, not replace it.

AI handles the repetitive reading and organizing so the person can spend attention on judgment.

Summarize conversations
Identify deadlines & requests
Connect related documents
Draft responses
Extract action items
Organize follow-ups
Flag missing information before it becomes a problem
Human confirmation points

Nothing leaves without a yes.

Three explicit checkpoints keep the person in command of the outcome:

Before a summary is trusted

The person confirms the AI read the thread correctly.

Before a response is sent

Every draft is reviewed and edited before it leaves.

Before an action is finalized

Tasks and follow-ups are approved, not auto-created.

Key screens & diagrams

One screen: attention, context, action.

Inbox — Needs attention AI assist on
Needs attention · 3 Sorted by AI
Due todayMaya · Acme
Contract redline — sign-off needed
Requests your approval on clause 4 before 5:00 PM.
This weekDesign team
Q3 brand review — agenda & deck
Two owners unassigned. Deck draft awaiting your notes.
FYIFinance
Invoice #2214 received
No action required. Filed to Acme · 2026.
AI summary

Maya needs your sign-off on clause 4 of the Acme contract by 5:00 PM today. The redline follows your earlier comment on liability. One question is still open.

Connected documents
Acme_Contract_v4.pdfclause 4
Liability_notes.docyour comment
Suggested action
"Approved on clause 4 as revised. One note: please confirm the liability cap still matches our March agreement before we countersign."
You confirm before sending

Representative interface — click "Review & confirm" to try the confirmation step.

Outcome

AI can support knowledge work without removing user control.

Email and documents stop being passive information and become a clearer system for decisions and action.

5
step review-and-confirm loop
1
screen for attention, context & action
0
actions sent without confirmation
What I learned

Trust is a design material.

  • Users accept AI faster when every suggestion is clearly a proposal, not a decision.
  • Showing why something needs attention matters more than showing more of it.
  • Fewer, well-placed confirmation points beat a wall of settings and toggles.
Next iteration

Where this goes next.

  • Test the attention ranking against real inboxes to measure trust and accuracy.
  • Add lightweight teammate assignment so responsibilities are explicit.
  • Explore a bilingual mode so summaries and drafts adapt to the reader's language.
Fabian Delven
AI & design workflow specialist
"The best design tool you have is a clear question."

Visual documentation

How the experience works.

A practical visual set for reviewing the workflow, responsibilities, system boundaries, and human-control points. Screen imagery remains upload-ready where final interface captures are not yet available.

Before-and-after workflow

From fragmented effort to one guided, reviewable sequence.

SearchRebuild contextAct manually
OrganizeGuide next stepHuman confirms

User journey / service blueprint

The user journey aligned with visible system support.

User
ArriveUnderstandReview
System
GatherStructureRecord

Understandable system architecture

A high-level view of inputs, support logic, review, and output.

People + source materialOrganizing layerReview gateApproved output

Important decision flow

Consequential actions pause for context and explicit confirmation.

Is the information complete?
No → request contextYes → human reviews
Approve, revise, or stop

Screens with annotations

Reserved for final product screens and concise callouts.

Future screen uploadAdd 3–5 interface captures with numbered annotations describing the user need, system response, and confirmation state.

Where AI helps

AI reduces repetitive synthesis without owning the decision.

Raw inputSortSummarizeSuggestProposal

Where humans confirm

People retain authority at every consequential boundary.

AI proposalCheck accuracyEdit / approveUse or share

What is intentionally not automated

The product supports judgment; it does not replace accountability.

No autonomous sending, publishing, or consequential decisionsNo silent changes to approved informationNo replacement for qualified human expertise