Culture Change in Social Housing
Two cultures becoming one - built around what customers and colleagues were both asking for
Two of London's largest housing associations becoming one - 66,000 homes, two distinct cultures, and the question of how to build something genuinely shared rather than one organisation absorbing the other.

Two housing associations merging into one culture
This case study explores an organisation-wide culture change against the backdrop of a significant merger - how we unified teams and leaders around a common language, shared ways of working and a singular focus on the residents and customers they serve.
When Peabody and Family Mosaic merged, the immediate focus was structural - combining departments, aligning systems, reorganising teams across 66,000 homes. But the harder question was cultural. How do you bring together two organisations with different ways of working, different relationships and different identities, and build something genuinely shared?
This case study explores an organisation-wide culture change against the backdrop of a significant merger - how we unified teams and leaders around a common language, shared ways of working and a singular focus on the residents and customers they serve.
If you're studying this as part of your Chartered Institute of Housing work and have questions, feel free to send me a message.
Reframing culture from what's on the wall to what's in the work
Culture can be a nebulous topic sometimes. It's simultaneously easy to spot, and much harder to articulate and influence. In our work, we tend to focus on three areas of organisational culture that take it from values on the wall to what it should looks like in day-to-day work;
- Shared principles - what are the ground rules that the whole organisations shares? The clear, practical guidelines that are important above all else, and you can apply to anything - from a board meeting to a call with a customer.
- Common practice - what are the agreed ways of working that everyone can share? The shared habits, approaches and practices that create unity without forcing uniformity.
- Enabling environment - what environment are leaders and managers creating to enable those principles and practices? The CIPD describe this as the organisational climate - the environment that should make your principles and practice easy to follow.
Organisational culture change through the uncertainty of a merger
A merger will naturally create greater complexity in developing culture. Aside from the practical and operational factors, they also bring uncertainty, and can impact staff as they find their feet, manage uncertainty and learn to work with new colleagues.
People lose things that don't show on an org chart - the informal networks they relied on, the rhythm and identity of their team, the shorthand that made daily work predictable. Everyone is already stretched by restructuring and uncertainty about their own role, which is exactly when people retreat to what's familiar rather than reaching toward something new.
For this reason, it was even more important to make sure everyone felt they were active participants in shaping the culture - not just passive recipients of a new set of values.
Our messaging focused heavily on a "best of both" approach - taking the best parts of each organisation and building something new from it. This gave people a chance to share what they valued, what mattered to them, and crucially, what mattered most to customers.
But it also gave permission to challenge what wasn't working. To share the frustrations, bottlenecks, silos and systems that prevented people delivering well. This took culture away from abstract values, and focused more on how work got done - and how we might change things for the better.
Culture change is a cultivation exercise, not a project to manage
When we work with leaders on organisational culture, one of the harder shift is to treat it less like a project and more like a garden to cultivate.
Organisational culture isn't delivered, it's something nurtured. It doesn't achieve sustainable results from creating a new set of values - it achieves them by those values being used, role-modelled and applied. And it's this cultivation of principles, practice and environment that needs on-going attention.
This can be where cynicism for culture change comes from - by treating it as a project with a start and end date. Culture doesn't shift the day a new culture is announced - it changes when those people can see those principles and practices applied on a Monday morning.
Changing organisational culture at scale
Culture change can be a nebulous topic sometimes. It's simultaneously easy to spot, and much harder to articulate and influence. In our work, we tend to focus on three areas of organisational culture that shift the emphasis from values on the wall to what it should look like in day-to-day work:
- Shared principles - what are the ground rules that the whole organisation shares? The clear, practical guidelines that matter above all else, and that you can apply to anything - from a board meeting to a call with a customer.
- Common practice - what are the agreed ways of working that everyone can share? The shared habits, approaches and practices that create unity without forcing uniformity.
- Enabling environment - what environment are leaders and managers creating to enable those principles and practices? The CIPD describe this as the organisational climate - the environment that should make your principles and practice easy to follow.
Organisational culture change through the uncertainty of a merger
A merger will naturally create greater complexity in developing culture. Aside from the practical and operational pressures, mergers also bring uncertainty, and affect staff as they find their feet, adjust to change and learn to work with new colleagues. This is true for any post-merger integration.
People also lose things that don't show on an org chart - the informal networks they relied on, the rhythm and identity of their team, the shorthand that made daily work predictable. Everyone is already stretched by restructuring and uncertainty about their own role, which is exactly when people retreat to what's familiar rather than reaching toward something new.
For this reason, it was even more important to make sure everyone felt they were active participants in shaping the culture - not just passive recipients of a new set of values.
Our messaging focused heavily on a "best of both" approach - taking the best parts of each organisation and building something new from it. This gave people a chance to share what they valued, what mattered to them, and crucially, what mattered most to customers.
But it also gave permission to challenge what wasn't working. To share the frustrations, bottlenecks, silos and systems that prevented people delivering well. This took culture away from abstract values, and focused more on how work got done day-to-day - and how we might change things for the better.
Culture change at scale and complexity
The approach to changing culture shifts as the scale increases. For a 50-person organisation, culture often lives in who you know and how your colleagues behave. That means relationship-focused interventions can be more beneficial. At 3,000+ employees the approach needs to be more systemic - built into the mechanics of day-to-day operations.
Housing associations are complex operating models too, which means being too prescriptive can backfire. The target culture needs to make sense for frontline teams, development teams, fire and safety teams and every other department.
The work had to change the conditions that produce culture, not describe what the culture should be. And it had to do that while protecting customer experience through the period when internal disruption was at its highest, which meant culture change couldn't be a separate initiative competing for attention. It had to be woven into the work of improving services.
Culture change in social housing - built around what mattered to customers
We needed a reference point to ground the work - a "reason to change" that would resonate with staff in both organisations.
All culture change, in fact all organisational change, needs a "reason to change". A single reference point that captures why it's worth people's time, energy and engagement.
In a merger, two organisations becoming one need a shared language fast. People need something to point at when they ask what kind of place this is now. But they also need something they can apply practically as their services, teams and ways of working shift.
The temptation was to follow a values-led approach. Values are easy to communicate, and give leadership something visible to stand behind at exactly the moment people are looking for reassurance.
Values aren't wrong, but at this scale they tend to arrive as adjectives - and adjectives don't tell anyone what to do differently on Monday. "Caring" doesn't resolve whether you send the standard arrears letter. A merged housing association with thousands of staff needs a shared language they can operationalise - one formed of practical priorities rather than adjectives.
From values to practice
So the objective was to shift the emphasis from describing a set of value-based adjectives to posing a small set of questions - universal enough for every team, simple enough for a busy Monday meeting, and clear enough that everyone knew what mattered most.
From early conversations with staff and customers it was clear that they wanted something practical - a set of tools, priorities or provocations that they could use in their daily work.
That meant designing culture change around things people could see in conversations, feel in what got prioritised and use in a cross-departmental meeting. And it meant accepting that we couldn't prescribe how everyone should work. What a repairs team needs is different from a care and support team, which is different again from a contact centre. The aim was to get the whole organisation using the same framework to talk about its work, while each team found its own answers.
Starting with what customers and colleagues need
Where customer and colleague evidence overlapped
The starting point for the culture change was evidence, and there was a lot of it: customer data and complaints, service performance, employee insight from both organisations, and time with frontline teams, senior management and the CEO.
Most programmes handle that material in two streams. Customer experience is one workstream, employee engagement another, and each produces its own set of findings, its own priorities, its own plan. It's a sensible division but it hides the most useful thing in the data.
Read together, the two often converge. What customers said they wanted turned out to be, in different words, what staff kept pointing at as the thing they wanted more room to do. Customers described being treated like a case rather than a person; staff described processes that made them sound like one. Customers wanted to sort something out in one go; staff were frustrated at handing people between teams. Both groups were describing the same handful of things, from opposite sides.
That overlap gave us the foundations for the change approach. And it helped us define the reason for change that would resonate with colleagues and with customers - because it was universal. A truth that holds for customers and colleagues doesn't need selling to either. Nobody has to be persuaded of it, because they said it first.
A simple framework, thoughtfully implemented
When it comes to any type of change, simplicity of message matters. And this is no less true for culture change. So we deliberately kept the framework simple.
One distinction to note: simplicity belongs in the framework, not the delivery. Behind the framework sat real machinery: nine workstreams covering quick wins, cross-departmental sessions, team support, leadership development, Heads of Service toolkits, performance management, internal engagement, customer voice and measurement. A simple idea needs solid delivery behind it, because it's carrying so much.
Keep simple the thing people have to hold in their heads - the work behind it can be as detailed as it needs to be.
Built around three provocations - focused on what customers and colleagues wanted
Three key questions came out of our early work, and formed the framework for everything else:
- Are we providing a low-effort experience for customers?
- Are we working well with other teams and colleagues?
- Are we being human and kind in the way we communicate?
Each of these was distilled from customer and colleague feedback, based on the most common frustrations and what people said mattered most.
Effort was consistently highlighted by customers as a frustration, and by colleagues as a bottleneck which meant they couldn't invest time in the things that matter. Effort is also a better measurement of success for operational service delivery - from repairs to safety, the same message kept coming out: "Just make it easy to get what we need".
For working well, a customer described it best - "How you work together internally is how we experience you externally." The success of internal relationships, handovers and internal workflow ultimately impacted what customers experienced at the end.
For "human and kind", customers weren't asking for customer-centricity, they were describing, over and over in different words, letters that felt hostile and staff who sounded like a process. They wanted to be treated as human beings, with a kindness that was sometimes lacking.
Because these came from customer and colleague data, it was easier to validate each of them with real voices and real needs.
These three questions needed to work across the whole organisation, so we validated them with four tests:
- Is it true everywhere? If it only works for frontline teams then it's not universal. A finance team has to be able to answer it about the colleagues it serves.
- Can a team act on it this week? "Be more innovative" can't easily be acted on. The questions only work when they prompt teams to change a form, a letter or a handover before the next session.
- Does it come from evidence rather than aspiration? Anything we wanted to be true, rather than found to be true, came out. The three questions were honest, if unglamorous, and encouraged teams to go back to the fundamentals rather than lay aspirational values on top of their work.
- Does it help a team look truthfully at how they work? Quiet compliance does more harm to change than disagreement does. "Do we care about our customers?" gets a yes from every team in the organisation and changes nothing. "Are we providing a low-effort experience for customers?" can't be answered without going and looking at the service. A good question sends a team off to check. If people can answer it just by nodding, it isn't doing its job.
Built through sessions, not launched as a programme
People First, the name of the programme, was introduced through action-focused workshops with teams, always opened by the CEO or a senior sponsor, always focused on practical application rather than abstract ideas about culture. It was soft-launched with the executive and a range of frontline teams rather than the whole organisation at once, so that when it did spread, it spread on evidence that it worked rather than on an announcement.
The sessions took away the ambiguity of "culture" and replaced it with something concrete: how things work here. Instead of asking people to change how they felt about the organisation, the sessions asked how the work could be done differently in their context. That's a conversation people can engage with regardless of how they feel about the merger, the leadership, or the idea of culture change.
How the culture change actually spread
The launch was deliberately light-touch, and focused more on proving the concept through workshops and sessions rather than telling people about it. Our approach was simple - make the sessions engaging, practical and meaningful enough that it spread more through positive feedback than leadership decree.
People First spread by word of mouth. Through the water cooler, the informal networks that survive any reorganisation, colleagues telling colleagues it had been worth a day. Demand for sessions came from people who'd heard about them from someone they trusted, not from a communications plan.
We didn't mandate attendance, because peers were generating the demand - and a recommendation from someone at the next desk carries something no all-staff email can buy. It also cost nothing. The most effective distribution channel in the organisation was one that already existed and was free.
Most importantly, it sidestepped the "done to us" problem that follows so many change programmes. A programme that arrives by decree is something happening to you. A programme you heard about from a colleague who found it useful is something you might choose. Same content, completely different relationship to it.
The feedback from those first sessions was consistent enough to be a finding in its own right, and it kept arriving unprompted weeks after the event. Some of it was about the work - people naming, for the first time, things about their own service they'd stopped noticing. Some was about the organisation, from people who'd been through years of restructuring and found that hearing directly from the top, in a room, changed what they thought was happening. Several said it was the best session they'd been to in a career measured in decades.
The risk with a non-mandated approach is that the content doesn't create engagement. Word of mouth only works if the thing is genuinely good. A mandated programme can be mediocre and still reach everyone; an optional one that relies on peer recommendation has to be worth recommending, every session, from the first. If those early workshops had been unremarkable, nothing would have spread.
Principles agreed before anything started
Before any of it ran, we agreed five principles with the steering team. They were there to help us decide things when the arguments we expected came up:
- Everyone will have a voice, and a chance to make a difference
- It's about internal and external customers alike
- This will be co-designed with people, not imposed on them
- It won't be one-size-fits-all - teams customise with support
- The long-term aim is to give teams the tools to do this for themselves
Agreeing those upfront is what made it possible to say no later, when the pressure came to mandate attendance or standardise what teams produced.
Two levels, both connected
The work ran at two levels simultaneously.
Leadership worked on systems and environment - the structures, policies and conditions that shape how people are able to work. This is where the systemic blockers sit: approval processes that slow things down, communication templates that feel hostile, performance frameworks that measure the wrong things.
Teams worked on their own area - taking the three questions and working out what they meant in practice. What does "a low-effort experience for customers" look like for a housing management team? A contact centre? A care and support team?
The split matters because it addresses the most common reason culture change stalls. Work only with teams and they hit systemic barriers they can't fix. Work only with leadership and you get policies that look good on paper and change nothing at team level.
The two levels were joined by a feedback loop. As teams worked through the questions, they surfaced what needed to change structurally, and that went straight to leadership. Leadership made changes. Teams saw them happen. Ten high-priority challenges were picked as early wins - things that could be fixed quickly without disruption - precisely so the feedback loop had something visible to show early.
The ideas, suggestions and feedback that came back to leaders were more useful than a survey would have been, because people weren't rating the organisation they had. They were describing the one they wanted to be part of:
- Measures that reward the experience they were being asked to create, so that reducing a customer's effort and hitting your numbers pull in the same direction
- The trust to write to a resident in their own words, rather than through enough layers of review that the letter comes back unrecognisable
- Teams working together to finish what another team started, instead of each optimising for its own targets
- Ways of handling arrears and enforcement they could stand behind when they knocked on the door
- Managers who treat time spent on this as part of the job
We treated this feedback as a specification: the merged organisation, described by the people who would have to work in it, in enough detail to act on. None of it is fixable by a single team, and none of it would have come out of a questionnaire. It came out because people were asked a concrete question about their own work and given somewhere for the answer to go.
What built trust was what happened after people spoke up. Leaders acted on what they heard, so they were showing the culture they wanted, not just describing it. It does mean a leadership team has to be willing to hear that some of the answer sits with them, including in how they measure. That's the price for this approach, and it's higher than a values workshop.
A focus on small changes, deliberately
The challenge to every team was small: what can you do in your own part of the organisation to begin shifting how you work?
That was deliberate, for three reasons.
- Aggregation - hundreds of teams making small changes is the system change; no single team has to transform anything.
- Disruption - during a merger, small changes are manageable, and a transformation programme stacked on top of a merger overwhelms people.
- And most importantly, it bypasses "someone else's job" - when culture change is only about big structural moves, most of the organisation concludes it isn't their problem to solve.
Underneath all three sits a principle that was agreed at the start: the people closest to a problem should have the power to fix it. Most organisations agree with that in the abstract and are structured to prevent it. Making it real is what turns a small change from a suggestion into something that actually happens.
The pilot sessions alone produced more than fifty ideas, all direct from staff. At one end, automatically refunding leaseholders who ended the year in credit rather than making them ask - money returned to residents who were owed it and would mostly never have claimed it. At the other, a positivity jar on a desk.
The positivity jar is one worth dwelling on. It was one person's idea, in one team, and sounds so small as to feel insignificant - but it was quite the opposite, and it worked so well that other teams picked it up and ran their own. Reception ended up with a version residents could contribute to.
It's worth focusing on because no programme would have commissioned that. Put "introduce a positivity jar" in a change plan and it dies of embarrassment in the first review. Owned by a person whose desk it sat on, it became something else entirely, and then it grew on its own.
That's the argument in miniature. Someone made the change locally because they wanted to, and other people saw it working and wanted one too. The culture spread by being shown, which is the only way it ever really moves.
Small didn't mean trivial. It meant local - changes made by the person closest to the problem. The person who knows the year-end credit is sitting there is the person processing it.
The three questions in practice
Customer experience and service design. The first question drove a focus on customer experience and service design - with customer effort as the measure. With every service being reviewed during the merger anyway, there was a natural opening to balance internal process against a genuinely customer-centred approach.
The move was from satisfaction measurement to customer effort - how much work it took someone to get what they needed. Effort is actionable in a way satisfaction isn't. If a process takes fourteen steps you can redesign it; if satisfaction is 6/10 it's less obvious where to start.
The decision that made this work organisation-wide was defining "customer" to mean internal as well as external. Every team, wherever it sat, answered two questions in order: who do we serve? and then how much effort does it take them to get what they need from us? A finance team, an HR team, a repairs scheduling team - none of them talk to residents daily, and all of them have customers.
That did something a customer experience programme aimed only at frontline teams can't. It gave the whole housing association one measure of whether the work was any good: low effort, easy to deal with, the customer gets what they need. Back-office teams stopped being the audience for customer experience and became participants in it. That is what made customer experience an organisation-wide measure rather than a frontline one. And because internal and external effort are connected - staff losing time to bureaucracy is a cost customers eventually pay - improving one tended to improve the other.
Working together across departments. When people are anxious, they retreat to what's familiar. The "us and them" that forms after a merger is a predictable response to disruption, and seeing it that way makes it easier to design for.
Cross-departmental sessions were opt-in. That was deliberate: mandating attendance at culture change sessions during a housing association merger would have contradicted the message, and it would have broken the third of our five principles. Opt-in also filtered for people who were genuinely motivated rather than compliant. Around 20% of the housing association engaged through those early sessions, well above most tipping-point thresholds, and those early adopters became the champions who later ran sessions with their own teams alongside the Learning and Development team.
That's standard adoption-curve thinking: put the energy into the early adopters rather than spending it trying to drag along the disengaged. The majority in any organisation are waiting to see evidence, and the only thing that produces it is other teams' results.
Human and kind communication. This started with something concrete: letters and notices that came across as hostile, confusing and unnecessarily formal, damaging relationships with residents and creating tension where none needed to exist.
Here's what came out of one session. A team rewrote the letter that offers residents contents insurance - the kind of letter that normally opens by announcing a scheme:
What would it cost you to replace your things if there was a flood or a fire in your flat?
If you looked around your flat now, what would it cost to replace things like your cooker, your TV and your sofa? As unlikely as it seems, fires and floods happen, but if you are insured, the insurance company will cover the cost of replacing them.
Because we can't replace these things for you, we've found an insurance company that will give you cover from £2 a week - and you can pay this weekly. We don't get paid a commission from this.
Three things happened there. It starts inside the reader's flat rather than inside our processes. It uses the words a person would use. And it volunteers something nobody asked about - that we take no commission - because the team realised the offer wasn't believable without it.
Nobody could have written that from a values statement. They wrote it from a question.
"Human and kind" also turned out to travel further than communication. Teams began using it as a test for how they behaved and how they made decisions, not only how they wrote - which makes sense, because the way you communicate shapes a relationship as much as it reflects it.
Closing the capability gap for managers
Asking "Are we providing a low-effort experience for customers?" is simple. Doing it needs skills most managers don't have - service mapping, facilitation, customer research, running sessions with their own team. That gap is a common reason culture change programmes stall: people buy the principle and can't act on it.
A core toolkit was developed to address this - customer experience, effort and service design (including a Customer Experience Scorecard teams used to assess their own service across effort, working together, human and kind, and customer-led); cross-departmental problem solving; and how to write in a simpler, more human way. Specific teams got tailored support on their own challenges, including care and support, complaints, service charges, rent collection and HR.
For leaders, we ran "Leading the Way" workshops that brought Heads of Service and Directors together with people they didn't normally work with, and built a leadership programme with the internal L&D team.
Performance management, rebuilt on the same three questions
What an organisation measures tells people what it actually values, regardless of the poster. If performance management doesn't align with the culture you're building, it actively undermines it.
The existing framework used complex assessment criteria - the kind that become a box-ticking exercise. We replaced them with something simpler: people demonstrated how their work reflected the three questions. The focus moved from scores to the conditions for good conversations - honest dialogue between peers about how they were working, rather than whether they'd hit a number. For leaders, a simplified 360 looked at the environment they created and whether it supported or blocked the three areas.
A culture that showed up in what residents experienced
The system running without us
The clearest sign something had shifted was that the loops became visible and were working without external intervention. Teams took the three questions and made them their own. They fed structural blockers upward. Leadership changed things. Those changes showed up in how customers experienced the organisation.
That circular pattern - teams owning their part, leadership responding, improvements reaching customers - is what embedded looks like. The programme had become a way of working that kept itself going. Three years after the work began, the three questions were part of the customer voice at both organisational and team level.
What changed for residents
Customer experience measurement shifted to effort and real-time feedback rather than retrospective satisfaction scores, which gave teams something they could act on directly. Cross-departmental problem solving became ordinary rather than something requiring an initiative. A merger that could have been defined by disruption and lost identity became the occasion for building something more intentional than either organisation had been before.
Designed to make us unnecessary
We planned from the start for the organisation to run this itself: champions ran sessions with their own teams supported by L&D, managers used the toolkit day to day, and leadership modelled the approach and responded visibly.
A monthly Pulse Check gave teams a simple diagnostic across eight areas, from enabling environment and innovation to cross-team collaboration and customer focus, with a traffic light system to prioritise where to act. Its job was to read the conditions each month, because culture isn't something you fix once and leave.
Alongside it, a maturity model gave the organisation a way to locate itself and see what came next. Five stages: tactical, where good practice happens in pockets and solves specific problems; planned, where it becomes deliberate rather than reactive; evaluated, where it's measured on a schedule against objective criteria; embedded, where it's business as usual; and cultural, where it's a core part of the operating model and of how the organisation plans. Naming the stages gives people something to act on: "we're at planned, and evaluated is next" is a conversation an organisation can have. "Our culture needs to improve" isn't.
What was hard about culture change at this scale
Culture change in social housing of this kind takes 18 to 24 months to take hold, and we said so at the start.
It wasn't frictionless. There were people who'd watched programmes come and go and had good reason to be sceptical. There was constant tension between wanting visible results and knowing this needed time. Some teams engaged immediately and others were much harder to reach, which required patience rather than pressure. The feedback loop surfaced uncomfortable truths that leadership then had to respond to. And all of it happened while the merger itself created continuous disruption and competing demands.
None of that is unique to this project. It's what working with culture as a living system looks like, rather than a programme with a start and an end date.
Why culture change in social housing works when it faces outward
Every instinct in a merger pulls inward. Whose systems do we keep, whose way of working wins, what do we call ourselves now. A values exercise is that instinct in its most respectable form - an organisation spending months talking about itself at exactly the moment it can least afford to.
What shifted the culture here was giving everyone something outside the organisation to point at. That something was three truths about what the people we serve needed - and, because the evidence matched, what colleagues had been asking for too. "Whose culture wins?" stops being a live question when the answer isn't about either of you.
That external anchor is what made it hold at scale. A shared identity has to be agreed, and agreement is fragile in a merger. A truth about a resident's experience doesn't need agreeing - it needs checking, in your own service, this week. A repairs team and a finance team answering "Are we providing a low-effort experience for customers?" arrive somewhere different and are still doing the same work.
And it's why the questions carried an authority no internally written value could. They came from boiling a few hundred complaints and a lot of staff insight down to what they had in common. Nobody needed selling on them, because both groups had said them first.
Why it works: artefacts first
Edgar Schein's three levels of culture explain the mechanism. Schein describes culture as operating at three levels: artefacts (the visible things - how services are delivered, how people communicate, how decisions are made), espoused values (what an organisation says it believes), and underlying assumptions (the deep, often invisible beliefs that drive behaviour).
Most culture programmes work on the middle layer. They define values and hope those values change the artefacts above and the assumptions below. This project bypassed that layer. It worked directly on artefacts - service design, communication, team practice, performance management - and let the assumptions shift as a consequence.
That's the significant move. Rather than telling people what to value and hoping behaviour follows, we changed what people did and let the meaning follow. Nobody needed to be told customer experience mattered. They experienced it mattering, through redesigned services, through effort data that showed where things were broken, through leadership responding to what teams raised. The values became real because the practice made them real.
It's also why the three questions worked as leverage points for culture change. They're places where a small shift in thinking ripples across a whole system, which is what let hundreds of teams making small changes add up to system-wide shift without a system-wide mandate.
Culture change and the Tenant Satisfaction Measures
The Regulator of Social Housing's Tenant Satisfaction Measures now require every housing association to report on exactly the outcomes this approach was built around - satisfaction with services, communication, and how landlords listen and act. The TSMs measure things that are shaped by culture: how residents experience an organisation, not what it says about itself. Organisations still relying on values statements to meet them are working against the grain.
The Competence and Conduct Standard asks the same question
Since October 2026, the Competence and Conduct Standard has gone further. Alongside qualification requirements for senior housing staff, it sets expectations about conduct - how people actually behave toward residents. That is a meaningful shift in what a regulator is willing to look at, and it lands squarely on the territory this project worked in.
Conduct is an artefact, in Schein's sense. It is visible, it happens in specific interactions, and it can be worked on directly. It is not an espoused value, and it cannot be reached by declaring one. A housing association that meets the standard by writing a behaviour framework and running training will produce people who can describe the expected conduct. One that changes what its letters say, how its handovers work, and what its performance conversations reward will produce the conduct itself.
Read that way, the three questions are a conduct test that happened to arrive years before the standard did. "Are we being human and kind in the way we communicate?" isn't a value. It's a question a housing officer can answer about a letter sitting in front of them, right now, and act on before the end of the day. That is the difference the standard is going to expose.
We've since built a practical guide for housing leaders working with it - the Competence and Conduct Standard toolkit.
Where to start
For any housing association facing significant change - a merger, a restructuring or the demands of a new regulatory standard - the question worth sitting with isn't what your values should be. It's whether you know, from evidence rather than assumption, what the people you serve actually need from you - and whether the whole organisation could point at the same answer.
If the merger is the pressing part, our article on culture after a merger covers why structural integration so often completes while the organisation still feels like two. For the wider practice, see developing organisational culture.
About this work
James Freeman-Gray was principal consultant on this programme. He developed the approach, worked with the executive team, and ran the workshops and sessions across the organisation.
See more of our work across social housing, including another housing association merger integration.
More case studies like this
Competence and Conduct Standard - free culture readiness toolkit
The Competence and Conduct Standard applies from October 2026. The qualification requirements are well documented elsewhere. The culture and behaviour side - how your organisation evidences conduct, gives residents real influence, and shows that training leads to better outcomes - is the harder leadership work.
We built a free toolkit for housing leadership teams preparing for this side of the standard. It includes a breakdown of the culture requirements, six practical challenges providers are working through, reflective questions for leadership teams, and a diagnostic you can complete in five minutes.

Facing something similar in housing?
From culture under the consumer standards to merger integration and service improvement, the hardest part is usually the organisational side - connecting strategy to how the work actually gets done. If that's where you are, we'd like to hear about it.
Let's talk about what you're working on
Whether you're navigating a merger, rethinking how you're structured, or trying to shift a culture that isn't working - underneath, it's the same job: getting the whole organisation pulling in the same direction. Start with a conversation.






