Topic 7.5 — People & Organizational Development

In one sentence: People and organizational development is the deliberate work of growing your people's capability and confidence and reshaping the organization's culture, leadership, and ways of working so that digital change becomes something the organization is able to sustain rather than merely survive.

Why this matters in health and care#

You can buy technology and you can hire staff, but you cannot buy a learning culture, psychological safety, or digital confidence — you have to develop them. Most digital transformations fail not on the technology but on the human system around it: staff who fear the change, leaders who cannot model new behaviours, and an organization with no muscle for continuous learning.

In health and care this is acute. The Topol Review concluded that preparing the workforce for a digital future would require sustained effort at every level, and that the binding constraint is a digitally ready workforce — engaged, skilled, and confident — not the availability of technology itself. Meanwhile the evidence is strong that team climate directly affects patient safety: psychological safety and compassionate leadership are associated with staff speaking up about risk, learning from error, and better outcomes.

People and OD is also where equity is won or lost. Digital transformation can widen or narrow inequalities among staff and, through them, among patients. Investing in inclusive development, digital literacy, and fair access to opportunity is both a statutory expectation (the NHS People Promise, the Public Sector Equality Duty) and a practical condition for change to stick. This topic is the human counterpart to Workforce Planning (see Topic 7.2) and the enabler of Change Management (see Topic 8.1).

Core concepts#

Learning organisation and learning culture. An organization that continuously improves by enabling its people to learn — where reflection, experimentation, and knowledge-sharing are normal, expected, and rewarded, rather than squeezed out by operational pressure.

Continuing professional development (CPD). The structured, ongoing development of skills and knowledge across a career. In digital health this must cover both the deepening of professional expertise and the broadening of digital and data literacy across all staff.

Communities of practice. Groups who share a craft or domain — user researchers, clinical safety officers, information governance leads — and meet across team and organizational boundaries to develop standards, share learning, and reduce isolation. They are how expertise spreads in a federated system.

Psychological safety. A shared belief, defined by Amy Edmondson, that a team is safe for interpersonal risk-taking — that you can ask a question, admit a mistake, or raise a concern without fear of humiliation or punishment. It is the precondition for both safety-critical candour and the experimentation digital work depends on.

Compassionate and inclusive leadership. The leadership model at the heart of the NHS People Promise and Our Leadership Way: leaders who attend, understand, empathize, and act, and who create cultures where all staff feel they belong. Its explicit purpose is to build effective teams and psychologically safe cultures.

Talent management and succession. The systematic identification and development of people for future critical roles, so the organization is not left exposed when a key individual leaves — especially important where digital expertise is scarce.

Organisational development (OD) interventions. Planned, evidence-based efforts to improve an organization's health and effectiveness — culture change, team development, leadership development, and structural or process redesign.

Best practices#

1. Build learning into the working week, not the annual appraisal. Protect time for development, reflection, and experimentation as a normal part of delivery. A learning culture that exists only in a once-a-year form is not a learning culture; capacity to learn must be designed into how teams work.

2. Make digital literacy a whole-workforce programme, not an IT topic. Following the Topol Review, treat digital and data capability as something every role needs at an appropriate level — clinical, operational, managerial — using the NHS Digital Readiness resources and structured self-assessment. The goal is confidence and engagement, not just tool training.

3. Develop compassionate and inclusive leaders deliberately. Leadership behaviour sets the team climate that determines whether people speak up. Invest in leadership development aligned to the NHS People Promise and Our Leadership Way, and hold leaders accountable for the culture they create, not only the targets they hit.

4. Cultivate psychological safety as a safety-critical asset. Actively build teams where questions, dissent, and error-reporting are welcomed — through how leaders respond to bad news, how mistakes are handled, and how concerns are followed up. In a clinical-digital context, silence about risk is the failure mode you most need to prevent.

