Information Architecture

#practical-application #system-architecture

What It Is

Information architecture is prevention architecture applied to attention and information consumption. The modern information environment is adversarially engineered to capture attention, fragment focus, and maximize engagement time. Default configuration (notifications enabled, apps accessible, infinite scroll available) produces outcomes most people don't want: fragmented attention, working memory overflow, reactive consumption patterns. Architected configuration produces different outputs automatically.

The Alpha/Beta distinction provides deep framework: Beta signals (push notifications, social media feeds, news alerts) fragment attention across external demands. Alpha signals (pull-based querying when needed) maintain coherent internal thread. The architectural question: remove Beta interference sources (prevention) or resist each interrupt (expensive, fails).

Information consumption follows Boltzmann distribution—you naturally consume what has lowest activation energy. Phone on desk, notification visible = 0.1 units to check. Resistance costs 2-3 units per notification. You will check phone. Not moral failure—thermodynamics. Solution: phone locked in drawer = 4 units to check, continuing work = 0.5 units. Now thermodynamics selects for work.

Push vs Pull Architecture

The fundamental architectural choice: allow world to push information to you (Beta architecture) or query world when you need information (Alpha architecture).

Push architecture (Beta):

graph LR
    A[Work Thread] --> B[External Signal<br/>Notification]
    B --> C[Interrupt]
    C --> D[Process Notification]
    D --> E[Attempt Resume]
    E --> F[External Signal]
    F --> C
    style B fill:#ff9999
    style C fill:#ff9999

Characteristics:

World controls timing (you are reactive)
Information arrives regardless of relevance
Working memory constantly disrupted
High reactivation cost after each interrupt
Attention fragmented across external demands

Pull architecture (Alpha):

graph LR
    A[Work Thread] --> B{Need info?}
    B -->|Yes| C[Query]
    C --> D[Get Answer]
    D --> A
    B -->|No| A
    style A fill:#99ff99
    style D fill:#99ccff

Characteristics:

You control timing (you are proactive)
Information serves current focus
Working memory remains coherent
Low continuation cost (no interrupts)
Attention maintained on chosen priority

Comparison table:

Dimension	Push (Beta)	Pull (Alpha)
Control	External (reactive)	Internal (proactive)
Relevance	Variable (often irrelevant)	High (queried as needed)
WM impact	Fragments across 7+ items	Maintains 1-2 item focus
Reactivation cost	0.5-1 unit per interrupt	0 (no interrupts)
Total daily cost	20-50 units (notifications + resistance)	2-5 units (occasional queries)
Effectiveness	Low (fragmented execution)	High (sustained focus)

The intervention: Remove all push sources. Phone notifications off. Email checks scheduled (not constant). Social media apps deleted. News alerts disabled. Query when needed, ignore otherwise.

Prevention Architecture for Digital Environment

Specific architectural interventions that eliminate resistance cost:

Phone management:

Configuration	Check Cost	Resist Cost	Daily Total	Behavioral Result
Phone on desk, visible	0.1 units	2-3 units × 50/day	100-150 units	Check constantly
Phone in pocket	0.3 units	2 units × 30/day	60 units	Check frequently
Phone in drawer	4 units	0 (no visibility)	0-4 units	Check rarely
Phone off entirely	6 units (find + turn on)	0	0-6 units	Almost never

Website/app blocking:

Prevention through technical barriers:

Block DoorDash/entertainment sites during work hours
Remove social media apps from phone (not just hide—delete)
Browser extensions prevent infinite scroll
App time limits hard stop (not notifications—actual blocking)

The redirect pattern:

Instead of resisting urge to check DoorDash:

Attempt to open app
See redirect screen (different positive signal)
Experience different outcome (no food reward)
After 30+ repetitions: circuit rewires (DoorDash → redirect → no dopamine)

Not willpower defeating temptation. New temporal pairing replacing old pairing.

Deliberate Information Acquisition

Pull architecture doesn't mean zero information consumption—it means intentional consumption aligned with current priorities.

Strategic information categories:

Category	Purpose	Access Pattern	Examples
Domain building	Develop expertise in chosen area	Scheduled deep sessions	Technical docs, domain books, research papers
Current project	Solve active problems	Query as needed	Stack Overflow, documentation, specific searches
Horizon scanning	Discover unknown unknowns	Weekly/monthly reviews	Industry newsletters, curated feeds, mentor conversations
Recreation	Recovery and enjoyment	Time-bounded, chosen	Specific books, selected podcasts, planned content

