Start with the operating reality.
Before I want to see a plan, I want to understand what the opportunity is asking the business to become. A site can look compelling on a map and still be wrong for the operation it would require. The useful questions are practical: Who is the customer? What promise will the place make? How will people arrive, move through it, receive service and leave with the right impression? What has to work every day, not just on opening day? Those answers establish the real program. They also expose where an attractive concept is carrying an operating burden that has not yet been named.
In hospitality and mixed-use work especially, the program is more than a count of keys, units, seats or square feet. It is the relationship between front-of-house experience and back-of-house capacity; between peak demand and normal staffing; between privacy, circulation, maintenance and revenue-producing space. I have found that bringing the operator’s perspective forward changes the quality of the earliest decisions. It keeps a project from optimizing the image of the asset while quietly making its daily use harder. A program earns confidence when the team can explain how it will run with the same clarity it can explain how it will look.
Treat the site as a system, not a parcel.
A sophisticated evaluation does not stop at access, visibility and a preliminary test fit. It asks what the site needs from the larger system around it. Utilities, drainage, road capacity, grading, fire access, easements, environmental conditions and jurisdictional requirements can each become defining conditions. So can the less dramatic constraints: where deliveries occur, how waste moves, when construction traffic is allowed and whether a neighboring use changes the guest or resident experience. None of these questions are glamorous, but each can change the program, budget, phasing or schedule long before a finished drawing reveals the consequence.
Entitlement deserves the same disciplined view. The issue is not whether a proposed use is theoretically possible; it is what path would make it achievable, legible to the community and durable through the approval process. I prefer to identify the decisions that are fixed by regulation, the questions that require dialogue and the assumptions that must be tested rather than repeated. This is also where infrastructure and entitlement meet. A permitted program that depends on uncertain capacity, off-site work or a sequence of approvals is not yet a simple program. It is a delivery problem, and the team should describe it honestly.
Choose the delivery path before choices narrow.
Design has great value, but it should not be asked to solve problems that were available to solve earlier. By the time a concept has developed into coordinated drawings, a team may have made implicit commitments about construction method, procurement, phasing, capital timing and the opening date. Those commitments affect one another. A tight site may favor a different sequencing strategy. A repetitive program may invite a different construction approach. A seasonal operating calendar may make a single date more consequential than an incremental cost saving. The right answer is not a preferred method; it is the method that protects the intended outcome under the conditions actually present.
That is why I want the development, operations, design, engineering and construction perspectives in the same room before design becomes expensive. The goal is not to eliminate uncertainty or to manufacture false precision. It is to separate manageable risk from unexamined risk, assign ownership to the questions that remain and preserve options where more learning is needed. It also gives the team a common language for deciding what must be resolved now, what can proceed in parallel and what should remain contingent. A sound early evaluation gives the project a delivery strategy rather than a collection of hopeful assumptions. When that work is done well, the first drawing carries more than an idea. It carries a decision that has already been tested against reality.