Make an idea reviewable
A useful proposal connects a framed problem to a test question, a bounded change, observable evidence, and a responsible work owner.
State what you want to learn, not only what you want to install or change. Describe who and what the test covers, what will be compared, and what could make the observation misleading. The relevant work owner can help decide whether the proposed scope is appropriate.
Completed sample idea record
Fictional Northstar Supply shift-handoff example. The record is an illustration, not a submitted or approved idea.
| Record field | Illustrative entry |
|---|---|
| Problem | Some evening-to-morning handoffs do not clearly record the next owner and open item. |
| Proposed change | Try a short handoff prompt asking for the open item and its next owner. |
| Test question | During the agreed test period, are both details recorded in more handoffs than in the starting observations? |
| Owner role | The work owner for the handoff reviews scope and helps interpret the result. |
| Scope | A small, agreed sample of one handoff context; do not assume findings apply to other shifts or sites. |
| Evidence to compare | Count handoffs where both details are recorded; state the count, denominator, source, and observation dates. |
From broad suggestion to testable proposal
The change is not the question. Make the learning goal explicit so the work owner can assess the test.
Initial suggestion
“We should replace the handoff process with a new system.”
- The change is large before the problem is understood.
- The scope, dependencies, and measure are unclear.
- It may affect procedures or tools beyond the proposer’s role.
Reviewable first test
“Could we try a brief prompt for recording the next owner and open item in an agreed handoff context, then compare a small count with the starting observations?”
- Names a limited change and a learning question.
- Leaves scope and duration to agreement with the work owner.
- Makes a result possible to discuss without claiming proof.