Title

LATCOS

Build the future. Then deploy the technology.

Rhian Stone of Bolton Cares talks to Keystream Consulting's Isaac Vivian about how to get the most out of technology investment

Rhian Stone and Isaac Vivian © Keystream

Rhian Stone and Isaac Vivian © Keystream

When social care provider LATCO, Bolton Cares, needed to replace its Digital Care Recording System, Chief Executive Rhian Stone chose to ask a bigger question: how should our organisation work in the future to deliver on our purpose? She talks to Isaac Vivian, Local Government Lead at Keystream Consulting, about what changed, why the approach mattered and what other public service leaders can learn.

Back in May, what challenges was Bolton Cares facing, and why didn't you simply replace the digital care recording system?

We'd spent years moving from paper to digital, introducing different systems under considerable pressure. The trouble was, they weren't really speaking to each other. That created frustrations and workarounds across the business, especially for our colleagues delivering care. Then our care recording provider told us its system would no longer be available from April 2027.

It was a huge headache, but also an opportunity. We could rush out and buy a replacement, or pause and think about how we wanted Bolton Cares to work in the future. I wanted to start with how we deliver the best possible care, then ask what technology would help us get there. Otherwise, we'd risk investing in something new that simply embedded yesterday's problems.

What was different about working with Keystream Consulting, and what did involving your people help you discover?

Keystream stood out during procurement. You'd understood our brief, done your homework and recognised that the people we support had to be centre stage. It felt genuinely bespoke, rather than an off-the-shelf offer we'd have to fit ourselves into.

That wasn't just a promise. Your team was visible throughout, working alongside our registered managers, support workers, ICT and central services. Keystream brought people together for some very honest workshops, creating space to explore problems properly. We could challenge your thinking, and you listened. That collaboration helped us get beneath the symptoms and understand what wasn't working.

What surprised me was the amount of management time lost to duplication and spreadsheets created to work around systems and processes. Keystream helped us see the scale of that, but also reflected back the capability and commitment of our operational teams, which gave people a real boost. We'd been trying to tackle these issues ourselves; having that external impetus made a real difference. You did what you promised, and we could see that you genuinely cared about our organisation and the change.

What difference has the work made, and how is it shaping Bolton Cares' next technology investment?

The target operating model Keystream developed with us gave us a shared picture of how the organisation should work. Many recommendations weren't digital at all: they addressed how frontline, ICT and central teams should work together going forward. Keystream also brought the technical expertise to get under the bonnet of our existing systems and data architecture, helping us understand not just how we needed to work differently, but what technology and integrations would be needed to make that possible.

I was slightly worried about what would happen when Keystream left. Instead, the momentum has continued. Teams are implementing recommendations together. Previously, conversations could become about whether something was ICT's fault or operations' fault. Now there's more shared problem-solving, with frontline colleagues involved in decisions. That's a significant cultural shift.

We already had capable teams delivering good care. Keystream helped us identify the friction getting in their way. Our new system requirements now reflect what staff need, and we're planning to invest much more in helping people through implementation. There's plenty still to deliver, but we're better equipped to do it ourselves.

What advice would you give another chief executive, and what do you hope to share at the LATCo workshop?

Don't start by shopping for technology. Start by understanding the problem you're trying to solve and what needs to change in your organisation to solve it. Listen to the people delivering services to understand what's working, what isn't and where the gaps are. Only then decide what technology to buy or build, and find partners who will help your teams lead and own that change.

When Isaac and I deliver our workshop Build the Future. Then Deploy the Tech at the national LATCo conference workshop next April, I'm confident we can share the progress in the implementation of our operating model; a new care recording system having been introduced, and a continuing cultural shift of momentum. Above all, every decision will start with the people we support and our employees who support them. Technology should follow that purpose, not define it.

 

Rhian Stone and Isaac Vivian will speak at the LATCO conference in April 2027

LATCOS

Who will lead reform while services keep running?

By Ryan Miller | 12 November 2026

Ryan Miller argues that reform will succeed or fail on the depth of leadership below the director, and asks what support those leaders need.

LATCOS

Why insight should shape community infrastructure

By Natalie Gibson | 12 November 2026

Gaining an understanding of communities in essential to guiding investment in facilities, writes Natalie Gibson.

LATCOS

NCASC: Inaction on profiteering could risk early intervention cash

By Ann McGauran | 11 November 2026

The financial case for rebuilding early intervention could be undermined by lack of national action on placement profiteering, England’s children’s care chie...

LATCOS

Rayner admits LGR was 'always going to be litigated'

By Martin Ford | 11 November 2026

Local government reorganisation (LGR) was ‘always going to be litigated’, Angela Rayner has said as she defended bringing the process to a halt.

-->