The last product keynote I sat through had a three-act structure so tidy it could have been optioned for a streaming miniseries. CEO walks on stage, describes a problem I have never experienced, shows a chart proving the problem is urgent, reveals a device that solves it, and tells me I can pre-order by Friday. The audience applauds on cue. The press files their stories within the hour. And six months later, the device is quietly throttling its processor under sustained load because the vapor chamber cannot dissipate heat fast enough — a failure mode the keynote’s narrative arc had no room for, because it would have ruined the resolution.
This is not a complaint about one company. It is an observation about how the entire consumer technology industry has learned to script its product announcements using narrative techniques borrowed directly from screenwriting and dramatic structure. The problem is not that marketing uses narrative — that is expected. The problem is that the narrative is so effective at manufacturing urgency and masking iterative upgrades as meaningful ones that even skeptical buyers end up evaluating the story instead of the hardware. Learning to deconstruct these scripted plots is not a soft skill for discerning buyers. It is a core survival skill.
The Recurring Beats That Every Keynote Hits
Watch enough product launches and the structural pattern becomes impossible to unsee. There is a setup, in which the presenter describes a problem the audience did not realize it had — sometimes a problem the previous generation of the same company’s product created. There is rising action, in which incremental spec improvements are presented as breakthroughs, each one building tension toward the reveal. There is a climax, which is the moment the device appears on screen for the first time, usually accompanied by a cinematic video that shows the product being milled from a single block of aluminum in slow motion. And there is a resolution, which is the pre-order button, the shipping date, and the implicit promise that your life will be incrementally better if you act now.
These beats are not accidental. They are the same beats you find in any well-constructed narrative, and they serve the same function: they create emotional investment, build stakes, and channel that investment toward a specific action. The difference is that in a film, the stakes are fictional. In a product launch, the stakes are your money and your workflow, and the resolution is a purchase decision you are being manipulated into making before you have time to evaluate the hardware on its merits.
The Setup: Manufacturing the Problem You Didn’t Know You Had
The setup is the most manipulative beat because it frames the entire evaluation. A company stands on stage and tells you that your current device is too slow, too heavy, too dim, or too battery-constrained. Sometimes this is true. Often it is a reframing of a problem the company itself created in the previous product cycle — a phone that is too thick because the company prioritized thinness over battery capacity two years ago, or a laptop that throttles because the company designed a cooling system for benchmark bursts rather than sustained compile workloads.
The tell is when the problem being described is one you have never actually experienced in your daily use. If a presenter spends four minutes describing the inadequacy of last year’s camera sensor and you have never once looked at your photos and thought the sensor was the bottleneck, the setup is doing its job: it is creating a problem to solve rather than solving one you brought to the table. This is the narrative equivalent of a screenwriter introducing a conflict the protagonist did not need — it exists to give the plot somewhere to go, not to serve the character.
A concrete example: the recent wave of laptops marketed around AI acceleration. The setup describes a world in which local AI inference is a daily necessity, the rising action shows benchmark charts for neural processing operations per second, and the resolution is a machine with a neural engine that your actual workload — compiling code, running spreadsheets, editing documents — will never meaningfully engage. The narrative is complete. The hardware reality is that you just paid a premium for a coprocessor that draws power and generates heat for a use case the manufacturer hopes you will adopt later, not one you have today.
Rising Action: Incremental Specs Presented as Breakthroughs
The rising action is where the narrative does its heaviest lifting. Each spec improvement is presented as a step toward resolution, building tension and investment. A 15 percent improvement in CPU throughput becomes a story about how your workflow will transform. A 200-nit increase in peak display brightness becomes a story about outdoor visibility you will benefit from on the one day a year you work on a patio. A reduction in thickness of 0.4 millimeters becomes a story about portability, even when the device’s weight is unchanged and the thickness reduction was achieved by soldering RAM that was previously user-replaceable.
The technique here is specificity-as-misdirection. The presenter gives you a precise number — 15 percent faster, 20 percent brighter, 30 percent more efficient — and the precision itself functions as a substitute for relevance. You are so busy processing the number that you do not ask whether the number maps to anything you will notice. A 15 percent CPU improvement in a laptop used for email, browser tabs, and document editing is invisible in daily use. A 20 percent brightness increase on a display that already hits 400 nits is invisible indoors. The numbers are real. The narrative around them is fiction.
This is also where the narrative most aggressively masks trade-offs as upgrades. When a laptop gets thinner, the keynote tells you it is more portable. It does not tell you that the thermal headroom shrank, the battery capacity decreased, or the keyboard travel was reduced to the point where typing for more than two hours produces finger fatigue. Those are not rising-action beats. They are subplots the narrative has no intention of developing.
The Climax: The Reveal and the Emotional Hijack
The climax is the moment the product appears, and it is engineered to produce an emotional response before rational evaluation can begin. The cinematic video, the dramatic music, the audience applause — these are not decorative. They are techniques for short-circuiting critical thinking. The goal is to have you feel something about the product before you have time to ask whether the product actually addresses your needs.
This is why the climax is almost always visual rather than functional. You see the device. You do not see it sustain a 45-minute render. You do not see its thermals under load. You do not see its keyboard after two years of daily typing, or its battery after 300 charge cycles, or its hinge after 10,000 open-close cycles. The climax shows you the product at its best possible angle, in its best possible lighting, performing the one task it was designed to perform for the camera. Everything that matters about the product over its actual lifespan is excluded from the climax because it would break the emotional spell.
The Resolution: Manufacturing Urgency
The resolution is the pre-order date, and it is the most cynically engineered beat of all. The entire narrative has been building toward this moment, and the company needs you to act before the emotional investment fades and rational evaluation begins. This is why pre-orders open immediately after the keynote, why shipping dates are quoted in weeks rather than months, and why early reviews are embargoed until after the pre-order window has opened. The urgency is not about supply constraints. It is about ensuring that you commit before you have complete information.
If a company were confident that its product would hold up under sustained, independent evaluation, it would not need to manufacture urgency. It would welcome the scrutiny. The urgency itself is a signal: the narrative cannot survive the gap between the keynote and the long-term review, so the company needs you to buy before that gap closes.
What the Narrative Cannot Contain: The Engineering Reality
Here is where the plot breaks down. Inside every company that launches a product at scale, the engineering team is not running a narrative. They are running a checklist. Google’s Site Reliability Engineering book, which is publicly available and covers the company’s approach to launches at scale, includes an entire chapter on reliable product launches and a launch coordination checklist in its appendix. The chapter and checklist describe launches as risk-managed events requiring structured coordination, rollback plans, and explicit acknowledgment of failure modes. The SRE book’s framing of launches as deliberately scoped, checklist-driven events is the engineering counterpoint to the consumer-facing narrative: internally, a launch is a managed risk event with documented trade-offs, thermal constraints, and contingency plans. The polished keynote plot is a story layered on top of that messier engineering reality, and the two do not map to each other. The narrative says breakthrough. The checklist says we hope the thermal envelope holds under sustained load and we have a firmware patch ready if it does not.
This gap between the narrative and the engineering checklist is exactly what discerning buyers need to learn to see. When a company says its new laptop is 15 percent faster and 10 percent thinner, the engineering reality behind that claim is a thermal design that may throttle under the sustained workloads the marketing implies it can handle. When a company says its phone supports seven years of software updates, the engineering reality is a support commitment that depends on the company’s willingness to maintain driver compatibility for hardware that will be three generations behind the current silicon by year five. The narrative does not contain these realities because they are not resolution beats. They are the engineering equivalent of a plot hole.
A Framework for Deconstructing the Script
What I am arguing for is not cynicism. It is structure. Specifically, it is the application of a standardized analytical framework to vendor narratives, the same way professionals in other domains apply frameworks to evaluate claims rather than accepting them at face value. The NIST Cybersecurity Framework, for example, exists because organizations learned they could not rely on vendor security marketing to accurately describe real security posture. The CSF provides a structured way to map claims against standardized outcomes and controls — to translate a vendor’s high-level assertions into specific, testable practices. The principle transfers directly: when a tech company tells you their product solves a problem, you need an external framework to evaluate whether that claim holds, not just the company’s own narrative. The CSF’s approach of mapping vendor claims to standardized outcomes is the same analytical discipline I am advocating for hardware evaluation, and it has the advantage of being a proven methodology in a domain where the stakes are higher than a laptop purchase.
The point is that narrative structure is not accidental, and it is not harmless. It is a deliberate, tool-assisted craft. Screenwriters and dramatists have always known this — they use structural frameworks to build plots that produce specific emotional responses, and the tools available for this have become increasingly explicit. An AI plot generator that maps narrative beats for a draft does the same thing a marketing team does when it structures a keynote around a problem-solution arc: it applies structural principles to manufacture a specific response from an audience. The difference is that a fiction writer is honest about the craft. A tech marketing team is using the same structural techniques to sell you hardware by making you feel something about it before you can think about it. Understanding that the keynote is a plotted narrative — constructed with the same deliberateness as a screenplay — is the first step in learning to evaluate the hardware instead of the story.
The Practical Deconstruction Checklist
Here is the framework I use, and that I recommend to anyone who has ever pre-ordered a device they regretted six months later. Run every product launch narrative through these four questions.
First, identify the setup. What problem is the company describing, and did you experience that problem before the keynote told you it existed? If the problem is new to you, the setup is manufacturing a need, not addressing one. This does not mean the product is bad. It means the narrative is doing persuasion, not description.
Second, trace the rising action to its source. Each spec improvement presented as a breakthrough should be traced to its practical impact on your actual workflow. A 15 percent CPU improvement means nothing if your workload is memory-bound. A 200-nit brightness increase means nothing if you work indoors. A thinner chassis means nothing if you carry a 90-watt power brick and a cooling pad. Translate every spec claim into a concrete daily-use scenario before you let it build investment.
Third, interrogate the climax for what it excludes. The cinematic reveal video shows the product at its best angle performing its best task. What it does not show is the product under sustained load, after battery degradation, or in the hands of a repair technician. Every omission from the climax is a potential plot hole. List them. If the climax does not show thermals under sustained load, that is a plot hole. If it does not show the keyboard after 50,000 keystrokes, that is a plot hole. If it does not show the repairability score, that is a plot hole.
Fourth, question the resolution’s urgency. Why is the pre-order window opening now? Why are early reviews embargoed? Why is the shipping date quoted in weeks rather than months? If the company needs you to act before independent long-term testing exists, the narrative cannot survive that testing. The urgency is the tell.
What This Framework Cannot Do
This framework will not tell you whether a product is good. It will tell you whether the narrative around it is trustworthy, which is a necessary precondition for evaluating the product on its merits. A product can survive a dishonest narrative and still be worth buying — a laptop with a misleading keynote may still have a serviceable keyboard, a replaceable battery, and adequate thermals for your workload. But you will not know that from the keynote. You will know it from teardowns, long-term reviews, failure reports, and your own testing under conditions that approximate your actual use.
The framework also cannot protect you from supply chain variance. A laptop that reviews well in the first production batch may have a different panel supplier in the second batch, a different SSD controller in the third, or a different thermal compound application in the fourth. This is a failure mode that no narrative can account for because it is a failure of consistency, not of design. The only defense against it is buying from retailers with return policies that outlast the variance window, and supporting publications that test multiple units across production batches rather than a single cherry-picked review sample.
The Conditional Verdict
If you are the kind of buyer who evaluates a product by the keynote that introduced it, you are evaluating the narrative, not the hardware. The narrative is designed to make you feel, not to make you think, and the company that scripted it has a financial interest in ensuring you act before the feeling fades. The only reliable defense is to treat every product launch as a constructed story — plotted with the same deliberateness as a screenplay, built with the same structural beats, and engineered to produce the same emotional response — and to refuse to evaluate the product until the story has been replaced by data.
Wait for the teardowns. Wait for the long-term reviews. Wait for the reader-sourced failure reports. Wait for the second production batch. If the product is as good as the narrative claims, it will be just as good in three months, and you will have the information to confirm it. If it is not, you will have saved yourself the cost of believing a story that was never designed to survive contact with reality.