The Case Study Is A Hack

Every consulting site has a Case Studies page. This one does not. This page is where it would be. This piece is why it is not.

The case study is the load-bearing marketing instrument of the restaurant consulting industry. It is also broken at the mechanism level. Not marginally broken. Not “sometimes misleading.” Formally disqualified as evidence by the research community that invented the instrument, and deployed by the consulting industry anyway.

That is the fact. This piece prosecutes it.

The Instrument The Restaurant Industry Runs On

Walk into any restaurant consulting engagement, any restaurant conference stage, any restaurant trade publication, any restaurant business-school elective, any private-equity restaurant thesis, and you will find case studies doing the load-bearing work.

The consultant closes the deal with case studies. The trade publication builds the issue around case studies. The conference programs the operator whose case study is the season’s story. The business school teaches through the case method. The PE firm markets the portfolio company on the case study of the turnaround. The book publisher acquires the operator memoir because memoir-as-case-study is a category.

Every layer of the industry’s authority structure runs on the same instrument. The instrument does not work.

What A Case Study Actually Is

A case study, as the restaurant industry deploys it, is a retrospective narrative about one operator, at one operation, in one market, at one moment in time, with one specific capital position, one specific cast, one specific Guest base, one specific competitive set, one specific vendor ecosystem, and one specific set of external conditions that will never occur in that configuration again.

That narrative gets presented as evidence that a method works.

The audience is expected to conclude: this operator ran this play, this outcome resulted, therefore this play produces this outcome. The audience then hires the consultant, buys the book, attends the conference, or invests in the fund on the basis of the inferred causal chain.

The inference is broken. The narrative is not evidence. The outcome is not proof of the method. The restaurant consulting industry runs on the audience’s inability to see the break.

The Reduction

The specific move is a reduction. A rich, multi-variable, path-dependent, context-locked outcome gets compressed into a linear cause-and-effect story. Everything that made the outcome possible gets stripped out of the story so the method can carry the narrative weight.

The operator’s fifteen years of accumulated Guest relationships before the case study period — stripped.

The operator’s specific market timing, when the neighborhood was inflecting demographically, or when a competitor closed, or when a food trend was landing — stripped.

The operator’s specific capital structure, the fact that the family bought the building in 1987 and the operation carries no rent burden — stripped.

The operator’s specific cast — a kitchen manager who had been with the operation for eleven years and knew every quirk of the equipment and every recipe by feel — stripped.

The operator’s specific Guest base — a dense population of regulars accumulated across a decade of before-the-case-study relational work — stripped.

The operator’s specific labor market position — a location where the wage floor was low enough and the applicant pool deep enough that staffing was not the constraint — stripped.

Every one of those factors was load-bearing for the outcome the case study presents. Every one of them gets removed from the story so the story can be told as: the operator applied the method; the method produced the outcome; therefore the method works.

That is Case Study Reduction. The reduction of a specific, path-dependent, context-locked outcome into an executable path presented as generalizable.

The Research Community Formally Disqualified This Instrument

The failure is not my complaint. It is settled.

The National Institutes of Health names case studies’ primary limitations as: no broad application (results reflect only one unique context, person, or setting), difficulty of replication (other researchers cannot repeat the exact conditions to verify the findings), no cause-and-effect proof (case studies describe what happens but cannot prove why or show direct links between variables), researcher subjectivity (the author’s personal views alter how data is collected, viewed, and reported), and subject self-reporting bias (people in studies misremember past events or change behavior because they know they are watched).

Every intro research-methods textbook teaches the same consensus. The major limitation of case studies is the inability to generalize findings from a single case, small group, or unique event to a larger population. This is not fringe. It is not contested. It is what a first-year graduate student learns in the first month of a research-methods course.

The academic research community — the community that invented the case study as a methodological tool, refined it across decades, and understands its actual epistemic limits — trains its own researchers to treat case studies as illustrative, not as generalizable evidence.

The restaurant consulting industry deploys case studies as generalizable evidence anyway. The industry knows what the academy knows. The industry deploys the instrument the academy has disqualified because the instrument works commercially even when it fails epistemically.

