Asking well · for operations and project managers
Asking well in operations and project management
A request like "make a project plan for the office move" gives the model almost nothing to work with. It does not know the move date, the number of people, the budget, or what is already booked. It returns a generic plan with generic phases.
Asking well means putting the planning decisions into the request. What is the deadline, and is it fixed? Who owns each workstream? What format will the team use, such as a table, a checklist, or a Gantt-ready list? What must the output leave out?
Where it comes up
A work breakdown for a system rollout
You need the tasks for rolling out a new scheduling system to four sites. A strong request names the go-live date, the sites, the teams involved, and asks for tasks grouped by phase with a column for dependencies.
Action items from a long meeting
A planning meeting ran ninety minutes. A good request asks for decisions, action items, and open questions as three separate lists. It also asks for each action item to carry an owner and a due date, or a note that none was stated.
A comparison table for three vendors
You have three proposals for facilities cleaning. The request should list the criteria you care about, such as price per site, contract length, and notice period. It should ask for the same columns for every vendor and a blank cell where a proposal is silent.
What it looks like at each band
E1 · Foundational
Gets usable output on familiar tasks with short requests. Requests name the document type but rarely the deadline, the owners, or the format. Corrects the output by hand instead of improving the request.
E2 · Proficient
Writes requests that state the scope, the dates, the audience, and the format. Asks the model to flag missing information instead of filling it in. Revises the request when the first output misses, adding what was left out.
E3 · Distinguished
Splits a large planning job into steps: phases first, then tasks within each phase, then dependencies and risks. States what the output must not do, such as invent owners or move fixed dates. Asks the model to list the questions a sponsor would raise before drafting.
E4 · Exceptional
Writes request templates the team reuses for recurring work, such as weekly meeting summaries or project kickoff plans. Knows when one precise request is enough and when a short exchange is better. Teammates produce more consistent documents by using these templates.
Common mistakes
Asking for a plan without the fixed points
A request without the deadline, the budget, and existing commitments leaves the model free to treat everything as flexible. You then rework the plan around constraints it never knew about.
Letting the model fill gaps silently
Ask the model to mark missing owners, dates, and figures as missing. Otherwise it supplies plausible ones, and a guessed date looks the same as a real one.
No format stated
A plan in paragraphs is hard to paste into a tracker. Name the columns or the structure you need, so the output fits the tool the team already uses.
A worked example
A project plan for moving a fifty-person team to a new office floor.
Create a project plan for our office move.
The model does not know the move date, the team size, the budget, or what is already arranged. It will produce a generic plan with invented phases and durations that match nothing in your situation.
Create a task list for moving 50 people from floor 3 to floor 6 of the same building. The move date is fixed: the weekend of March 14. IT, facilities, and each department lead own their own tasks. Furniture is already ordered. Return a table with columns for task, owner team, start, finish, and depends on. Mark any date you cannot derive from these facts as "to confirm". Then list the five risks most likely to move the date.
The request gives the fixed date, the scope, what is done, the owners, and the format. It tells the model to mark unknowns instead of inventing them. The risk list gives the manager something to check.
The full study guide for this skill, for every role, is Asking well. 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 prompt checklist.
See where you stand
The free check grades asking well and the other five skills in about fifteen minutes. Nobody sees the grade but you.
Then build the skills and prove it. The three steps for operations and project managers list the courses and templates that fit the work.