A How might we states an opportunity as a question to explore, in three sections: the person it is for, the opportunity, and the outcome for that person.

A How might we is one of the four kinds of finding you receive. It arrives as one message in Slack or one issue in Linear, titled with its question, for example How might we let a traveller move the dates of a stay they have already paid for, without calling anyone. Under the title come its three sections, always in the same order: "For", "How might we", "So that".

Each heading begins the phrase written under it. The three sections read in order form one question, and it is a question to explore, not an answer that has been decided.

Example

Read the three phrases in order. For example:

  • For a traveller whose dates changed weeks before the trip,
  • how might we let a traveller move the dates of a stay they have already paid for, without calling anyone,
  • so that a small change to their plans stays a small change

The finding also carries a theme: the name given to a pattern that several pieces of feedback share.

a delivered How might we in Linear, demo account (Acme Stays) · the title and the three headings For, How might we, So that, each with its quotes · cropped above Confidence

How it relates to a Problem statement or a Need statement

A How might we is not a rewording of a Problem statement or a Need statement. It has its own quotes under its own sections.

A Need statement says what the person wants. A How might we asks how they could have it.

Example

One theme, a Need statement and a How might we. For example, under the theme "Changing a booking after paying":

  • Need statement, "I want to": set new dates for my trip myself
  • How might we: let a traveller move the dates of a stay they have already paid for, without calling anyone

When a Problem statement or a Need statement backs a How might we, the delivered How might we carries a line that names that finding. The line starts with Problem statement: or Need statement:, followed by the title.

In Linear, the two issues are also related, so each shows the other as a related issue. In Notion, a finding in the same database is linked: the row names it in its 19 Problem statement field or its 20 Need statement field, and the row of that finding lists the How might we in its 18 How might we findings field. Each row shows the link whichever was delivered first. In Slack, the title in the line links to the message of that finding when that message is in the same channel.

A How might we can arrive with no Problem statement or Need statement behind it yet. It then carries this line: No Problem statement or Need statement backs this in the topic's feedback so far. The line only describes what the topic's feedback holds so far. It does not rate the How might we, and there is nothing for you to do.

A Problem statement or a Need statement can be delivered after the How might we that it backs. The earlier How might we then gets a link to that finding and a dated note: Linked on 14-10-2026 to the Need statement "Paid, and the dates no longer fit". Dates in these notes are written as day, month, year.

In Linear, the note is a comment, and the two issues become related. In Notion, the note appears at the end of the row. When that finding is in the same database, the 19 Problem statement or 20 Need statement field also links to it, and the row of that finding lists the How might we. In Slack, the message stays as it was delivered, and the note is a reply in the thread of that message.

A How might we with no Problem statement or Need statement behind it can later get this dated note: No new feedback has backed this lately. Marked on 20-10-2026. The note appears as a comment in Linear, at the end of the row in Notion, and as a reply in the thread in Slack. In Notion, the 21 Gone quiet field also shows that date. The note does not say the How might we was wrong.

A How might we can also arrive with no line about a Problem statement or a Need statement. It then says nothing about whether one backs it, and the How might we can still get either dated note later.

For

This section names who the opportunity affects: one kind of person, in a situation you can recognise. It is not a label as wide as "users" or "customers", and it is not two kinds of person joined by "and". It may name a product or a system when the person's situation needs it.

Example

One kind of person in a situation you can picture. For example:

a traveller whose dates changed weeks before the trip

How might we

This section names the opportunity. It starts with a verb and names one opportunity only. The person, or the person's experience, is the subject of the sentence.

The section may name your product, a system, a service or a department, because that is the situation the person is in. It does not make the system the subject, and it does not name a feature to build.

Example

A verb first, and the person is the one who acts. For example:

let a traveller move the dates of a stay they have already paid for, without calling anyone

So that

This section names the outcome for the person: what the opportunity would mean in their life. It states one outcome, in the person's own words.

It never names a product, a system, a brand, a company or a department. A word for something in everyday life that does not belong to one provider, such as a phone or a bank account, may appear. It is not a measure of the system, such as fewer calls or a faster process.

The outcome can be something the person gains, or something they avoid. When the outcome makes sense on its own, the section does not add the problem after it with "rather than", "instead of" or "without".

Example

What the person gets, not what the system does. For example:

a small change to their plans stays a small change

What arrives with it

Under each section are the quotes that support it, each with its voice, its source and its date.

A note called Confidence states how far the evidence reaches and what it does not cover.

How to read the quotes, the Confidence note and the scores is the subject of article 18.

Related articles

Last verified:

23 October 2026