Skip to content

How to explain a technical product

Explain a technical product by naming the job in the buyer’s words, then giving the person who will check you something they can verify. April Dunford’s framing point is that features and technology, offered before a frame, leave a prospect guessing what you are. Learn the words from their past work, which is the rule in The Mom Test.

On this page
  1. The frame comes before the mechanism
  2. Use their words for a week they already had
  3. Steps
  4. What to move down
  5. FAQs

The frame comes before the mechanism

Dunford describes framing as the context that lets a prospect see what you are and why it matters. She writes that startups often skip it and open on features or technology, so the prospect guesses, or guesses wrong. The architecture can be the reason the outcome is true. It is a poor opening for someone who does not yet know the job.

Use their words for a week they already had

Rob Fitzpatrick’s The Mom Test puts the interview rules in one place: talk about their life rather than your idea, ask about specifics in the past rather than opinions about the future, and listen more than you talk. The explanation should reuse a phrase they used about last week’s work. A phrase you coined in the office is not yet an explanation. The customer interview page covers how to ask.

Steps

  1. Name the category and the customer

    What it is, and who it is for, before any component.

  2. Use one phrase from their work

    A step they did last week, in their words.

  3. One outcome

    What they can now do, or what they stop doing.

  4. Then the mechanism

    For the reader who will check you. After the frame, not instead of it.

  5. Put proof they can open

    A sample, a request, a diagram, a doc. Next to the claim.

What to move down

If you lead withA stranger can sayMove it
The architectureNothing about the job yetBehind the outcome
A new category nameA word they cannot placeAfter a familiar frame
The job in their wordsWhat it is and who it is forLeave it first
A sample they can runWhether the claim is checkableBeside the outcome, not above it

FAQs

How technical should the page be?

As technical as the reader who has to trust it. Precise terms, after the job is clear. Skip adjectives.

What if the buyer is not technical and the user is?

Two lines, one position. The buyer hears the outcome. The user hears how they would check it.

Can a diagram replace the sentence?

A diagram can carry the mechanism. The first sentence still has to say what it is and who it is for.

Sources

  1. April Dunford, Product framing can help grow your startup (or kill it)
  2. Rob Fitzpatrick, The Mom Test

See this on your own homepage

Talk through your positioning in 15 minutes

Book a call