Attention architecture

Attention Architecture

This skill exists because many portfolios fail not only in what they show, but in how they ask the visitor to process it.

The problem is often not:

• bad design
• weak copy
• missing proof

The problem is that too much arrives at once, or the right things arrive too late.

That is an attention problem.

Core Rule

A portfolio should not leave the visitor's attention to chance.

It should deliberately shape:

• what lands first
• what deepens next
• what can wait
• what creates fatigue
• what earns continuation

What This Skill Evaluates

This skill looks at:

• information density
• section rhythm
• signal timing
• proof timing
• CTA timing
• cognitive load
• reading momentum
• fatigue caused by repetition or overload

Common Attention Failures

Failure 1: Early overload

Symptoms:

• too many badges
• too many buttons
• too many support layers
• too many parallel claims

The portfolio asks for too much processing before trust exists.

Failure 2: Delayed proof

Symptoms:

• atmosphere first
• explanation first
• labels first
• real evidence later

The visitor spends attention before receiving a reason to keep spending it.

Failure 3: Flat section rhythm

Symptoms:

• every section has similar weight
• repeated card logic dominates
• there is too little contrast between narrative beats

The portfolio becomes harder to continue through.

Failure 4: CTA timing mismatch

Symptoms:

• the CTA appears before trust
• or after the user is already fatigued

What To Favor

• one clear beat at a time
• earlier proof
• stronger contrast between section roles
• information pacing that respects cognitive load
• section sequence designed around attention, not accumulation
• fewer simultaneous asks

What To Avoid

• treating every section as equally urgent
• stacking signals without hierarchy
• long stretches of similar information weight
• decorative density that competes with meaning
• CTA overload

Audit Questions

Before approving a homepage, section flow, PDF, Notion page, slide deck, or portfolio page, ask:

1. What is the visitor meant to understand first?
2. Is too much arriving before that lands?
3. Does proof arrive at the right moment?
4. Does each section change the rhythm enough to justify continued attention?
5. Is the CTA timed after trust, but before fatigue?
6. Does the portfolio feel guided, or simply accumulated?

Channel Applications

Web

Look at:

• section stacking
• scroll fatigue
• repeated UI patterns
• CTA placement

Mobile

Look at:

• vertical density inflation
• proof delay
• repeated card fatigue
• support layers that become too heavy

PDF / Notion / Slides

Look at:

• reading blocks that become too dense
• poor sequencing of information
• too many conceptual jumps without hierarchy
• lack of attention guidance between sections

Rewrite Method

When attention architecture feels weak:

1. identify what must land first
2. remove one early overload layer
3. move one proof element earlier
4. increase contrast between two adjacent sections
5. reduce repeated patterns that slow momentum
6. retime the CTA

Relationship To Other Skills

Closest neighbors:

• client-signal-prioritization
• hero-construction
• proof-first-case-studies

Difference:

• client-signal-prioritization asks what matters most
• attention-architecture asks whether the visitor receives it in the right sequence and at the right cognitive speed

Success Condition

This skill succeeds when the portfolio feels like:

• attention is guided
• proof arrives on time
• information breathes at the right pace
• the user keeps going for good reasons

Not:

• overloaded
• flat
• tiring
• or accidentally sequenced