--- title: "How Architecture Teams Turn Client Goals Into Clear Design Priorities" url: "https://architecttoday.com/qa/how-architecture-teams-turn-client-goals-into-clear-design-priorities/" author: "Architect Today" published: "2026-10-13" updated: "2026-10-13" --- # How Architecture Teams Turn Client Goals Into Clear Design Priorities ## How Architecture Teams Turn Client Goals Into Clear Design Priorities Great architecture starts with clear priorities, not a long list of wishes. This article shows how teams turn client goals into focused decisions about function, budget, appearance, and field constraints. Insights from architecture experts reveal practical ways to align stakeholders and define success before design begins. ### Classify Wishes by Sacrifice 1\. What are the few key fears hiding behind a client's broad goals for a project that they will regret in 5 years? In real estate at Huttons, for example, many couples come in with seemingly conflicting 'wishes' (open-plan living area vs. quiet home offices to work, more space vs. lower budget). I first write down all their wishes on 3 columns: things they 'must have' in a project (non-negotiables), things they 'would like to have' (nice-to-haves), and things they 'would happily trade off' (trades). By getting them to write down all their wishes on these 3 columns, the conflicting 'wishes' between the couple soon become a list of choices that they can then use to decide on trade-offs. Non-negotiables then form the basis of all subsequent decisions. Will a bigger kitchen be OK if that means giving up on something else? 2\. One of the biggest exercises to prevent future heartache is a "day in the life" walkthrough of a typical Tuesday and a Sunday with family and guests. The husband of one of our families described taking overseas calls in the evening after 10pm. His wife is a light sleeper. We immediately changed our approach for their layout needs. I have also supported development work at CDL and it's the same lesson - stories reveal priorities that spreadsheets cannot. It's only when a client hears themselves describe their typical behavior that they can realize what's really important to them and we can begin to write their brief. *— [Corina Tham](https://www.linkedin.com/in/corina-tham-94a568a4), Sales, Marketing and Business Development Director, CheapForexVPS* --- ### Define Success Before Design Begins I like to start projects with ambiguous client-goals with a "missioning" process. Projects are destined for conflict if the stakeholders aren't all subscribed to a common understanding of the mission of the project. I often like to frame this as, "5 years after ribbon cutting, after all the 'newness' has worn off, what will demonstrate to you that this project was a success?" If you can't get a client group to a shared understanding of what success looks like, be prepared for some capricious design changes at every point in the project. Most first-time clients are a bit thrown by our kick-off \*not\* being about design, but being about their shared vision of success, but it can radically improve how a project proceeds, and becomes a framework for resolving challenges along the way; "would option A or option B get us closer to the 5-years vision of project success?" Then it's not about winning or losing ideas, but service towards the shared mission. *— [Tobias Gilk](https://www.linkedin.com/in/tobiasgilk), Senior VP, RADIOLOGY-Planning* --- ### Align Stakeholders Around a North Star At the inception of an architecture project, we use a compulsory mapping exercise called the "North Star" that ensures every stakeholder adheres to a single main business goal before technical designs commence. We find that the majority of our projects are delayed by conflicting project requirements from various stakeholders. For instance, the executive sponsor is interested in facilitating rapid implementation; the operations lead wants the design to focus on detail; and the engineers want the project's be perfectly scalable. Thus, we conduct a structured workshop for MoSCoW prioritization during the discovery phase. In the workshop, stakeholders have a fixed quota of "Must Have" features to prevent a situation where everything is treated as crucial. Stakeholders must link their requirements to the previously approved North Star metric, which can be either the speed of acquiring new customers or performance of the system. During the project start-up, we discover many discrepancies in views of the stakeholders, for example, the requirement of one stakeholder to have real-time data synchronization conflicting with the need of another stakeholder to minimize costs. Therefore, the MoSCoW framework helps facilitate the trade-offs before the architect's drawing process begins. In other words, we ask stakeholders to identify what is essential and what can be postponed until later. Hence, the collaboration at the early stage of the project allows establishing an accurate baseline for navigating the project. *— [Amit Agrawal](https://www.linkedin.com/in/amitagrawal8cis), Founder & COO, Developers.dev* --- ### Rank Function, Budget, and Appearance On renovation projects, I ask clients to rank daily function, budget and appearance before anyone discusses finishes. Then we test every request against existing services, compliance needs and the cost of moving hidden infrastructure. The decisive exercise is choosing which priority wins when two cannot coexist. That written order gives the architect a practical brief and prevents cosmetic choices from quietly overruling function or budget. *— [Jesse Fowler](https://www.linkedin.com/in/jesse-fowler-016024191), Founder, Plumber, J & J Plumbing Services* --- ### Surface Conflicts Through Silent Cards We work with groups whose goals conflict before any plan exists, so this answer comes from facilitation rather than from architecture. The exercise we rely on starts in silence. Each person writes their own answer to one question on cards before anyone speaks: what has to be true for this project to count as a success? The group then clusters the cards without pre-set categories, names each cluster, and marks where two clusters pull against each other. Those contradictions become the agenda for the first meeting, well before construction begins. At OISE at the University of Toronto, academic staff were divided over research and school funding. Working in teams of 20 per action plan, they produced plans the dean approved on the spot, and three years later those plans were still active. *— [John Miller](https://www.linkedin.com/in/jmillerica), President, ICA Associates Inc.* --- ### Allocate Points to Core Values We prefer to begin every project with a simple constraint auction that encourages focus. Each client receives a limited pool of points to divide across outcomes like quiet, daylight, resilience, adaptability, cost predictability, and easy upkeep. The limit forces thoughtful choices because every point given to one priority leaves less for another. We learn what truly matters instead of assuming every goal deserves equal attention naturally. After scoring, we ask everyone to explain the point they refused to move most. That answer often reveals personal experience, daily challenges, or concern about future regret clearly. We record the reason beside the score so every decision keeps its original context. This gives the team a shared guide for future tradeoffs with clearer conversations together. *— [Brian Lebeau](https://www.linkedin.com/in/brian-lebeau-b7773a1), CEO, Attic Projects Company* --- ### Set Vision Through Result Ranges For me, one of the most difficult situations at the start of an architectural project is when a client says, "I want it to be beautiful." At first glance, this seems like a clear request, but in practice it can stand for completely different ideas of what the result should be. One of the exercises we use is the "image of the result." If we see that a client finds it hard to articulate their expectations or isn't ready to fill out a detailed brief, we ask three simple questions: what result would be most satisfying for you, what outcome would you be fine with, and what result would be the minimum you could accept? Set the exact system, turn the conversation toward the client's specific vision, and get on the same page regarding the final result. In commercial projects the final goal should be revenue. And it's crucial to make sure that the business owner understands that customers' expectations come first, since it is customers who bring money to the business, not vice versa. A brief should go beyond square meters, budget, and technical requirements. We want to understand the brand. Is there an established brand platform? How is the company positioned? Who is the customer? Once we have agreed with the client on these basic questions, we divide the project into two related categories. We start with technological design with a focus on the functions of the space, such as internal processes, the organization of customer flows, zoning, and other components. Only then we move on with the visual design concept, where we define the look, the architectural and stylistic techniques, and how the space reflects the brand's positioning. One more exercise that helps to keep the project within the defined boundaries is a roadmap. At the very beginning of a project, it's crucial to define the milestones with a clear scope, interim checkpoints, and the deadlines for client's feedback, so that we make sure a projects' launch dates won't be moved. This exercise allows both sides to see not just the final result but the overall process that leads to it. Clients understand what they are approving, what other decisions they have to make, and what will be required next. For complex projects, we also establish in advance the rules for making changes and the number of iterations. This is not a restriction on the creative process, but a way to protect the project from an endless accumulation of new ideas that begin to contradict the original task. *— [Aliaksandra Nazarkina](https://www.linkedin.com/in/aliaksandra-nazarkina), CEO, NZR* --- ### Measure Goals Before Commitment Most clients arrive with goals that can't all be true at once: faster releases, tighter compliance, lower cost, more features, all by Q3. That's normal. Nobody has had to choose yet, and my first job is to make them choose before the design does it for them by accident. I start by asking what each goal is for. Half the time a goal is a solution in disguise. "Move to microservices" is a plan, and when I ask what happens to the business if it works, the answer is often "we stop losing a week every time a payer changes a format." That's the real goal. Digging like this usually shrinks a page of wishes to four or five outcomes someone can measure. Then I attach numbers: latency, availability, recovery time, cost ceiling, how many engineers they actually have. A goal with no threshold can't settle an argument. When two outcomes collide, say delivery speed against strict auditability, I don't split the difference. I lay out what each path costs and ask the people with authority to rank them. Everyone agrees everything matters. It takes a room to find out what they'd give up first, and that answer is the most useful thing I learn in the first month. The exercise I keep going back to is a half-day scenario workshop with business and engineering together. We write three to five concrete scenarios, each with a trigger and an expected response. For example: a payer changes its submission format on a Friday, and we adapt within two business days without a production redeploy. Then people force-rank them and say out loud what they'd sacrifice for the top one. It gets uncomfortable around the middle of the list, which usually means it's working. I finish with a one-page priority statement: the ranked outcomes, the explicit non-goals, and which constraints are fixed versus negotiable. I keep it short so people actually read it. About six months into one engagement, a team proposed a costly real-time integration. Nobody had to argue taste. We held it against the page, saw it served the fifth-ranked goal, and parked it. It also took pressure off the sponsor, because changing the ranking now required a deliberate, recorded decision instead of a hallway conversation. After twenty years, I think much of this job is agreeing early, in writing, on what we won't optimize for. That conversation costs far less than the redesign it prevents. *— [Harshil Lodhiya](https://www.linkedin.com/in/harshil-lodhiya-8419b813), Chief Software Architect, SlicedHealth* --- ### Picture the Guest’s First Ten Seconds The briefs that land on my desk usually say the same five things: timeless, unique, durable, easy to maintain, and "not like the hotel down the road." That's a wish list, not a priority. What turns it into one is a question I ask in the first meeting: describe the ten seconds after someone walks through the front door. What do they notice first, and what should they feel? People who have spent months unable to agree on a brief usually answer that in about thirty seconds. And once a client tells me "I want the floor to feel like it was always part of the building," every later argument gets shorter — each option either serves that moment or it doesn't. The conversation that has saved me the most grief is even simpler. Early on, we sort every decision into two piles: things you can change later and things you can't. In my trade, the stone, the pattern geometry and the junctions sit firmly in the second pile, so those get settled first — drawn at full scale and signed off before anything is cut. Finishes and borders can wait. Teams that do this sorting in week one don't find themselves redrawing the foyer in month eight. *— [Wang Fei](https://www.linkedin.com/in/wang-fei-a8160743a/), Senior Technical Director, Art Inlay* --- ### Match Goals to Field Constraints I'm Philip Oloo, licensed California general contractor, AIA Associate, and founder of SPACIALISTS, an architectural visualization studio, plus co-founder and CEO of PlanCheckerPro. After 20+ years in the AEC industry, the exercise that consistently prevents confusion is forcing early prioritization against real constraints: I sit with the client and map every stated goal to budget, schedule, and constructability, then rank them and walk through the trade-offs out loud. What clients say they want first and what they actually protect in the field are often different, and that mismatch is cheapest to surface in week one, not after framing. When I built our plan review workflows, I applied the same principle to code compliance: every finding has to be anchored to a specific plan or code reference before it is treated as a priority, which stops opinion-driven churn from overriding documented constraints. My advice: document the ranked priorities, get sign-off, and treat every later change as a change order against that agreement, both in conversation and on paper. *— [Philip Oloo](https://www.linkedin.com/in/philipoloo/), Co-founder & CEO, PlanCheckerPro* --- ### Related Articles - [Getting Client Decisions to Stick in Architecture Projects](https://architecttoday.com/qa/getting-client-decisions-to-stick-in-architecture-projects) - [Aligning Architecture, Structure, and Systems Early to Avoid Rework](https://architecttoday.com/qa/aligning-architecture-structure-and-systems-early-to-avoid-rework) - [11 Essential Questions to Ask Commercial Clients at the Start of a Project](https://architecttoday.com/qa/11-essential-questions-to-ask-commercial-clients-at-the-start-of-a-project)