That is the frame. Now the mechanism.

Six Ways The Restaurant Industry Exploits The Disqualified Instrument

Each of the NIH-named limitations has a specific counterpart in how the restaurant consulting industry deploys the case study. The academic literature names the limitation. The industry exploits the limitation. Named side-by-side:

The limitation: no broad application, results reflect one unique setting. The exploitation: the industry sells the case study as a template the next operator can execute.

The case study documents one operator’s specific outcome inside one operator’s specific context. The consultant then packages the narrative as a repeatable method the next operator can apply. Every element of the case study’s context — the market, the cast, the capital, the timing, the Guest base — is context-specific and non-transferable. The consultant either does not know this or knows it and sells the case study anyway.

The limitation: hard to replicate, other researchers cannot repeat the exact conditions. The exploitation: the industry deploys the case study as evidence of a repeatable method.

If academic researchers cannot replicate the case study’s conditions to verify the finding, no operator can replicate the case study’s conditions to reproduce the outcome. The next operator is in a different market, at a different moment, with a different capital position, a different cast, a different Guest base. The case study’s method has no evidentiary claim on the next operator’s context. The consultant presents it as if it does.

The limitation: no cause-and-effect proof, case studies describe but do not prove causation. The exploitation: the industry attributes the outcome to the consultant’s method as if causation were proven.

The case study documents that the operator implemented the consultant’s method and the outcome improved. It does not — and cannot — establish that the method caused the improvement. The operation was running dozens of other variables simultaneously. The market was moving. The Guest base was shifting. The competitive set was evolving. Any one of those could have carried the outcome. The case study attributes the outcome to the method. The math cannot support the attribution.

The limitation: researcher subjectivity, the author’s views alter data collection and reporting. The exploitation: the case study is written from the consultant’s perspective, selecting for outcomes that flatter the method.

The consultant is both the author of the case study and the seller of the method. The consultant chooses which engagements to write up, which metrics to feature, which timeframes to use, which context to include, and which context to omit. Every editorial decision is made by the person whose commercial interest depends on the case study reading favorably. This is not a bug in the consulting-industry case study. This is the operating condition.

The limitation: subject self-reporting bias, people misremember or change behavior when watched. The exploitation: the case study sources the operator’s own recollection of the engagement.

The featured operator is the primary source of the narrative. The operator’s recollection is filtered through the desire to be featured favorably. The operator has commercial and reputational interests in the case study reading well. The operator’s memory of the engagement was formed during a period when they knew the engagement might become a case study. Every self-reporting bias the NIH warns about operates in the case-study interview.

The limitation: selection bias built into which cases become case studies at all. The exploitation: the consultant selects for engagements where the outcome landed favorably; failed engagements never become case studies.

The universe of restaurant consulting case studies is the small subset of engagements where the outcome was favorable enough to survive as a narrative. Every operator who applied the method and failed does not become a case study. Every operator who applied the method and produced an ambiguous outcome does not become a case study. Every operator who applied the method and cannot be reached because their operation closed does not become a case study. The industry publishes only survivors. The industry’s case study library is a survivor’s ledger. Nothing in the ledger contains evidence about the method’s actual failure rate, because the failures are systematically excluded before the ledger is compiled.

Six mechanisms of exploitation. Every restaurant consulting case study fails on some subset of them. Most fail on all six simultaneously. None of the six are disclosed in any case study I have ever read.

The Sibling Move — Framework Substitution

Case Study Reduction has a sibling that operates alongside it. Where Case Study Reduction takes a specific operation’s outcome and presents it as a generalizable method, framework substitution takes the absence of a framework and substitutes a case study in the framework’s place.

The restaurant consultant who has no operating framework — no articulated physics, no lexicon of load-bearing terms, no theory of what the operation actually is and how it produces its outcomes — needs something to fill the framework-shaped hole in the sales pitch. Case studies fill it.

Three case studies read as “here is a track record.” Ten case studies read as “here is a methodology.” The consultant never has to articulate the methodology, because the audience infers a methodology from the volume of cases.

