A teammate resists documenting a decision, task owner, or project support file because the team can remember it. We do not need another system. Just keep it in your head. I am not documenting this for ceremony. I am documenting it so the next action, owner, and support file survive past the meeting and we do not spend next week reconstructing the same decision. The response reframes documentation as speed and reliability. It uses GTD's trusted-system principle and PARA's actionability without lecturing. Do not over-document low-risk chatter. Keep the capture lightweight: decision, owner, next action, support file. Avoid implying the…
Read the full lesson
Sign up free: one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in