Minimum Necessary Context

Share only the information a helper or tool actually needs for the task, and strip the rest.

You are handing a freelancer a customer-research task, and the easy move is to share the whole folder: the full client list with emails and purchase histories, two years of internal threads, the strategy deck. It saves you 10 minutes of curation. It also hands a stranger far more of other people's information than the task could ever require.

The rule is to share only what the helper or tool actually needs for the operation, and strip the rest. The cue is the moment a person or an app requests, or you are about to volunteer, more personal, proprietary, or historical data than the work packet requires. Run it in three steps: define the task precisely, ask what inputs it genuinely needs (segments and anonymized patterns, not names and emails), and redact or withhold everything else, including permissions, since access is context too. Check the choice against consent, law, and your own retention promises. When it works, the freelancer does the job just as well and your exposure surface, what could leak, be misused, or need cleanup later, is a fraction of what it would have been. The stop condition runs the other way: when stripping context starts degrading the work's quality, safety, or fairness, you have cut too deep; add back what the task truly needs.