Phrase.book

Guide

Add one feature without breaking things

How to ask for something new on a site that already works.

Difficulty: intermediate

  1. 1. Describe what the visitor can do, not how it works

    Say the capability. Naming a specific tool or service too early narrows the answer before you have heard the options.

    Visitors should be able to book a 30 minute appointment and get a confirmation email.
  2. 2. Say what happens when it goes wrong

    Most feature requests only describe the happy path, so that is the only path that gets built.

    If the slot is taken while they are filling the form, tell them clearly and offer the next available time.
  3. 3. Say where it lives

    A feature with no home ends up bolted onto the front page.

    It goes on its own page linked from the main menu, with a button in the hero that jumps to it.
  4. 4. Set the boundary

    New features are where scope quietly triples. State what this must not turn into.

    Do not add customer accounts or logins. Do not take payment. Ask me before adding any paid service.
  5. 5. Ask what it will affect

    Get the blast radius before the change, not after.

    Before you build it, tell me which existing pages this will change and whether anything might break.

The two questions that prevent almost all of the pain here are what happens when it fails, and what this must not become.

The second one matters more than it sounds. "Let people book appointments" becomes accounts, then payments, then a dashboard, unless you say where it stops.

See also

Add a feature