Command Palette
Search for a command to run...
Positions
Core ConceptPositions are the options being considered in a decision. Each position represents a potential path forward.
What are Positions?
A position is one of the options being considered in a decision. For example, if the decision is "Which database should we use?", the positions might be:
- PostgreSQL - Relational database with JSON support
- MongoDB - Document-oriented NoSQL database
- DynamoDB - AWS managed NoSQL service
Each position can have arguments made for or against it. When the decision is concluded, one position is selected as the winner (for Approved decisions) or no position is selected (for Rejected/Deferred decisions).
Creating Positions
Positions can be created in several ways:
- Magic Paste: AI automatically extracts positions from your text
- Manual: Click "Add Position" on the decision page
- During discussion: Team members can propose new positions
Position Structure
Title
A clear, concise name for the option. Often starts with a verb or describes the technology/approach (e.g., "Use PostgreSQL", "Build in-house", "Adopt microservices").
Description (Optional)
Additional context about what this position entails. Useful for options that aren't self-explanatory.
Arguments
Claims made for or against this position. Each argument has a stance (support or oppose) and evidence backing it up.
Votes
Team members can vote for positions they prefer. Votes are informational—the decision owner makes the final call.
The Winning Position
When a decision is concluded with "Approved" status, the decision owner selects a winning position. This becomes the official choice and is highlighted in the UI.
The winning position:
- Gets a visual badge indicating it was selected
- Is included in the comprehensive summary
- Is exported to Git when syncing ADRs
- Appears in briefings and reports
Best Practices
Include "Do Nothing"
For decisions that might not need action, include a "Status Quo" or "Do Nothing" position. This makes "no change" an explicit choice rather than an oversight.
Keep positions distinct
If two positions are very similar, consider merging them or clarifying their differences. Positions should represent meaningfully different paths.
Name positions neutrally
Avoid biased names like "The Best Option" or "Last Resort". Neutral names encourage fair evaluation of all options.