Curiosity Wins Shortlists. Technical Depth Does Not.

About This Series: BD, Proposals, and Building the Function That Wins - Post 3 of 11

I have watched technically excellent teams lose shortlist interviews to teams that were, objectively, less qualified on paper. It happens more than most firms want to admit.

The pattern is consistent: the losing team walked in with a comprehensive presentation, rehearsed answers, and deep command of the methodology. The winning team walked in prepared to listen.

Ernest Burden wrote extensively about the importance of the audience's perspective in architectural presentations. His argument was not that technical competence was unimportant. It was that technical competence is table stakes. What the audience is actually evaluating, particularly in a public sector context where the committee is often composed of non-technical stakeholders, is something harder to quantify: do these people understand what we are trying to do? Can we work with them?

The shortlist interview is not a test of your knowledge. It is a trust-building exercise with a time limit.

Here is what that means practically for interview preparation.

Spend serious time on the questions you will ask, not just the answers you will give. What do you know about this project that is not in the RFP? What is the client worried about that they did not write down? What has gone wrong on similar projects that you want to address proactively? The right questions signal something that rehearsed answers cannot: genuine engagement with the client's actual situation.

Open the interview with their project, not your portfolio. The instinct to lead with your greatest hits is understandable, but it sends a message: we are here to present ourselves. The teams that win lead with: here is what we understand about what you are trying to accomplish. That reordering changes the entire dynamic in the room.

Let the presentation breathe. The teams that leave white space in the agenda, that invite questions early rather than at the end, that visibly adapt based on where the committee is engaged, are the teams that feel like collaborators rather than vendors.

There is also a macro point here worth naming. As AI tools become increasingly capable of doing the technical lifting in design and delivery workflows, the differentiator in the room becomes the human one. The team that is genuinely curious about the client's problem, that listens with specificity and responds with relevance, has an advantage that no algorithm produces.

Curiosity is a competitive advantage. Train for it the same way you train for anything else: deliberately, with repetition, and with feedback.