Perception-First Design™

The Bouncer

I figured out my design methodology in a nightclub.

I was head of security at a 300-capacity venue. Staff of 15. Every night at 1:30 AM, same problem: lights slam on, DJ announces we’re closed, and I’m barking at 300 drunk people to get out. They hated it. I hated it. Fights happened. Stragglers lingered. The whole thing was hostile.

So I tried something different. At 1:10, I walked table by table. “Hey, last call’s coming up. Get any drinks you want. Thanks for coming out tonight.” That’s it. No urgency. No authority voice. Just information, a suggestion, and respect.

At 1:30, when the DJ made the announcement and the lights went up, half the venue was already walking out the door. No barking. No fights. And bar sales went up 30% in those last 20 minutes.

I didn’t know what to call that. I just knew it worked, and I knew why it worked. The old way treated people like obstacles. My way treated them like people with their own goals who’d cooperate if you gave them the right information at the right time with the right tone.

That’s Perception-First Design before I had words for it. Everything I’ve done in the 15 years since; revenue 3x, Costco pallets and Walmart shelves and Disney licensing, improv theaters and smart home brands. It all comes from that same instinct. Design for how people actually perceive and process the world, not how you wish they did.

The Thesis

The design industry has spent 15 years saying the same thing: users have limited attention, so don’t waste it. Lower friction. Reduce steps. Don’t make them think.

My version is different: users don’t think. Not until you make them.

Nobody is thinking. They’re on autopilot. The same way you catch a ball without calculating trajectory, or walk without planning each step; that’s how people interact with websites, products, brands, everything. Autopilot. Energy conservation. The brain handles the vast majority of processing unconsciously. Kahneman (2011) calls this System 1: the fast, automatic mode that runs most of cognitive life. System 2, slow and deliberate and conscious, only activates when something demands attention.

Contemporary cognitive science calls this predictive processing (Clark, 2013; Friston, 2010). The brain is constantly generating predictions about what it expects to encounter. When reality matches prediction: autopilot. When reality violates prediction: attention fires, System 2 kicks in. That prediction error is what I call the activation point.

The design challenge isn’t “don’t waste their limited attention.” It’s that effortful attention is dormant by default. The real question is: when you do make them stop and actually think, when you generate a prediction error that activates them from autopilot, what do they think about? How do they feel? And what do they do next?

That’s what I design for. Not the funnel. The activation.

Steve Krug wrote Don’t Make Me Think. Great book. It gave me the vocabulary to talk to stakeholders early in my career. His scope was usability, and he stayed in it deliberately. But nobody’s thinking in the first place. Design for that bias, the bias of making someone stop and engage, instead of funneling them to an action with an affordance of attention they never gave you.

Why I See This

Two things about my brain that I didn’t choose but that turned out to be professional advantages.

I’m autistic. After my formal ASD diagnosis, my partner pointed out something I’d been missing: “Do you realize you’re not picking up on me not being interested at all in what you’re talking about, and you seem to be getting frustrated?” Around 2012, a friend I met at a Chicago meetup about emotions in video games suggested I try improv. I went in already analytical. I had impaired social instincts, not absent ones. I didn’t need to learn what a smile means. I had to learn what eye contact can mean, what a pause signals, what “said vs. unsaid” reveals. I learned it like you’d learn an instrument or ballet: theory, practice, application loops, over and over.

That means I can see and articulate the unconscious patterns that most designers apply intuitively but can’t explain. People interact with websites the same way they interact with other humans. We form first impressions on products the same way we do when someone walks into a room. It’s all unconscious, and we can’t help it.

I also have severe combined-type ADHD. Some experiences are literally painful for me because of how taxing they are on my attention and cognitive load. I’m acutely sensitive to friction, clutter, noise, confusion. The things that bad design inflicts on everyone, I feel at a higher volume. I design because I’m sensitive to these patterns. What most designers theorize about, I feel.

And the ADHD gave me something else: years of building mental prostheses. If it’s out of sight, it’s literally out of mind for me, so I keep post-it notes on my desk for today’s tasks. “Out of sight, out of mind” becomes: what MUST we show vs. what we want to show vs. what we could show. Then cut everything but what we must show.

