Battlecard: Just Keep It Positive
Respond when someone wants to keep an update positive at the expense of useful risk clarity.
A teammate asks you to keep a project update positive by removing an unresolved dependency or early risk. Remove the risk so the update lands better with leadership. Keep the tone constructive while naming the dependency, consequence, and next trigger. Make the update more alarming so nobody can miss the risk. Keep the risk, but frame it as a useful early-warning signal. Use: Progress is strong; Barrier is the dependency that could move the date; Next is the owner/date trigger that will resolve it. Let's keep it positive. We do not need to mention the dependency yet. We can keep…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in