Give Clear Instructions And Improve The Answer

A manager asks, write something about sales. An assistant can produce fluent text from that request, but it may be the wrong text for the decision. Does the manager need a sales total, a recommendation, or a short update on agreed actions? A clear brief gives the assistant a useful starting direction and gives you something concrete to check. In this lesson, we will improve a weekly briefing by finding a specific omission and changing the instruction that should address it. This is Give Clear Instructions And Improve The Answer, from Practical AI For Work, by Learn with Q. The main point is to state the task, relevant context, constraints and expected output, then revise an observed problem. You will build a brief from supplied facts, inspect a prepared draft, make a targeted revision and compare the result against the same criteria.

No programming or specialist AI knowledge is needed. We will work in three stages. First, define the brief and its source. Second, inspect what the draft actually did. Third, change the relevant instruction and check the whole result again. We will use the supplied fictional Harbor Desk Supplies case, connect the method to current official guidance and a documented workplace evaluation, then finish with practice and two learning checks. Include the details that let you complete and check this task.

A prompt is the instruction and context supplied to an assistant. Context means information relevant to the task, such as the source notes, audience or purpose. A revision is a specific change made after inspecting the result. These ideas apply to a separate chat and to assistance inside an application. In an application, selected text or connected files may already provide some context. Check what the actual tool can use instead of assuming it has every file or remembers another conversation. Before using a tool, confirm the permitted information and actions. This exercise uses supplied fictional notes and unsent drafts.

In real work, use business information only within an authorized workflow and the actual account settings. Keep passwords and access keys out. Reading a source does not authorize sending a message or changing a record. If no suitable permitted tool is available, complete the same reasoning with the prepared examples and a document editor. You can learn the method without buying anything. Here are the facts for our fictional April twenty twenty-six case. Operations will confirm the O one hundred and eight return count, with no deadline agreed. The sales lead will prepare a product-mix note by April tenth.

No new promotion decision was made. The communications role owns the weekly briefing, due April thirteenth, and all messages remain unsent. The briefing's due date belongs to the briefing. It does not become the deadline for the separate Operations action. Keep the numbered source notes available. Now inspect the request, write something about sales. It does not identify the audience, purpose, source or required form. An assistant could fill those gaps with plausible material that does not meet our task.

We need a short manager briefing about the stated actions. If an essential fact is missing, ask for it or preserve the unknown. Keep the context focused on the decision. Build the brief from the work. Name the task and audience. Identify the source notes to use. State the facts and limits that must survive, including owners and dates. Set an output form that fits the manager's use.

Here, the briefing must be at most one hundred and fifty words, preserve both actions, show the unagreed deadline, and add no promotion decision. These are acceptance criteria: conditions the finished result must meet. Use them when inspecting the draft. Our instruction can say: Draft an unsent weekly briefing for the fictional manager, using only the supplied Harbor notes. Keep the briefing within one hundred and fifty words. Preserve both actions, their owners and dates. State that the Operations deadline was not agreed. Do not invent a promotion decision.

Use plain, concise language. This brief tells the manager which actions to review and gives you a clear checklist for the draft. The complete copyable instruction and source are in the materials. Our two drafts are authored teaching examples. The first is readable and keeps the Operations action, the unagreed deadline and April tenth. But it says a product-mix note will be prepared without naming the sales lead. That omission matters: the manager cannot see who owns that action. The draft gives us useful starting text, and we have identified a particular defect to fix.

Compare that sentence with note two. The source names the sales lead, while the draft leaves the owner out. Mark the failed criterion, preserve the original draft and record the source line. A request to make the answer more professional would change style without clearly addressing this omission. You could directly repair the sentence in a document editor. If you want to improve a reusable instruction, test a change that makes the missing relationship visible. Change the output instruction to request a short source-check table before the briefing. Ask for one row per action from notes one and two, with columns for action, owner and deadline.

