# Will Larson - Navigators (Highlights) ![rw-book-cover|256](https://lethain.com/static/author.png) ## Highlights - It’s not that Architecture teams can’t be good, I’ve worked with a number of very good ones, but even the best are slowed by consensus, and suffer the downsides of consensus-driven decision making (particularly, optimizing for acceptable decisions rather than best decisions). I’ve also found that consensus-driven groups are slow to improve, even with direct coaching, because it’s generally difficult to figure out who to coach, and accountability can be a bit amorphous. ([View Highlight](https://read.readwise.io/read/01hg4neh1jad088nemyf4zn6w1)) ^631808810 - There is exactly one Navigator for a given area; Navigators do not overlap ([View Highlight](https://read.readwise.io/read/01hg4nfd480e1k16t19s51dtw9)) ^631808847 - In practice, most real issues are an intersection of technical, prioritization and people constraints. Navigators are responsible for aligning with the people leadership in their area when making technical decisions ([View Highlight](https://read.readwise.io/read/01hg4nfzbqk811df5rwagz51ra)) ^631808870