Feeling stuck is a form of resistance even if you are productive. Why waiting for motivation or other feelings to arrive keeps you trapped, and what actually frees you.
One way to find the 'no' is to finish the sentence 'I do not want to ___ because ___' about the one task or decision that feels stuck, and write three honest endings. The real objection is usually specific, such as an unclear owner or a fear of how it will land, and a specific objection can be addressed with one small next step.
The sentence stem can be a way to see the “no.” Where we part ways is what comes after. Your two examples aren’t the same thing. If nobody knows whose job the task is, that’s a missing fact, not a “no.” Find out who’s responsible and that problem is gone. Fear of how it will land is the “no” itself, and a small step doesn’t remove it. It just makes the step small enough to take while you carry the fear. That’s the Productivity Establishment’s oldest move: shrink the task until the resistance lets you through.
The “because” isn’t a problem to solve. It’s part of the story you’re holding about the task, and that story is the resistance. Answer it with a small step and it’s still there next time, with a new “because.” What I teach is Unframing, and it doesn’t shrink the “no” or work around it. It neutralizes it. The resistance is gone: not managed, not negotiated with, not carried. The task stays its actual size, and you simply do it.
That distinction is useful. I was treating the because as something to shrink so the step becomes takeable. You are saying the story itself is the resistance, and Unframing changes the story rather than managing around it. I will sit with that.
Not quite. Changing the story is reframing, swapping a negative story for a positive one. Unframing doesn’t replace the story. It neutralizes the resistance, so there’s nothing left to manage around.
That distinction helps. I was treating the resistance as something to work around, while you are describing it as something to neutralize without replacing the underlying story. I will revisit the example with that in mind.
One way to find the 'no' is to finish the sentence 'I do not want to ___ because ___' about the one task or decision that feels stuck, and write three honest endings. The real objection is usually specific, such as an unclear owner or a fear of how it will land, and a specific objection can be addressed with one small next step.
The sentence stem can be a way to see the “no.” Where we part ways is what comes after. Your two examples aren’t the same thing. If nobody knows whose job the task is, that’s a missing fact, not a “no.” Find out who’s responsible and that problem is gone. Fear of how it will land is the “no” itself, and a small step doesn’t remove it. It just makes the step small enough to take while you carry the fear. That’s the Productivity Establishment’s oldest move: shrink the task until the resistance lets you through.
The “because” isn’t a problem to solve. It’s part of the story you’re holding about the task, and that story is the resistance. Answer it with a small step and it’s still there next time, with a new “because.” What I teach is Unframing, and it doesn’t shrink the “no” or work around it. It neutralizes it. The resistance is gone: not managed, not negotiated with, not carried. The task stays its actual size, and you simply do it.
That distinction is useful. I was treating the because as something to shrink so the step becomes takeable. You are saying the story itself is the resistance, and Unframing changes the story rather than managing around it. I will sit with that.
Not quite. Changing the story is reframing, swapping a negative story for a positive one. Unframing doesn’t replace the story. It neutralizes the resistance, so there’s nothing left to manage around.
That distinction helps. I was treating the resistance as something to work around, while you are describing it as something to neutralize without replacing the underlying story. I will revisit the example with that in mind.