Decision 1Ask one clarifying question
Use it when: You can't yet tell what happens, where it happens or what the employee proposes.
Example: Which station uses the gauge, and where does the next operator look for it?
Next action: Ask one specific question and keep the idea in review. Don't ask the employee for a business case.
Decision 2Approve a small test
Use it when: The problem is clear and a team can try a small change.
Example: Production tests one marked spot for the gauge at station 3, and both shifts use it for two weeks.
Next action: Name the department, the next action and what they will check. Approval starts the handover; it doesn't finish it.
Decision 3Decline with a reason
Use it when: The proposal conflicts with a requirement or can't work the way it is suggested.
Example: We can't remove the required protective insert. Logistics will check approved alternatives for the empty space.
Next action: Give the reason through your agreed feedback route. Keep the decision separate from any follow-up action.
Decision 4Link it to a duplicate
Use it when: Another suggestion or a running test already covers the same work.
Example: Production is already testing a new gauge location. We'll add your shift's input to that test.
Next action: Record which idea it belongs to and tell the employee where to follow it. You do this by hand; ideas don't merge automatically.
Decision 5Defer to a set date
Use it when: There is a real reason to wait, such as a planned layout change or another team's work.
Example: We'll revisit the shelf position after the station move. The coordinator confirms the date with Production.
Next action: Name who follows up and when. 'Later' on its own is not an action.