Decide what application would look like
To learn whether readers use your advice, define a specific action outside the content itself, then ask for evidence appropriate to that action. Keep opening, attempting, producing, using, and getting a result separate. Do not turn a download or a positive rating into a claim that the method worked.
If your book teaches people to write clearer project briefs, an application could be using a revised brief to start a real project. Generating that brief inside a companion is an earlier step. A favorable comment about the companion is a different signal again.
The worksheet below is an original planning resource for authors. It is not a description of analytics automatically available in Skillfully, and its fictional examples are not customer results.
Separate appreciation from a reported action
Readers can value a book in several ways. In a discussion of personal-development books, u/Kawersauce wrote:
“I wouldn't say I've applied any concepts directly from the books, but they have made me think more about how I spend my time.”
That is a meaningful reported benefit. It is still different from evidence that a particular exercise was used.
In the same discussion, u/-ramona described applying a specific technique from Marie Kondo's book:
“I started folding all of the clothing the way she recommends and have never been tempted to go back.”
This is a concrete self-report of behavior. It is not independently observed, and it does not establish what caused every later benefit the commenter experienced. Neither account measures Skillfully or your method. Together, they illustrate why “the book helped” needs a more specific follow-up before you classify the kind of help.
Training evaluation makes related distinctions. The Kirkpatrick Model separates reaction, learning, behavior, and results. The author worksheet here uses its own practical categories; it is not a validated substitute for that model or a causal evaluation design.
Use an evidence ladder for one reader task
Choose a bounded task, such as preparing a brief for a volunteer design project. Then fill in this resource:
| Stage | What you want to know | Possible evidence | What it does not establish |
|---|---|---|---|
| Access | Did the reader reach the material? | A recorded visit or confirmed access | That they read or understood it |
| Attempt | Did they try the exercise? | Submitted inputs or a reader's account | That the work was completed correctly |
| Artifact | Did they produce something usable? | A brief reviewed against explicit criteria | That anyone used it outside the session |
| Use | Was it used for the intended task? | Reader reports sharing it at the project kickoff | That it improved the project |
| Observed result | What happened afterward? | A dated account or relevant record of what changed | That the method alone caused the change |
“Possible evidence” means evidence you could deliberately collect with an appropriate process. Do not assume your current tools record it. If you cannot observe a stage, mark it unknown.
The stages also need not form a neat funnel. A reader might use the book's worksheet on paper without ever opening the skill. Someone might return with an artifact created elsewhere. Preserve the route rather than treating missing product activity as absence of application.
Copy this outcome record
Use one record per reader task, with only the information needed for the question:
Task: What was the reader trying to do?
Method step: Which part of the book or skill did they use?
Starting situation: What was happening before the attempt?
Attempt and artifact: What did they actually produce or change?
Use: When and where did they use it, if at all?
Result: What happened afterward, including no change or an unwanted result?
Evidence type: Reader report, inspected artifact, observed behavior, or another record?
Other influences: What else changed during the same period?
Unknowns: What can you not establish?
Permission: What may you retain, inspect, or quote?
A fictional filled example might say: “Reader reports using a revised volunteer brief at Tuesday's kickoff. The brief names the audience, deliverable, and decision owner. Reader reports two clarification questions were resolved during the meeting. No independent observation of the meeting; previous kickoff not measured; team members also changed.”
That is useful evidence for learning about the experience. It does not support “the skill reduced project confusion” as a causal marketing claim. Keep the modest account rather than polishing away its limits.
Ask a follow-up that makes non-use easy to report
After the reader has had a plausible opportunity to use the artifact, ask:
What happened with the brief after our session? You can say you used it, changed it first, have not used it yet, decided it did not fit, or tried it and found a problem.
Follow with a question matched to the answer. If they used it, ask for one specific example of what happened. If they did not, ask what prevented use. Avoid requiring an upload to answer a simple question; a description may be enough for your immediate purpose.
Do not combine the research question with pressure to provide a testimonial. Readers should be able to report an ordinary or disappointing outcome without feeling they failed the author. Ask separately before publishing a quote, and preserve its meaning.
Timing should fit the task. A brief can be used at the next relevant meeting; an annual planning exercise may have a much longer interval. A fixed follow-up date that arrives before the opportunity to act can make non-use look like failure.
Report counts with their missing information
If you summarize a small pilot, name the population, observation period, and response count. For example, a hypothetical report could state: “We invited ten participants to a two-week follow-up; six replied. Four reported using their artifact, one had not yet had the relevant meeting, and one decided the task did not fit.”
Those numbers are invented to demonstrate reporting and must not be reused as Skillfully results. The four nonresponses remain unknown. Do not quietly classify them as successes or failures, and do not report four out of six as the application rate for all ten without explaining the difference.
Likewise, count readers and attempts separately. One enthusiastic reader completing five exercises is valuable, but it does not show that five people adopted the method. Keep small samples visible as small samples.
Use the record to decide what to improve
The evidence should lead to a decision. Many attempts without usable artifacts suggest inspecting the exercise and feedback. Usable artifacts without use suggest examining task fit, timing, authority, or transfer into the reader's work. Use without a desirable result calls for investigating the method and surrounding conditions, rather than assuming another onboarding message will solve it.
These are diagnostic leads, not automatic conclusions. The agent skill quality guide can help inspect the artifact itself; this record adds what happened beyond the output.
Bring one reader task and a filled or blank outcome record to Skillfully and choose Book onboarding. Define the evidence you want before choosing what to count.