Press Release

Origin & evolution

The press release traces to Ivy Lee, a former newspaperman who is widely credited with issuing the first modern release in 1906. After a Pennsylvania Railroad accident, Lee gave reporters a factual account from the company's perspective; the New York Times ran it close to verbatim. The same year he drafted a Declaration of Principles, pledging that the work would be accurate and open rather than the hidden press-agentry of the era, a stance that earned him a place as a founder of modern public relations (PR Academy).

For most of the twentieth century the form held steady: dateline, headline, inverted-pyramid body, boilerplate. The interesting evolution happened inside product teams. Amazon inverted the release's purpose. Beginning in the early 2000s, the company adopted Working Backwards: before building anything, a team writes the press release for the finished product as if it had already shipped, paired with a set of FAQs. The PR-FAQ is never published. It is a forcing function that makes the team describe the customer benefit in plain language before committing engineering effort, detailed later by Colin Bryar and Bill Carr in Working Backwards (2021).

The field now holds two readings of the same artefact. The external release is a distribution document aimed at coverage. The internal PR-FAQ is a thinking document aimed at clarity. Both share the constraint🔒ConstraintStrategyA constraint entityView reference → that gives the form its discipline: say the value in language a stranger would repeat.

How it works in practice

A team proposing a new integration writes a one-page PR-FAQ in week one. The mock release opens: "Today, Acme announced two-way sync between its planner and Slack, so teams stop copying tasks☑️TaskProduct SpecificationA unit of work within a story or epicView reference → by hand." The FAQ that follows is unsparing: how many users hit the manual-copy problem, what the build costs, why now. Reading it aloud, the team finds the benefit is thinner than assumed; only a sliver of accounts use Slack heavily. The proposal is reshaped before a line of code is written. Eight weeks later, when the feature⭐FeatureProduct SpecificationA product capability or featureView reference → ships, the real external release reuses the same opening sentence almost unchanged, because the work was designed around a claim that already had to survive being written down.

Press release vs. its neighbours

• Launch is the event: the coordinated moment a product becomes available. A press release is one instrument of a launch, the on-the-record statement; a launch also carries pricing, enablement, and timing that never appear in the release.
• Marketing strategy🔱Marketing StrategyMarketingA marketing strategyView reference → sets the positioning🎪PositioningGo-To-MarketProduct positioning statementView reference → and channels that decide whether a release is issued at all and what it must say. The strategy is the standing intent; the release is a dated act that executes it.
• Feature is the capability💪CapabilityStrategyAn ability that enables value deliveryView reference → being announced. The PR-FAQ flavour of a release is written about a feature before it exists, which is why the two are distinct nodes: the feature is what gets built, the release is the claim that justified building it.

In the graph

In the Unified Product Graph, a press release sits in the marketing region with two canonical edges that capture its dual life. marketing_strategy_publishes_press_releaseMarketing StrategypublishesPress Releasehierarchy records the strategic act of issuing one. product_announced_via_press_releaseProductannounced viaPress Releasehierarchy links the release to the product it makes public, which is the structural hook for the Working Backwards pattern: a release can be drafted against a planned product and later resolved to the real launch, keeping the original claim queryable against what actually shipped.