5. Stand up communities of practice across boundaries. Give each discipline (research, design, clinical safety, data, engineering) a cross-team community with time, sponsorship, and a remit to set standards and share learning. This spreads scarce expertise (complementing the enabling-team pattern in Topic 7.0) and reduces the isolation of lone specialists.

6. Use coaching and mentoring to grow people, not just direct them. Embed coaching as a leadership habit and offer mentoring for those moving into digital and leadership roles. Coaching builds the autonomy and problem-solving capacity that self-organizing delivery teams need.

7. Manage talent and succession for scarce digital roles. Identify critical roles and the people who could grow into them, and develop them ahead of need. Given the digital labour shortage (Topic 7.2), losing a key architect or Clinical Safety Officer with no successor is an avoidable, self-inflicted risk.

8. Treat equality, diversity, and inclusion as integral, not adjacent. Make development opportunities, recruitment, and progression demonstrably fair, and pay attention to who is and is not getting digital opportunities. Inclusion is both a duty and a driver of the diverse thinking that safe, usable services require.

9. Run OD interventions with evidence and evaluation. Approach culture and behaviour change as you would any intervention: diagnose the current state, choose an evidence-based approach, and evaluate whether it worked. Culture-change initiatives that are asserted rather than measured tend to fade with the away-day that launched them.

Questions to discuss with your team#

1. Is it genuinely safe on our teams to admit a mistake or raise a concern about a new system — and how would we actually know? Psychological safety is not a soft nicety in a clinical-digital context; the evidence links team climate directly to patient safety, because staff who fear humiliation or blame stay silent about the near-misses and usability problems that are the earliest signals of risk. The hard part of this conversation is that almost everyone believes their own team is safe, so the useful question is evidential rather than aspirational: what would you expect to see if it were true, and do you see it? A telling and counter-intuitive signal is reported near-misses rising rather than falling when a new record goes live — because reporting finally feels safe — so a suspiciously quiet incident log may be a warning, not reassurance. Debate how your leaders actually respond when they hear bad news about a system they championed: do they act on it visibly, or defend the system and subtly punish the messenger? Consider too that safety varies team by team and manager by manager, so a single organizational average can hide real cold spots. An honest answer moves past "of course we're safe" to concrete evidence — how mistakes were handled last month, whether concerns were followed up, what happened to the last person who raised an awkward problem.

2. Is our digital-literacy investment reaching the anxious and the late adopters, or flowing to the already-confident and quietly widening the gap? The Topol Review's core conclusion is that the binding constraint on digital transformation is a digitally ready workforce, not the technology, and readiness means confidence and engagement across every role — yet development effort has a natural tendency to reach the people who seek it out, who are usually the ones who need it least. This matters beyond fairness: People and OD is where equity is won or lost, and inequitable uplift among staff translates, through them, into inequitable services for patients, which also engages the Public Sector Equality Duty. The trade-off to debate is that supporting the anxious and the resistant is slower, more resource-intensive, and less visibly rewarding than showcasing your champions, so it is exactly the work that gets squeezed under operational pressure. Look honestly at who has actually taken up your digital-readiness support and who has not, and whether you have protected time for the people who learn slowly rather than only for the enthusiasts. A good answer can point to how it reaches late adopters specifically, treats digital literacy as a whole-workforce programme rather than an IT topic, and monitors uptake by staff group so widening gaps are caught rather than assumed away.

3. When we say we are changing the culture, are we doing evidence-based OD — or launching an away-day and hoping? Culture-change-by-away-day is a recognized failure mode precisely because it feels like action: a launch event, a poster campaign, a leadership framework published, and then nothing sustained or measured, so the initiative fades within months of the event that launched it. The deeper tension is that culture follows what leaders do, not what strategies assert, which makes the uncomfortable question whether your leaders' own behaviour and the climate they create are part of the intervention or conveniently exempt from it. Treating OD as you would any clinical intervention — diagnose the current state, choose an evidence-based approach, and evaluate whether it actually worked — is the discipline that separates real change from theatre, but it requires agreeing measures of behaviour change rather than measures of activity. Debate what you would count as evidence that a culture initiative succeeded: attendance at training and a signed-off strategy are outputs, whereas staff confidence, reported near-misses, adoption, and observed leadership behaviour are impact. Consider a past initiative honestly and ask whether it was ever evaluated at all, or simply assumed to have worked because it was launched. A strong answer commits to diagnosing before intervening, names impact measures rather than output measures, and refuses to exempt leadership behaviour from the change it asks of everyone else.

