Architectural programming is the process of defining the problem before you solve it. And the most tested framework for that process on the ARE is Problem Seeking, developed by William Pena and Steven Parshall. NCARB lists it as a primary study resource for the PA division.

Problem Seeking organizes programming information into four categories: Goals (what the client wants to achieve), Facts (what you know about the existing situation), Concepts (the functional and organizational ideas that link goals to reality), and Needs (the quantifiable requirements that translate everything into square footage, budgets, and schedules).

These four categories don't operate in isolation. They interact through a structured five-step process: establish goals, collect and analyze facts, uncover and test concepts, determine needs, and state the problem. The result is a building program that captures the client's priorities, reflects real constraints, and provides the design team with a clear framework to begin schematic design.

For the ARE, Objective 4.3 requires you to identify and prioritize components of the building program. That means understanding primary vs. subsidiary spaces, front of house vs. back of house, occupied vs. unoccupied areas, phasing, circulation, and area requirements including the distinction between net and gross square footage. Problem Seeking gives you the methodology. The exam tests whether you can apply it to actual scenarios.