The author opens with a concrete failure: “I spent six months building something nobody wanted… The problem was I built what I thought I was supposed to build. I looked at what other people in my space were doing and I did a version of that. Copied the model. Followed the template. And it didn’t work. Because the template was designed for someone else’s situation. Someone else’s audience. Someone else’s strengths.” The diagnostic question he eventually asks himself: “I’m 23. I don’t have the same audience as someone who’s been doing this for a decade. I don’t have the same resources. I don’t have the same strengths. Why would the same playbook work?”
The hidden cost of templates is that the assumptions they encode are invisible — you see the playbook, you don’t see the constraints it was tuned to. This is the practical-failure mode of Reasoning by analogy has a ceiling — you can never get beyond what already exists by copying what already exists — even within the space of existing solutions, copying often fails because the borrowed solution was solving a slightly different problem. The author’s worked example: assuming “be on every platform” was the right strategy without checking whether his audience and time budget made it true. When he broke it down — what am I trying to achieve? where do those people actually spend time? what’s my constraint? — the answer was the opposite of the template (“Go deep on one or two platforms instead of shallow on five”). The general fix: before adopting a playbook, name the constraints it assumes about its user and check each one against your situation.