Design is prosthesis for human cognitive functions and limitations. I know that because I’ve been building prostheses for myself my whole life. The curb cut effect: what I built for my own cognitive accessibility turned out to help everyone.

I’ve come to think of this as a curb-cut effect. The cognitive constraints I designed around — limited working memory, sensitivity to disfluency, impatience with unnecessary friction — are constraints every user has. Mine are just louder. A design that works for the constrained case tends to work better for everyone.

The five PFD layers draw from two largely distinct bodies of cognitive science — perception psychology and ADHD cognitive neuroscience — connected here for the first time. The citation lists share no duplicate entries.

The Conductor Model

I don’t build funnels. I conduct.

Think about a musician who’s reached unconscious mastery. They stop thinking about how things are done and focus entirely on how the music makes you feel. That’s the goal. Prime someone with a first impression, then conduct their thoughts and emotions through the experience. Design a mental waterfall.

There’s a flow of thought and perception: momentum, weight, cadence, tone, speed, context, priming, expectations. Like singing down a scale in front of a crowd and pausing before the last note. Everyone knows what comes next. That recognition, that pattern completion, is satisfying. That’s what a great CTA feels like: the only possible resolution to the experience that preceded it.

The User’s Mental Waterfall

The unconscious sequence of questions every visitor processes:

1. What am I trying to accomplish here? → Intent
2. Is there a clear path to that? → Navigation
3. What’s the point of this site? → Value proposition
4. For whom is this? → Do I belong here?
5. What is it trying to tell me? → Messaging: ew or cool?
6. What is it trying to get me to do? → Call to action
7. How do I feel about doing it? → “Prove you’re worth my time” or “Tell me more!”
8. Where’s the win-win? → Mutual value
9. Does this give me what I want? → Delivery

The hero section is the activation point; the table visit at 1:10. If it answers questions 1 through 5 in the first second or two, the user is primed. Then you conduct them through 6 through 9 as they scroll. If the hero fails, it’s the lights slamming on.

My improv teacher gave me a formula: (Listen) × (Act + React). If Listen equals zero, if the user isn’t attending, then everything else multiplies by zero.

Methodology Siblings

PFD is a practitioner synthesis; the lineage isn’t novel. Three older traditions solve the same problem from different angles.

Kansei engineering (Nagamachi, 1995)

Developed at Hiroshima University in the 1970s, formalized in the mid-90s. Kansei = “psychological feeling, image of a new product.” The methodology maps consumer affective response onto measurable product attributes, then engineers toward the target feeling. This is the closest ancestor to PFD: both start with the pre-verbal response and work backward to design decisions. Kansei is PFD’s Japanese cousin. Anyone doing serious work in automotive, consumer electronics, or product design in Japan already knows it.

Gestalt psychology (Wertheimer, 1923; Metzger, 1936/2006)

The Berlin School’s empirical treatment of perception as organized wholes, not sums of parts. Proximity, similarity, closure, continuity, common fate, figure/ground. These aren’t decorative rules. They’re the first systematic description of how the visual system constructs meaning from raw input. PFD’s L1 (First Impression) and L2 (Processing Fluency) are applied Gestalt. The debt is direct.

Neuroaesthetics (Skov & Nadal, 2020; Leder, Belke, Oeberst & Augustin, 2004)

Modern empirical aesthetics, rooted in Vienna (Leder’s lab) and Copenhagen (Skov’s). Where Kansei engineers the feeling and Gestalt describes the perception, neuroaesthetics maps the neural substrate: amygdala, orbitofrontal cortex, reward pathways. Leder’s 5-stage aesthetic appreciation model (perception → implicit integration → explicit classification → cognitive mastery → evaluation) is a finer-grained L1 subroutine within PFD’s stack.

How PFD differs

PFD is a dependency stack. Upstream failures degrade everything downstream. Kansei maps feeling to attributes but is silent on ordering. Gestalt describes perception but not decision. Neuroaesthetics explains the brain but isn’t a working methodology for a Tuesday afternoon. What PFD adds is the ordering rule and the operational protocol. The sciences are shared; the stack logic is the practitioner contribution.

