#25 Moments When Architectural Perspectives for Meetings Are Useful vs. Not Useful
Will the discussion move forward, or will it expand? The turning point is the first 30 seconds.
Have you ever had this experience when showing architectural perspectives to a client during a sales meeting or in the early stages of design?
“It’s fine if we just confirm the direction today.”
A meeting that started with those words ends up becoming a series of detailed confirmations before you know it.
Conversely, there are times when, despite almost no explanation, they decide, “Okay, let’s move forward with this.”
That difference isn't just created by the level of completion of the perspective or the skill of the explanation.
In many cases, it happens because of the assumptions under which the architectural perspective for the meeting is presented.
Depending on how you present it, an architectural perspective for a meeting can either move the discussion forward or, conversely, increase the number of items that need to be confirmed.
Today, I will clearly organize the “moments when architectural perspectives are useful” and the “moments when they are not.”
Chapter 1. Moments when architectural perspectives are useful in meetings
First, let’s look at situations where they are functioning well.
When a meeting proceeds smoothly, architectural perspectives share several common features.
1. The order in which they are viewed is naturally determined
A perspective where the gaze moves naturally from the whole → volume → atmosphere, even without special instructions.
When such a perspective is present, the meeting proceeds quietly.
This is because everyone is naturally looking at the same place without having to decide “where to start talking first.”
Conversely, with a perspective where the eyes are drawn to the details from the start, the topic also tends to start from the details.
As a result, discussions that you originally wanted to postpone can end up coming to the forefront.
2. It is vaguely conveyed “what we want to decide today”
When a meeting perspective is functioning, the moment it is seen, an atmosphere like this is created:
“We are confirming the direction of this area today.”
Even without being explained in words, one naturally feels this from the composition and the amount of information.
This is not so much the perspective explaining things as it is a state of gently indicating the scope of the agenda.
3. What is finalized and what is not is intuitively understood
In meetings, drawing the line between “this is decided” and “this is still subject to change” is very important.
Well-utilized architectural perspectives convey this boundary even without explanation.
Conversely, if everything looks like a finished product, the discussion will proceed on the assumption that even the parts that haven't been decided yet are already settled.
That discrepancy leads to the trouble of corrections and explanations later, such as “But we hadn't decided that yet...” or “I thought we were moving forward with that as it was...”
Chapter 2. Moments when architectural perspectives become unhelpful
On the other hand, there are times when meetings become disorganized.
There are common patterns to this as well.
1. Starting with confirmation of details
The first words spoken are,
"Will this material change?"
"What are the actual dimensions here?"
Of course, confirmation itself is not a bad thing.
However, when those questions are concentrated at the beginning of a meeting, the overall direction tends to be pushed to the back burner.
As a result, after spending a lot of time, you end up back in a state of "So, what were we going to do overall?"
2. Being misunderstood as the final version
A perspective presented for meeting purposes is suddenly perceived as the "final image."
This also happens often.
It is not that anyone is at fault.
Because perspectives are visually powerful, they carry a sense of "finality" even if not intended.
As a result, explanations like "this part is still under adjustment..." increase later on.
3. The topic spreads too wide
Perspectives with a high volume of information give each viewer a different point of focus.
One person looks at the exterior, another looks at the materials, and another looks at the surrounding environment.
Everyone is correct, but the topic becomes scattered.
When you feel that a meeting perspective is not useful, it is often because you are in this state.
When an architectural perspective feels unhelpful, it is almost never because of the perspective itself.
In many cases,
"What is the meeting for deciding?"
"How far are we discussing today?"
the architectural perspective is placed right at the front without that premise being shared.
In other words, the problem is not the quality of the representation, but ratherhow the architectural perspective is used and how the meeting is conductedlies in that.
In the next chapter, while assuming scenarios where architectural perspectives for meetings are used, I will organize the flow for moving the discussion forward and phrases that can be used directly in practice.
Chapter 3. Flow and phrases for successfully conducting meetings using architectural perspectives
From here on, while assuming scenarios where architectural perspectives for meetings are used, I will organize the flow and useful lines that can be used directly in practice.
1. Before presenting the perspective (Most important)
👉First, grasp the flow of the meeting here
What to do
Here, you simply declare the 'goal for today'.
Do not guide their gaze yet.
Useful phrases
'Today's purpose is to confirm the direction, so we will set aside detailed specifications for now.'
'This perspective is for sharing the image. It is not a final decision.'
'I will proceed with the understanding that we are not discussing specifications today.'
* Your role is to state 'what we will not do today'
Set the 'premise' for viewing the perspective first.
Just by doing this, the client can prepare for 'what they should do now,' allowing them to choose how to interpret the architectural perspective and what kind of questions to ask.
2. Immediately after showing the perspective (The first 30 seconds)
👉Control the 'order of viewing' here
What to do
Do not go silent immediately
But do not over-explain either
Useful phrases
'For now, it is fine if you just look at the overall impression.'
'Please tell me your first impression without worrying about the details for now.'
'Please check if the volume of the building and space matches your image.'
Before going into details, keep their gaze on the whole.
Fixing 'what kind of meeting this is' in the first 30 seconds is the key to proceeding smoothly with subsequent questions and confirmations.
3. After the first response (Confirming the direction)
👉There are basically 3 patterns for a client's initial reaction
"This is good."
"It's more [something] than I thought."
"I'm concerned about this part."
Try not to panic and explain the fine details here.
Useful phrases
"Thank you. Regarding the overall direction, does this feel like it's on the right track?"
"Is what you're concerned about right now the atmosphere, or the specific shape?"
The initial reaction is an impression, not a conclusion.
Instead of taking it at face value, ask a question that converts it into a judgment of "whether or not to proceed" to move the meeting to the next stage.
Don't expand on the impressions, but use them to confirm the direction.
That is how to make the most of architectural perspectives for meetings.
④ When things are about to get into fine details
👉This is the most common turning point. The key here is to "prevent derailment."
What to do
Do not immediately respond to detailed critiques with explanations
Do not try to reach a conclusion on the spot
Only accept the fact that they are "concerned"
Useful phrases (for acknowledging)
"I have noted your concern about that point."
"Let's organize the points raised just now as items to be refined next time."
"Today is for confirming the direction, so let's look at that point again later."
Useful phrases (for giving meaning)
“The fact that specific details are coming up suggests that the overall picture is starting to come into view.”
“We have reached the stage where such concrete discussions are emerging.”
“It has become clear where we need to focus next.”
Focusing on small details does not necessarily mean that things are off-track.
As the overall direction becomes visible, questions like “How will this part turn out?” naturally arise.
This is because at the stage where one doesn't know where to look, the points to confirm don't even emerge yet.
Therefore, when detailed topics come up during a meeting, there is no need to treat them as a misalignment.
Accept them as a sign that the overall image is beginning to be conveyed and it is sufficient to organize them as material to be refined next.
⑤ When moving from the overall impression to the discussion of details
👉 This is not a brake, but a gear change.
Assuming the whole is visible, move the topic to the next stage.
What to do
Confirm once that the overall impression has been shared
Clearly indicate the flow of “looking at the details from here on”
Organize the points of discussion instead of answering immediately
Useful phrases (for switching)
“The overall impression seems largely fine, so let’s look at the points of concern one by one.”
“I think we have shared the direction, so it seems fine to move on to specific discussions from here.”
“After looking at the whole, please tell me the parts you are concerned about.”
Useful phrases (for traffic control)
“What is being brought up now is about this area.”
“Let’s confirm that point together later.”
It is fine to bring up all the points you are concerned about at once.
Once the overall impression is shared, the next phase is to look at the details.
By simply putting this transition into words, the meeting changes from a state of "vaguely entering into detailed talk" to a
meeting that proceeds in stages.
⑥ When concluding a meeting (confirming decisions)
👉 What you do at the end of a meeting is not to "end the conversation," but to "align the status."
At this point,
it is not necessary for everything to be decided.
However, what has been decided and what has been carried over to the next time must be put into words.
There are three points to organize at the end
What was agreed upon as a direction in today's meeting
What was intentionally not decided today
Points to confirm/consider next time
Useful phrases
"It seems safe to understand that we are proceeding with this plan as the overall direction for today."
"Let's confirm the XX and XX that came up in the details again next time."
"I will proceed with the understanding that we are aligning the direction today and will finalize the specifics next time."
These phrases are not for adding new explanations.
They are words to fix the shared understanding on the spot.
If there is a common understanding at the end that "this much was decided today" and "this and that are for next time," the perspective changes from an image for consideration to a tool for confirming decisions from that moment on.
Concluding a meeting does not mean cutting off the topic.
It means aligning the status and handing it over to the next step.
That is the way to conclude a meeting to make full use of architectural perspectives until the end.
Summary | Where to use architectural perspectives for meetings
Architectural perspectives for meetings are not just simple materials for explaining things well.
Align the order of viewing
Turn impressions into decisions
Switch the stage of the discussion
Finally, put what has been decided into words
These are tools to support that flow.
Even without changing the perspective itself, the quality of the meeting can change significantly just by changing how you proceed and what you say.
When showing architectural perspectives during the design phase, the finish or level of completion may not be satisfactory.
Even in such cases, by following an orderly flow, it helps to clarify "what you want to show," "what you want to convey," and "what you want to decide" with this perspective today.
Explanations decrease, decisions move forward, and "what to do next" becomes naturally visible.
Architectural perspectives for meetings are not for showing, but for aligning decisions.
When used in that way, the perspective becomes more than just "study material"; it becomes a reliable tool that moves decisions forward.
📌 In this note, I share practical know-how for architectural visualization production and tips for smoothing out ordering and progress.
I update twice a week with articles from a field perspective that are useful not only for architectural perspectives and CG production, but also for those involved in "work that conveys space," such as design and planning.
If you are interested, please follow and check them out.
GRUND Inc.
With the concept of "I want this person to create it," we are the [only] juried CG studio in Japan specializing in architectural visualization.
We deliver the intent and atmosphere of architecture as a beautiful single visual.
We create the best encounters between visualizers who possess both technology and sensibility, and clients who seek serious visuals.
Consultations are free. Please feel free to contact us.