Keep the original briefing requirements. This changes one part of the brief: the review structure. The one-hundred-and-fifty-word limit applies to the manager briefing. Use the extra table to compare each relationship with its source. The second example includes Operations beside the return check and not agreed in its deadline field. The other row names the sales lead, the product-mix note and April tenth. The revised briefing also names both owners. Compare each row and sentence with the original notes.

The owner omission is now resolved. Recheck the remaining criteria too: length, dates, the unagreed deadline, no new promotion decision and the unsent boundary. A small format example can help explain the output you want. Show the column headings Action, Owner and Deadline, with placeholders. Say that it is an example of structure, while the numbered notes supply the facts. This keeps an invented example date out of the source evidence. For a simple edit, use the short structure that makes the result easy to check. Inspect the new answer before deciding what to do next.

If it introduced another defect, identify that defect and correct it or make another targeted revision. If the source itself is unclear, obtain clarification from the responsible person instead of pressing the assistant to sound certain. Keep the earlier versions so you can explain what changed. Stop iterating when the result meets the criteria and the review effort is reasonable. For a one-off short sentence, a direct human edit may be the efficient choice. There is a real workplace connection. A UK tax authority evaluation published in July twenty twenty-six described a Microsoft Copilot trial conducted from September to December twenty twenty-four.

Document drafting was among its widely used functions, and the report identified a need for practical, tailored training and time to learn effective use. Much of the evidence came from staff surveys, with additional methods. The evaluation describes workplace use; it did not test our fictional Harbor revision. Microsoft's official prompting guide, updated in September twenty twenty-six and checked for this lesson in October, describes a goal, context, source and expectations, followed by further conversation when needed. Apply that guidance to the work: identify the task and manager, supply the permitted notes, preserve the owners and dates, and specify the briefing's form. Check the context available in the actual tool.

You can ask an assistant to flag possible omissions, then verify them against the source notes. For an actual permitted test, record the instruction, source version, tool and account, date, first output, observed defect, revision and new output. Keep the criteria and relevant context consistent, and record changes. A single response does not establish reliability across other tasks or runs. Include preparation, the extra check table, generation, checking and correction in the effort log. Measure time and cost where possible; otherwise mark them unknown. The authored examples demonstrate the method without a measured speed or product-performance claim. Practice with the prompt-and-revision log and verified case facts.

Start from the vague request and write your own brief. Inspect the prepared first draft, identify the owner omission and link it to the source. Write one targeted revision, then compare the prepared second draft against every criterion. If a suitable permitted tool is available, test your instruction on the same fiction and save its actual output separately. Record what changed, what you verified and any unresolved issue. Keep all communications unsent. Learning check one. A colleague asks an assistant to write something about sales, but wants the fictional manager briefing from our notes.

What information should the brief add before you can judge the result? Pause and decide before the explanation. Add the task and audience, identify the supplied source, state the important facts and limits, and specify the expected form. For this case, that includes the brief length, both actions with owners and dates, the unagreed Operations deadline and no invented promotion decision. Do not supply invented sales numbers to make the request seem complete. The result can then be checked against explicit criteria. Learning check two. In a different fictional task, the source says the office closes on Friday.

A revision makes the announcement friendlier, but the new draft says Thursday. Has the revision produced an acceptable improvement, and what comparison would show that it helped? Pause before the explanation. The new draft fails the source-fact criterion, even if its tone improved. Correct the day to Friday, then compare the before-and-after versions against the same requirements for facts, audience, clarity and form. Recheck the complete result for other changes. Record the defect, revision, verified correction and review effort. The final announcement must preserve the source facts as well as suit its audience.

Give a clear brief, inspect the actual draft and revise the observed problem. Supply the relevant task, context, constraints, source and output form. A useful starting draft can reduce the work of getting organized, while the source check keeps its facts connected to the task. Use the log to explain what changed and whether it met the criteria. In the next lesson, we will inspect sources and distinguish a supported claim from an inference or an unresolved point.