Background and Context
This maxim was collected in 2020, filed with an unusual piece of self-documentation attached: Mike's own note that he "stole the three key phrases from somebody...no idea who," and that only "the interpretation for courseware design is mine." That admission is itself part of the artifact — a working maxim built by borrowing a structure and fitting it to a specific professional problem, rather than inventing whole cloth. The problem it answers is a chronic one in instructional design: the gap between talking about a course, planning a course, and a course that actually exists in front of learners. By 2020, digital courseware and e-learning were mature disciplines, but strategy decks and learning-objective documents that never survived contact with an actual build remained the field's most familiar failure.
Interpretation
The maxim's structure is a three-step escalation, and the grammar of each step is doing more work than it first appears. Words are cheap and strategy is fragile are both framed as warnings — "you can talk... but if you don't produce, nobody learns," "you can plan... but if you don't execute, nobody learns" — conditional threats about what happens in the absence of a further act. The third line breaks that pattern: building is everything is not a warning but a causal claim, "because only after you build it will students benefit." The first two steps tell you what goes wrong if you stop short; the third tells you what has to be true for anything to go right. That shift from conditional to causal is the argument in miniature — talk and strategy are necessary but not sufficient, while building is positioned as the sufficient condition, the one gate through which value must actually pass before a student sees any of it.
Note, too, the specific word Mike reaches for in the second clause: not "strategy is worthless" or "strategy is cheap" (which would flatten it to the same status as words), but strategy is fragile. Fragile is a stronger and more precise claim than worthless — a fragile thing has real structure and real value right up until the moment it meets a force it wasn't built to survive. The implication is that a course strategy is a genuine, worthwhile artifact that nonetheless breaks the instant it collides with the actual constraints of building — the SME who can't get the hours, the platform that can't render the interaction as storyboarded, the pilot cohort that reveals the sequencing was wrong. Strategy isn't dismissed here; it's diagnosed as brittle under exactly the pressure that matters.
The maxim's target is also narrower than a generic "execution beats ideas" claim — it names the actual unit of value: not activity, not a shipped deliverable, but student benefit. A course can be fully built, on time, on budget, and still fail the test this maxim actually sets, because "building is everything" is shorthand for "the built thing is the only vehicle through which benefit can occur," not a claim that any completed build automatically produces it. That distinction matters for how the maxim should be read: it collapses the talk/plan/build hierarchy down to one gate you must pass through, without collapsing the separate question of whether what passes through that gate is any good. Mike's own instructional-design vocabulary — a field organized around models like ADDIE (Analyze, Design, Develop, Implement, Evaluate) precisely because build-without-analysis and analysis-without-build are both recognized failure modes — sits behind the compression here; the maxim isn't naive about design process, it's impatient with design process that never converts into a finished course.
Current Relevance
The maxim reads differently in an era where the cost of producing courseware content has collapsed. Generative AI authoring tools — AI-assisted script and storyboard generators, automated slide-deck builders, text-to-video platforms like Synthesia, the AI features Articulate and other authoring suites have added since 2023 — can now draft a course outline, a script, or a rough interactive module in minutes rather than the weeks a strategy phase used to require. That means "words are cheap" and "strategy is fragile" are truer, and cheaper to demonstrate, than at any point since the maxim's 2020 origin: an AI-generated strategy document or content outline is nearly free to produce, and just as unable to teach anyone anything on its own. Rather than retiring the maxim, this sharpens the gate it names. When talking and planning cost almost nothing, the maxim's real test — did you build the thing, and does it hold up once a learner is actually inside it — becomes the only differentiator left, because production capability no longer separates the teams shipping real learning from the ones shipping polished outlines nobody will ever sit through.
Two adjacent movements in the field track the same instinct. Corporate learning-and-development teams increasingly favor rapid-prototyping models — the Successive Approximation Model (SAM), built explicitly as a faster, iterative alternative to ADDIE's more sequential planning phases — precisely because a rough built prototype, tested with real learners early, surfaces problems no strategy document catches. And the broader post-pandemic shift toward high-volume, fast-turnaround corporate training (a response to remote and hybrid work reshaping how organizations onboard and reskill people) has made courseware production itself a commodity skill; the scarce, differentiating work has moved back to instructional judgment — knowing what to build and whether it actually landed — which is exactly the territory this maxim reserves for "building is everything" rather than "building is easy."
Impact and Legacy
As a personal maxim rather than a published statement, its legacy is best read within the folder it lives in — alongside Mike's other maxims on incompetence, disparaging education, the "Pharisees of education," and merit and perception, which together sketch a working philosophy of professional judgment forged specifically in instructional design, not borrowed wholesale from general business writing. Read against those neighbors, "words are cheap... building is everything" functions as the constructive counterpart to the more critical entries in the same folder: where "Mike on Incompetence" and "Mike on the Pharisees of Education" diagnose failure from the outside, this maxim states the positive discipline that would prevent it — a personal production standard, not just a complaint about others falling short of one.
What distinguishes this entry from a typical private aphorism is the line closing it out in the file: "See if you can figure out who said this." Mike treats his own maxim as unfinished, an open research question rather than settled wisdom he's simply repeating — a small, deliberate invitation to verify rather than inherit an idea uncritically, which is the same posture this corpus project itself takes toward every quote it collects, and the reason a maxim collected in 2020 is only now, in this pass, getting the sourcing attempt Mike originally asked for.
Contrasting Views or Controversies
The strongest objection to "strategy is fragile" comes from instructional design's own front-end-analysis tradition: models like ADDIE exist because building the wrong course quickly is often more expensive than building the right course slowly. In safety-critical or compliance training — aviation, medical, regulatory — a course built without rigorous upfront needs analysis can certify learners on incorrect procedures, a failure no amount of shipping speed redeems. Dwight Eisenhower's famous inversion, "plans are worthless, but planning is everything," locates the value of strategy in the process of planning itself — the discipline of thinking through contingencies — even while agreeing the resulting document will be discarded. That framing sits in real tension with "strategy is fragile," which risks being read as license to skip the thinking, not just the document.
There's a second, quieter risk in "building is everything": it can slide into activity bias, mistaking we shipped something for we shipped something good. A poorly designed course that gets built and deployed satisfies the maxim's literal test — students can now, in principle, benefit — while still failing them in practice if the content is wrong, confusing, or untested. The maxim measures whether the gate was passed, not what came through it; taken uncritically, it could reward speed over instructional quality as readily as it corrects for paralysis-by-planning.
A third objection is structural rather than philosophical: the maxim assumes building is a choice available to whoever is talking and planning, when in practice it's frequently gated by resources the designer doesn't control — headcount, subject-matter-expert access, platform licenses, executive sponsorship. A designer can produce a rigorous strategy and still never get to "build" because the organization starves the project of the people or tools required to execute it. Read uncharitably, "building is everything" risks locating the fault entirely in the designer's follow-through when the actual bottleneck was organizational, not personal — a distinction the maxim's individual-scale framing doesn't make room for, and one worth holding onto before using the line to judge a stalled project.
Practical Application
- Individual (designer) — Treat every strategy document as disposable scaffolding, not a deliverable in its own right: timebox the planning phase deliberately (a fixed number of days, not "until it feels solid"), and protect the majority of project time for an actual build, prototype, or storyboard a learner can react to — a SAM-style rough prototype earlier is worth more than a fully polished strategy document later.
- Organizational (learning teams) — Track build-and-ship velocity as a real KPI alongside content-quality metrics, so "we finished the strategy phase" is never mistaken for progress in a status report; pair fast build cycles with lightweight learner-testing loops (even a five-person pilot) so speed doesn't outrun instructional quality, and use a Kirkpatrick-style evaluation check afterward to confirm the built course actually produced learning, not just completion.
- Organizational (resourcing) — Audit stalled courseware projects for the structural version of this maxim's failure mode: before concluding a team "didn't execute," check whether they were ever actually given the SME access, tooling, or headcount to build — the maxim diagnoses effort, not resourcing, and conflating the two produces the wrong fix.
- Civic (education policy) — Apply the same test to curriculum reform: a new standards document or policy framework benefits zero students until it's translated into classroom-ready materials a teacher can actually use tomorrow morning — the reform has only "talked" and "planned" until that translation exists.
- Cross-domain — Wherever "we agreed on the strategy" substitutes for "we shipped the thing," reread this maxim as a plain check: has anyone downstream actually benefited yet, or only the people in the planning room?
Background on the Author
Mike Hower's collected maxims — on courseware design, incompetence, disparaging education, and the "Pharisees of education" among them — read as the accumulated judgment of a career spent in instructional design, a field where the gap this maxim names (talk, plan, built course) is a daily, practical hazard rather than an abstraction. That professional vantage is what authorizes the specific target of "building is everything": not a generic Silicon Valley execution slogan borrowed for effect, but a claim scoped precisely to students benefiting — the deliberate word choice of someone whose actual job output is measured by whether a learner walked away able to do something they couldn't do before, not by whether a deck was well received in a stakeholder review.
The maxim's closing invitation — to identify the phrases' real origin rather than simply claim them — is consistent with the same generalist, precedent-checking habit visible elsewhere in his collection: the cross-cultural research on "expert generalism" filed alongside "Mike on Being an Expert Generalist" shows the same instinct to test a personal conviction against outside precedent instead of resting on instinct alone. Taken together, the maxim collection reads less like a set of slogans and more like field notes from someone who has watched, repeatedly and up close, what happens to courseware projects that never make it past talk or strategy — and who built this particular line to name the pattern precisely enough to catch it early next time.