The Director's CV: Stop Describing Buildings, Start Describing Leadership

A few weeks ago, I reviewed the CV of an Architectural Director who had held his leadership role for fifteen years.
On first reading, it was perfectly competent. It told me a great deal about the buildings he had worked on. It told me remarkably little about the leader.
I have known him for six years, and I know how impressive he is. He runs a studio of more than 150 people, is trusted by the practice's most important clients, and is closely involved in shaping the direction of the business.
Yet none of that was immediately apparent from the document in front of me. Read cold, it could have belonged to an experienced Project Architect. Fifteen years of senior leadership had been reduced to a portfolio of schemes.
This is not an isolated case. In my experience, it is the most common issue I see when Directors in architecture and design begin to consider their next move.
The most common mistake
The pattern is remarkably consistent: a job title, followed by a long list of projects.
There is a good reason it happens. For most of an architect's career, this is exactly the right approach. Early on, a CV should focus on projects and technical delivery, because that is the work being assessed. The habit forms, and it rarely gets revisited.
The difficulty is that the role changes long before the CV does. A list of projects is an excellent summary of a Project Architect's contribution. It is a poor summary of what a Director does. It describes the output of the studio, not the leadership that made that output possible.
The question every Director should ask of their CV is simple: does this really summarise what I do?
There is no such thing as a generic Director
One of the reasons project lists fall short is that they flatten important differences. In architecture, the title "Director" covers a wide range of people with very different strengths. Among them:
Work winners, who generate new opportunities and convert them into fee income
Relationship builders, who hold and grow the practice's most valuable client relationships
Project leaders, who take responsibility for complex schemes from inception to completion
Finance and compliance experts, who keep the business commercially sound and well governed
Design leaders, who set and protect the creative standard of the studio
Delivery directors, who ensure the practice delivers reliably, on programme and on budget
The list goes on. These are very different skill sets, and every one of them is valuable in the role. Most Directors are a blend of several, with one or two clear areas of strength.
Two Directors could have worked on an almost identical set of projects and still offer a practice entirely different things. A project list cannot tell them apart. A well-written CV can.
That is why I encourage Directors to spend more time defining what sort of Director they are, and the value they bring to a business, and less time listing projects.
Rewriting the story: how a Director actually operates
Returning to the Director I mentioned at the start, we did not discard his projects. We re-focused the CV around how he operated as a Director. Four themes did most of the work.
Where he was winning work. Securing new commissions is one of the clearest signals of seniority in a practice. We made it explicit which opportunities he had personally generated, pitched for and converted, rather than leaving the reader to assume he had simply been allocated them.
How he built and led teams. Leading a studio of more than 150 people is a significant leadership responsibility in its own right. We set out how he had structured, grown and developed his teams, and the kind of culture he had created.
How he balanced design oversight with commercial responsibility. This is one of the defining tensions of Director-level work in architecture. We showed how he maintained design quality across the studio while remaining accountable for the commercial performance of the work.
How he showed up for clients and influenced strategy. Being trusted by key clients, and having a voice in the direction of the practice, are what distinguish a Director from a senior project lead. We made both visible.
The result was a far clearer reflection of the role he was actually doing. Rather than presenting him as someone who had worked on good buildings, it positioned him as a leader who added value to a business.
If you list projects, explain why you mattered
None of this means projects have no place on a Director's CV. They remain valuable evidence. The point is that, at this level, the project itself is not the story. Your contribution to it is.
If you are going to list projects, focus on why you were great on them. For each one, ask yourself:
Did you win the work?
Did you lead the team?
Was it highly profitable?
Was there an interesting challenge that you overcame as a leader?
A shorter list of projects, each one demonstrating your leadership, will say far more than an exhaustive schedule of everything the studio has delivered under your name.
From what you have worked on to the value you add
Early in a career, a CV should absolutely focus on projects and technical delivery. At Director level, the emphasis changes.
It becomes less about what you have worked on, and more about how you can add value to a company. The practices hiring at this level are not simply looking for someone who has been around good buildings. They are looking for someone who will win work, lead people, protect quality and strengthen the business.
If your CV does not make that clear within the first page, it is underselling you. For many of the Directors I speak with, the leadership is there. It simply has not yet made it onto the page.
This is just one of the mistakes I see Directors make when beginning a job search. I will be exploring others in the weeks ahead.