The Framework

Five layers as a dependency stack. Each depends on the layer below it. Fix them in order, because upstream failures degrade everything downstream. But think of it less as a stack and more as a composition. The foundation sets the key. Each layer adds another instrument. If the foundation is broken, the whole piece is noise.

In predictive processing terms (Clark, 2013; Hohwy, 2013): when a design matches the brain’s predictions at every layer, processing is fluid and unconscious. Autopilot. When a layer fails, it generates prediction error that demands conscious attention. Good design means each layer confirms predictions so the brain’s resources flow toward the decisions that matter, not toward deciphering the interface.

The Diagnostic

How I actually diagnose a site. Not a checklist; a process.

Step 1: Feel (Pre-Verbal)

Arrive at the page and let the emotional response fire before Wernicke’s area translates it into words. “This makes me feel X.” The feeling comes before the language. System 1 before System 2. My ADHD sensitivity is an advantage here; I feel cognitive load and friction more acutely than most users. The emotional response IS the diagnostic instrument.

Step 2: Unpack

“Why does this feel X?” Now I’m looking for the systematic rule that’s broken: don’t overload, be specific, get to your point, signal-to-noise ratio, everything has a purpose, this should feel X. Does it?

Step 3: Diagnose

Step 4: Prescribe

Fix the lowest failing layer first. Always. Fixing decision architecture when the first impression is broken is like optimizing a trail that nobody enters.

The 5-Minute Perception Audit

The Generative Protocol

The Diagnostic decodes failures. The Generative Protocol derives solutions. Evaluation and generation are different cognitive operations. Evaluating a proposal against PFD catches surface violations. Deriving a solution bottom-up from PFD’s constraints surfaces requirements that no existing proposal addresses.

1. State the Design Problem in terms of user experience, not missing features
2. Work Each Layer Bottom-Up. For each: state the constraint, state the violation, derive the MUST requirement, label R[n]
3. Accumulate Requirements. R1–R5, all non-negotiable. Lower layers win conflicts.
4. Derive the Solution. What satisfies R1 AND R2 AND R3 AND R4 AND R5?
5. Test Against Proposals. Which requirements does each proposal fail?
6. Identify the Gap. Requirements no proposal satisfies = where the non-obvious solution lives

The Gate

Run before shipping. Each layer is pass/fail. If any layer below L4 fails, do not ship.

The Communication Hierarchy

Music, humor, and stories: three modalities for changing perception, ranked by power.

Music (Most Powerful)

Music communicates emotion and bypasses rational processing entirely. Koelsch (2014) showed music modulates subcortical emotion structures rapidly, potentially prior to conscious evaluation. Juslin & Västfjäll (2008) identified six mechanisms for music-evoked emotion, the majority bypassing conscious processing. In design: typography rhythm, spacing cadence, visual flow, animation timing, scroll momentum. The “music” of a page controls pacing and emotional state.

Humor (Second)

Jokes change how people feel about a thing by pointing out absurdity and giving permission to think without rigidity. A joke is: setup creates expectation, punch reveals a pattern that either aligns with your self-image or doesn’t, and the anxiety between amplifies the payoff. Laughter is the anxiety being released. Three comedy escalation patterns map to UX: linear repetition (brand consistency), sequential escalation (funnel narrative), exponential escalation (hero → proof → testimonial → CTA).

Stories (Third)

Green & Brock (2000) demonstrated “narrative transportation,” where absorption into a story produces belief changes. Two meta-analyses confirm (van Laer et al., 2014; Braddock & Dillard, 2016). The story isn’t the events. It’s how someone changes from A to B. The user is the protagonist. “I have a problem” → “This solves my problem.” The hero is the inciting incident. The CTA is the climax.

Websites as Relationships

Users evaluate websites the same way they evaluate people. Same unconscious process, same red and green flags.

The trust-killer that operates before anyone reads a word: disrespect. A site that doesn’t treat users with respect, their time, their intelligence, their needs, triggers the same rejection as a person who acts like you’re lucky to interact with them.

