Architecture Programming

Architecture programming (more precisely architectural programming) is the pre‑design research and decision‑making phase in architecture. It defines what needs to be built before any drawings, models, or design concepts are created.

🧩 What Architectural Programming Is

• Project definition — It identifies the problem the building must solve and clarifies the client’s mission, goals, and constraints.
• Scope development — It lists all required spaces, their sizes, relationships, and performance needs.
• Data gathering — It includes interviews, surveys, site analysis, and studying user workflows.
• Criteria setting — It synthesizes information into design criteria that guide the architect through the entire project.

🎯 Why It Matters

• Reduces scope creep by clarifying needs early.
• Saves money because changes on paper are cheaper than changes during construction.
• Aligns design with real user needs, not assumptions.
• Improves long‑term building performance by grounding decisions in research.

🛠️ What Happens During Programming

• Establish goals — mission, vision, functional needs.
• Collect data — interviews, surveys, site conditions, codes.
• Analyze relationships — adjacency diagrams, circulation needs.
• Define space requirements — room lists, sizes, environmental needs.
• Report findings — a formal program document guiding design.

🧠 In Simple Terms

Architectural programming is like writing the blueprint for the blueprint. It answers what, why, and how much before the architect answers what it looks like.

Please submit your personal programming to me via Google Drive share link: