Programming vs design: problem seeking vs problem solving

One-line orientation

Programming defines the problem. Design develops a physical response. The exam tests the difference between those two purposes.

Key points

• The core distinction: Programming = problem seeking (gathering, organizing, and defining the problem). Design = problem solving (generating a solution to that defined problem). Programming comes first conceptually, but projects may overlap phases or revise the program later.
• Where programming sits: Programming occurs after Feasibility and before Schematic Design. The broader project-service sequence is:
  • Feasibility Study → assess viability
  • Programming / Pre-Design → define needs and goals
  • Schematic Design (SD) → explore design concepts
  • Design Development (DD) → refine and coordinate
  • Construction Documents (CD) → produce permit/build set
  • Construction Administration (CA) → administer the construction contract and observe the work
• What programming produces: A program document — spaces, square footage, adjacency requirements, client goals, and budget parameters. This is the design criteria package.
• Who is responsible for programming: The owner — under AIA B101 (§5.1) the owner must provide a written program (objectives, schedule, constraints and criteria, space requirements and relationships). In practice the architect or a specialized programming consultant often develops the program on the owner’s behalf — but for the architect that is a Supplemental or Additional Service under B101, never part of Basic Services.
• Programming is not passive: It demands judgment about which needs matter and how to frame the problem. The quality of the program directly shapes the quality of the design.

Programming defines the problem before design solves it

Schematic

Feasibility asks whether to proceed; programming states what must be solved; design develops the answer.

View diagram Hide diagram

Scroll horizontally to explore →

Programming is not schematic design. Architect assistance with developing the program may be a supplemental or additional service.

Confusions / comparison

Phase	Primary goal	Key deliverable
Feasibility Study	Assess project viability — technical, financial, legal	Site analysis, risk assessment, go/no-go recommendation
Programming / Pre-Design	Define needs and goals — the problem	Program document: spaces, SF, adjacencies, budget parameters
Schematic Design (SD)	Develop initial design concepts — begin solving	Rough plans, elevations, sections; preliminary cost estimate
Design Development (DD)	Refine the design; coordinate systems	Coordinated drawings; updated cost estimate; consultant input
Construction Documents (CD)	Produce the complete build set	Permitted drawings + specifications for bidding and construction
Construction Administration (CA)	Ensure construction matches design intent	RFI responses, submittals, site observations, punch list

Related

→ prog-five-step-process (this module): the five-step method for conducting programming · prog-function-form-economy-time (this module): the four considerations that organize every program statement · prog-degrees-of-sophistication (this module): how programming depth varies by project complexity · pp-basic-vs-additional-services (ProPractice module): why architect-developed programming is a Supplemental/Additional Service under B101.