Signal — Meaning — Action

A methodology for closing the gap between what people say and what outcome they want.

Most communication fails not because the signal was wrong or the action unclear — but because the meaning in between was never designed.

01 — The Method

What SMA Is

SMA is a structured approach to one of the oldest problems in design and communication: the gap between what someone asks for and what they actually need. It operates at three levels simultaneously — as a diagnostic tool, a communication framework, and a design methodology.

At its core, SMA treats every communication as containing three distinct layers: the signal being sent, the meaning that needs to be decoded, and the action that should result. Most systems optimize the signal and hope for the action. SMA designs the meaning in between.

The framework applies wherever communication produces outcomes — client relationships, product design, organizational strategy, AI interfaces, and digital experiences. The context changes. The pattern does not.

02 — The Problem

It Doesn't Pop

After 25 years in digital design — across Fortune 500 companies, startups, and independent ventures — one phrase kept appearing in every client relationship, at every level of seniority, across every industry:

"It doesn't pop."

The phrase is vague, subjective, and almost completely uninformative as design feedback. And yet it appears constantly. Not because clients are bad communicators, but because they are accurately reporting an experience they cannot yet name. Something is wrong. They know it. They cannot explain it.

The traditional response is frustration — from the designer who followed the brief, and from the client who cannot articulate what they want instead. Both parties are stuck. The meeting goes in circles. Revisions pile up. The actual problem remains unsolved.

SMA emerged as the answer to that cycle. Not by dismissing the vague feedback, but by treating it as exactly what it is: a signal. One that, when decoded properly, contains a precise meaning — and points to a clear action.

SMA Applied — "It doesn't pop"
Signal "It doesn't pop" — the raw, unprocessed feedback
Meaning The visual hierarchy is not establishing clear priority. The eye has no entry point.
Action Increase contrast between primary and secondary elements. Establish a dominant focal point. Reduce visual competition.

The signal did not change. The meaning was decoded. The action became obvious. That is SMA working as intended.

03 — The Framework

Signal. Meaning. Action.

S Signal

The raw input. A piece of feedback, a user behavior, a query, a stakeholder request. The signal is what is expressed — not what is meant. It is the starting point, not the conclusion.

M Meaning

The interpretation layer. What does this signal actually represent? What intent, frustration, goal, or need is embedded in it? Meaning is where most systems fail — it requires context, experience, and structured thinking to decode reliably.

A Action

The outcome. Once meaning is established, the action becomes specific and defensible. Not a guess. Not a reaction. A design decision grounded in decoded intent.

The framework is deceptively simple. Its value is in the discipline it imposes — the refusal to skip from signal directly to action without passing through meaning. That middle layer is where design decisions are either grounded or arbitrary.

Hierarchy Shifts by Context

One of the most practical applications of SMA is understanding that the dominant element in the triad shifts depending on industry, audience, and objective. A SaaS company's homepage elevates Meaning — because technical users are skeptical and need to understand the how before they trust the what. A direct-to-consumer brand elevates Action — because the purchase decision is emotional and the path to it should be as frictionless as possible. The framework remains constant. The emphasis adapts.

04 — The Decouple

Separating the Interface from the Architecture

Traditional web design treats UI and IA as a single object. The navigation is the architecture. The page structure is the experience. Every user receives the same hierarchy, the same path, the same sequence of decisions. The interface is built once and handed to everyone identically.

That model worked when information was static and audiences were homogeneous. Neither is true anymore. And the arrival of AI has made the problem impossible to ignore — because AI removed the navigation burden of search without restoring the signal that search preserved.

Three Eras of Information Retrieval

Where We've Been. Where We're Stuck. Where This Goes.
Search You query. You get a list of sources. You triangulate. Effortful — but the disagreement between sources is visible, and that disagreement is the information.
AI You query. You get one confident answer. Faster — but the disagreement has been smoothed over. The tradeoffs are invisible. The user has less work and less signal.
Avatar You declare who you are once. Content pre-configures around that declaration from the moment you arrive. No query required. The IA detaches from the UI — the same architecture serves every persona without being rebuilt, rendering differently based on the active context node.

We are currently caught between the second and third eras. The decouple is the structural answer.

When UI and IA operate as separate layers — when the architecture remains intact underneath while the surface adapts to the person using it — the same underlying system serves radically different users without requiring two sites, two navigation structures, or two content strategies. The IA becomes the meaning engine. The UI becomes its output surface.

