REVIEW: Sense and Respond by Jeff Gothelf (3-stars)

A Practical Book for Leaders Moving Beyond Industrial‑Age Thinking

Most business books either bury you in abstract frameworks or force you through a fictional executive’s personal life to make a point. Sense and Respond doesn’t do that. It stays grounded in real examples and focuses on the mechanics of modern work: feedback loops, adaptive planning, and the shift from industrial‑age certainty to software‑age change. That alone puts it ahead of a lot of what’s out there.

Industrial‑Age Planning vs. Software Reality

One of the strongest parts of the book is the way it explains why traditional planning models don’t translate into software. It’s not because industrial planning is outdated or wrong. It’s because it was built for a completely different category of problems.

If you’re building a bridge, you’re working with fixed materials, established safety requirements, and environmental conditions that are mostly knowable. The physics don’t change halfway through the project. You can plan that work with confidence because the domain is stable.

Software is the opposite. The problem space shifts while you’re working. User needs evolve. Market conditions change. Technology capabilities expand. You discover constraints as you go. The environment is fluid, and the cost of change is low enough that learning as you build isn’t just possible — it’s necessary.

That’s the core point the book gets right: industrial planning is built for certainty; software work happens inside uncertainty.

Experiments as a Normal Operating Rhythm

The book pushes hard on the idea that experimentation shouldn’t be a special event. It’s not a one‑off discovery sprint or a quarterly research push. It’s part of the regular operating rhythm. The author suggests talking to customers every six weeks. In 2026, that’s slow, but the principle holds: if you’re not in regular conversation with your users, you’re not building a product. You’re building a guess.

Small experiments, quick tests, and ongoing validation are still the most reliable way to reduce risk in software.

Parallel‑Track Agile That Actually Works

One of the most practical ideas in the book is the separation of discovery and delivery. Expecting a single team to “innovate” and hit delivery deadlines at the same time is unrealistic. A parallel‑track model — one track focused on figuring out how to solve the hard problems, the other focused on shipping — is cleaner and more humane. It reflects how real teams actually work when they’re not being forced into fantasy timelines.

Give Teams Problems, Not Requirements

Another point that still holds up: developers should be given problems to solve, not a list of requirements to execute. When you hand a team a pre‑defined set of tasks, you’re not using their expertise. You’re treating them like a feature factory. And you’re cutting them off from the feedback that tells them whether their work mattered. Teams need visibility into outcomes, not just velocity charts.

Who This Book Is Actually For

It’s also important to acknowledge the book’s age. Written in 2017, it predates a lot of what defines modern product work today. If you’ve spent years in Agile environments, worked on design systems, or led empathy‑first projects, much of the book will feel obvious. Not wrong — just foundational. And in 2026, with AI reshaping delivery and late‑stage consolidation changing how teams operate, the examples don’t fully match the complexity of what teams face now.

But that doesn’t make it irrelevant.

The book is genuinely useful for people who are early in their leadership journey or who are coming from traditional command‑and‑control environments. It gives them a clear contrast between two modes of working and concrete examples that make the shift understandable. It’s a better starting point than dropping someone straight into a stack of Marty Cagan books. It gives them anchor points before they dive into deeper product thinking.

The VUCA Reality (Even Though the Book Never Uses the Term)

The author never uses the term VUCA, but he describes it constantly. Software, marketing, and consumer‑product work all operate in environments that are volatile, uncertain, complex, and ambiguous. User behavior changes quickly. Competitors move fast. Information is incomplete. Signals are messy. You can’t manage that kind of work with planning models built for stable, predictable domains.

The book doesn’t name VUCA, but it circles the idea over and over: you need continuous sensing, iterative response, and teams empowered to solve problems because the environment demands it.

If You Want a Next Step

If you want to go deeper into why planning models must match the problem domain, How Big Things Get Done is a good follow‑on. It comes from a completely different world, but it helps clarify why software can’t be managed like the Golden Gate Bridge.

After that, Marty Cagan’s books are the natural extension. They go much further into empowered teams and outcome‑driven product leadership. But they can also feel impossible to implement in traditional command‑and‑control environments. For leaders who are still operating inside those structures, the gap between Cagan’s ideal state and their current reality can feel too wide to cross.

That’s where Turn This Ship Around fits in. It offers a clear, concrete example of how to shift from a culture of followers to a culture of leaders, and it does it in a way that’s easy to understand even without a military background. It shows what distributed authority looks like in practice and how to build competence and ownership at every level. For many leaders, it’s a more accessible bridge between industrial‑age habits and the kind of empowered teams Cagan describes. 

REVIEW: Sense and Respond by Jeff Gothelf

RATING: 3-stars

REVIEW: Silos, Politics, and Turf Wars (2006) by Patrick Lencioni (3-stars)

I’ll be honest: I’m not usually a fan of the “business fable” format, and this one has all the classic early‑2000s fable tropes. The personal‑life padding, the pregnancy storyline, the protagonist’s wife designing his logo — none of that adds anything. It feels dated and unnecessary, like the book is trying to make the protagonist “relatable” in a very specific, very last‑century way. But in 2006, people often needed these ideas wrapped in a story to actually absorb them. The fable structure made the message feel safe enough for leaders who would have tuned out a more direct approach.

