📎 Webclip
Principles for decision-making in a flat organization
The article says Doist wants open feedback, but too much input can slow execution. It uses the IETF idea of rough consensus to show how a team can keep decisions moving while still checking for serious problems and shared understanding.
Reading notes#
- The piece began as an internal Twist thread about asking and giving feedback more mindfully.
- Doist says open and sincere communication improves decision-making across technical work, team management, and product management.
- As the team grew, feedback overload became a problem because time was spent responding to comments instead of executing decisions.
- The IETF model is presented as a useful reference for technology teams that need to converge on a solution without unnecessary delay.
- Rough consensus is contrasted with voting and top-down decision-making.
- In this model, “not the best choice” feedback is different from objections based on fundamental flaws.
- Non-critical objections should not slow a decision once everyone can live with the solution.
- Fundamental flaws are issues such as added technical debt, poor scalability, or work that does not justify the value added.
- The organization should share a definition of what counts as a fundamental flaw before discussing proposals.
- When asking for input, it is better to ask whether people can live with a choice than whether they like it.
- The article distinguishes engineering tradeoffs from compromises that simply mean a minority has given up arguing.
- In remote async teams, vague “two cents” can slow decisions if the point is not explained clearly.
- Doist says rough consensus fits technical and product decisions better than a perfection standard.
- Hiring can use a stricter “hell yeah” threshold, but shipping work should move through quick iteration.
- The article says consensus should be a tool for better outcomes, not an end in itself.
