RETRIEVE

Surface the right information at the exact moment of action, not buried where no one looks.

Twenty minutes into the Tuesday meeting, your team is energetically debating a question you are certain was settled last quarter. Someone even wrote up the decision. But the writeup lives in a doc nobody has open, so the group re-litigates from scratch, and this time drifts toward the opposite conclusion, unaware it is overturning anything.

Retrieve means surfacing the right information at the exact moment of action or decision, instead of leaving it buried where no one looks. The cue is a decision or task about to happen that prior knowledge should inform. The operation: identify the moment of action in advance, pull the specific state that moment needs, such as prior decisions, open questions, and owners, and attach it directly to the moment, like a one-page brief pasted into the meeting invitation. When it works, the meeting starts from what is already known and spends its time on what is genuinely new. The failure mode to avoid comes straight from the spec: retrieving stale material can be worse than retrieving nothing, as when an expired policy gets reused without checking its review date. And do not retrieve answers before an attempt when the struggle itself is the point, as in learning.