Skip to content

untool.ai — manifesto, research, credo

A tool that asks to be noticed is a tool that interrupts. The best tools disappear into the task. We are building toward that disappearance.

This document is the source of truth for the brand. Design tokens, voice, and component decisions in app/design-system/ are derived from what is written here — not the other way around.

1. The premise

Software has gotten louder. Every product wants attention, a confirmation, a celebration, a chrome of its own. The cost of that loudness is the user's attention — the only real budget in any session.

The premise of untool is simple: the point of a tool is not the tool. It is the work. So we will, with discipline, take tooling away — menus, modes, management, configuration, dashboards-about-dashboards, decorative motion, celebratory chrome — until what remains is the work and the result.

The "un" is active. Like unlock, unfold, uncover. To untool is to dismantle the friction between intention and outcome.

We are not building "minimalism." Minimalism is a style. Untool is a discipline: the rigorous removal of anything that does not serve the act.

2. Heritage — where this thinking comes from

Heidegger — Zuhandenheit

In Being and Time (1927), Martin Heidegger draws a distinction between two modes of an object:

  • Vorhandenheit — present-at-hand. The object as theme; you stare at it.
  • Zuhandenheit — ready-to-hand. The object as extension; you act through it. The hammer in use is not noticed — the nail is noticed. Heidegger says the hammer's "tool-being" is invisible until it breaks, at which moment it becomes painfully vorhanden again.

The aspiration of every screen we ship is ready-to-hand. If the user notices the screen as a screen, we have failed somewhere — usually by adding something we could have removed.

Edward Tufte — graphical integrity, data-ink

From The Visual Display of Quantitative Information (1983) and Envisioning Information (1990):

  • Graphical integrity. "Above all else show the data." The number is right. The unit is present. The source is visible. Aesthetics serve the truth, never the reverse.
  • Data-ink ratio. The ink that is not data is doing harm. Erase non-data ink. Erase redundant data ink. Revise and edit.
  • Small multiples. Repeated structure with varying content. The eye compares; the layout disappears.
  • Sparklines. Data, words, and graphics on the same plane — at the scale of a sentence. The chart is a glyph, not a stage.
  • No chartjunk. Decorative gridlines, gratuitous 3D, vibrating moiré, the "duck" of pictorial frames — all forbidden.

Tufte tells us: a UI is also a display of information. The pixel that does not inform is doing harm. We will measure ourselves by this.

Dieter Rams — the ten principles

Rams (Braun, 1955–1995) gives us a checklist we still cannot beat:

  1. Good design is innovative.
  2. Good design makes a product useful.
  3. Good design is aesthetic.
  4. Good design makes a product understandable.
  5. Good design is unobtrusive.
  6. Good design is honest.
  7. Good design is long-lasting.
  8. Good design is thorough down to the last detail.
  9. Good design is environmentally friendly.
  10. Good design is as little design as possible. Weniger, aber besser.

Less, but better. We post #5 and #10 on the wall.

Don Norman — affordances and signifiers

From The Design of Everyday Things (1988, rev. 2013):

  • An affordance is what an object permits. A door affords pulling or pushing.
  • A signifier is the visible cue that signals which affordance is intended.
  • Doors should not need labels. Interfaces should not need tutorials.

When we write a tooltip, we have already failed once. When we add an empty state with three paragraphs of explanation, we have failed twice.

Steve Jobs & Jony Ive — think different, simplicity is sophistication

Jobs's Stanford commencement (2005), Ive's design notes for the original iPhone, the Apple "Think Different" campaign (1997) — all converge on the same practice: removing is harder than adding. The thing you cut is the thing you designed. The genius is choosing what not to ship.

Ive on the iPod click wheel: "It was about making something feel inevitable." Inevitability — the form that, once seen, could not have been any other way — is the destination of every component we build.

Bret Victor — Magic Ink, ladders of abstraction

Victor (2006, 2011): a good interface is information software before it is control software. It answers questions. It collapses the gap between "what is true now?" and "what should I do?" Direct manipulation of the thing itself beats forms about the thing every time.

John Maeda — the laws of simplicity

From The Laws of Simplicity (2006):

Reduce. Organize. Time. Learn. Differences. Context. Emotion. Trust. Failure. The one — simplicity is about subtracting the obvious and adding the meaningful.

Maeda gives us SHE: Shrink, Hide, Embody. When you cannot remove a thing, shrink it. When you cannot shrink it, hide it until needed. When you cannot hide it, give it the quietest body you can.

Massimo Vignelli — the discipline

Vignelli (1972 NYC subway map, American Airlines, Knoll): the discipline of restraint. A small set of typefaces. A small set of grids. A small set of colors. The system is the value; the variations are derived. Vignelli told designers: "if you do it right, it will last forever."

We have one type family. We have one accent color. We have one set of spacing steps. We do not introduce a second of any of them.

Susan Kare — humane pictograms

