Idea Office Hours
Pressure-test a product idea with forcing questions before jumping to solutions, then capture the decision in a short design doc — a structured 'office hours' diagnostic.
How it runs
| # | Step | Who runs it | What happens |
|---|---|---|---|
| 1 | Frame the opportunity | Developer | Turn the rough idea into a specific problem, audience, outcome, and assumption set. |
| 2 | Pressure-test the options | Researcher | Challenge the premise and compare meaningful alternatives before choosing a solution. |
| 3 | Write the decision record | Copywriter | Capture a defensible decision and the smallest useful real-world action. |
| 4 | Evaluate the deliverable | Reviewer | Independently grade the observable deliverable and route it to finish, repair, or user escalation. |
| 5 | Repair the deliverable | Developer | Fix only the concrete gaps from the latest independent review. |
| 6 | Finish | Developer | All deterministic and reviewer criteria passed. |
| 7 | Escalate unresolved concerns | Developer | The bounded repair loop ended without a defensible pass. |
Say something like "brainstorm this" or "is this worth building" or "help me think through" or "office hours" in chat to start it.