Adam Gonnerman

"Innovation is saying no to a thousand things."  -  Steve Jobs There is a meeting to align on a proposal. Turnout is good, including some fairly senior people. Opinions differ. Time runs out. A follow-up is scheduled, a revised deck will be produced, a pre-read will be distributed before the next alignment meeting. Nothing is blocked. No one has said no. Yet nothing moves. This is what organizational stall actually looks like. Not conflict. Not resistance. Diligence. Leaders often equate consensus with alignment, but they are not the same thing. Consensus means everyone agrees. Alignment means everyone understands the direction and their role in it, even if they would have chosen differently. One is a state of unanimous opinion. The other is a condition for coordinated action. When consensus becomes the goal, progress slows while risk quietly compounds. Consensus optimizes for harmony. It is a room full of nodding heads, objections softened or withdrawn, everyone heard and id...

“The purpose of a system is what it does.” — Stafford Beer A team drowning in slow approvals decides the problem is speed, so they add AI. Leadership announces a new assistant to unlock productivity. A chatbot is rolled out to close knowledge gaps and reduce internal friction. Demos look promising. Early outputs feel impressive. But weeks later, nothing fundamental has changed. Decisions are still unclear. Ownership is still fuzzy. Data is still inconsistent. If anything, the noise level has increased. You can't use AI to repair broken systems. What it does in reality is accelerate their weaknesses. You see, AI multiplies what already exists. Unclear decision rights leads directly to faster confusion. If no one knows who owns decisions, AI generates more options. Further, more stakeholders weigh in, and decision latency increases. Think about it like this: AI increases surface area of disagreement. Poor data result in confidently wrong outputs. If your data are incomplete, incons...

“By failing to prepare, you are preparing to fail.” - Benjamin Franklin In startup and tech culture, we celebrate the last-minute save. But heroics are often symptoms of earlier neglect. Hero Culture thrives on moments like this: it's Friday at 4:47pm, a ticket has been sitting in review for two weeks, the stakeholder is impatient, and the engineer has a flight to catch, so someone pushes the deployment button because it's a small change and it's always fine. By 9pm there's a Slack thread, by 10pm it's a call, the engineer is somewhere over Ohio in airplane mode, and the one person who knows that part of the codebase is stepping outside a birthday dinner every fifteen minutes to check their phone. The fix takes forty minutes, the post-mortem takes two weeks, and the person who stayed up to save the night gets praised on Monday morning while the person who warned against Friday deployments three sprints ago is quietly forgotten. That's the thing about Hero Cult...