The interface should not make the user navigate the entire architecture to find the one path that was built for them.

SMA's role in this is to design the meaning layer that makes the decouple coherent — to ensure that the signal a user sends, the interpretation the system applies, and the surface it renders are in deliberate alignment. Experience Avatars are the mechanism that makes it usable.

05 — Experience Avatars

The Extension Into UX

SMA began as a communication framework. Experience Avatars extend it into a full UX methodology — a system for building interfaces that adapt to the person using them, not the other way around.

The core problem SMA consistently surfaces in digital product design is bifurcated audiences. A company like Neo4j serves both the developer and the C-suite decision maker. A commerce platform serves both the mission-driven buyer who knows exactly what they want and the exploratory shopper who wants to be surprised. Traditional navigation and information architecture treat both users identically. They receive the same structure, the same hierarchy, the same path. The meaning layer is collapsed.

The interface should not force the user to navigate the alphabet to find the letter they came for.

Experience Avatars solve this by making the signal explicit. Instead of inferring user context from behavioral tracking, cookies, and UTM parameters — all of which are imprecise, privacy-invasive, and increasingly unavailable — the user is invited to self-identify. Like choosing a character class at the start of a game. The avatar becomes the primary node through which all subsequent content, navigation, and recommendations are filtered.

Avatars as Nodes

In knowledge graph terms, the Experience Avatar is a first-class node. Its edges determine relevance. Its weight determines priority. The same underlying information architecture serves every user, but the interface rendered from it is dynamically assembled around the avatar's context. The IA remains intact. The UI becomes adaptive.

This is the UX correlate of how a knowledge graph operates — structuring relationships to derive meaning and drive outcome. SMA is the design-side expression of the same logic that makes graph systems powerful at scale.

06 — Where It Applies

The Framework Is Industry-Agnostic

SMA emerged from design communication. Its applications extend significantly further. Any context in which signals are received, interpreted, and acted upon is a context in which SMA applies.

Professional Services

Client briefs, stakeholder feedback, strategic presentations. SMA decodes vague requests into specific deliverables and eliminates revision cycles driven by misaligned meaning.

Product Design

UX research synthesis, design system governance, feature prioritization. SMA structures the meaning layer between user signal and product decision.

Digital Marketing

Landing page architecture, conversion optimization, lead generation. SMA ensures every touchpoint carries clear intent, delivers the right meaning, and drives a specific action.

AI & Conversational UX

In AI-native interfaces, every utterance is a signal. SMA provides the framework for designing the meaning layer between user intent and system response — the layer that makes AI interactions feel human rather than mechanical.

Commerce

Experience Avatar-driven personalization, recommendation systems, affiliate ecosystems. SMA maps user intent into graph relationships that surface the right product at the right moment without behavioral surveillance.

Organizational Communication

Internal messaging, change management, design governance. SMA gives organizations a shared vocabulary for translating ambiguous direction into clear, coordinated action.

07 — The Standard

A Framework, Not a Style Guide

Brad Frost's Atomic Design gave the industry a shared language for building scalable interface systems — atoms, molecules, organisms, templates, pages. It was structural. It described how interfaces are composed.

SMA operates on an adjacent plane. Where Atomic Design is structural, SMA is interpretive. Atomic Design answers: how do we build this? SMA answers: what should this mean, and what should it make someone do?

Both are necessary. Neither replaces the other. A design system built without SMA produces components that are consistent but directionless. SMA applied without a design system produces clarity without scalability. Together, they produce interfaces that are both coherent in construction and deliberate in effect.

If Atomic Design is the grammar of a design system, SMA is its semantics — the layer that determines what the words actually mean in context.

SMA is not a methodology that requires licensing, certification, or proprietary tooling. It is a discipline — a structured habit of mind that, once internalized, changes how designers read feedback, how teams communicate, and how products get built.

08 — Work

25 Years of Application

SMA was not developed in a research context. It emerged from practice — from client meetings, stakeholder reviews, design critiques, and product decisions across 25 years of enterprise and independent work. The companies where it has been applied include Neo4j, Anthem, Carelon, MetLife, PennMutual, Fortress Investments, and Callaway, among others.

The framework currently underpins the design and communication strategy for BREATHmg, a structured breath training system built and launched independently in 2025, and informs the approach to ongoing client engagements through Accidental Systems.

A full portfolio of applied work is available at jig-me.com.

View Portfolio →