Biswarup Mondal
Bengaluru
Foundation

Principles

Dieter Rams’s ten principles, marked up the way I’d mark up any brief: what this portfolio keeps, what it bends, and the one it rewrites. Then ten of my own, in his grammar, for the questions the system leaves open.

Ten principles for good design

Dieter Rams

marked up by biswarup — 6 kept · 2 bent · 1 reinterpreted · 1 rewritten

  1. 01

    Good design is innovative.

    The ideas here are new to a portfolio, not to the world: the About page is a geologist’s section drawing, the site’s chrome is a design tool’s ruler and frame. Borrowing a practice whole is what keeps novelty legible.

    Kept

    new, but borrowed whole from a real practice

    see it: the dig
  2. 02

    Good design makes a product useful.

    The cookie is the consent. The pull-tab flyer is the contact form. The sky in the footer is the hour and the weather where I am, before you write. Nothing is there only to be looked at.

    Kept

    every playful piece has a job

    see it: the cookie
  3. 03

    Good design is aesthetic.

    One accent, a cool neutral ground, tight corners and a wide gap between small and large type. The beauty is in proportion and finish, which is why it survives being switched to black and white.

    Kept

    beauty from restraint, not from effects

    see it: Typography
  4. 04

    Good design makes a product understandable.

    “I make complex products understandable” is the one sentence I’d keep if everything else went. In the work that means AI products that show their reasoning; on this site it means every page explains itself before the copy has to.

    Kept

    the headline of my About page

    see it: About
  5. 05

    Good design is unobtrusive.

    Rams wanted tools that step back. The chrome here does — ticks at reduced strength, frosted bars, hairlines instead of shadows — so that a few chosen moments can perform: the reel, the dig, the cookie. Unobtrusive where you work, expressive where you remember.

    Bent

    quiet chrome, loud moments

    see it: the ruler
  6. 06

    Good design is honest.

    Status is shipped, unverified or next, and says so. Store figures are the verified ones. Work I can’t show yet is locked, not left out. Every grey clears WCAG AA, and where a measured value failed it was darkened rather than defended.

    Kept

    it says what state the work is in

    see it: Work
  7. 07

    Good design is long-lasting.

    A website can’t be timeless the way a radio can. It can be cheap to keep: one token file, content in MDX, primitives that pages may arrange but not restyle. Changing the look means changing a value, not rebuilding a page.

    Bent

    built to be kept, not to be timeless

    see it: Foundation
  8. 08

    Good design is thorough down to the last detail.

    The ruler’s readout is opaque so a tick label never prints through it. The page rails stay one continuous stroke through the frosted bar. Details nobody will name are the ones everyone feels.

    Kept

    the rails run unbroken through the nav. nobody asked.

    see it: Material
  9. 09

    Good design is environmentally friendly.

    A website’s footprint is the reader’s data, battery and patience. Pages are prerendered, images ship as AVIF and WebP with their real dimensions so nothing shifts as it loads, and motion stops when the reader asks for less.

    Reinterpreted

    on a screen: light on the reader

    see it: Motion
  10. 10

    Good design is Struck through: as little design as possible.

    “Less, but better” survives; “as little as possible” doesn’t, for a portfolio whose job is to be remembered. Each page gets one idea — a section through the ground, artboards under review, a pinboard — and that idea is carried to the last mark rather than diluted by a second.

    Rewritten

    Rewritten as: one idea per page, carried all the way

    see it: one idea, all the way
My additions, in his grammar

11–20

  1. 11

    Good design is drawn, not decorated.

    Every mark on this site is borrowed whole from a real drawing practice: a section drawing’s level marks and borehole, a design tool’s ruler and frame, a reviewer’s red pen. A mark that can’t name the practice it came from is ornament, and it goes.

  2. 12

    Good design is named once.

    A value worth typing twice is worth a token. A literal in a component is a decision no other page can inherit and no later change can reach.

  3. 13

    Good design is ordered before it is coloured.

    Size, weight and space first; colour last. Colour is the smallest lever and the first one overused — if a layout only works once something is blue, the layout isn’t working.

  4. 14

    Good design either answers or tells.

    Motion that answers you — a press, a hover — is fast enough to go unnoticed. Motion that tells a story — a drawing drawing itself, a frame walking between beats — is slow enough to follow. Both stop when you ask for less.

  5. 15

    Good design starts at a fingertip.

    The touch state is designed first and a cursor adds to it. Hover never hides anything a reader needs, because a phone has no hover at all.

  6. 16

    Good design is legible by measurement.

    Every ink clears WCAG AA on the surface it sits on, checked with numbers rather than eyes. This page’s red pen is a few points darker than the site’s for exactly that reason.

  7. 17

    Good design keeps its chrome quiet and its numbers loud.

    The ruler’s ticks sit back; its readings don’t. Chrome is there to be read when you need it and ignored when you don’t.

  8. 18

    Good design writes by hand only on things.

    Handwriting is for what is written on an object — a print’s foot, a note in a margin, a correction on a sheet. Never a button, never a label, never navigation.

  9. 19

    Good design lets a replica wear its own clothes.

    A mock of Gmail uses Gmail’s palette and corners, kept in tokens only the mock can read, so it reads as Gmail and never leaks into the site around it.

  10. 20

    Good design admits when the system is wrong.

    When a page needs something the system lacks, the answer is a new token or primitive, not an exception inside a component. Exceptions are invisible; additions can be reviewed.

— biswarup, 2026