Most stubborn problems stay that way for the same reason.

My friend Seth Godin calls it a knot.

Seth's one of us and one of the clearest thinkers I know on how people and organizations get stuck and stay there. He published a new book last week called The Knot, and it has changed me for the better.

Here's the idea and it's simple enough: a stubborn problem stays stubborn because we're trying to have two incompatible things at once. Change without risk. Progress without sacrifice. A new path forward and the comfort of staying put.

"I can't get the system to disappear, and no, I shouldn't have to rethink the loudspeakers. They're already great."

The knot isn't the problem itself — it's the grip we keep on both ends. The book asks you to name the conflict, decide which part you're actually unwilling to release, and figure out whether you're looking at something solvable or something you simply have to accept.

Here's an example. We have a product roadmap we're all passionate about—things we all badly want to build. Need to build. And we have a finite bucket of engineering resources. The knot: we want it all but can't have it, so nothing is moving forward. We're fricking stuck. We'd been pulling both ends of that rope for months without naming it. Seth's framework made me stop and ask which end I actually have to hold.

What knots have you been pulling on? Not the easy ones — the ones that have been stuck so long you've stopped noticing them? Are you holding both ends of a rope that can't stretch any further?

Seth's short book won't untie them for you. But it will give you a way of seeing them clearly enough to start.

Read it once for the framework.

Read it again for the knots you missed the first time.