Writing

Five questions that make a project discussion more useful

An editorial checklist for moving from an attractive idea to an understandable delivery plan.

Website editorial team · Published 26 September 2026 · Updated 26 September 2026 · 1 minute read

A project becomes easier to assess when the discussion starts with the task someone needs to complete. In payments, that might be receiving a disbursement, matching a receipt or resolving a disputed instruction. A clear task gives the rest of the conversation a purpose.

Who needs the service?

Identify the people expected to use it and the situation in which they will rely on it. A cooperative payment team and a freight operator may face different constraints even when both need a reliable record.

What is the present difficulty?

Describe the current process and the point where it becomes expensive, slow or hard to explain. Use an actual example where one can be shared. A well-defined problem makes it easier to judge whether the proposed service addresses it.

Who owns delivery?

Name the organisations and responsibilities involved. Explain how a question moves between them and who can make the decision that unblocks the work.

What can be tested first?

A limited, well-described pilot can answer a focused question. State what will be observed, what counts as completion and how an exception will be handled. Record the result over a defined period.

What happens after the test?

The next decision may be to expand, revise or pause a part of the process. A useful project record explains that decision and the evidence behind it.

These questions are an editorial framework for discussing the programmes in the Work collection. Use them alongside each project’s published stage and source material.