Sample answers to chapter exercises
The chapter exercises are hands-on, so there is no single right answer. These sample responses show what a strong attempt looks like.
Chapter 2: Choosing features and models for five tasks
Chapter 3: Rewriting a vague prompt
Original. "Write a LinkedIn post about our award."
Rewritten.
Write a LinkedIn post for our company page announcing that Tallyline Forecasting won the 2026 Regional Small Business Innovation Award for our inventory-forecasting tool. Audience: operations leaders at mid-size retailers. Goal: credibility and demo requests. Tone: proud but understated; credit the team and our pilot customers. Under 150 words. End with a call to book a demo. No hashtags beyond two relevant ones.
What to compare. The rewritten version should name the award correctly, speak to the audience's interests, and end with a clear call to action, while the original is likely to be generic and may invent details.
Chapter 4: Verifying a factual answer
Applies to all businesses Statute scope section Incorrect; small businesses below a threshold are exempt
Corrected
Penalty up to $50,000 Statute penalties section Not found; penalty amount differs Replaced with the official figure
Takeaway. One of three claims was wrong and one was partly wrong. That is typical enough to justify checking specifics every time.
Chapter 5: Building a Project
Sample instructions for a recruitment coordinator's Project:
Purpose. Help draft job ads, interview guides and candidate emails for Northfield Manufacturing. Audience and voice. Candidates for skilled trades and engineering roles. Friendly, clear, inclusive language; no jargon; no gendered or age-coded words. Sources. Use the role descriptions, benefits summary and EEO statement in this Project. Do not invent benefits or salaries. Format. Job ads under 350 words with sections: role, what you'll do, what you'll bring, benefits, how to apply. Boundaries. Never draft rejection reasons or assess candidates. Flag legal questions to HR. Uncertainty. List any assumptions at the end.
Typical corrections moved into instructions after five test requests: use "you" rather than "the candidate"; include the salary range from the role description; put the closing date at the top.
Chapter 6: Mapping a weekly process
Process: weekly client status report.
Summarize progress and risks Augment: Claude drafts Lead checks risks and dates
Calculate budget burn Augment: code execution from the budget sheet Lead reconciles total Decide what to escalate to the cli‐
- ent
- Keep manual Lead's judgment
- APPENDIX F. SAMPLE ANSWERS TO CHAPTER EXERCISES
- Step Augment, redesign or keep manual Review point
Format and send Augment: Claude formats; lead sends Final read before sending
Estimated saving. From about three hours to about one hour per week, including review.
Chapter 7: Summarizing your AI policy
A strong one-page summary has five headings: approved tools and plans; data classes allowed in each tool; outputs that need human review or disclosure; prohibited uses; who to contact. If your organization has no policy, the summary should note that and list the questions to raise with your manager.
Chapter 8: Fixing an unsatisfying output
Example. A meeting summary was too long and missed action items.
Diagnosis using the symptom table. Wrong format and length, because the format was not specified. Single fix. Add: "Return three sections: decisions, action items (table with owner and due date), open questions. Under 200 words."
Result. The new summary was 180 words and captured all six action items.