01
Observe anomalies
Start with the detail that does not fit the accepted story: a workaround, a new interaction, a changed queue, an unexpected purchase, or language people suddenly begin using.
HAAM Signals / Trend catching / Updated July 3, 2026
Catch the shift before it becomes the consensus.
HAAM looks for weak signals across products, technology, culture, markets, policy, and physical life. The aim is not prediction theatre. It is to notice meaningful change early, connect the evidence, and explain what the shift changes for design, strategy, and public life.
What counts as a signal
A signal is an anomaly that repeats, points to a structural pressure, and creates a practical consequence. Virality alone does not qualify.
See how trends are caught ↓Editorial method
Catching trends is a reporting practice.
Trend work starts before a category has a stable name. HAAM combines observation, primary sources, product analysis, cross-market comparison, and practical design judgment to decide which changes deserve attention.
Read the full HAAM editorial system ↗02
Triangulate evidence
Compare what appears in products, research, policy, business models, culture, physical spaces, and firsthand conversations. One example is interesting. Repetition across worlds is a signal.
03
Find the pressure
Ask what structural force makes the pattern durable: a new capability, falling cost, regulation, distribution change, demographic shift, or unresolved human need.
04
Name the consequence
Turn the signal into a practical implication. What should a product team research, prototype, measure, govern, preserve, or stop doing next?
Signal inputs
Strong trend work mixes sources that usually live in separate feeds and disciplines.
Firsthand field observationNew product behaviorNiche communities and languagePlatform and distribution shiftsRegulation and standardsBusiness-model changesResearch and user evidenceCultural and spatial patterns
The living trend map
Ten shifts, one connected practice
Each signal links an emerging pressure to what changes and how a product team can respond. The map is revised as evidence strengthens, weakens, or changes direction.
AI + interaction
01
NowSignal
AI interfaces are becoming collaborative workspaces
The useful AI product is moving beyond a single prompt box. It combines conversation with visible controls, editable artifacts, progress states, sources, approvals, and reliable ways to recover when the model is wrong.
What changes
Interaction design now has to choreograph intent, generation, inspection, correction, and execution. The interface must make the system’s current state and limits legible without forcing people to understand the model underneath it.
Design response
Design the human decision points first. Keep consequential actions reviewable, make uncertainty visible, preserve an undo path, and test the full loop after the AI has acted—not only whether it produced a plausible answer.
Story + media
02
AcceleratingSignal
Storyworlds are replacing isolated content campaigns
Generative media lowers the cost of producing many formats, but volume is not the strategic advantage. The stronger opportunity is a coherent storyworld that can unfold through short video, social posts, interactive experiences, games, audio, and physical spaces.
What changes
Transmedia work increasingly resembles product architecture. Teams need canon rules, character systems, reusable assets, migratory cues, release logic, and continuity checks so every channel adds something rather than repeating the same message.
Design response
Build the narrative system before scaling production. Give each channel a distinct job, define what is canonical, and use AI for variation and adaptation under human editorial direction.
Trust + access
03
StructuralSignal
Trust is becoming a designed product capability
Accessibility, provenance, privacy, understandable language, and human accountability are converging. They are no longer separate compliance tasks; together they determine whether people can confidently use an increasingly automated service.
What changes
The European Accessibility Act has applied since June 28, 2025, while AI transparency and governance requirements continue to mature. Teams need evidence of how decisions were made, who reviewed them, and whether critical journeys work for different bodies, devices, languages, and levels of digital confidence.
Design response
Treat trust requirements as acceptance criteria. Include keyboard and assistive-technology flows, authorship and source labels, escalation routes, consent states, plain-language explanations, and named owners in the product definition.
04
ExpandingSignal
Localization is moving into product architecture
Translation at the end of a project is too late for products that cross markets. Locale affects navigation, identity, payments, address formats, search behavior, content density, trust signals, cultural references, and expectations around support.
What changes
AI makes first-pass translation faster, which exposes the harder work: deciding what should remain consistent, what should adapt, and who validates cultural meaning. Strong localization now connects content design, interface behavior, operations, and regional growth.
Design response
Model locale as a system variable from the beginning. Test complete journeys with local users, allow layouts to expand, maintain terminology and tone guidance, and separate translation quality from cultural product fit.
Discovery + growth
05
NowSignal
Discovery is shifting from result lists to synthesized answers
People increasingly encounter brands through AI summaries, recommendation systems, assistants, maps, marketplaces, and social feeds before they visit a homepage. Discoverability depends on whether machines and people can both understand what an organization knows, offers, and has actually done.
What changes
Traditional SEO remains foundational, but content needs stronger entities, visible evidence, clear authorship, structured data, original points of view, and internal relationships. A pile of interchangeable AI-written pages is easier to produce and easier to ignore.
Design response
Publish specific, attributable knowledge. Connect services to case studies and expert explanations, keep structured data aligned with visible content, and make pages useful even when the visitor arrives deep inside the site.
06
MaturingSignal
Growth design is becoming an evidence loop
The old split between research, design, analytics, and conversion optimization is weakening. Effective teams combine qualitative observation, behavioral data, experiments, and commercial outcomes in one continuous learning loop.
What changes
This changes what counts as a deliverable. A launch is not the end state; event definitions, hypotheses, dashboards, experiment notes, and follow-up decisions are part of the designed product. Loyalty and ecommerce experiences are judged by long-term confidence, not only the first conversion.
Design response
Instrument the decisions that matter, not every possible click. Pair numbers with user context, define expected behavior before shipping, and review whether an optimization improves comprehension and retention as well as short-term conversion.
Systems + delivery
07
NowSignal
Performance is being felt at the interaction level
Fast loading is necessary but insufficient. People judge quality every time a menu hesitates, a tap produces no feedback, a transition obscures state, or a long task blocks the interface.
What changes
Interaction to Next Paint made responsiveness a first-class web quality signal, while browser interoperability work makes more capable native experiences practical. The opportunity is richer interaction with less framework weight—but only when progressive enhancement and device testing remain disciplined.
Design response
Measure real journeys, especially the slowest interactions. Design immediate feedback, split expensive work, respect reduced-motion preferences, and choose platform capabilities based on support and user value rather than novelty.
08
StructuralSignal
Design systems are expanding into behavior systems
A component library cannot create consistency by itself. Products also need shared rules for motion, content, data states, AI behavior, accessibility, analytics, and what happens when the expected path fails.
What changes
As more interfaces are assembled or generated, the valuable system is the one that preserves intent. Tokens and components remain useful, but contracts, examples, evaluation criteria, and decision records increasingly carry the real product knowledge.
Design response
Document states and behavior alongside appearance. Include empty, loading, error, permission, offline, generated, reviewed, and destructive states; connect design tokens to code; and test the system through real flows.
09
ContinuousSignal
Modernization is becoming continuous product care
The useful life of a digital product is shaped less by the launch stack than by the team’s ability to keep dependencies, content, accessibility, performance, and operational knowledge healthy over time.
What changes
AI can accelerate migrations and code production, but it can also multiply inconsistency and hidden maintenance cost. The durable advantage is a small, regular maintenance loop with ownership, tests, observability, and a clear definition of what should remain boring.
Design response
Budget for maintenance as product work. Remove unused paths, update incrementally, record architectural decisions, test high-value journeys after changes, and modernize around user and business risk rather than framework fashion.
Public value
10
EmergingSignal
Digital products are being judged by the systems they shape
Health, civic, cultural, sustainability, and community products cannot be evaluated only by engagement. Their interfaces influence habits, access to resources, public understanding, participation, and who gets represented.
What changes
As AI lowers the cost of prototyping, more people can explore difficult problems quickly. That increases the need for situated research, local partnerships, responsible data use, and a clear boundary between a provocative prototype and a service people can safely depend on.
Design response
Define the public outcome before the feature set. Involve affected communities, state uncertainty, minimize sensitive data, test for exclusion and unintended incentives, and use prototypes to learn before claiming impact.
Editorial position
The strongest trend is convergence
Interaction design is becoming governance. Storytelling is becoming product architecture. Accessibility is becoming market access. Analytics is becoming product memory. Maintenance is becoming strategy. The work is increasingly about connecting these disciplines without losing clarity or human accountability.
Design for agency
People should understand what the system is doing and retain meaningful control.
Build for evidence
Claims, decisions, and improvements should be inspectable rather than merely persuasive.
Create connected systems
Content, components, data, operations, and narrative need shared rules.
Maintain the whole lifecycle
Quality includes what happens after launch, after automation, and after something fails.
Primary references
Signals, not certainty
This is a living editorial synthesis, not a list of fixed predictions. HAAM revisits signals as firsthand evidence, platform behavior, standards, markets, and regulation change.
- European Commission: AI Act application timeline
- European Commission: transparency of AI-generated content
- W3C: Web Content Accessibility Guidelines 2.2
- European Commission: European Accessibility Act
- web.dev: Baseline 2026
- web.dev: Interaction to Next Paint
- Google Search Central: AI features and your website
- Apple Human Interface Guidelines: Generative AI
Apply the signals
Turn a trend into a product decision
Use the map to identify the shift affecting your product, then define the smallest research, design, or implementation step that creates evidence.