Decision Request Format (CQ)¶
Owner: Vi | Updated: 2026-02-05
Purpose¶
When you need a decision from Erik or Ryan, come prepared. They are busy—don't make them do your thinking. Bring options, bring a recommendation, make it easy to say yes or no.
The rule: If you haven't thought about it, don't ask yet.
The Problem We're Fixing¶
| Bad Pattern | What Happens |
|---|---|
| "What should I do about X?" | Erik has to research X, think of options, decide |
| Long Slack message with no summary | Gets skimmed or ignored |
| No recommendation | Decision sits in limbo |
| No deadline | Gets deprioritized |
Result: Slow decisions, frustrated leadership, you're still blocked.
The Format¶
Every decision request must have:
**TL;DR:** [One sentence: what you need decided]
**Context:** [2-3 sentences max: why this matters]
**Options:**
1. [Option A] - [Pro] / [Con]
2. [Option B] - [Pro] / [Con]
3. [Option C] - [Pro] / [Con]
**My Recommendation:** [Option X] because [reason]
**Need decision by:** [Date/time]
**If no response:** I'll proceed with [default action]
Example: Good Decision Request¶
**TL;DR:** Should we support SSO login for enterprise customers now or defer to Q2?
**Context:** Enterprise prospect (Acme Corp) asked about SSO during demo.
We don't have it. They said it's a "nice to have" not a dealbreaker.
Building SSO would take ~2 weeks.
**Options:**
1. Build now - Pro: Shows enterprise readiness / Con: Delays dashboard feature by 2 weeks
2. Defer to Q2 - Pro: Stay on roadmap / Con: May lose enterprise deals
3. Fake it - Pro: Fast / Con: Technical debt, security risk
**My Recommendation:** Option 2 (defer). One prospect isn't worth derailing the roadmap.
We can revisit if we get 3+ enterprise requests.
**Need decision by:** Friday EOD
**If no response:** I'll proceed with Option 2 (defer).
Why this works: - Erik can read TL;DR and decide in 10 seconds - Options show you've thought about it - Recommendation shows conviction - Default action means it doesn't stall if he's busy
Example: Bad Decision Request (Don't Do This)¶
Hey Erik, so I was working on the integration and the client mentioned
they might want SSO but I'm not sure if we should build it because it
might take a while and we have other stuff to do but also enterprise
customers seem to want it and I was wondering what you think we should
do about this situation?
Why it's bad: - No TL;DR (have to read everything to understand) - No options (Erik has to think of them) - No recommendation (no conviction) - No deadline (sits forever) - No default (blocks until answered)
The "So What" Test¶
Before sending, ask yourself:
| Question | If No... |
|---|---|
| Can Erik understand the decision in 10 seconds? | Rewrite TL;DR |
| Have I listed at least 2 options? | Think harder |
| Do I have a recommendation? | Pick one and defend it |
| Is there a deadline? | Add one |
| Is there a default if no response? | Add one |
When to Use This Format¶
| Situation | Use Decision Request? |
|---|---|
| Need approval to proceed | Yes |
| Choosing between approaches | Yes |
| Prioritization question | Yes |
| Resource/timeline tradeoff | Yes |
| Simple factual question | No - just ask |
| Blocked and need help | No - use Blocked Protocol |
| Feedback on work | No - use Stakeholder Feedback |
Response Expectations¶
| Urgency | Expected Response |
|---|---|
| Blocking work | Same day |
| Important but not blocking | 24-48 hours |
| Strategic/can wait | Within the week |
If No Response¶
- At deadline: Ping in thread: "Bumping—will proceed with [default] if no input by EOD"
- 24 hrs past deadline: Proceed with your recommendation
- Log it: Note that you proceeded with default in #cq-product
The default action is there for a reason. If they don't respond, you move forward.
For Erik/Ryan: How to Respond¶
Quick responses that work:
| Response | Meaning |
|---|---|
| "Go with your rec" | Approved your recommendation |
| "Option 2" | Chose that option |
| "Not now - revisit in Q2" | Defer, with timeline |
| "Need more info: [question]" | Can't decide yet, specific blocker |
| "Let's discuss live" | Too complex for async |
Don't: Leave it unanswered. Even "I'll think about it, decide by Friday" is better than silence.
Conviction Matters¶
Weak: "I'm not sure, but maybe Option A?"
Strong: "I recommend Option A because [reason]. Happy to adjust if you see it differently."
Leadership wants to know: - You've thought about it - You have a point of view - You can defend it
It's okay to be wrong. It's not okay to have no opinion.
FAQ¶
Q: What if I genuinely don't know which option is best? A: Pick one anyway and explain why. "I'm leaning toward A because [reason], but B is also valid because [reason]. Your call." Still shows thinking.
Q: What if there's only one option? A: Then you're not asking for a decision—you're asking for approval. Frame it as: "I plan to do X. Any objections?"
Q: What if Erik picks an option I disagree with? A: You can push back once: "I hear you, but I'm concerned about [X]. Still want me to proceed?" Then commit to his decision.
Q: What if it's truly urgent? A: DM + #cq-product. "Urgent: [TL;DR]. Need answer in next 2 hours to avoid [consequence]."
Q: Can I ask Vi first? A: Yes. Vi can help you refine the options or answer directly if it's within her scope. She'll escalate if needed.
Summary¶
| Element | Required | Why |
|---|---|---|
| TL;DR | Yes | Busy people read this first (and maybe only) |
| Context | Yes | But keep it short (2-3 sentences) |
| Options | Yes | Shows you've thought about it |
| Recommendation | Yes | Shows conviction |
| Deadline | Yes | Creates urgency |
| Default action | Yes | Prevents stalling |
Come with answers, not just questions.