The audience is doing the work the consultant refuses to do. The audience is constructing the framework the consultant does not have. The audience credits the consultant with a framework that exists only in the audience’s inference. And the consultant collects the fee.

This is why the field runs on case studies rather than on frameworks. Frameworks are evaluable. Frameworks can be tested against the operator’s own operation and either hold or fail. Frameworks commit the consultant to a specific claim about how the operation works. Case studies commit the consultant to nothing. Every case study is exempt from generalization by construction — the operator was specific, the context was specific, the outcome was specific. The consultant is not on the record for anything.

A consultant who publishes a framework is exposed. Every claim in the framework can be tested. Every mechanism can be prosecuted. Every prediction can be checked. A consultant who publishes only case studies is protected. Nothing in the case study can be prosecuted because nothing in the case study is a claim about the future. It is only a claim about the past, and the past is beyond dispute.

Framework substitution is the reason the field runs on case studies. Case Study Reduction is what the field does inside the substitution.

The Industry Infrastructure That Keeps Producing The Reduction

Case Study Reduction is not one consultant’s technique. It is the operating instrument of an entire industry infrastructure.

The trade press. Runs case studies because they close ad deals with the featured operators’ vendors, because they generate reliable reader traffic, and because they are cheap to produce relative to investigative reporting. Every restaurant trade publication has a “success story” beat. Every one of those stories is a case study reduction executed at scale, without a single disclosure of the epistemic failures the NIH names.

The business school. Runs case studies because the case method is the load-bearing pedagogical instrument of the MBA program. Two years of case-method instruction trains a generation of executives to reason from retrospective narrative to prospective decision. The training produces graduates who cannot evaluate a claim without a case study to anchor it, and cannot see the reduction happening because the training is the reduction. Every MBA-trained restaurant consultant is a Case Study Reduction propagator by pedagogy.

The consulting firm. Runs case studies because the sales cycle depends on them. A prospect asks “what have you done” and the case study is the answer. The consultant cannot answer “here is our framework and here is the physics that generalizes across operations” because the consultant does not have a framework and has not thought at the physics level. The case study substitutes for the missing framework.

The conference stage. Programs the operator whose case study is the season’s story because the operator’s presence produces registration revenue. The operator tells the story of the case study. The audience hears the reduction. The audience buys the consultant, buys the book, buys the software, buys the next conference ticket. The industry’s event revenue model requires the reduction to keep operating.

The private equity firm. Produces case studies because portfolio value depends on presenting the thesis as executed. The PE narrative that turned a distressed restaurant chain around into a scalable growth story is Case Study Reduction at institutional scale, deployed to raise the next fund on the strength of the last narrative.

The book publisher. Acquires the operator’s memoir because memoir-as-case-study is a category. The operator writes the narrative. The reduction is the book’s central move. The book sells because the audience wants the reduction. The publisher underwrites the acquisition on the audience’s willingness to buy retrospective narrative as evidence.

Six industry infrastructure layers. Every one of them runs on Case Study Reduction. None of them can afford to name the mechanism. The industry’s entire authority structure requires the audience to accept case studies as evidence.

This Is Not A Restaurant Problem

The mechanism the restaurant industry runs on shows up wherever advisory services are sold on retrospective narrative.

UX design’s practitioner community indicts its own case-study economy for cherry-picked data, fabricated linear process narratives, and portfolios that read as fiction. B2B SaaS marketing prosecutes case studies as self-serving vendor promotion disguised as customer praise. Academic methodology critics have named the non-repeatability and non-generalizability problems for decades. Design and creative fields prosecute the cookie-cutter templates that pass as evidence of capability. Small-business acquisition consulting sells case studies as proof the acquisition playbook works, ignoring the population of buyers who followed the playbook and got buried.

Every field that has looked carefully at case studies has named subsets of the same failure. None of them have locked the mechanism as a term or prosecuted the reduction as a specific move.

