Apply the Ladder of Inference to separate observable data from interpretation and action.
A team turns two missed QA comments into the conclusion that Support does not care about launch quality. Ladder of Inference: Data -> Meaning -> Assumption -> Conclusion -> Action The trap is treating an interpretation about intent as if it were observable fact. Observable data Name only what happened: Support missed two QA comments before launch. This removes motive language and gives the team something checkable. Selected data Ask what data is missing: ticket load, assigned reviewer, deadline clarity, and outage context. Teams often select the data that confirms the easiest story. Added meaning Identify the meaning added: missed…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in