4. When operational pressure spikes, is protected learning time the first thing we sacrifice — and what does that tell us about whether we truly value development? A learning culture is built into how teams work or it does not exist, yet development, reflection, and experimentation are precisely the activities that feel optional when the rota is short and the waiting list is growing. The revealing question is not whether you have a training budget but what actually happens to protected time on a bad week: if it is quietly cancelled first and every time, then in practice you have decided that learning is a luxury, whatever the strategy says. The genuine tension here is real and not to be waved away — patient-facing operational demand is a legitimate and often safety-critical claim on the same hours, so this is a hard prioritization, not a straw man. The trap is that treating development as the permanent shock-absorber for operational pressure guarantees that skills and confidence decay, staff revert to workarounds, and the organization loses its capacity to absorb the next change. Discuss who actually loses their learning time when things get tight — is it shared, or does it always fall on the same frontline groups who most need to build digital confidence? An honest answer looks at the last few months of cancelled sessions rather than the policy, acknowledges the real trade-off with operational demand, and names what the organization is willing to protect even under pressure.

5. If one of our two hardest-to-replace digital specialists left next month, would their knowledge walk out with them — and what have we done to spread it while we still can? Digital expertise is scarce, and a lone specialist — a key architect, a Clinical Safety Officer, an information-governance lead — is often genuinely alone, so their departure is an avoidable, self-inflicted risk rather than bad luck. The uncomfortable part of this conversation is that the people most critical to keep are usually the busiest, which makes investing their time in succession, documentation, and communities of practice feel like a cost you cannot afford right up until the moment you cannot afford not to have. There is a real trade-off to name: time a specialist spends mentoring a successor or writing down tacit knowledge is time not spent shipping, and under delivery pressure that trade is easy to defer indefinitely. Communities of practice are part of the answer because they spread scarce expertise across boundaries and reduce the isolation that drives burnout and single-person knowledge loss. Consider concretely who could step into each critical role today, who is being actively developed to do so tomorrow, and whether any of your specialists are one resignation away from leaving a hole no one can fill. A strong answer identifies the specific roles where you are exposed, shows real successors in active development rather than named on a chart, and treats knowledge-spreading as ongoing work rather than an exit-interview scramble.

6. Are we coaching people to grow their own judgement, or just training them to follow the new system's steps? Self-organizing delivery teams and confident frontline staff need autonomy and problem-solving capacity, not just the ability to click through a workflow, and the difference between coaching and instruction is the difference between people who can adapt when the system behaves unexpectedly and people who freeze or work around it. This matters in a digital-health setting because a member of staff who understands why a safety check exists will protect the patient when the software does something odd, whereas one who has only memorized the steps may not. The tension is that directing and tool-training are faster and feel more controllable, while coaching is slower, harder to measure, and asks leaders to tolerate people reaching their own answers — which is uncomfortable under time and safety pressure. There is also a genuine question of where autonomy is appropriate: some clinical-digital tasks demand strict adherence to protocol, so this is about growing judgement within safe boundaries, not licence to improvise everywhere. Debate whether your managers actually coach or simply instruct, and whether people moving into digital and leadership roles get mentoring that builds their independence or supervision that keeps them dependent. An honest answer distinguishes where standardization is essential from where judgement should grow, and points to coaching and mentoring as deliberate habits rather than occasional favours.

In practice: a health & care example#

A community health and social care provider is deploying a new electronic patient record and expanding remote monitoring — a change that lands hardest on people, not servers.

