Example Decision Record
This is a template post showing the structure of a decision record on SilverBullet.
The Constraint
State the real-world constraint that forces a decision. This is not hypothetical. This is the operational reality that demands clarity.
Examples:
- Limited engineering capacity relative to product surface area
- Regulatory compliance requirements that conflict with user experience
- Technical debt accumulated over years that threatens system stability
- Competing stakeholder priorities with no clear authority
The Decision
State the decision clearly. One sentence if possible. No hedging.
Example: "We will not build custom integrations for clients with fewer than 100,000 users."
The Tradeoff
Every decision has a cost. State it plainly.
What are you giving up? What will you not do? Who will be disappointed?
This is where clarity becomes valuable. The tradeoff reveals what you value.
The Consequence
What happens because of this decision?
- How does the system change?
- What behaviors does this enable or prevent?
- What second-order effects occur?
- What signals does this send to the team, the market, or partners?
Why This Matters
Decision records serve several purposes:
- Reference: Can be shared in 1:1 conversations without re-explaining context
- Filter: Attracts alignment, repels misalignment before engagement
- Clarity: Reduces ambiguity for teams operating under real constraints
- Accountability: Documents reasoning for future review
Format Guidelines
Posts on SilverBullet follow these conventions:
- Written as internal memos, not blog articles
- No SEO optimization or trend chasing
- No listicles or "thought leadership" framing
- Every post must earn its existence
- Publishing is infrequent and intentional
Audience
If you do not already feel the pain being described, this is not for you.
This site is for senior engineers, architects, founders, and principals responsible for outcomes, not activity.
This is an example. Replace it with real decision records drawn from operational experience.