Posts

Build a Small Glossary Before Asking AI to Explain Technical Notes

Simplifying a technical note can introduce error when an assistant replaces a precise term with a familiar but different one. Prepare a small glossary and an audience statement before requesting the rewrite. Keep definitions tied to the source material. Set up a practical example For a fictional project note, distinguish a draft, a scheduled release and a public release. Explain which terms must remain exact and which can be followed by a plain-language explanation. Avoid asking for a universal definition when the term has a specific meaning inside your project. Ask the assistant to rewrite one paragraph first. Require it to preserve the relationships between components and to mark any term it cannot explain from the supplied notes. An unanswered question is more useful than an elegant analogy that changes the mechanism. Verify before proceeding Compare the rewrite with the original. Check whether a possibility became a guarantee, whether a prerequisite disappeared and whether the anal...
Post a Comment
Read more

Keep an AI Draft From Inventing Personal Experience

A draft may sound more persuasive when it claims that the writer tried a product or learned a lesson firsthand. Do not publish that claim unless it reflects a real, documented experience you are authorised to describe. A fictional example should remain visibly fictional. Set up a practical example Search the draft for phrases such as “I tested,” “we found,” and “in my experience.” For each one, identify the underlying observation, date and scope. If there was no test, rewrite the passage as a proposed method or an illustrative scenario. For a fictional productivity article, replace “This saved me two hours every week” with a worked example showing the steps the method removes. Do not turn the example into a measured time saving. The reader can still evaluate whether the workflow suits their situation. Verify before proceeding Check photos, captions and charts for the same problem. An illustrative screenshot or generated scene should not imply access to a real customer, laboratory or pr...
Post a Comment
Read more

Use a Change Table to Review an AI Rewrite

A clean rewritten document can hide changes you did not request. For a substantial edit, ask for a short change table beside the proposed copy. Review meaning, facts and commitments before spending time on sentence rhythm. Set up a practical example Create columns for Original passage, Proposed passage and Reason. For a fictional service notice, protect dates, URLs and the distinction between a confirmed event and a possible event. A revision from “may be delayed” to “will be delayed” is not merely a style improvement. Focus the table on material changes rather than every comma. Ask the assistant to flag removed qualifications, added examples and altered instructions. Its table may omit a change, so compare the final copy with the original as well. Verify before proceeding When you reject a change, state the rule it violated. “Preserve uncertainty where the source is uncertain” is more reusable than asking for a vaguely softer tone. Apply the rule to the whole document and check other ...
Post a Comment
Read more

Make an AI Handoff Note Useful to the Next Person

A handoff note should let the next person continue without guessing what happened. Ask for current state, verified actions, evidence locations and remaining work. Keep plans and completed actions in separate sentences. Set up a practical example For a fictional website update, “Contact page drafted” is different from “Contact page published and opened successfully.” Include the actual page or file reference when available, along with any unresolved limitation. Do not describe a preview as the live result. List what must be preserved before the next edit: existing posts, scheduled dates, account identity and backups. Add the smallest useful reproduction steps for a failure. An unexplained “does not work” note forces the next person to repeat the investigation. Verify before proceeding Read the handoff against the real service state before sharing it. Remove stale instructions that refer to an abandoned version. Keep credentials and unnecessary personal information out of the note; use a...
Post a Comment
Read more

Review an AI File-Renaming Plan Before Anything Moves

A file-renaming task should begin with a proposed mapping, not with moving files immediately. Ask the assistant to show the current name, proposed name and reason for each change. Keep ambiguous files unchanged until you can identify them confidently. Set up a practical example Use a fictional folder containing report.pdf, report-final.pdf and report-final-2.pdf. The names alone do not prove which document is latest. Have the assistant list the evidence needed to distinguish them instead of deleting or overwriting the apparent duplicates. Review the mapping for collisions. Two source files must not silently become the same destination name. Check extensions, date formats and whether another application depends on the existing path. Preserve a backup and use the recovery mechanisms appropriate to your actual environment. Verify before proceeding Approve a small reversible example first. After execution, compare the actual folder with the approved mapping and open representative files. A...
Post a Comment
Read more

Split an AI Writing Job at the Point Where Verification Changes

A single request to research, write and verify an article can hide which stage failed. Split the work where the required evidence changes. Each stage should produce an inspectable result before the next one relies on it. Work through an example For a fictional guide to a software feature, research produces checked vendor references and a list of unresolved questions. Drafting turns those notes into an explanation. Verification compares the finished claims with the sources and checks any demonstrated steps in the relevant environment. Do not label a research outline as a finished article or a suggested test as a completed test. Use status words that match the actual result: prepared, drafted, checked and published describe different states. Check the result Keep handoffs compact. The drafting stage needs the reader promise, factual notes, source links and claim boundaries. It does not need an unfiltered transcript of every abandoned idea. If a fact remains uncertain, carry that uncertai...
Post a Comment
Read more

Record AI Task Timing Without Inventing a Speed Benchmark

An answer that appears quickly may still require substantial correction. If you want to compare workflow speed, define the start and finish of the task before measuring. Record actual observations and keep the original outputs. Work through an example For a fictional document-formatting job, start the timer when the prepared input is submitted and stop when the output meets your acceptance checks. Record drafting time and correction time separately if you can measure both consistently. Do not infer exact timings from a progress animation. Use the same input and completion criteria for each trial. Include time spent checking facts, repairing formatting and transferring the result into its destination. Record interruptions or failed attempts instead of discarding them without explanation. Check the result A small comparison can help you choose a workflow for your own task. It does not establish a universal product ranking. Avoid presenting one fast result as an average or inventing decim...
Post a Comment
Read more