The Responsibility

If we’re engineers of thoughts and emotions, we need a Hippocratic oath.

The distinction: The designer controls the perception layer: presentation, UX, visual hierarchy, emotional messaging, activation points. The organization controls the value layer: product quality, pricing integrity, fulfillment, service. PFD’s ethical mandate is to align perception with reality.

When the product is good and the perception is bad (the Simply Smart Home case) PFD closes the gap upward, bringing perception up to match genuine value. That’s not manipulation. That’s correction. The violation occurs in the opposite direction: inflating perception above reality.

The Three-Part Ethical Test

1. The Alignment Test: Does this design bring perception closer to reality, or further from it? (Berdichevsky & Neuenschwander, 1999)
2. The Sincerity Test: If the user fully understood what this design choice does, would they feel served or exploited? Consumers don’t object to persuasion. They object to persuasion perceived as insincere (Friestad & Wright, 1994; Campbell & Kirmani, 2000).
3. The Golden Rule: Would I, as the designer, consent to being influenced by this technique if I were the user?

Dark patterns (Brignull, 2010; Gray et al., 2018), nagging, sneaking, forced action, are the cheap laughs of design. They convert short-term and destroy trust. PFD is the expensive laugh: genuine emotional resonance that compounds.

Relationship to Value Sensitive Design

PFD’s ethical framework sits within the HCI tradition of Value Sensitive Design (Friedman, Kahn & Borning, 2002). Knobel & Bowker (2011) extended this to ask how values get embedded into designed systems, not just studied after the fact, but actively inscribed through design decisions that privilege certain stakeholders, workflows, and outcomes over others.

PFD’s perception layer is exactly such an inscription point: every visual hierarchy, every default, every activation point encodes a judgment about whose attention matters and what they should do with it. Where VSD asks broad questions about which values a system embeds, PFD’s ethical mandate is narrower and operational: does this specific design bring perception closer to reality, for this user, in this context?

What PFD Doesn’t See

Every framework has blind spots: things it makes visible and things it occludes. Knobel’s concept of ontic occlusion (how one representation of reality blocks another from being seen) applies to PFD itself. Naming these isn’t a weakness. It’s a quality criterion.

Structural power dynamics. PFD’s ethical test says “align perception with reality.” But it doesn’t interrogate who decides what “reality” is. When SSH’s product page undersold a good product, the “reality” was clear: the product was better than the perception. But what about a company whose product is mediocre and whose “reality” is genuinely ambiguous? The alignment test assumes a knowable ground truth. In practice, “reality” is contested, and the designer choosing which reality to align with is itself a power move that PFD doesn’t surface.

Individual vs. collective. PFD models one user’s cognitive journey through the mental waterfall. It doesn’t model what happens when thousands of users are conducted through the same waterfall simultaneously. Individual perception optimization can produce collective harms: engagement loops, attention extraction at scale, homogenization of choice. PFD’s unit of analysis is the user. The effects that emerge at population scale are outside its frame.

The fluency trap. Processing fluency is L2’s core mechanism: “if it’s easy to process, it feels true.” That mechanism is value-neutral. It works for honest brands and dishonest ones. A fluent lie is more persuasive than a disfluent truth. PFD’s ethical tests catch deliberate manipulation, but they don’t address the structural problem: by optimizing for fluency, PFD makes it harder for users to engage the critical evaluation that would catch deception. The very thing that makes PFD effective (reducing prediction error, keeping users in autopilot through the desired path) is the same thing that can prevent them from stopping to question. This is ontic occlusion baked into the mechanism.

The designer’s own perception biases. PFD’s diagnostic starts with “Feel”: the designer’s pre-verbal emotional response as the primary instrument. But that instrument is calibrated by the designer’s own culture, class, neurotype, and aesthetic history. I name my neurodivergence as an advantage (heightened sensitivity to friction). But heightened sensitivity to friction could also mean under-sensitivity to other things: social warmth cues, cultural signifiers outside my experience, accessibility needs I don’t personally feel. The diagnostic instrument has its own biases, and PFD doesn’t yet have a protocol for calibrating them.