Anti-patterns to prevent:

Anti-pattern	Mechanism	Cost	Prevention
Infinite scroll	Engineered for endless consumption	Fragments attention, wastes hours	Delete apps, use website blockers
News addiction	Novelty dopamine hits	Anxiety, no actionable information	Batch news to weekly, curated sources only
Reactive reading	Following links endlessly	No coherent learning, surface-level	Queue to read later, batch processing
Comparison browsing	Social media, competitor obsession	Beta anxiety, no productivity	Scheduled check-ins only, not continuous monitoring

Content Selection Framework

Not all information is equal in value/cost ratio. Information value = uncertainty reduction × decision impact. Information cost = time + attention + cognitive load.

Value/cost matrix:

        High Value
            |
   Q2       |      Q1
 (Medium)   |   (Consume)
            |
────────────┼──────────── High Cost
            |
   Q4       |      Q3
  (Avoid)   |   (Limited)
            |
        Low Value

Examples by quadrant:

Quadrant	Information Type	Consumption Strategy
Q1: High value, Low cost	Directly applicable technical docs, mentor advice, customer feedback	Consume immediately, high priority
Q2: High value, High cost	Textbooks, research papers, complex frameworks	Schedule dedicated time, deep sessions
Q3: Low value, High cost	Random articles, trending topics, general news	Minimize or eliminate
Q4: Low value, Low cost	Quick entertainment, memes, light content	Allow as recovery (time-boxed)

The deliberate queue:

Instead of consuming reactively:

Encounter interesting article → Save to read later
Batch process queue weekly
Skim to assess value/cost
Deep read Q1/Q2, discard Q3/Q4
Extract actionable insights
Execute or archive

Separates discovery (low cost) from consumption (high cost). Enables filtering before commitment.

The Information Diet Protocol

Will's current system (zero social media, phone off by default):

Prevention layers:

Layer	Intervention	Effect
Physical	Phone locked in drawer during work	4-unit cost to access
Software	Social media apps deleted (not logged out—deleted)	6-unit cost to reinstall
Network	Website blockers on work device	Prevents access entirely
Temporal	Scheduled communication windows only	No reactive checking

Consumption windows:

Morning 6-8am: Zero information input (braindump, work launch)
Work blocks 8am-12pm: Query-only (Stack Overflow, docs as needed)
Midday 12-1pm: Gym (zero information)
Afternoon 1-5pm: Query-only work blocks
Evening 5-8pm: Deliberate consumption window (if desired)

The architecture prevents reactive fragmented consumption, enables sustained focus, reduces willpower expenditure on resistance.

Signal Theory - Alpha (pull) vs Beta (push) information architecture
Prevention Architecture - Remove notification sources, not resist notifications
Focus - Sustained attention through removing interrupt sources
Willpower - Each interrupt/resistance costs units
Working Memory - Information overload fragments capacity
Activation Energy - Access cost determines consumption patterns
Statistical Mechanics - Thermodynamic flow to lowest-cost option
Neural Positivism - Positive replacement signals, not mere absence
AI as Accelerator - Use AI for query acceleration, not continuous feed

Key Principle

Design information environment for pull, not push - Modern information environment is adversarially optimized to capture attention through notifications, infinite scroll, algorithmic feeds. Default configuration produces fragmented attention, reactive consumption, and capacity overflow. Architected environment: remove push sources (delete apps, disable notifications, lock phone), enable pull when needed (scheduled query windows, deliberate batching). This isn't asceticism—it's Alpha architecture that maintains coherent internal thread versus Beta fragmentation across external demands. Each push interrupt costs 0.5-1 willpower unit for context switch. Each resistance to notification costs 2-3 units. With 50+ daily notifications, cost exceeds budget. Prevention (sources removed) costs 0 units ongoing. Phone in drawer not visible = thermodynamics selects for continued focus. Same information accessible through pull queries (Stack Overflow, docs, searches) but you control timing. The difference: reactive scattered consumption vs intentional targeted acquisition.

Your attention is finite. The information environment is infinite and adversarial. Design architecture that prevents push, enables pull, and preserves sustained focus for priorities that matter.