Protocol

Specify the needed outcome before prescribing the solution

Add another dashboard may be a solution to a question nobody has asked yet.

About 1 min read

Before you use it

Use when
  • A feature request names a particular tool or interface before the underlying need is clear.

Keep this limit in mind

  • Do not remove security, compatibility or other binding constraints in the name of creativity. A solution-neutral sentence can still be vague or untestable.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Why it matters

Restate the required outcome and how it can be checked. Separate that requirement from a proposed implementation. Preserve genuine constraints, but label them as constraints with a reason. This leaves room to find a simpler solution without weakening what the system must achieve.

Steps

  1. Ask what the proposed feature must enable someone to do.
  2. Write an observable result and relevant operating conditions.
  3. Record mandatory implementation constraints separately from preferences.

An example

Instead of requesting a new dashboard, specify that the operator must identify every rejected record and its actionable reason after a run.

Check your result

Two different designs could be compared against the same stated outcome, unless a justified constraint excludes one.

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingSpecify the needed outcome before prescribing the solution

Evidence and sources
Supports

NASA's requirement-writing guidance recommends stating what is needed rather than prematurely specifying how, with precise verification criteria.

Necessary implementation constraints must still be retained and justified rather than removed merely to make the statement solution-neutral.

Appendix C: How to Write a Good Requirement · C.2 Product Requirement; C.4 Verifiability/Testability

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details