asky.design

Documents. In order.

DESIGN SYSTEM / 01

How I build a system for a data-dense interface, and the workflow with an AI agent — from the first measurement to a new scenario.

Explore the screens
Laptop mockup of the Diadoc dashboard: incoming documents, amounts and statuses
Object
Document workspace for business
Focus
System · scenarios · checks
Format
Research-led redesign
Output
8 screens + a system showcase

A dense interface.
Too many
different rules.

In a document workspace people work with acts, invoices, counterparties and signatures. Details matter: who is waiting for an answer, where the amount is, what is already approved and which action comes next.

An audit of five screens of the original workspace showed the same entities styled differently. My task was to build one shared visual language and test it on the core scenarios.

Where the case stops

The starting point is an audit of a live Diadoc session available to a sole proprietor. The case mockups are a standalone prototype with their own visual system. There is no rollout data and no user metrics.

01

One action,
many styles

The inbox contains 10 visual variants of the same button. The priority of an action has to be read from its label.

10 button styles
02

Same data,
different format

A date changes shape between screens. In the document card the amount loses its thousands separator: 2640.00 ₽.

5 date formats
03

A form with
no visible guide

In the default send state the script found no labels and no required markers. In the prototype they become part of the field.

0 labels in the default state

Same data.
One set of landmarks.

SYSTEM COMPONENTS One rule set
StatusSignedAction required
Data
20 Jul 202623 Dec 20252,640.00 ₽
Action
SignDownloadReject
Status, format and action priority are recognisable on any screen.

Enlarged fragments rebuilt from the audit. They illustrate the rules; they are not screenshots of the original product.

Every decision is
made once.

Colour, spacing, radius and state are fixed in tokens. Components use those values, screens are assembled from components. A change to the foundation spreads across the whole prototype.

Open the system showcase
COLOUR / SEMANTICS

Teal with a role

The primary action, hover and accent use different steps of one palette.

700#00655A
600#008274
500#009B85
100#D8F1ED
Primary button + white text4.72:1
TYPOGRAPHY / HIERARCHY
Аа123

Four weights.
A clear hierarchy.

400500600700
Cyrillic · tabular figures12–32 px
COMPONENTS / STATES

A shared vocabulary

SignedIn approvalSignature requiredRejected
Document number *
Act №394
The field label stays after input
State = text + marker + colour
GEOMETRY / RHYTHM

A 4 px step

Seven spacing values.
Three radius roles.

481216243248
48∞

One system.
The whole working day.

From an incoming document to a signature. Eight scenario mockups and a component showcase.

Incoming documentsExplore the screen
01

Incoming documents

Documents, amounts and statuses are gathered into one table. Selection and the bulk action sit right next to them.

Document cardExplore the screen
02

Document card

Details, files, history and the approval route are available on one screen. The next action carries the main accent.

New documentExplore the screen
03

New document

Field labels, required markers and errors form a single pattern. The state shown is the one that needs correcting.

Document filtersExplore the screen
04

Document filters

Filters expand above the list. Active conditions show as separate tags and keep the context of the search.

CounterpartiesExplore the screen
05

Counterparties

The same table pattern and the same statuses applied to a different object. The system transfers between sections.

Plans and paymentExplore the screen
06

Plans and payment

Plan, limits and invoices use the shared typography. The limit warning carries its own semantics.

Empty and error statesExplore the screen
07

Empty and error states

An empty list, no results, an error and restricted access: each state explains itself and offers a next step.

Approval batchesExplore the screen
08

Approval batches

The sign-off queue shows the waiting step and its deadline. An expanded route explains whose decision the batch is waiting on.

Design system showcaseExplore the screen
09

Design system showcase

Palette, typography, geometry and component states in one place. The full showcase opens in its own tab.

The mockups show styling and states. Sending, signing and approving documents are not connected to a live service. Names, organisations and details are demonstration data.

Original size. Scroll the screen to explore the details.

Open prototype separately
Hypothesis · internal sign-off

Who is holding
the document?

Before a signature, a document can pass through accounting, legal and the manager. A separate queue shows where it stopped and whose decision is needed.

The prototype gained approval batches: waiting time, current step and route. This is a design proposal; its effect on processing time still has to be tested.

See the queue
APPROVAL ROUTEStep 3 of 3

Reconciliation act №394

Internal check before signing

  1. AccountantAmounts and details checked
    01
  2. LawyerApproved with a comment
    02
  3. Manager · youWaiting for your sign-off
    03

The route steps needed again, the banner and the key–value pairs were moved from the document card into the shared component base.

I set the rules.
The agent checks
that they hold.

In this case the process itself is part of the design: I choose the direction, define the boundaries of each task and insist on reproducible numbers.

The agent turns decisions into code and measurements. The output of every step is an artefact you can open, check and change.

ON MY SIDE

Choosing the task and the object
Visual direction
Requirements for evidence

ON THE AGENT'S SIDE

Measurements and prototype assembly
Extracting shared components
Re-checking the rules

  1. 01

    Measure

    Capture the starting values from computed styles across five screens.

    measure.js → before/*.json
  2. 02

    Systematize

    Fix the decisions in tokens and build the shared components.

    tokens.css → base.css
  3. 03

    Assemble

    Test whether the rules transfer across scenarios and onto the new queue.

    make.py → 9 mockups
  4. 04

    Re-check

    Find the deviations with the same script and fix them in the foundation.

    measure.js → after/*.json
THE CHECK FOUND AN ERROR IN MY OWN SYSTEM

The contrast I claimed
had to be recalculated.

The first primary-button colour failed the threshold for normal text. Fixing the token changed buttons on every screen.

White text / primary button
3.484.72
Threshold 4.5:1 · WCAG 2.1
The sources of the process are open for checking.Measurement scriptContrast check

The system is built.
The rules are checked.

The result is an HTML/CSS prototype with a shared foundation and saved measurements. The assessment covers interface consistency, not how much faster people work.

Radii in the inbox
73

Compared on one screen.
No averaging across scenarios.

Date formats
51

Combined across the screens studied.
The system showcase is excluded.

Mockups checked
9screens

Eight scenario mockups
and one component showcase.

0 deviationsin the token values checked
19 / 19contrast pairs measured against a threshold
NEXT CHECK

Test document search, recovering from a form error and passing a sign-off with real users. Then move the agreed rules into the Figma library.

Next case study

LensCare

Analytics that help people care