The restaurant consulting industry is not exceptional in running this play. It is one of many. What is specific to the restaurant industry is that the play has produced a specific vocabulary of harm — franchise sales built on one-location concepts using franchise-development credentials that do not credential the sale, consulting engagements sold on the strength of case studies from operations the consultant never actually held, PE thesis-copy portfolios marketed on turnaround narratives whose actual failure rates never appear in the pitch. The restaurant industry’s version of the play harms restaurant operators specifically. That is the audience this piece is for.

But the mechanism generalizes. Every advisory-service industry that sells on retrospective narrative is running a version of Case Study Reduction. The term names what all of them are doing.

What The Operator Should Evaluate Instead

An operator considering hiring a consultant, buying a book, attending a conference, or investing in a franchise should not evaluate the case studies. The case studies cannot answer the operator’s question.

The operator’s question is: does this consultant’s method work for my operation, in my market, at my current position, given my accumulated path. The case study, by every mechanism the NIH names and by every mechanism the restaurant industry exploits, cannot answer that question. It cannot answer it in principle. It is the wrong instrument for the question.

What can answer the question:

The framework itself. Is there one? Is it named? Is it in writing? Is every term defined? Is every claim traceable to a physical mechanism that operates across operations, rather than to a specific operator’s specific outcome? Can the framework be tested against the operator’s own operation before the consultant is hired?

The mechanism. Does the consultant name the mechanism by which their method produces the outcome? Or does the consultant point to the outcome as if the outcome self-explains the mechanism? A named mechanism is evaluable. An outcome is not.

The failure conditions. Does the consultant name the conditions under which their method does not work? A consultant with a real framework knows the framework’s boundaries. A consultant with only case studies has no framework and therefore no boundaries. The absence of failure conditions is the tell.

The refusal. Does the consultant refuse any of the industry’s default plays? Every field has plays that generate revenue at the cost of integrity. A consultant who runs every available play is optimizing for revenue. A consultant who publicly refuses specific plays is committing to a frame the plays would violate. The refusal is evidence of the frame.

The methodology in writing. Not “our approach is proprietary.” Not “our system is confidential.” A methodology worth hiring is a methodology worth publishing. If the consultant cannot show the operator what they will actually do — the frame, the reads, the discipline, the tests, the sequencing — before the operator writes the check, the operator is not buying a method. The operator is buying a case-study-shaped bet on a hidden method.

The pricing on the record. Consultants who hide their pricing hide it because pricing exposes them to comparison. A consultant confident in their frame states the pricing publicly and lets the audience decide. A consultant running a case-study sales cycle needs the case study to close the sale before pricing enters the conversation, so pricing is withheld.

The consultant’s own operating exposure. Has the consultant ever operated the operation they claim to advise on? Not been “involved in” one hundred and fifty openings. Not “worked with” the operator. Actually held the seat, made the payroll, closed on Saturday night, opened on Monday morning, absorbed the labor overrun, negotiated with the landlord, hired the kitchen manager, fired the kitchen manager, and absorbed the personal cost of the operation not working. Case studies do not require the consultant to have held the seat. Frameworks that generalize require the consultant to have held it, because the framework only holds if it was earned in the seat.

Seven evaluation moves. Every one of them cuts through Case Study Reduction. Every one of them favors a consultant with a real framework and disadvantages a consultant running the play. The operator who runs these seven evaluations before hiring will hire different consultants than the operator who reads case studies.

Why This Site Does Not Have Case Studies

This site does not have case studies for three reasons, in this order.

The first reason is that case studies are broken at the mechanism level. The research community that invented the instrument has formally disqualified it as evidence. Publishing case studies would deploy an instrument I have named as broken. The frame is symmetric or it is dishonest. Every hacksterism.com piece I have published prosecutes the deployment of broken instruments as if they were sound. Deploying one myself would collapse the entire body of prosecution work.

The second reason is that my framework does not need them. Every claim in the framework is traceable to physical mechanisms that operate across operations. The claims are testable. The mechanisms are named. Every diagnostic can be run by the operator against the operator’s own operation without needing to reference another operator’s outcome. The framework carries the evidentiary weight case studies were supposed to carry, and carries it better, because it holds across operations rather than at one operator’s specific context. The framework is the evidence.

