Negotiate a Shared Team Habit
Negotiate a shared team habit by reducing ability cost and making team rewards visible.
Marcus M Engineering lead skeptical of process 1 Respect 2 Co-design 3 Reward Process objection 20 sec Only one of five experiment learnings reached roadmap, but Marcus worries the proposed habit adds process load. Resistance is a design signal, not a character flaw. Objection -> ability data Use Fogg to treat the objection as ability data, Clear to simplify the environment, and Duhigg to close the shared loop. A team habit earns adoption by fitting the workflow. Marcus: I get the intent, but one more required note after every experiment is process tax. What do you say first?
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in