Market Trend

Origin & evolution

The discipline of reading external forces predates the word "trend" as product teams use it. Francis Aguilar's Scanning the Business Environment (1967) gave managers the first structured taxonomy, a mnemonic he called ETPS for the Economic, Technical, Political, and Social sectors of the environment a firm should watch. That scheme was reordered to STEP and later widened into the PEST and PESTEL frameworks still taught today, adding legal and environmental factors. Aguilar's contribution was the idea that the outside world has scannable structure, so a firm can watch it deliberately rather than react to it.

The question of when a trend is real enough to act on got its sharpest answer from Gartner. In 1995 analyst Jackie Fenn published the first Hype Cycle, mapping a technology's path through five phases: the Technology Trigger, the Peak of Inflated Expectations, the Trough of Disillusionment, the Slope of Enlightenment, and the Plateau of Productivity. Fenn had noticed a repeating shape across artificial intelligence, genetic engineering, and personal computers, where early excitement ran far ahead of real adoption. The Hype Cycle gave teams a vocabulary for the gap between a trend's noise and its substance, and a reason to wait out the trough.

Geoffrey Moore's Crossing the Chasm adds a second timing obstacle that sits past the trough: even a technology whose substance is now beyond dispute faces a structural discontinuity before it reaches mainstream buyers. Moore argued that early adopters purchase a new capability💪CapabilityStrategyAn ability that enables value deliveryView reference → because it is new, while the early majority will only commit once they can see peers like themselves using it successfully. A trend can therefore be technically validated and still stall if no product manages to bridge that gap, which means the moment a trend clears Gartner's trough is not yet the moment it is safe to treat mainstream adoption as guaranteed.

The live debate now is whether the Hype Cycle describes reality or manufactures it, and whether annual trend reports reward genuine signal or recency. Most practitioners hold a working distinction: a fad spikes and collapses with no lasting change to behaviour, a hype curve inflates then corrects toward a real plateau, and a trend shifts the baseline permanently. The same surface movement can be any of the three, and you only know in hindsight, which is exactly why a trend deserves to be tracked as a watched object rather than a one-time judgement.

Clayton Christensen's The Innovator's Dilemma offers a structural account of why established firms are especially prone to misclassifying disruptive trends as fads. His argument is that a disruptive trajectory typically enters at the low end of a market, offering worse performance on the metrics🔢MetricStrategyA unified metric that measures progress, health, or behaviour across the productView reference → incumbents use to serve their best customers, while being cheaper and simpler enough to attract a different set of buyers. Because those early signals look like low-margin noise by internal measurement standards, rational resource allocation🥧Resource AllocationProgram ManagementAn allocation of team capacityView reference → inside a large firm systematically under-invests in responding until the trend has already shifted the competitive baseline. The implication for trend-tracking is not just that hindsight is required to tell fad from trend, but that the tracking instrument itself — an incumbent's measurement system — is structurally biased toward missing the signals that matter most.

How it works in practice

A team building project-management software notices that three enterprise prospects in one quarter asked, unprompted, whether the tool could be driven by an AI agent. That is a weak signal. They log it as a market trend, "agent-operable software", and attach the evidence🔎EvidenceValidationData supporting or refuting a hypothesisView reference →: the three quotes, a Gartner note, two competitor🥊CompetitorMarket IntelligenceA competing product or companyView reference → launches. Over the next two quarters they watch the signal's slope. Competitor count rises from two to nine; analyst coverage moves from speculative to advisory; one large customer makes agent-readiness a procurement requirement.

That slope is the trigger. The trend has opened an opportunity window the team can now size and act on, ahead of the laggards but past the trough where the fad-versus-trend question was still open. They scope an agent-facing API as a bet explicitly justified by the tracked trend, so when a sceptical board asks "why now", the answer is a documented movement and not a hunch.

Market trend vs. its neighbours

• Opportunity is the addressable opening a trend creates for a specific product. The trend is the external weather; the opportunity is the door it blows open for you in particular. One trend can create several distinct opportunities, and most trends create none you can serve.
• Competitive analysis📊Competitive AnalysisMarket IntelligenceA structured analysis of the competitive landscapeView reference → is the act of studying rivals, and it is one of the instruments that detects trends. When several competitors move the same direction at once, that convergence is itself trend evidence. The analysis is the telescope; the trend is what it spots.
• Market segment🎯Market SegmentMarket IntelligenceA distinct group of potential customersView reference → is a stable description of a population you can sell to. A trend is a movement that can reshape a segment, grow it, split it, or hollow it out. Segments answer "who"; trends answer "what is changing about them".

In the graph

In the Unified Product Graph, a market trend lives in the market intelligence region as a first-class external force. Competitive analysis surfaces it (competitive_analysis_identifies_market_trendCompetitive AnalysisidentifiesMarket Trendhierarchy), and from there it does its strategic work along three edges: it opens openings (market_trend_creates_opportunityMarket TrendcreatesOpportunitycross-domain), it bends results (market_trend_influences_outcomeMarket TrendinfluencesOutcomecross-domain), and the product can commit to watching it (product_tracks_market_trendProducttracksMarket Trendsemantic). Modelling the trend as a node, rather than a sentence buried in a strategy deck, means the evidence behind a "why now" decision⚖️DecisionStrategyA recorded decision with context, rationale, and consequencesView reference → stays queryable, and a trend that has gone quiet shows up as a tracked signal with no recent supporting evidence.