Start with the problem, not the artifact

Sometimes the hardest part of showing someone an idea is not explaining how it works. It is making clear what problem it is meant to solve.

Imagine presenting a checklist. To the person listening, it might look like a small document with boxes to tick. But perhaps the actual problem was that important decisions kept getting lost between handoffs. Without that context, they can see the document and completely miss its significance.

The artifact is what we made. The problem is why it had to exist.

We don't encounter things without a frame

A path through a forest looks different when you know where it leads. A list of questions becomes something else when you understand which mistakes it is trying to prevent.

In the same way, people rarely evaluate a design, a plan, or a system in isolation. They try to fit it into a story about what matters, what is changing, and what it will make possible.

That story can be misleading. It can also be useful. The point is not to manufacture importance. It is to provide enough context that the work can be understood at its actual scale.

Explaining a problem helps you understand it

There is another reason to begin with the problem: the explanation is useful to the person giving it, not only to the audience.

An idea often feels perfectly clear while it remains in your head. Try to put it into one honest sentence and you may discover missing assumptions. Which part is broken? For whom? How do we know? What changes if it stays broken? What would count as a better outcome?

The sentence does not merely communicate the thought. It tests whether there is a thought there to communicate.

From artifact-first to problem-first

Instead of beginning with “We built a dashboard,” try a different sequence:

State the problem. What was unclear, unreliable, slow, or costly?
Explain why it matters. What consequence follows from leaving it unsolved?
Show the artifact. What have you actually made, and what does it do?
Describe what it enables. What can someone do now that they could not do before?
Name the next test. What remains uncertain, and how will it be checked?

This order is not a sales trick. It is a way of keeping the shape of the solution proportional to the shape of the problem.

A prototype does not have to pretend

Early work can be worth discussing without being called a finished product. In fact, saying where it is incomplete may make the conversation more useful.

A modest prototype can address a real problem. A spectacular presentation can address no clear problem at all. The difference is worth making visible.

Before showing what you've made, make room for the question that made it necessary.

The point

A useful frame is neither exaggeration nor decoration. It helps other people understand what they are seeing, and it forces us to check whether we understand it ourselves.

Start with the problem. Then let the work speak for itself.