Architect walking a site with community members
Insights
A Catalyst Factor EssayDesign Practice

What Should We Know About a Place Before We Design for It?

CP

Craig Park, FSMPS

Strategist · Author · AEC Advisory

AI can help a design team read a place's public record before the first meeting. The people who live and work there can show the team where that record falls short.

Imagine a town preparing to replace its library. The planning documents describe the property as well connected. There's a bus stop on the adjacent street, a sidewalk to the entrance, and a marked crossing at the corner. The site plan supports that description.

Then a librarian walks the route with the design team. She points out where teenagers coming from school cross to avoid a long detour. A parent describes trying to get a stroller across the same street as cars turn through the intersection. A library employee explains where people wait after closing when their ride is late.

The bus stop, sidewalk, and crossing are all where the plan says they are. The walk changes what the team understands about using them. It may also change a decision that will be difficult to reverse once the building is designed: where to put the front door.

Read the record for the questions it raises

A design team can arrive better prepared than it could by reading the project brief alone. With a defined set of sources, an AI assistant can compare a comprehensive plan, transit maps, public meeting minutes, and the library's own service priorities. It can help trace how an idea changed over time or flag where two documents appear to assume different things about the same site.

The value is in what the team does with those findings. If a transportation plan calls an intersection a pedestrian priority and the capital plan shows no scheduled improvements, pull both sources and check their dates. Then ask a question the design team can act on: What should we assume about the crossing on opening day?

That question could change the entrance location, the budget, or the sequence of work. It could also bring the right public works or transit staff into the conversation while the team still has choices. AI helps prepare the question. The people who know the place help establish what the answer means.

Learn how the place works on an ordinary day

Some of the most useful engagement happens when someone shows you what they do. Walk the route from the bus stop with a regular patron. Ask the maintenance supervisor to show you what happens during a heavy rain. Spend twenty minutes by the entrance at dismissal and see where people gather, where they hesitate, and how they find their way.

A public meeting can tell you what people want a project to accomplish. An ordinary day can show you what might keep them from using it. Look for people whose experience is easy to miss in the meeting record, including those who come at different hours, use different routes, or keep the place running behind the scenes.

Expect accounts to differ. Teenagers may value the most direct route. Staff may need a clear view of the entrance at closing. A patron with limited mobility may care most about how far it is from the drop-off to the door. Each describes a different condition the same design will have to serve. Hear enough of those accounts to understand who benefits from each option and who would have to adapt.

Carry what you learn into a decision

At the first design review, show how the team's understanding changed. In the library example, compare two entrance locations using the actual routes people described. Walk each option with library staff and patrons. If the preferred entrance depends on a crossing improvement outside the project's scope, identify who owns that decision and show how the library would function if the improvement came later.

Then report back to the people who helped. Tell them what changed, what tradeoffs the team weighed, and what still needs a decision. If a suggestion couldn't be carried forward, explain why and give people a chance to point out what the team may have missed. That's how a conversation about a place becomes a working relationship with the people who use it.

After opening, return at the same hour you first observed the site. Watch where students cross and where patrons wait for rides. Ask staff what they've had to adjust. That visit tells the owner whether the design is working as intended and gives your firm something specific to carry into the next project.

Before the next concept review, ask the team to bring one decision that changed because someone showed them how the place works. It might be the location of a door, a route that stays open after hours, or a sheltered spot to wait. Then put a date on the calendar to go back and see how people use it.