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:

DimensionPush (Beta)Pull (Alpha)
ControlExternal (reactive)Internal (proactive)
RelevanceVariable (often irrelevant)High (queried as needed)
WM impactFragments across 7+ itemsMaintains 1-2 item focus
Reactivation cost0.5-1 unit per interrupt0 (no interrupts)
Total daily cost20-50 units (notifications + resistance)2-5 units (occasional queries)
EffectivenessLow (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:

ConfigurationCheck CostResist CostDaily TotalBehavioral Result
Phone on desk, visible0.1 units2-3 units × 50/day100-150 unitsCheck constantly
Phone in pocket0.3 units2 units × 30/day60 unitsCheck frequently
Phone in drawer4 units0 (no visibility)0-4 unitsCheck rarely
Phone off entirely6 units (find + turn on)00-6 unitsAlmost 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:

  1. Attempt to open app
  2. See redirect screen (different positive signal)
  3. Experience different outcome (no food reward)
  4. 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:

CategoryPurposeAccess PatternExamples
Domain buildingDevelop expertise in chosen areaScheduled deep sessionsTechnical docs, domain books, research papers
Current projectSolve active problemsQuery as neededStack Overflow, documentation, specific searches
Horizon scanningDiscover unknown unknownsWeekly/monthly reviewsIndustry newsletters, curated feeds, mentor conversations
RecreationRecovery and enjoymentTime-bounded, chosenSpecific books, selected podcasts, planned content

Anti-patterns to prevent:

Anti-patternMechanismCostPrevention
Infinite scrollEngineered for endless consumptionFragments attention, wastes hoursDelete apps, use website blockers
News addictionNovelty dopamine hitsAnxiety, no actionable informationBatch news to weekly, curated sources only
Reactive readingFollowing links endlesslyNo coherent learning, surface-levelQueue to read later, batch processing
Comparison browsingSocial media, competitor obsessionBeta anxiety, no productivityScheduled 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:

QuadrantInformation TypeConsumption Strategy
Q1: High value, Low costDirectly applicable technical docs, mentor advice, customer feedbackConsume immediately, high priority
Q2: High value, High costTextbooks, research papers, complex frameworksSchedule dedicated time, deep sessions
Q3: Low value, High costRandom articles, trending topics, general newsMinimize or eliminate
Q4: Low value, Low costQuick entertainment, memes, light contentAllow as recovery (time-boxed)

The deliberate queue:

Instead of consuming reactively:

  1. Encounter interesting article → Save to read later
  2. Batch process queue weekly
  3. Skim to assess value/cost
  4. Deep read Q1/Q2, discard Q3/Q4
  5. Extract actionable insights
  6. 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:

LayerInterventionEffect
PhysicalPhone locked in drawer during work4-unit cost to access
SoftwareSocial media apps deleted (not logged out—deleted)6-unit cost to reinstall
NetworkWebsite blockers on work devicePrevents access entirely
TemporalScheduled communication windows onlyNo 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.

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.