Design examples for readers outside your usual audience

To adapt an example for a different reader, identify the principle that makes the original example work. Write down its necessary conditions. Then change the setting, language, and available resources while checking whether the same reasoning still applies.

Replacing “marketing manager” with “shop assistant” is not enough if the original example assumes the reader can set everyone else's priorities. The new reader may understand every word and still lack the authority the method requires.

For an author creating an AI companion, this matters whenever a reader asks, “How would this work in my situation?” A plausible story can make the advice feel personal without making it appropriate. Your instructions should explain both how to adapt an example and when to stop adapting.

The worked examples below are fictional. They show a proposed way to design examples for a book about finishing small projects. They are not reader results, model outputs, or evidence that the method works in every setting.

Suppose a chapter teaches this principle:

Define the immediate task through an observable piece of work that the reader can complete or hand over. Separate that task from the larger outcome it may contribute to.

The original example concerns a designer preparing a poster. “Make the event successful” is too broad for that task. “Prepare a poster draft with the confirmed date, location, and contact details for organizer review” identifies a visible artifact and a handover point.

Before adapting it, record the reasoning:

1. The larger goal contains factors outside the reader's control.
2. The reader needs a bounded contribution they can actually make.
3. The completed contribution must be recognizable.
4. Any dependence on another person's decision must remain visible.

The poster is replaceable. The distinction between contribution and outcome is the teaching target.

The method has conditions, too. The task needs a meaningful completion point, the reader needs enough information to describe it, and someone must know what happens after handover. Producing an artifact is not automatically progress if it serves no relevant purpose.

An author companion could ask:

What are you trying to contribute? What can you decide yourself? Who needs to use or approve the work? What information is still missing?

These questions help distinguish two readers with the same job title. One may own the whole project; the other may be preparing a recommendation for someone else. Giving both a managerial example would conceal that difference.

A retail worker described their circumstances this way:

“I am trying to focus on breaking the workload into chunks, and completing them one at a time, though this can be difficult with constant interruptions around me, as there is not a time I can work that avoids customers (or other staff who ask for my help).”

— u/butterflyparadise, asking about productivity in a retail role

That is one person's account, not a description of every retail job. It makes a concrete point for example design: the person's work conditions matter more than a familiar occupational label. An example requiring uninterrupted control over a shift would need checking before it could help this reader.

Here is a proposed adaptation map for the small-project principle. All entries are invented teaching examples.

Read across each row. Does the proposed task still contribute to the stated goal? Can the reader recognize completion? Have we quietly changed a dependency into something the reader controls?

Then read down each column. The settings differ, but the same distinction remains visible: complete a bounded contribution without pretending it guarantees the larger outcome.

The examples also vary in useful ways. The illustrator follows another person's requirements. The volunteer needs organizer confirmation. The hobbyist must distinguish sources already inspected from promising leads. Those differences create opportunities to teach the principle's limits, rather than merely display different nouns.

For the illustrator, a weak adaptation would say, “Your finished task is to win the commission.” That makes someone else's selection decision the reader's completion criterion. A better example identifies the submission the illustrator controls and preserves the uncertainty about selection.

The companion should also avoid inventing a client's requirements. If the reader does not know the requested format, the next task may be to locate or clarify the brief. Creating a polished sample sheet against guessed requirements would not follow the proposed principle well.

For the volunteer, “Write the correct arrival instructions” hides an information dependency. The author should show how a draft distinguishes confirmed details from questions for the organizer. A reference card with an unresolved opening time is a review artifact, not a final instruction to distribute.

For the family-history hobbyist, “Prove where the relative lived” turns a research hope into a task promise. The adapted example instead describes a source list and its limits. A reference to a record is different from inspecting that record; the completion evidence should preserve that distinction.

These explanations do more than make the examples longer. They reveal the same decision in three forms, giving the reader something to compare with their own situation.

Now consider a reader asking for an example about repairing a friendship. The proposed task is: “Send a message, then mark the relationship repaired.”

This is an invalid transfer. Sending a message may be a bounded action, but another person's response and the state of a relationship cannot be treated as a finished artifact under the sender's control. The example has changed the meaning of success while pretending to preserve it.

The companion can acknowledge that the book's distinction may help someone describe their own next action. It should not use that distinction to promise a relational outcome or supply specialized advice outside the author's expertise.

Write the rejection beside the valid examples:

Do not turn an action someone controls into proof of an outcome
that depends on other people, unresolved evidence, or later events.

If the requested adaptation needs expertise the method does not
provide, explain the boundary instead of inventing a complete plan.

A rejected example is useful authoring material. It identifies a tempting mistake that a collection of successful-looking examples might never expose.

After showing two examples, ask the reader what stays the same. Avoid a vague “Does that make sense?” that can be answered without using the distinction.

For this fictional chapter, the check could be:

Which part of your goal is your contribution, and which part depends on something beyond that contribution? What would let you recognize that your own part is complete?

Yale's Poorvu Center recommends comparative scenarios as one way to teach transfer between contexts. The author exercise here follows that design idea; it has not been evaluated as a learning intervention.

A published Science Learning Hub account offers a concrete classroom illustration. A teacher first used a marine food-web activity, then adapted the work to organisms on the school grounds. The report attributes this reflection to the teacher, Cath:

“It’s broadening their thinking, getting them to think a little wider and deeper.”

— Cath, in the Science Learning Hub account

That comment concerns the reported classroom activity. It does not establish an outcome for author AI companions. The relevant design lesson is narrower: a new setting can be connected explicitly to the concept being taught, instead of being offered as an unrelated story.

For each adaptable example in your skill, keep a short brief:

Principle:
Decision the reader must make:
Necessary conditions:
Details that may change:
Details that must not change:
Information to ask for first:
Two valid adaptations:
One invalid adaptation and why:
Question that checks the reader's application:
When to defer to the author or another source:

For the small-project method, “profession” belongs among the details that may change. Control over another person's approval does not. Missing information should remain missing until supplied; it should not be filled in merely to make the scenario flow.

Label invented teaching examples as hypothetical. Keep genuine reader cases separate, with permission and appropriate anonymization. A realistic name and a specific situation do not make an invented example customer evidence.

If you need the implementation structure, the guide to writing an agent skill covers the underlying format. The adaptation brief supplies the author judgment that belongs inside it.

Before treating an adaptation as ready, ask a reader familiar with that context to inspect its assumptions. Can the person in the example make the stated decision? Does the proposed artifact have a real use? Is the language understandable? Is an important dependency absent?

Ask them to identify one point where the example would fail in their actual situation. That request is more informative than asking whether the example feels relatable. Record what they found and revise the particular assumption involved.

A positive review of the example does not validate your method in a new profession or culture. Keep the publication claim at the level the evidence supports: an example designed for a stated situation, with its boundaries visible.

To develop examples around your own book, visit Skillfully and choose Book onboarding. Bring one chapter example, one unfamiliar reader context, and one situation where you would decline to apply the method. Those three inputs make the adaptation decisions concrete.