The Results

Simply Smart Home

The problem: Template site. No unified branding. Feature-focused marketing. Premium price point with a presentation that said “knockoff.”

Every layer was failing: site didn’t answer basic questions (L0, cognitive load), no faces or warmth (L1), template at premium price (L2), feature specs instead of emotional connection (L3), homepage structured around company, not user goals (L4).

What I did: Unified brand system. Emotional messaging: “stay connected, even when you’re apart.” Hero sections with faces. Consistent collateral across every touchpoint. 4-year systematic brand infrastructure build.

• Revenue 3x within a year
• Disney licensing, Costco pallets, Walmart shelf space
• Competitor stole the tagline two years later

iO Theater

“Doesn’t look like a real theater.” Full redesign: dramatic photography, clear event navigation, integrated payment. Online ticket sales 50% → 75%. Same shows. Different perception.

VacuumSealersUnlimited

Embedded design partnership, 5+ years. Revenue 4x running on infrastructure I built and maintain. The long game. Perception compounds.

What’s Teachable

3 Hours with Business Owners

Hour 1: Business Design. Your business IS a design. Feedback loops between your vertical, users, and staff. I’d give them the tools to see their business as a system.

Hour 2: People as Research. Your staff and clients are your greatest resources. Design problem-solving is really just a lens of empathy. “For whom is this?” gives you directionality that frameworks can’t.

Hour 3: Tactics. The 5-Minute Perception Audit. The dependency stack. The red flags. Application, communication, process.

The Teachability Line

The lens (empathy, for-whom, design-as-problem-solving) is fully teachable. The pattern library (hundreds of projects of instant recognition) takes years. The sensitivity (neurodivergent tuning fork for bad design) may not be teachable. But the diagnostic process (Feel → Unpack → Diagnose → Prescribe) can be taught as a substitute.

The Improv Rules

My design practice runs on principles I learned from improv classes. These aren’t metaphors. They’re operational tools.

The Dual Foundation

(“Foundation” here means evidentiary base: two non-overlapping citation pools. Not the L0 layer described above.)

PFD’s original 55 citations come from perception psychology: cognitive load theory, processing fluency, decision architecture, predictive processing. The Inverse Inflection research (2026) added 22 citations from ADHD cognitive neuroscience. Zero overlap between the two bodies. The v3.6 international expansion (April 2026) added 17 further citations across German, Austrian, Swiss, Japanese, Chinese, French, Dutch, Israeli, and Scandinavian research traditions. ~100 citations total, converging on the same design principles from distinct angles.

The Connection

Why do two separate literatures point to the same principles? Because they describe the same cognitive architecture from different angles. Perception psychology measures how the typical brain processes input: working memory limits, first-impression timing, fluency effects. ADHD neuroscience measures what happens when those same systems operate under tighter constraints: lower working memory ceiling, higher friction sensitivity, sharper temporal discounting. Same architecture, different parameters.

The five PFD layers map cleanly to ADHD neuroscience findings. Every layer has independent support from the ADHD literature, and the support is strongest at the layers that matter most: cognitive load (L0) and Processing Fluency (L2).

PFD-ADHD Layer Mapping

The Curb-Cut Argument

PFD was not designed for ADHD. But because ADHD involves the most constrained version of the cognitive architecture PFD designs for (lower working memory ceiling, higher friction sensitivity, sharper temporal discounting), designs that work for ADHD users satisfy the tightest constraints. Everyone benefits.

The principle is the same one behind curb cuts, closed captions, and automatic doors. Curb cuts were designed for wheelchair users but turned out to help parents with strollers, travelers with luggage, delivery workers with carts. Designs that reduce cognitive load for ADHD users reduce cognitive load for all users. The constrained case reveals what the general case tolerates but shouldn’t.

Cowan (2010) established that working memory holds 3–5 chunks. ADHD brains hit the ceiling of that range faster and harder, making violations visible sooner. A page that overloads an ADHD user’s working memory is overloading everyone’s. The ADHD user just notices first.

