An emerging trend in the market
A market trend is a directional movement in demand, technology, behaviour, or regulation that persists long enough to change what a product should be. It is an external force, outside any one company's control, and its strategic value comes from timing: a trend opens a window of opportunityOpportunityDiscoveryA validated gap worth solvingView reference → and then closes it again. The hard part is telling a real trend from a passing fad or a wave of hype before you have committed a roadmapRoadmapProduct SpecificationA strategic plan of features and milestonesView reference → to it.
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.
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.
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 evidenceEvidenceValidationData supporting or refuting a hypothesisView reference →: the three quotes, a Gartner note, two competitorCompetitorMarket 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.
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 AnalysisidentifiesMarket Trendhierarchy), and from there it does its strategic work along three edges: it opens openings (competitive_analysis_identifies_market_trendMarket TrendcreatesOpportunitycross-domain), it bends results (market_trend_creates_opportunityMarket TrendinfluencesOutcomecross-domain), and the product can commit to watching it (market_trend_influences_outcomeProducttracksMarket Trendsemantic). Modelling the trend as a node, rather than a sentence buried in a strategy deck, means the evidence behind a "why now" decisionDecisionStrategyA 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.product_tracks_market_trend
Type-specific fields on BaseNode
relevanceobjectRelevance to our product (1 = low, 5 = critical).
timeframestringExpected peak or mainstream window. @example "12-18 months", "2027"
impactobjectExpected impact on our market or category.
sourcestringSource of the trend data: analyst report, research firm, observed behaviour. @example "Gartner Hype Cycle 2025", "Observed in user interviews Q1 2026"
idstringrequiredUnique identifier (UUID)
typeNodeTyperequiredDiscriminator for the entity type
titlestringrequiredDisplay name
descriptionstringOptional detailed description
statusstringLifecycle status
tagsstring[]Freeform tags for filtering
4 edge types connected to this entity.
product_tracks_market_trendcompetitive_analysis_identifies_market_trendmarket_trend_influences_outcomemarket_trend_creates_opportunity