Errata and feedback
The Playbook promises evidence on every claim, runnable prompts in every play, named companies in every case study. If a claim slipped, a prompt does not run, a citation is broken, or a case has materially changed shape since publication — that is what this page is for.
The standards the Playbook holds itself to are public. Errata is how the Playbook is kept at those standards after it ships.
What to flag
The five categories that get the fastest turnaround:
- Unsourced statistic. A bolded number with no named source attached, or a source that does not resolve. Tier-1 corrections (primary research) jump the queue.
- Non-runnable prompt. A template that fails its own declared example, has a missing variable, or returns a structurally wrong output for the stated failure mode.
- Broken citation. A footnote URL that 404s, a journal reference that was retracted, or a vendor report that has since changed shape.
- Case study that no longer holds. A named company case where the cited outcome has been retracted, restated, or substantially changed by the company itself.
- Voice or evidence drift. A passage that breaks the style guide (third-person drift, hedge filler, anonymous case) or the evidence standard (T4 source carrying a T1-coded badge).
Typos and broken internal links are welcome too — they ship between releases rather than waiting for the v1.x update track.
How to report
Errata is reported through GitHub Issues — public, archived, and version-controlled, so every report and every fix stays visible. A free GitHub account is all you need; GitHub handles sign-in, rate limiting, and spam filtering, so there is no form on this site to break or abuse.
Open an erratum report
The report form asks for the chapter or page, what is wrong, what you believe is correct, a supporting source, and — optionally — the name you would like credited if the fix ships. Required fields keep triage fast.
Open an issue
What happens after you submit
| Step | When |
|---|---|
| Acknowledgement | Within seven days. Every report is read by the author. |
| Triage | Within fourteen days for substantive corrections; within thirty days for voice and style notes. |
| Substantive fixes ship | Within sixty days, in the next v1.x release. |
| Typos and broken links ship | Between releases when the queue is short. |
| You hear about the fix | On updates, with named credit if you gave a credit name. |
The seven-day acknowledgement is a standard the page holds itself to. If you submit and have not heard back in two weeks, please flag it again — the original report likely got lost.
Credit policy
Reader-reported corrections are credited by name on updates when the fix ships, if you give a credit name in the report. The default is anonymous. Credit is something the reader earns and the author offers; it is not a condition for triage. The acknowledgements page in the v1.x edition lists every named reporter from that release cycle.
What this page is not
This is not a customer-support page. Questions about which play to start with, whether the Playbook covers your use case, or team licence pricing belong in a different place — start at about, and email the author at the address listed on author for anything the site does not answer.
This is also not a discussion forum. Errata reports are read and acted on. Conversations about the Playbook happen on the author’s social channels and at the events the Playbook gets reviewed at; this page is the public ledger of what got fixed.