The research supports this directly. Kasatskii et al. (JetBrains, 2023) found that high perceptual load degrades ADHD-symptomatic developers’ performance faster than neurotypical developers’. Mark et al. (2008) measured context-switching recovery at 23 minutes for typical workers. For ADHD developers, Mark et al. (2024) found the cost approaches an hour. Same friction, amplified. Design for the amplified case and the typical case improves too.

The Diagnostic Instrument

I’m autistic and have severe combined-type ADHD. The autism means I learned social cognition analytically: theory, practice, application loops. I can see and articulate unconscious patterns that most designers apply intuitively but can’t explain. The ADHD means cognitive load and friction are literally painful for me. What most designers theorize about, I feel.

That sensitivity is a diagnostic instrument. When I arrive at a page, the emotional response fires before language catches up. System 1 before System 2. My ADHD sensitivity means I feel cognitive load and disfluency more acutely than most users. The feeling IS the diagnostic. The autism means I can then unpack exactly why, tracing the violation back to the systematic rule that’s broken.

I’ve come to think of this as a curb-cut effect applied to cognition. The cognitive constraints I designed around (limited working memory, sensitivity to disfluency, impatience with unnecessary friction) are constraints every user has. Mine are just louder.

The L0 Refinement

Dodson’s Interest-Based Nervous System (IBNS) proposes that ADHD attention is regulated by interest, not importance. The PINCH model identifies five drivers that override cognitive load ceilings: Passion, Interest, Novelty, Competition, Humor.

This means L0’s “reduce load” is incomplete. For ADHD users (and partially for everyone under low motivation), the correct formulation is “reduce load OR increase interest.” This is not a contradiction of L0. It is the specification of when load reduction alone is insufficient. When interest is absent, no amount of cognitive streamlining produces engagement.

Cognitive Constraint Design

The Inverse Inflection research surfaced a unifying meta-framework: Cognitive Constraint Design. The principle: cognitive constraints are design material, not obstacles to work around.

Most design approaches treat cognitive limitations as problems. Reduce choices because people can’t handle too many. Simplify because users are overwhelmed. The framing is defensive: protect the user from their own brain.

CCD inverts this. The constraint is the design input. Working memory holds 3–5 chunks? That’s not a limitation to accommodate. That’s a specification to build for. The constraint tells you what to build, not what to avoid.

Same principle, different surfaces. PFD applies Cognitive Constraint Design to interfaces. The five layers (L0 through L4) are a systematic treatment of perceptual and cognitive constraints as design specifications. Each layer names a constraint (bandwidth, first impression, fluency, bias, decision load) and prescribes a design response grounded in how that constraint actually operates.

CCD is the genus. PFD is a species. This distinction matters because it explains why PFD’s approach transfers across domains. The bouncer story, the improv rules, the diagnostic protocol: they all work because they’re applications of the same principle. Observe the constraint, design for it, test whether the design honors it.

The methodology page focuses on PFD as a design tool. This reference documents the broader intellectual framework. CCD is for researchers and practitioners who want to understand why PFD’s approach to interfaces also explains how to build session memory systems, voice preservation tools, and spatial orchestration canvases. The connecting thread is always: what constraint does the user face, and how do you design the system so the constraint becomes productive rather than destructive?

Practitioner Cognition

This section explains HOW PFD’s diagnostic produces insights that standard UX heuristics miss. It is not a different checklist. It is a different cognitive operation.

Bisociation

Koestler (1964) coined bisociation for the creative act of connecting two independent frames that don’t normally intersect. Standard association operates within a single frame. Bisociation jumps between frames to produce something neither frame contains alone.

PFD’s cross-domain structure (psychology + design + improv + neuroscience) is bisociative by architecture. The derivation protocol forces collision between constraint frames. When you work Layer 0 (cognitive load theory) and then Layer 3 (perception bias), the accumulated requirements R1 through R3 create a constraint space that neither field produces independently. The non-obvious solution lives in that collision.

Janusian Thinking

