Giving good context in operations and project management

A model knows how projects are usually run. It does not know how your company runs them. It has not seen your approval steps, your team’s capacity, the contract terms with your suppliers, or the decision made in last week’s steering meeting. Without that material it describes a typical company, not yours.

Giving good context means handing the model what a new project coordinator would need on their first day. That includes the charter, the current plan, the relevant procedure, the actual data, and the names of the systems you use. It also means removing out-of-date versions that would mislead it.

Where it comes up

• Updating a standard operating procedure

  Paste the current procedure, the change that prompted the update, and notes from the person who does the task each day. The model can then revise the steps that changed and keep the rest intact.

• A risk register for a new project

  Provide the project charter, the timeline, and the list of external dependencies. Add the risks from a similar past project if you have them. The register will then reflect this project, not a textbook list.

• A handoff document between teams

  Give the model the open tickets, the decisions log, and the contact list for the receiving team. A handoff built from these sources covers what the next team needs to act on.

What it looks like at each band

1. E1 · Foundational

   Gives the task and a sentence of background. Output describes a generic process and needs heavy editing to match how the team works. Does not yet connect the generic output to the missing material.

2. E2 · Proficient

   Includes the current plan or procedure, the key dates, and the relevant data. Output reflects the real project. Pastes source documents in rather than summarizing them from memory.

3. E3 · Distinguished

   Selects context for each task. Removes superseded plans and old versions of procedures. Labels each fact as confirmed or estimated. Keeps a current project brief ready to paste into any request.

4. E4 · Exceptional

   Maintains shared reference material the whole team uses with AI: current procedures, a glossary of internal terms, system names, and approval rules. Notices when that material falls out of date and corrects it before it causes errors.

Common mistakes

• Describing the process instead of pasting it

  A summary from memory leaves out the steps you do without thinking. Paste the written procedure, or a recording transcript of someone doing the task, so the model works from the real steps.

• Mixing old and current versions

  If you paste last quarter’s plan alongside this quarter’s, the model may blend them. Remove superseded documents or label them clearly as old.

• Leaving out internal terms

  Every company has its own names for systems, approval stages, and teams. Define them in the request, or the model will substitute general terms that your colleagues will not recognize.

A worked example

A revised returns procedure for a warehouse team after a change in carrier.

The full study guide for this skill, for every role, is Giving good context. The other five skills for operations and project managers are on the AI skills for operations and project managers page. A one-page summary is in the AI context checklist.