The third reason is that I do not want the reader who arrives looking for case studies. That reader has been trained by the industry to buy on retrospective narrative. That reader will not evaluate the framework. That reader will read the cases, feel the story, and hire whichever consultant produced the most emotionally resonant narrative. That reader is not my audience. My audience is the operator who has been through enough consulting engagements to know case studies do not answer their question, and who is looking for something else. This page — this refusal — is how that reader finds their way here.

There will be no Case Studies page on this site. Ever. The refusal is architectural. The refusal is itself part of the offer.

What Changes Tomorrow

If you are an operator currently in the market for a consultant, a coach, a book, or a conference — or currently in the market to buy a franchise, sign with an agency, or invest in an advisory service in any industry — run the seven evaluation moves before writing any check.

Ask for the framework. Ask for the mechanism. Ask for the failure conditions. Ask what plays the consultant refuses to run. Ask to see the methodology in writing. Ask for the pricing on the record. Ask what operation the consultant has actually held.

If the answer to any of the seven is “let me send you some case studies,” you have your answer. The consultant is running the play. The consultant has no framework. The consultant is selling you a case-study-shaped bet on a hidden method, deploying an instrument the research community has formally disqualified as evidence, and asking you to buy on the strength of a narrative that cannot answer your question by construction.

If the answers hold across all seven, you have found a consultant worth the conversation.

That is the shift the operator makes tomorrow. Not “read more case studies to get better at picking a consultant.” Refuse to read case studies as evidence at all. Evaluate the framework instead. The framework is the evidence. Nothing else is.

Digging Deeper

Positions on the record.

• Two Roads — https://jeffreysummers.com/two-roads/
• What Is The Framework — https://jeffreysummers.com/what-is-the-framework/
• The Diagnostic — https://jeffreysummers.com/the-diagnostic/
• The Tool Stack Is Not A Framework — https://hacksterism.com/the-tool-stack-is-not-a-framework/
• The Chipotle Of X Is Framework Arbitrage — https://hacksterism.com/the-chipotle-of-x-is-framework-arbitrage/

Term definitions from the Knowledge Base.

• [Case Study Reduction] — https://kb.jeffreysummers.com/dictionary/case-study-reduction/
• [Framework Arbitrage] — https://kb.jeffreysummers.com/dictionary/framework-arbitrage/
• [Transactional Arbitrage] — https://kb.jeffreysummers.com/dictionary/transactional-arbitrage/
• [Survivorship Filing] — https://kb.jeffreysummers.com/dictionary/survivorship-filing/
• [Filing Bias] — https://kb.jeffreysummers.com/dictionary/filing-bias/
• [Visibility Bias] — https://kb.jeffreysummers.com/dictionary/visibility-bias/
• [Frame Blindness] — https://kb.jeffreysummers.com/dictionary/frame-blindness/
• [Dogma Trap] — https://kb.jeffreysummers.com/dictionary/dogma-trap/
• [Meta-Opinion] — https://kb.jeffreysummers.com/dictionary/meta-opinion/
• [Two Roads] — https://kb.jeffreysummers.com/dictionary/two-roads/

Sources

1. National Institutes of Health — Case study methodology limitations (generalizability, replication, causation, researcher subjectivity, self-reporting bias). Federal research authority.
2. Standard academic research-methods textbook consensus — The major limitation of case studies is the inability to generalize findings from a single case, small group, or unique event to a larger population. Taught across first-year graduate research-methods curricula.
3. UX design practitioner critique — Reddit r/UXDesign, “Hot Bad Take: Case Studies Are Mostly Fluff.” Cross-industry practitioner testimony on cherry-picked data and fabricated linear process.
4. B2B SaaS marketing critique — Velocity Partners, “Why Case Studies Suck.” Cross-industry practitioner testimony on self-serving vendor promotion disguised as customer praise.
5. Design and creative fields — Medium, “A Case Against Case Studies” and “Serious Flaws.” Cross-industry critique of cookie-cutter portfolio templates presented as evidence of capability.
6. Academic methodology blog — WordPress-hosted analysis of case study advantages and disadvantages, formalizing the non-repeatability and non-generalizability limits.