Skip to content

Practical guide / Ceprefi

Before the first build

A short project brief gives a team something useful to disagree with.

Ceprefi editorial · 15 September 2026

Studio table prepared for a project planning session

Write the problem in one paragraph

Before listing features, describe the person who needs help and the task they are trying to finish. Explain what makes the task difficult today. If the paragraph only names a technology, keep going.

For example, a team might need several organisations to check the same record. That describes a coordination problem. Whether a blockchain belongs in the solution is a separate question.

Give the first version a boundary

Write down what the first version must let someone do. Then write down what can wait. Name the person who can decide when the brief needs to change.

Keep a short list of assumptions: who will use it, where the data comes from and who will maintain it. An unanswered question is easier to handle when it has an owner.

Check it with the people involved

Ask someone who will use the product to walk through the proposed task. Ask the person responsible for support what would be difficult to explain. Note the points where their understanding differs from yours.

Finish with a written next step, an owner and a way to check whether the step helped. The brief should be short enough for the team to revisit when new information arrives.

Have a question about your own project?

Talk with Ceprefi ↗
Read the cookie policy