Decision Records
42 articles on decision records. Page 2 of 2.
When Knowledge Lives in People's Heads, the Team Pays for It
When knowledge lives in people's heads, work stalls every time the one person who knows is busy. Here is how to get it out without wikis.
Searchable Team Knowledge Base vs. Wiki: What's the Difference?
A wiki stores pages; a searchable team knowledge base answers questions with a named source. Here is the real difference and when each one works.
How to Document Decisions So People Actually Find Them
How to document decisions so people find them later: skip the write-once doc and build a record you query by question, with a named author.
How to Capture Institutional Knowledge Without Building a Wiki Nobody Reads
Capture institutional knowledge without a dead wiki: auto-index work to make it discoverable, declare answers to make them trustworthy.
Async Decision Making Frameworks That Actually Stick
Async decision frameworks (DRI, RFC, disagree and commit, time-boxed input) and why each only works if the decision lands in a queryable record.
What Is an RFC Process for Engineering Teams (and How to Run One Async)?
An RFC process lets engineers propose a change, gather comments async, and land the decision in a queryable record, not a stale doc.
What Is a Directly Responsible Individual (DRI) and Why It Beats Committee Ownership
A directly responsible individual is one named owner per decision or area, so 'who owns X' has a single answer you can query.
Where Should a Distributed Team Record Decisions?
Chat, wiki, tickets, or ADRs? Where distributed teams should record decisions, compared honestly, with the case for a queryable record.
A Decision Log Template for Engineering Teams (And Why It Goes Stale)
A ready decision log template with explained columns, plus why a static template goes stale and how a queryable record fixes it.
What Is a Decision Log in Project Management?
A decision log in project management records key project choices and why. What to capture, and why a queryable record beats a spreadsheet.
How to Stop Losing Decisions in Slack
Decisions made in Slack threads scroll away. Stop losing them by declaring each one into a record you can query later.
How to Query Your Engineering Decision Log Instead of Just Storing It
A queryable engineering decision log lets you ask who decided what, when, and why, instead of rereading old threads.
The Decision-Shaped Hole in Your Tech Stack
The tools to document business decisions fall between wikis, trackers, and chat. Here is why your stack has a decision-shaped hole and what it takes to fill it.
Why Teams Keep Re-Arguing Decisions They Already Made
Why teams revisit decisions: the original call was never recorded with its reasoning and authority. Here is what triggers relitigation and how a decision record stops it.
Decision Log vs Decision Record: What Is the Difference?
Decision log vs decision record: a log lists what was decided and when; a record captures why, by whom, and under what authority. Here is how they differ and why you need both.
The Hidden Cost of Undocumented Decisions
The cost of undocumented decisions hides in re-debate, lost context, slow onboarding, and AI that guesses. Here is what it really costs and why it stays invisible.
Your Company Has a System of Record for Everything Except Decisions
Your company tracks code, tickets, and customers in dedicated systems. Decisions live in Slack and memory. Here is where to track team decisions instead.
What Is a System of Record for Decisions?
A system of record for decisions is the authoritative store of what your team decided, who, why, and under what authority. Here is what it is and why it matters.
Your team’s week, answered from the work.
If this is your team’s week, see what a StandIn does with it.