Rather than run tool-training alone, the OD and digital teams design a people programme. Every staff group completes a digital-readiness self-assessment based on the Topol/NHS Digital Readiness materials, and tailored digital-literacy support is offered from confident champions down to anxious late adopters — with protected time to learn. Communities of practice are established for digital champions and for clinical safety leads across sites, meeting monthly to share what works and to set shared standards. Frontline and middle managers go through a compassionate leadership development strand, because the programme team recognizes that whether staff raise problems with the new system depends on how their manager responds when they do.

Psychological safety is made explicit: teams are encouraged to report near-misses and usability problems with the new record, and leaders visibly act on what they hear rather than defending the system. Coaching supports several nurses moving into new remote-monitoring roles, and a succession plan is drawn up for the two hardest-to-replace digital roles. Progress is evaluated not by attendance at training but by staff confidence surveys, reported near-misses (rising, as intended, because reporting feels safe), and adoption. When a ward struggles, the response is coaching and community support, not blame — and adoption there recovers.

Sector lenses#

Startup#

In a startup, "organizational development" is culture-setting by the founders, not a formal OD function — the habits established in the first dozen hires become the culture, for good or ill. Psychological safety is easy to achieve when everyone shares a room but fragile under funding pressure, and there is rarely protected learning time or a CPD budget, so development happens on the job. There is no succession plan and no community of practice; a lone specialist is genuinely alone, which makes burnout and single-person knowledge loss the acute risks. The winning move is to bake learning and candour into rituals early — blameless retrospectives, an explicit "it is safe to raise problems" — while it is cheap, because retrofitting culture into a scaled company is far harder.

Small business#

An established small provider — a GP practice, a community pharmacy, a care home or domiciliary-care agency, a single-site clinic, or a small health-tech supplier past the pre-revenue stage — has real patients and staff but rarely any dedicated OD, learning, or digital-training function, so development lands on an already-stretched manager or owner alongside everything else. It must meet the same duties as a large trust — the Public Sector Equality Duty, fair development opportunities, safe reporting cultures — without the budgets, protected learning time, or leadership-development programmes an enterprise takes for granted. Psychological safety is shaped almost entirely by one or two visible leaders, which is a strength when they model candour and a serious risk when they do not, because there is no wider system to dilute a blame culture. Digital-literacy uplift has to be pragmatic and low-cost: making use of free NHS Digital Readiness materials, learning during quiet clinic hours, and leaning on external communities of practice and peer networks (a Primary Care Network, a pharmacy association) rather than building internal ones. Succession is acute, since a single departing person may hold all the digital knowledge and cover is thin, so cross-training even one colleague and writing down the essentials matters more here than any formal talent pipeline. The realistic move is to protect small, regular pockets of learning and to be deliberate about candour and knowledge-sharing, because the organization has no slack to absorb either skills decay or a sudden loss of expertise.

Enterprise#

A large trust or health-tech firm has dedicated OD, learning, and leadership-development functions but fights scale and inertia: a learning culture must be sustained across thousands of staff and many sites, against relentless operational pressure. Communities of practice, talent-management pipelines, and structured succession for scarce digital roles become formal, sponsored, budgeted programmes. The hard part is consistency — psychological safety and compassionate leadership vary team by team and manager by manager — so the enterprise must develop leaders deliberately and hold them accountable for the climate they create, not only the targets they hit. Whole-workforce digital-literacy uplift (Topol) is itself a major, multi-year OD programme.

Government#

A national body shapes the people-and-OD agenda for the whole system: the NHS People Promise, Our Leadership Way, the Topol Review, and NHS Digital Readiness are national instruments that individual trusts then implement. Its levers are frameworks, funding, and standards rather than direct line-management of the affected staff, so success depends on adoption it cannot mandate. Accountability runs to ministers and the public, and equity duties (the Public Sector Equality Duty) make inclusive development a statutory obligation, not a nicety. The characteristic risk is that culture change is asserted through a published strategy or a leadership framework yet never lands as changed behaviour on the ground — so national OD work must be evaluated for real-world impact, not output.

