Giving and Receiving Feedback in Presentation Rehearsals at an Architecture Firm
Architecture firms rehearse before big interviews, but many rehearsals produce little improvement. The team runs through the slides, someone says it looks good, and the real problems surface in the room. The missing ingredient is usually feedback that is specific, structured, and delivered in a way the presenter can use. Presentation training for architects should teach the team how to give and receive that kind of feedback.
Decide What the Rehearsal Is For
A rehearsal can test timing, content, delivery, or handling of questions, and trying to test all four at once leads to vague comments. Before each run, name the focus. The first run might check the story and the time limit. The second might focus on handoffs between speakers. The third might be a full dress rehearsal with questions. Clear purposes help reviewers watch for the right things.
Use a Simple Feedback Format
A format that works well is to ask reviewers for one thing that worked, one thing that was unclear, and one suggestion. Limiting the number of comments forces reviewers to prioritize. It also makes the session feel constructive rather than critical. Write the comments down so the presenter does not have to rely on memory, and collect them on a shared page the team can refer to later.
Be Specific About Behavior
Comments such as be more confident are hard to act on. Better comments describe what the reviewer observed and what effect it had: you looked at the screen during the whole second section, so I lost the connection to your point. Training should include examples of vague and specific comments so reviewers learn the difference. Specific feedback is easier to hear because it concerns an action rather than a personality trait. A short checklist helps reviewers focus: opening clarity, eye contact, pace, use of visuals, and handling of questions. Reviewers can mark one or two items per run so the presenter receives focused input instead of a long list.
Make It Safe for Junior Staff to Speak
In many firms, junior team members hesitate to critique principals. Yet they are often the best proxy for the panel, because they are less familiar with the project and notice jargon and gaps. Ask the principal to invite their comments explicitly, and respond with thanks rather than defense. Over time this builds a habit of honesty that improves every pursuit.
Practice Receiving Feedback
Receiving feedback is a skill too. Presenters should listen without interrupting, take notes, and ask clarifying questions rather than explaining why they did something. A good practice is to wait until all feedback is delivered before responding. Principals who model this behavior set the tone for the whole team and make rehearsals more productive. One simple technique is to have the presenter repeat the main point of each comment back in their own words before moving on, which confirms understanding and slows the urge to defend.
Close the Loop
Feedback matters only if the presenter acts on it. At the end of each session, agree on the two or three changes to make before the next run. Start the next rehearsal by checking whether those changes were made and whether they helped. This habit turns rehearsal into a cycle of improvement instead of a repeated performance of the same flaws.
The Bottom Line
Architecture firms that treat feedback as a trained skill get more out of every rehearsal. Defining the purpose of each session, using a simple format, focusing on observed behavior, inviting junior voices, and following up on changes make presentations steadily better. The practice also strengthens the culture of the firm, since people learn to speak plainly with one another and to improve their work in the open, which benefits client meetings and design reviews as much as pursuit interviews.
