top of page

Five Trends in Technical Leadership, and What They Mean for Practice Leaders

Writer: Ryan Gorman
Ryan Gorman
3 days ago
6 min read

Earlier this year, as part of a retained search for a Technical Director, I carried out in-depth competency assessments with 13 technical directors and leaders from across the industry. They came from a wide range of practices, from global design-led studios and large multidisciplinary consultancies to delivery-focused firms and growing independents.


The conversations covered technical governance, quality assurance, risk and leadership. Everyone I spoke with was remarkably candid about what works and what does not in their own organisations. That openness was given in confidence, so this piece does not describe any individual, practice or project. Instead, it draws out the patterns that came up again and again.


Those patterns say a great deal about where the industry is. For anyone running a practice, they also point to some practical lessons. Here are the five trends that stood out most clearly.


1. QA rarely fails because of the process. It fails because of time.


Very few of the leaders I spoke with described a practice without a quality process. Most described sound, well-documented ones, with clear stages for drawing, checking, reviewing and authorising information. The principle was rarely the problem.


The problem was time. Again and again, the same pattern emerged: deadlines set too close to issue, teams working late to hit them, and the review quietly dropped in the rush to get information out. In many studios, the late-night push to meet a deadline is still quietly celebrated, even though it is often the very thing that removed the check.


The leaders who had solved this did so with simple, deliberate habits. They set internal deadlines well ahead of the issue date and protected the time in between for review. They were also comfortable telling a client that information would arrive a day later, properly checked, rather than on time and unchecked.


For practice leaders:


  • Treat review time as part of the programme, not something squeezed in at the end.

  • Look at what your culture rewards. If heroic deadlines are praised and missed checks go unnoticed, people will act accordingly.

  • Give project leads explicit permission to delay an issue to protect quality.


2. Bolted-on QA gets ignored. Embedded QA sticks.


The second trend concerned where quality systems come from, and whether they fit the practice they serve.


Several leaders had experienced quality systems written to satisfy an accreditation or an auditor, but with little connection to how projects were actually run. These systems tended to sit outside the work, owned by one person and treated as a box to tick. Unsurprisingly, people worked around them.


The systems that worked were the opposite. They were built around the way the studio already operated, refined rather than imposed, and maintained by the teams who used them. They were seen as part of the design process rather than a constraint on it, so design leaders did not feel quality checks were getting in the way of their vision.


A related point came up in larger practices with several studios or offices. Where each studio had developed its own way of doing things, knowledge stayed local and standards varied. The answer was not a heavier rulebook, but a common framework that every studio could see the value in.


For practice leaders:


  • Ask whether your quality system reflects how your teams really work, or how someone thought they should.

  • Involve the people who use the system in shaping it.

  • In multi-studio practices, look for shared standards that travel, rather than parallel systems that compete.


3. The best technical leaders persuade rather than enforce


The assessment asked how quality standards are enforced. Many of the strongest leaders I spoke with challenged the word itself. Enforcement, they pointed out, implies that people do not know what they are doing, which is rarely the case.


Their preferred approach was to bring people with them: explaining why a standard exists, showing the benefit of following it, and using real-world consequences to make the risks tangible. Leading from behind and nudging teams in the right direction came up far more often than leading from the front.


There was also a clear shared view on what to do when something goes wrong. The first question should be about the system, not the individual. Did the person have enough time, the right knowledge and enough context about the decisions behind the work? Blame might feel decisive, but it rarely fixes the underlying cause.


That does not mean an absence of accountability. Several leaders made a point of involving people in client and coordination conversations, so they understood the consequences of their work and the context for it.


Perhaps most telling, many pointed upwards rather than downwards. QA tends to break down when reviewers lack the experience to spot what is missing, or when senior leadership on a project is stretched or absent. Securing buy-in from directors was described as a bigger challenge than securing compliance from junior staff.


For practice leaders:


  • When a check is missed, look at the conditions around it before the person who missed it.

  • Make sure reviewers have the seniority and time to review properly.

  • Remember that director-level behaviour sets the standard. If senior people skip the process, everyone else will too


4. Risk now lives at the edge of design responsibility


When the conversations turned to technical and contractual risk, the projects varied widely, but the underlying lesson was remarkably consistent: know exactly where your responsibility starts and stops, and make sure it is written down.


A recurring source of exposure was practices drawing or specifying elements that sat outside their appointment, often with good intentions, and in doing so taking on liability they were never contracted for. The leaders who managed risk well tackled this at the outset, defining scope, deliverables and what counts as a change clearly in the contract, before pressure built up later in the project.


The Building Safety Act was a constant presence. It is visibly reshaping the technical leader's role. Several described clients trying to pass duties that legislation assigns to them onto the architect, sometimes as a condition of appointment, and sometimes outside the cover of professional indemnity insurance. Others described growing scrutiny of products being used in configurations they had not been tested for, and of systems that met the letter of a test but raised wider safety concerns.


What stood out was a willingness to hold the line. The strongest leaders were prepared to challenge clients and contractors firmly, back their position with evidence, and record their advice in writing when it was not followed. Equally, they were clear that a firm disagreement on one project need not damage a relationship for good. Construction is a small industry, and how a dispute is handled is remembered.


For practice leaders:


  • Make sure someone senior reads every contract properly before work starts, not after problems emerge.

  • Check that teams understand the design responsibility matrix and work within it.

  • Ensure your practice has the confidence, and the backing from leadership, to push back on duties that are not yours to carry.


5. Experienced technical leaders are hitting a ceiling


The final trend emerged when I asked each person what would motivate a move. Their circumstances differed, but a clear pattern appeared.


In many organisations, the route to the top for technical leaders runs out. Beyond a certain level, progression means moving into general or executive management and leaving behind the technical expertise that made them valuable in the first place. In smaller practices, the issue looks different but has a similar effect: the most experienced technical person becomes the go-to for every question and every problem, with little time left for strategic work.


What these leaders wanted was consistent. They were looking for a role where technical expertise is treated as a strategic asset, with real influence over how a practice operates, rather than a reward for good delivery that gradually pulls them away from it.


Many practices have a well-defined path for design leaders and for commercial or operational leaders. Far fewer have an equivalent route for technical leaders. As regulation becomes more demanding, that gap is becoming harder to justify.


For practice leaders:


  • Ask whether your best technical people can see a route to senior leadership that does not require them to stop being technical.

  • Protect strategic time for technical leaders, rather than letting them become the practice's permanent help desk.

  • Consider whether technical leadership has a voice at board level.


The bigger picture


Taken together, these trends point to a shift in what technical leadership in architecture really involves.


Technical knowledge remains essential, and every leader I assessed had it in depth. But it was not what distinguished the strongest. What set them apart was how they thought about people, culture and time: protecting the programme for review, building systems that fit how a studio actually works, bringing colleagues with them, and having the confidence to say no when the risk is not right. 


For many practices, the gap is not a lack of procedures. It is the absence of someone with the standing and the skills to make existing procedures work, and to influence directors as well as technical teams.


That is a leadership role, not a checking role. The practices that recognise this, and give their technical leaders a genuine seat at the table, will be in a far stronger position to manage risk, protect quality, and attract and keep the best people in the field.

 
 

Our Vacancies

Explore our latest opportunities across architecture and interior design. From emerging talent to senior leadership, we connect exceptional individuals with practices where they can make a lasting impact.

bottom of page