Rescuing a dropped ball feels like help, but it quietly keeps your partner in a child role and proves the old system still runs underneath the new one. Today, if a domain slips, the former manager's job is to not rescue, and the new owner's job is to feel the real weight of the consequence and name an actual fix -- not just apologize.
Tap to view full size
This is the trap rescuing sets: the more capable one becomes at catching the other's dropped balls, the less the other needs to grow, and the more capable one is expected to keep catching. Today's assignment breaks the loop at step one -- refusing to become more competent so someone else doesn't have to.
If you are the former manager: prepare to watch a ball get dropped without catching it. Rescuing robs your partner of competence. If you are the new owner: prepare to feel the weight of real responsibility. Own the consequence and name your fix -- do not just apologize.
Your response here isn't saved yet -- that lands with activity persistence, a later step.
If a domain slipped, debrief without blame. Owner script: "I forgot [domain]. The consequence was [X]. Here is the system I will use to fix it." Non-owner script: "Thank you for owning that. I trust you to figure it out." Do not say "I told you so."
Your response here isn't saved yet -- that lands with activity persistence, a later step.
Did you catch yourself about to rescue, or about to say 'I told you so' -- and choose not to?
Day 10 of 28