Skip to content
Software Behaviorby Joost van der Zwan
Index

Framework · Sequence · from Chapter 8

Operational Taste Test

Converts taste from aesthetic preference into a set of operational decisions: what to automate, where to keep friction, what should not exist at all.
Read the chapter

The framework

Fig. · Operational Taste Test
  1. Does this deserve automation?: Decide whether the system should take over the work, prepare it, or leave it in human hands.
  2. Does this deserve friction?: Name where slowing the user down improves judgment, trust, or quality.
  3. Does this need visibility?: Decide what must be made legible instead of hidden behind convenience.
  4. Does this need restraint?: Identify where the product should refuse, pause, ask, or back off.
  5. Does this simplify the user's work?: Separate true simplification from merely moving complexity somewhere else.
  6. Should this exist at all?: Ask whether the feature creates enough value to justify its behavioral surface.
  1. 01

    Does this deserve automation?

    Decide whether the system should take over the work, prepare it, or leave it in human hands.

  2. 02

    Does this deserve friction?

    Name where slowing the user down improves judgment, trust, or quality.

  3. 03

    Does this need visibility?

    Decide what must be made legible instead of hidden behind convenience.

  4. 04

    Does this need restraint?

    Identify where the product should refuse, pause, ask, or back off.

  5. 05

    Does this simplify the user's work?

    Separate true simplification from merely moving complexity somewhere else.

  6. 06

    Should this exist at all?

    Ask whether the feature creates enough value to justify its behavioral surface.

4 · Do

How to use it

Apply to any product decision and turn the answer into an operational artifact: a deletion note, friction rule, visibility budget, or confidence threshold.

5 · Save

The Product Architect · Operational Taste Test

Framework · Sequence