Engineer Team Decisions for Consistency, Not Just Consensus

Map who’s really making which kinds of decisions. List regular decisions (e.g., resource allocation, feature choices, family purchases) and who usually makes each call. Notice overlaps, gaps, or unclear roles.

Define decision rights at the start of a project. Before launching work, specify how your group will choose, who will make the call (consensus, majority, sole decider), and what process you’ll follow.

Hold a 'process review' after major decisions. After your next group decision (or argument!), debrief: Did everyone understand the options? Who set the agenda? How could the process improve?

Experiment with decision models. Try a consensus approach for one project and majority rule or a clear decider for another. Note which works best for speed, buy-in, and results.