CSE Roadmap

Core tier · about 2 hours · 9 parts

Part 3 of 9 · 1 min read

Ask before you draw

The questions that pin down a problem, and why quick answers are a warning sign.

Think of a doctor. A good doctor asks questions before writing a prescription. A doctor who writes the prescription in the first ten seconds is guessing.

Many people feel pressure to answer fast. In design work, a fast answer to an unclear question is usually a wrong answer. The skill is to slow down and ask.

Five groups of questions cover most problems:

  1. Features. What exactly must the system do? Which two or three actions matter most?
  2. Users. Who uses it, on which devices, and in which countries?
  3. Size. How many users, and how many of them are active each day?
  4. Growth. How big will it be in three months, in a year? How fast does it grow?
  5. Limits. What technology does the company already use? What must be reused? What is the budget and the deadline?

When the person answering says "you decide", that is not a refusal. It is an invitation. Pick a reasonable answer, say it out loud, and write it down as an assumption.

Assumption

An assumption is a fact the designer chooses to treat as true because nobody has confirmed it. Good assumptions are written down, so that anyone can see them and correct them.

Example: "Assume 100,000 users open the app each day."

Read it as

A written assumption is a small contract. If it turns out to be wrong, everyone knows which part of the design to revisit.

Check yourself:

  • Why is it safer to write assumptions down than to keep them in your head?
  • Which group of questions would reveal whether the system must work in several countries?