What happened
Outcome evidence uncertain. GitLab makes decision ownership and documentation procedures publicly inspectable. Writing a durable update can initially take longer than sending a message, creating a recurring tension between immediate convenience and future usefulness. The written rules show how the arrangement is intended to work; how consistently people follow them and whether they save time overall remain open questions.
- A directly responsible individual consults stakeholders but holds ultimate responsibility for the decision without needing everyone’s agreement. Directly Responsible Individuals (DRIs)
- The proposed workflow connects issues, edits, merging, and announcements so a changed practice has a durable written location. Handbook usage
- Quicker conversations can bypass the handbook, so keeping the shared record current requires continuing effort. Handbook usage
What might explain it
Plausible
A named decision owner can prevent consultation from becoming an unresolved demand for unanimity. Directly Responsible Individuals (DRIs)
Alternative explanation: If relevant knowledge is missed or authority is mistrusted, a faster decision may simply move conflict downstream.
Participant explanation
Updating shared context at the time of change may reduce repeated explanation across locations and time zones. Handbook usage
Alternative explanation: The benefit depends on discoverability and reading habits; a large stale handbook could instead increase search costs.
Questions to take into practice
- Document who decides, who must be consulted, and where the final decision lives.
- Treat documentation maintenance as work with owners rather than an optional cleanup activity.
What remains uncertain
- When decisions are contested, how much influence do consultation and the named decision owner each carry?
- How often does documentation become stale, and who bears the effort of finding and repairing it?