Consensus Is Too Slow, Even With Two People | Mahesh Guruswamy, COO of Kajabi

Teams don't swirl because they disagree, they swirl because nobody is empowered to end the debate and move.Mahesh Guruswamy runs product, engineering, and customer support at Kajabi as a single-threaded leader, a model he picked up at Amazon and carried through Smartsheet and Kickstarter. His case is simple: when two peers share a decision and neither one can break the tie, the whole org waits for them to agree. We get into how he keeps genuine challenge in the room without giving anyone veto power, why he runs a business review every Wednesday, and exactly which decisions he keeps versus delegates. We also cover what it takes to get from your current model to an AI-native model when the change touches people's jobs and nobody volunteers to give up their turf.CHAPTERS00:00 Intro01:03 The case for a single-threaded leader05:12 Healthy tension without veto power06:53 The Wednesday business review09:17 Turning meetings into context for AI10:37 Recording everything by default12:30 Change management when it touches people's jobs14:18 How to tell if your exec team is too slow16:27 Business leaders, not functional leaders19:01 Anger, fear, and the decisions they cause19:49 Underwriting risk instead of pushing it down22:22 One-way doors and two-way doors23:37 The readme that names who decides what24:44 Calm but oddly ambitious27:31 Weasel words30:11 Pairing authority with accountability32:34 Who owns pricing35:39 One data layer for the whole exec team37:39 Hiring outside the bubble40:46 WrapMAHESH GURUSWAMYhttps://www.linkedin.com/in/maheshguruswamy/https://www.thesensiblemanager.comhttps://www.amazon.com/How-Deliver-Bad-News-Away/dp/B0D7FHTTNNKEITH COWINGhttps://linkedin.com/in/keithcowinghttps://keithcowing.comEXECUTIVES UNPLUGGEDhttps://execs.tv