The request said 20,000 square feet, but Todd Burns did not treat that number as the answer; he treated it as the first assumption to test.
In the 2018 Constructrr episode, Todd described looking at people counts, space use, work settings, and the type of environment the client wanted. That review might point to 16,000 or 18,000 square feet instead. Only then would the team compare buildings and move toward test fits.
The order matters. A faster layout cannot repair a demand assumption that no one examined.
Twenty thousand square feet is a hypothesis
Todd Burns described clients needing program, cost, and building information quickly enough to support real-estate decisions. His example started with “true demand.” The team first asked how much space the organization used and what kinds of spaces its work required.
Todd called the result “true demand.” That step changes every comparison that follows. Circulation factors, building options, test fits, and budgets are more useful when they are responding to a tested program instead of an inherited number.
A pre-design team can apply the same discipline without adopting the episode's specific product. Mark the first square-foot requirement as an assumption. Record the people, use, and operating evidence behind it. Keep the number open until the team responsible for the program agrees that the evidence is sufficient.
A quick picture needs a visible boundary
Speed introduces another risk: a visual concept can feel settled before it has received technical review. Todd Burns warned that layouts created by nontechnical users could contain code, corridor, or egress problems. He did not argue that clients should be kept away from early options. He described a handoff in which better program information gives architects and planners a clearer place to begin.
The boundary should be plain on the page. An early test fit can help people compare possibilities. It is not a technical approval, a code review, or a promise that the plan can be built exactly as shown.
That distinction protects the conversation from moving faster than the evidence. The client can react to the concept while the architect or planner remains responsible for the technical judgment.
One program can inform several portfolio choices
Todd Burns also applied the workflow beyond a single lease decision. He described a corporate campus moving departments among buildings, estimating the cost of those moves, and using the scenarios in annual capital planning.
At that scale, an untested program does not affect only one test fit. It can travel into several building comparisons and a future budget. A well-defined need gives the owner a common input for those choices, while each site still requires its own review.
The next time a team asks how quickly it can receive a test fit, pause on the number that will be entered first. Ask who supplied it, what evidence supports it, and who will decide when it is reliable enough to guide a layout. Those answers determine whether speed is helping the decision or simply carrying the first assumption farther.