Kare (Mac OS, 1983; Susan Kare, Inc.): icons that are friendly without being cute, legible at 16 pixels, and embedded in the system as native nouns. Our iconography aspires to this: line-weight consistent, optical sizes considered, no two icons doing the same job.

Apple HIG, Material, IBM Carbon — what we borrow, what we don't

We borrow:

  • The 8-point spatial grid (Material).
  • Type ramps anchored to the body size (HIG).
  • Tokenization of color, type, motion as design primitives (Carbon).
  • Reduced-motion respect (everyone).

We don't borrow:

  • Elevation as a primary metaphor. Tufte teaches that depth is rarely earned. We prefer rules (1px lines) over shadows.
  • Floating action buttons. The primary action lives inline with the thing it acts on.
  • Decorative motion. Springs, bounces, celebrations.

3. The credo

These are the operating principles. Disagreements with them are escalations, not preferences.

  1. The work, not the tool. Every screen asks: what is the user doing right now? Show that. Hide everything else.
  2. Truth before flair. Numbers are right. Units are present. Sources are visible. Aesthetics serve clarity, never the reverse.
  3. Quiet by default. Color is information. Motion is meaning. Reserve emphasis for what changed.
  4. Direct manipulation, where it can be earned. Act on the thing, not on a form about the thing.
  5. Density with respect. Information-dense screens are a kindness to the expert. We do not under-serve them with toy layouts.
  6. Reversibility. Every action that can be undone, can be undone. Confidence is built on safety.
  7. One thing well. Components do one thing, with edges. Compose them. Don't enrich them.
  8. The grid is real. Vertical rhythm and horizontal rhythm are visible promises. We do not break them.
  9. No fonts of intimidation. Display type announces nothing. The reader's eye should not be pried open.
  10. Disappear. The highest state of the interface is to be forgotten in the act of being used.

4. What we will not do

We name these so we don't have to argue them again.

  • Skeuomorphic chrome. We are not pretending to be a clipboard, a receipt, or a typewriter.
  • Decorative gradients. A gradient must encode magnitude or it does not ship. (See: heatmaps, sparkline fills.)
  • Bouncy animations. Springs are loud. Easing is calm.
  • Celebration animations. A task done is its own reward.
  • Empty dashboards as decoration. A widget without a question is theater.
  • Notifications that aren't actionable. A red dot you can't act on is anxiety, not information.
  • Tooltips that explain layout. If you need a tooltip to explain a control, the control is wrong.
  • Loading spinners as a hide-the-truth. Show structure (a skeleton), show progress (a bar), or tell the user honestly that you don't know.
  • More than one accent color. One signal. One.
  • Sentence-case headlines as Title Case Marketing Copy. We write like adults talking to adults.

5. What we will measure

These are the brand's metrics. They live in dashboards, not in the manifesto.

  • Time to first useful action. From cold load to user doing the thing they came for. Target: < 3 seconds for returning users.
  • Glanceability. Can the screen be read in 1.5 seconds and acted on in 3? We test with five-second tests on every new layout.
  • Decision integrity. Did the user have the right information at the moment of choice? We instrument which fields preceded which choices.
  • Recoverability. How far back can you walk a mistake? Target: every destructive action is undoable for at least 30 seconds.
  • Per-pixel information density. Tufte's data-ink ratio, applied to UI. We do not let it slip below a threshold per screen class.

6. Voice and tone

The voice is the same on a landing page, in an error message, and in a release note: calm, precise, useful.

  • We tell the truth, including unflattering truths. ("This took longer than it should.")
  • We do not write copy in exclamatory tense. No "Awesome!" No "Boom!"
  • We do not use the word "magic." If it works, explain how. If it doesn't, say so.
  • We do not use product jargon as decoration. Every technical term means what it means.
  • Sentence-case headlines. American English. Oxford comma.
  • Verbs over nouns. ("Search sources" over "Source search.")
  • Numbers in numerals from 10 onward; words for one through nine — except in data, where numerals always win.

A full voice guide lives at VOICE.md.

7. The mark and the name

untool.ai

Lowercase. The dot is a hinge, not a flourish.

The wordmark is set in our type. The un is lighter (weight 400). The tool is heavier (weight 600). The .ai is muted (the brand's --ink-subtle). As soon as you read it, the un recedes and the work — the tool, the substance — takes the visual weight. The mark performs the idea.

The brand has no logo beyond the wordmark. We do not commission an icon. A favicon is the wordmark cropped to u·. A social card is the wordmark on paper. There is no third option.

See app/design-system/brand/Wordmark.tsx for the canonical implementation.

8. How to use this document

  • If you are about to add an animation, re-read §4.
  • If you are about to add a second accent color, you may not.
  • If you are about to write headline copy, re-read §6 and VOICE.md.
  • If you are about to design a chart, sit with §2 (Tufte) for ten minutes first.
  • If you are about to argue with a credo item, write the argument as an ADR in docs/decisions/ and route it to architecture review. The credo is amendable; it is not optional.

untool.ai — make the tool disappear.