Rothenberg (1971) described Janusian thinking: the simultaneous conception of opposites as a creative process. PFD holds “reduce friction” AND “activate attention” simultaneously. The core thesis is literally Janusian: users don’t think, until you make them. Don’t make them think (L0). Make them think (activation point). Both are true. The resolution is not choosing between them but designing for the transition.

Deliberate and Spontaneous Modes

Dietrich (2004) mapped four creativity types to prefrontal function: deliberate/spontaneous crossed with cognitive/emotional. Creative insight involves both deliberate (prefrontal-guided, analytical) and spontaneous (defocused, associative) processing.

The PFD diagnostic protocol alternates between these modes. The Feel step is spontaneous: pre-verbal, emotional, System 1. The Unpack and Diagnose steps are deliberate: analytical, systematic, tracing violations back to specific layers. The protocol is not “first feel, then think.” It is “alternate between modes, and use each mode for what it does best.”

This is why the Feel step cannot be skipped. A pure checklist audit (deliberate mode only) catches surface violations but misses the emotional gestalt. A pure intuitive response (spontaneous mode only) identifies that something is wrong but cannot diagnose which layer is failing. PFD needs both.

Flat Associative Hierarchies

Mednick (1962) showed that creative people have flatter associative hierarchies: more distant conceptual connections are accessible. Where most people associate “table” with “chair” and stop, creative thinkers reach “table” to “periodic table” to “elemental structure” to “information architecture.”

Carson, Peterson & Higgins (2003) found eminent creative achievers were 7x more likely to have low latent inhibition: their brains let in more raw sensory and conceptual material. ADHD may produce flatter hierarchies via reduced latent inhibition through related mechanisms. The connection is indirect but convergent: ADHD involves reduced inhibitory filtering, creativity correlates with reduced inhibitory filtering, and PFD’s cross-domain derivation protocol rewards exactly the kind of distant associations that flat hierarchies produce.

The Communication Hierarchy

Three modalities for changing perception, ranked by power: Music > Humor > Stories.

Music communicates emotion and bypasses rational processing entirely (Koelsch, 2014; Juslin & Västfjäll, 2008; Huron, 2006). In design: typography rhythm, spacing cadence, visual flow, animation timing, scroll momentum. Humor changes how people feel about a thing by pointing out absurdity and giving permission to think without rigidity. Stories produce narrative transportation (Green & Brock, 2000; van Laer et al., 2014): absorption into a narrative produces belief changes.

The practitioner who understands all three modalities has more tools for changing perception than the practitioner who only understands information architecture. This is why PFD draws from improv, music theory, and narrative psychology alongside cognitive science. The communication hierarchy is not a bonus chapter. It is how the methodology gets delivered.

Evidence Tiers

Not all claims carry equal weight. This classification system governs what PFD states confidently, what it attributes carefully, what it frames as synthesis, and what it avoids. Every public claim should be traceable to one of these tiers.

Tier 1: Established Science

Well-replicated findings from peer-reviewed research, confirmed by multiple independent labs. PFD states these as facts.

Public framing: “Research shows...” or state directly without hedging.

Tier 2: Strong Single Studies

Solid methodology, credible venues, but not yet independently replicated. PFD cites the specific source.

Public framing: “A study by [X] found...” or “Research from [X] suggests...” Always name the source.

Tier 3: Reasonable Inferences

Logical connections drawn between established findings. The foundations are real. The bridge is untested. PFD presents these as synthesis, not established research.

Public framing: “Our synthesis suggests...” or “The evidence points toward, though this hasn’t been directly tested...”

Tier 4: Speculative or Corporate

Claims that lack methodology, independent verification, or peer review. PFD either avoids these or flags them explicitly as unverified.

Public framing: Do not use, or explicitly state: “Corporate reports claim...” Never present as research.

Accumulated Learnings

18 learnings from applying PFD across interfaces, spatial canvases, AI systems, pricing, ethics, and communication. These are not theoretical extensions. They emerged from practice and changed how the framework is applied.

Framework Comparison

PFD exists in a landscape of design frameworks. Understanding where it overlaps and where it differs helps practitioners decide when to use it and when something else serves better.

