← All writing

A question is not a brief

Before a product takes shape, find out what would change your mind.

A dense circle of silver grains is cut by a dark line and thins into a sparse arc on black

An idea can feel unusually clear right up until someone asks what, exactly, would prove it useful.

It is easy to turn an idea into a brief too soon. Give it a name. Sketch the interface. List the features. By then, several guesses have quietly become requirements. The work looks more concrete, but the central question may still be untouched.

We want to keep that question visible for longer at Einhar. Not to avoid making things. To make the right first thing.

Find the decision inside the idea

Imagine we are considering a creative tool. “Make creating easier” is a direction, not a problem we can test. Easier for whom? At what point in their work? Are they struggling to begin, to revise, to collaborate, or to finish? Each answer would lead to a different product.

A useful research note separates three things: what we have observed, what we think it means, and what we have not checked. That distinction can feel fussy when an idea is exciting. It saves us from building a polished answer to a question nobody asked.

The next step does not always need to be an app. It might be a conversation about an existing workflow, a rough interactive fragment, or a small tool used for one real task. The form depends on the uncertainty. If the doubt is whether a workflow exists, a beautiful interface will not settle it. If the doubt is whether an interaction works, another document will not settle that either.

Let the test have a consequence

The point of an experiment is not to collect reassuring reactions. It is to put a decision at risk. Before running one, we should be able to say what we expect to learn and what we would do differently if the result surprises us.

Sometimes the answer is to build more. Sometimes it is to change the problem, narrow the audience, or stop. A test that cannot change the plan is usually a demonstration, however convincing it looks.

This is also where intelligent tools are useful and where their limits become obvious. They can help us explore alternatives, prototype quickly, and find gaps in our reasoning. They cannot supply genuine evidence of what a person needs by confidently inventing that person's opinion. Speed is valuable when it gets us to a real test sooner; it is costly when it lets an assumption travel further without one.

Keep the middle visible

Finished products make tidy stories. The decisions between the initial question and the finished work are usually less tidy, and often more informative. We intend to use this Journal for some of that middle: what we asked, what we tried, what we found, and what changed afterward.

That record will include uncertainty. It should. If a question survives contact with reality, we can build with more confidence. If it does not, finding out early is still progress.

All writing