Skip to main content
Almost an Architect
Current page: Peña, Problem Seeking — Ch 1 — How Much Information is Enough?
PatternRecommended

Discriminate major ideas from details

Peña, Problem Seeking — Ch 1 — How Much Information is Enough?

Description

When a client provides too much information, the risk is that the architect's solution anchors on details rather than major ideas. The architect must plough through the abundance, demoting details to a later phase and surfacing the major form-giving ideas at the front.

Why this exists

Detail anchoring is the most common programming failure: the user mentions "a window seat in the kitchen" and the architect spends three days designing around it before realizing the kitchen orientation hadn't been settled.

Categories

Adjacency

Source

Caudill Rowlett Scott (via ERIC, US Dept of Education)authoritative
Problem Seeking: New Directions in Architectural Programming (early edition (ERIC ED037930, 1969))
Upgrade path: $75 for Problem Seeking 5th Edition (Wiley). 5th edition (2012, Wiley) is the current authoritative form of Peña's method. The ERIC PDF is the earliest published form — all the core method is present; later editions add case studies and refinements.
Section: Ch 1 — How Much Information is Enough?
Published 1969-01-01 · last verified 2026-05-14

Solver enforcement

Browsable only — the solver does not currently enforce this directive (no spec-level data to check against). This entry exists so the architect personas can cite it in conversation and the user can read what the rule says.

Related directives

Last reviewed 2026-05-14.