Built around people

Posted on by

In a recent post, I wrote about the importance of building infrastructure around the needs of students, keeping things clear, consistent, and supportive of how they navigate their learning. That piece focused on their experience: whether they can find what they need, understand expectations, and feel confident in the structure around them.

Institutions aren’t defined only by the experience of students. They’re shaped just as much by the people who design, teach, support, and maintain the work behind the scenes. This post takes the same principle and turns it inward. If we build the learning environment and experience around students, we should design our internal processes around staff in the same way.

When you focus on the detail of, for example, institutional-level projects, it’s easy to think about the mechanics: governance papers, risk logs, reporting cycles, templates, committees, integrations, and timelines. All of these are essential, but none of them are what staff experience day to day. For them, the institution is judged on something far simpler:

  • Can I do my work without unnecessary friction?
  • Do I understand what’s changing and why?
  • Is support available if/when I need it?
  • Is the cognitive load between teams fair and manageable?

If those answers aren’t clear, it doesn’t matter how polished the strategy presentation looks.

This is why people need to be designed into the work itself, not bolted on afterwards. Workflows, communication, leadership behaviours, and decision-making processes are all ‘design’ questions. They belong in planning just as much as the technical or operational components.

A people-centred institution will aim to:

  • Reduce friction: remove duplicated tasks and unnecessary complexity.
  • Protect capacity: recognise workload limits and avoid overlapping initiatives.
  • Embed clarity: ensure expectations, timelines, and decisions are transparent.
  • Connect purpose: link changes to the lived experience of the staff affected.
  • Support autonomy: trust teams to shape how they work within clear frameworks.

These principles matter because people make the organisation work. Strategy succeeds or fails in the space between meetings, in the daily routines that either help or hinder staff as they try to do their jobs well.

I’ve talked before about the importance of building environments around students. The same is true for the people who teach, support, design, and lead. When the institutional structure respects their time, understands their reality, and supports their growth, the whole organisation benefits.

Processes and technologies should sit in the background, supporting the day to day operation of the team and organisation. What matters is whether they help people feel clear, capable, and connected, able to focus on meaningful work rather than navigating avoidable complexity.

A new workflow or strategy refresh is never just an operational exercise. Done well, it makes the working culture clearer, fairer, and more humane. That has to be a deliberate choice from the start.

Photo by Se. Tsuchiya on Unsplash