And despite the saccharine framing, the book has a can‑do energy that, for a moment, made me wonder whether going freelance as a consultant was a viable option. It’s written to make you feel like you can walk into a messy organization, diagnose the dysfunction, and rally people around a shared purpose. That tone is part of why the book works, even if the personal‑life filler is something we could all do without.

The moment that actually matters: listening

The strongest part of the book isn’t the crisis or the characters or the manufactured drama. It’s the moment the protagonist realizes he actually has to listen to people. Not the performative “I hear you” version, but the real “tell me what you think the problem is” version. That’s the turning point. He stops trying to impose a solution and starts trying to understand the motivations, fears, and incentives of the people involved. Once he does that, he can help them find a common cause that isn’t just “stop being political” or “work better together.” People don’t align because someone tells them to. They align when they see themselves in the problem and the solution.

Workshops that actually work

Another part of the book that lands well is the use of workshops. Breaking people into groups, giving them space to talk, and letting them surface the real issues is simple but powerful. It reminded me immediately of how a group director organized our team at a large software company that was transitioning from traditional off‑the‑shelf products to cloud‑based SaaS. He didn’t lecture at us or hand down a vision from a podium. He put us into groups, gave us real problems to solve, and let us figure out the patterns ourselves. It worked. We saw real, recognized success because people were engaged, aligned, and actually talking to each other.

And then the team was split up because the organization insisted on grouping people by role. Program managers with program managers, designers with designers. The exact opposite of what had been working. The book captures that dynamic perfectly. Cross‑functional collaboration works, but organizations keep reorganizing themselves away from it.

The environments that suffer most are the ones where people are just mean

One thing Lencioni does well is highlight how much damage people do when they rely on stereotypes, reductionist labels, or just plain meanness. The environments that suffer the most in the book aren’t the ones with the biggest strategic problems. They’re the ones where people stop seeing each other as human beings and start treating each other like caricatures. That part felt very real.

You can have the best strategy in the world, but if people are dismissive, snide, territorial, or operating from assumptions about “those people over in that department,” nothing moves. The fictional drama exaggerates it, but the underlying pattern is familiar to anyone who has worked in a large organization.

And this is where Sense and Respond quietly overlaps. Even though it’s a very different kind of book, the author stresses the importance of people getting along socially and actually connecting. Not in a forced team‑building way, but in the sense that teams who like and respect each other simply work better. They share information. They surface problems earlier. They don’t default to defensiveness. Both books, in their own ways, point to the same thing: the social fabric of an organization matters more than the process diagrams.

The part the book doesn’t say out loud: communication skills are the real issue

Here’s where I diverge from the book. The story resolves because the protagonist listens, empathizes, and helps people articulate their needs. But the book never names the actual skill set behind that shift. This is where Nonviolent Communication comes in.

If more people in corporate environments understood how to express their needs clearly, hear other people’s needs without defensiveness, separate observations from interpretations, and navigate conflict without escalation, a lot of the so‑called silos and politics would evaporate. Not all of it, because incentives and structures still matter, but the day‑to‑day friction would drop dramatically.

Most organizational gridlock isn’t caused by strategy. It’s caused by miscommunication, assumptions, and emotional reactivity that no one has the tools to name or address. The book hints at this through the story, but it never says it directly. The real lesson isn’t “create a rallying cry.” It’s “learn how to communicate like an adult.”

Why the book still works

Even with the storytelling format (which I still think is unnecessary), the book works because it taps into something real. People want to fix broken systems. They want to feel connected to a purpose bigger than their department. They want to contribute without getting caught in territorial nonsense. The book isn’t a manual for organizational design and it’s not a deep dive into incentives or systems thinking, but it is a reminder that people want to work in environments where they feel heard and aligned.

Sometimes a story is enough to get someone to see that.

Where to go next

If someone finishes this book and wants to go deeper into the part that actually matters -- the human part -- I’d point them toward Nonviolent Communication. Not the corporate‑sanitized version found in many books, but the real thing. It’s the best framework I’ve seen that gives people a usable way to express needs, hear other people’s needs without spiraling, and navigate conflict without turning it into a referendum on someone’s character.

Both Silos and Sense and Respond hint at this. They show the symptoms. NVC gives you the underlying mechanics. It’s the difference between “we need to break down silos” and “here’s how to talk to each other in a way that doesn’t create them in the first place.”

If more people in corporate environments had even a basic grounding in NVC, a lot of the friction, misinterpretation, and territorial behavior that slows organizations down would disappear. Not all of it — incentives and structures still matter — but enough that the work would move faster and the culture would feel less like a minefield.

It’s not a magic fix. It’s just the part we keep skipping. I also kept thinking about how many people insist on keeping their “work life” and “personal life” completely separate, as if those two selves don’t influence each other. If someone is rigidly compartmentalized in their own life, they will bring that same separation into the workplace. And I don’t need to know the details of someone’s cancer treatment or their partner’s high‑risk pregnancy to understand that people need space and time to handle the realities of their lives. The point isn’t the specifics. The point is recognizing that people are whole humans, and organizations function better when they acknowledge that instead of pretending everyone is a blank, interchangeable worker during business hours.

REVIEW: Silos, Politics, and Turf Wars (2006) by Patrick Lencioni

RATING: 3-stars