Common failure modes#

• Training as a substitute for development. One-off tool training with no ongoing learning culture; skills and confidence decay and staff revert to workarounds.
• Culture change by away-day. A launch event and a poster campaign with no sustained intervention or evaluation; the initiative fades within months.
• Leadership exemption. Expecting frontline staff to change while leaders' behaviour — and the climate it creates — stays the same. Culture follows what leaders do.
• Fear-driven silence. No psychological safety, so staff hide problems with new systems; risks surface only as incidents.
• Lone-specialist isolation. Scarce experts with no community of practice, no succession, and no development path — who then burn out or leave.
• Inequitable uplift. Digital-literacy investment reaching the already-confident and missing the anxious, widening rather than narrowing gaps.

Maturity model#

Checklist#

• Development and reflection time is protected within the working week.
• Digital literacy is a whole-workforce programme with role-based self-assessment (Topol / NHS Digital Readiness).
• Leadership development aligned to compassionate/inclusive leadership and the NHS People Promise is in place.
• Leaders are held accountable for team climate and psychological safety, not only targets.
• Cross-boundary communities of practice exist for key disciplines, with time and sponsorship.
• Coaching and mentoring support staff moving into digital and leadership roles.
• Critical scarce roles have identified successors in active development.
• Development opportunities are demonstrably equitable, with EDI monitored.
• OD and culture interventions are diagnosed, evidence-based, and evaluated for impact.
• People & OD work is joined up with Workforce Planning (Topic 7.2) and Change Management (Topic 8.1).

Key sources#

• The Topol Review (2019) — Preparing the healthcare workforce to deliver the digital future; and NHS England Digital Readiness / Building a Digitally Ready Workforce
• NHS England — We are the NHS: People Plan and the NHS People Promise
• NHS Leadership Academy — Our Leadership Way; and NHS England on compassionate and inclusive leadership
• NHS Employers — Teamworking, psychological safety and compassionate leadership
• Amy C. Edmondson — The Fearless Organization (psychological safety)
• Michael West — compassionate leadership and team effectiveness in health and care
• CIPD — learning cultures, CPD, coaching, and talent management guidance

References#

1. Psychological safety — Wikipedia — https://en.wikipedia.org/wiki/Psychological_safety
2. Amy Edmondson — Wikipedia — https://en.wikipedia.org/wiki/Amy_Edmondson
3. Learning organization — Wikipedia — https://en.wikipedia.org/wiki/Learning_organization
4. Community of practice — Wikipedia — https://en.wikipedia.org/wiki/Community_of_practice
5. Professional development (continuing professional development) — Wikipedia — https://en.wikipedia.org/wiki/Professional_development
6. Compassionate leadership — Wikipedia — https://en.wikipedia.org/wiki/Compassionate_leadership
7. Talent management — Wikipedia — https://en.wikipedia.org/wiki/Talent_management
8. Succession planning — Wikipedia — https://en.wikipedia.org/wiki/Succession_planning
9. Organization development — Wikipedia — https://en.wikipedia.org/wiki/Organization_development
10. Mentorship — Wikipedia — https://en.wikipedia.org/wiki/Mentorship
11. Coaching — Wikipedia — https://en.wikipedia.org/wiki/Coaching
12. The Topol Review: Preparing the healthcare workforce to deliver the digital future (2019) — Health Education England — https://topol.hee.nhs.uk
13. We are the NHS: People Plan and the NHS People Promise — NHS England — https://www.england.nhs.uk/ournhspeople/
14. The Fearless Organization — Amy C. Edmondson — https://fearlessorganization.com
15. Compassionate and inclusive leadership — Michael West / The King's Fund — https://www.kingsfund.org.uk

See also Topic 7.0 — Team Structures, Roles & Responsibilities, Topic 7.2 — Workforce Planning, Topic 7.3 — Workforce Strategy, and Topic 8.1 — Change Management.