None of these frameworks are wrong. They are incomplete in different ways. Laws of UX catalogs principles without a generative method. Fogg models behavior but not perception. Krug covers L0 without the other four layers. Norman identifies processing levels without prescribing an order. Nudge Theory applies L4 without the dependency stack that determines when L4 interventions actually work.

PFD’s contribution is the dependency stack: five layers in a specific order, where each layer depends on the layer below it. Fix them in order, because upstream failures degrade everything downstream. This ordering principle is what separates PFD from frameworks that treat design principles as independent, parallel concerns. They are not parallel. They are stacked.

Make Me Think: Chapter Mapping

“Make Me Think: Perception-First Design for the Post-Usability Era” is a 12-part series that develops the framework through narrative, case studies, and citations. Each chapter maps to specific PFD layers and concepts.

The series is available at aurochs.agency/writing/make-me-think/. Each chapter stands alone. Read them in any order, though the dependency stack (Chapters 4–8) makes more sense sequentially.

Open Questions

These are genuinely unresolved. A living methodology names its edges.

Cultural generalizability (partially resolved, v3.6). The evidence base is predominantly WEIRD (Western, Educated, Industrialized, Rich, Democratic). The underlying cognitive architecture is expected to generalize: predictive processing, working memory limits, first-impression formation. But the parameters are culturally shaped: which visual patterns signal trust, what counts as “too much” cognitive load, how fluency maps to credibility.

Recent cross-cultural research resolves part of this. Masuda & Nisbett (2001) showed East Asian observers attend to background and relational context while Western observers focus on foreground and focal objects. Chua, Boland & Nisbett (2005) replicated this with eye-tracking: different scanning patterns on the same scenes. Goh et al. (2010) found cultural differences in face-processing cortex activation. Ji, Nisbett & Su (2001) showed cultural differences in prediction direction (linear vs non-linear reasoning about change).

What this resolves: the architecture is universal; the calibration is cultural. PFD’s 5-layer stack holds across populations. But L1 parameters (what triggers trust) and L3 parameters (what predictive priors load automatically) must be validated against target-market users before cross-regional rollout.

What it doesn’t resolve: L2 processing-fluency effects across non-Latin typographic traditions, L4 decision-architecture priors across markets with different default authority structures, and the relative dependency-stack ordering in high-context vs low-context cultures. These stay open.

Measurement. PFD lacks a validated measurement instrument. The 5-Minute Perception Audit is a practitioner heuristic: useful, fast, and directionally correct, but without inter-rater reliability data. A diagnostic tool where two PFD practitioners independently audit the same site and converge on the same layer diagnosis would strengthen the methodology from “expert intuition with a framework” to “teachable, repeatable diagnostic.” This is the gap between a clinical art and a clinical science.

Temporal dynamics. PFD describes the first encounter well: activation, first impression, mental waterfall. But user relationships with products evolve. At visit 100, the mental waterfall is different. Prediction errors that activated on first visit are now expected. Fluency that felt trustworthy can become invisible (users stop noticing). Does the 5-layer stack apply the same way to retention and long-term engagement as it does to acquisition? The current framework is weighted toward first contact.

Accessibility as justice vs. fluency. PFD frames accessibility through L0 (cognitive load reduction) and L2 (processing fluency). This produces good accessible design in practice. But disability justice scholars argue accessibility is a rights issue, not an optimization target. Framing it through “fluency” risks treating accessibility as something you optimize when the ROI justifies it, rather than something you guarantee because people deserve it. The framework’s utilitarian lens may not fully serve this.

AI-generated design. As AI tools generate more design artifacts, PFD’s emphasis on embodied sensitivity (the “neurodivergent tuning fork,” the pre-verbal Feel step) becomes harder to operationalize at scale. Can PFD’s diagnostic be automated? Can an AI run the Feel step? If not, the methodology has a ceiling on how far it scales beyond the individual practitioner. If yes, what’s lost when the diagnostic instrument is no longer a human body?

Appendix A: The Science

~100 citations across cognitive psychology, HCI, behavioral economics, design theory, STS, music cognition, narrative psychology, and ADHD cognitive neuroscience.

Appendix B: Glossary