alterNOTION Blog

Crafting what's next

Sat, 02 May 2026 15:40:11 GMT

A multi-workstream leadership transformation programme for a specialist healthcare technology provider, preparing for executive succession, AI integration and operating model change.

The challenge

The organisation was approaching a planned executive retirement with no structured succession process. Internal candidates existed but had never been assessed against future-state requirements. The senior leadership team's governance had not kept pace: meetings defaulted to operational updates, decision rights were unclear, and key person dependency sat unmanaged. AI adoption was happening individually but without shared standards or governance. Leadership capability had been defined for the current business but not for the AI-enabled, platform-driven market the organisation was entering. The challenge was the interdependency. Succession planning needed a leadership model that did not yet exist. AI integration required governance the senior team had not yet built. None of it could move without first agreeing what good leadership would look like in three years.

The approach

Change management was embedded across all workstreams rather than layered on top. The approach combined:

A structured succession process with phased evaluation, case-based assessment, assessor calibration and a defined feedback sequence
A five-dimension leadership capability framework mapping each candidate's development needs against the organisation's three-year direction
A psychometric assessment framework linking validated, locally applicable tools to the capability model
A senior leadership governance redesign covering decision rights, meeting structure, steering committees and escalation protocols
An AI readiness strand positioning AI as an organisational capability with defined adoption targets and governance
A key person dependency workstream with knowledge transfer, succession depth and resilience actions

The delivery

Individualised leadership development profiles for each succession candidate
Case-based assessments built around the organisation's actual strategic challenges, with model answers and scoring rubrics
A capability ladder mapping expectations from operational through to enterprise leadership
A RACI matrix across six functional domains
Revised senior leadership meeting cadence, agenda template and escalation framework
A talent strategy connecting AI capability, leadership development, line manager capability and succession depth
A three-year development roadmap with stretch assignments, coaching and feedback mechanisms

The shift

Leadership capability now has a shared language and visible development architecture. Succession is evidence-based rather than informal. The senior team has a governance model that distinguishes strategic oversight from operational review. AI integration has moved from individual experimentation to a defined organisational agenda. Key person risk is actively mitigated rather than acknowledged in passing.

The impact

What made the difference was treating these as a single programme. The succession process needed the leadership model; the leadership model needed the governance redesign; the governance redesign needed the AI work to define what the senior team would actually be governing. The executive transition is positioned as a stability-first process with clear criteria and managed communication. Leadership development has moved from generic training to targeted, psychometrically informed interventions. The senior team now operates with governance designed for the complexity of a regulated, platform-driven healthcare business.

An organisation already performing well is now positioned to sustain that performance through significant leadership and operating model change.

Built to land

Sat, 02 May 2026 15:26:45 GMT

Restructuring a finance function without losing what makes it work

A multi-workstream change management programme for the UK Finance function of a FTSE 250 international services organisation, supporting a structural shift from contract-aligned teams to a centralised hub model.

The challenge

The finance function had grown around its contracts. Each had its own team, its own processes and its own way of working. Capable people, operating in silos.

A programme to centralise transactional finance into a dedicated hub had been approved. Over a hundred people faced role changes, redeployment or departure. The challenge was human, not technical: land the change without losing the capability and relationships that made the function work.

The approach

Change management was established as an integrated programme workstream from the outset. The approach combined:

A stakeholder assessment mapping ten distinct groups, each with different impacts and information needs
A bespoke training curriculum spanning soft and technical skills, sequenced against programme milestones and differentiated by audience
An interaction matrix defining how finance activities flow between contracts, partners and the hub, socialised through structured feedback sessions before finalisation
A communications and engagement strand covering leadership cascade, listening loops, FAQs and a dedicated knowledge hub
A change agent network of Finance Directors and hub leaders, supported by a weekly steering committee

The work drew on the change curve, ADKAR and Bridges' Transitions model, applied selectively rather than by rote.

The delivery

Stakeholder impact analysis across all ten groups with tailored intervention plans
A rolling weekly steering committee at FD level
An interaction matrix developed through iterative consultation, capturing feedback before finalising accountabilities
Over fifteen training courses across six audience groups, from continuous improvement to resilience and career preparation
Structured support for departing colleagues alongside programme delivery
Readiness assessments at two checkpoints before Go-live, with targeted remediation

The shift

A shared interaction model is now in active use, replacing what had previously been understood informally. Role clarity has improved. Training is sequenced to real milestones rather than delivered as a standalone calendar.

With the change network and steering committee operational, issues surface earlier. The programme has a visible feedback loop rather than relying on escalation.

The impact

What made the difference was treating this as a change programme from the start, not a restructuring project with comms bolted on. The interaction matrix was built through genuine consultation. Training was designed around what each audience actually needed, not what was available off the shelf.

For the organisation, Finance now operates with standardised processes, a hub with its own identity and development pathway, and business partners freed to focus on commercial value. Career conversations have a framework. The function's credibility with the wider business is strengthened by a visible operating standard.

A finance function that was already delivering is now positioned to operate as one team.

Capability by design

Sat, 02 May 2026 15:02:45 GMT

From execution to enterprise impact

A bespoke twelve month capability programme designed and delivered by alterNOTION - through a consulting partner - for the technology team of a Fortune 100 global healthcare organisation.

The challenge

Engaged to address a familiar but stubborn pattern; a bespoke baseline survey confirmed it. The team had the skills and the will to collaborate but what was missing sat around them, not in them: unclear decision making across teams, no shared definition of success, and no agreed way to handle disagreement. The investment case was structural and cultural, rather than skills based.

The approach

We led a deep discovery phase combining the baseline survey, one to one interviews and focus groups across the team, their managers and senior stakeholders. Findings were synthesised into a fully bespoke programme, designed end to end:

A skills catalogue setting out what good looks like at each career stage
A learning roadmap sequenced against real work
A human skills training series covering influencing, facilitation, handling challenge and managing conflict
A central online hub as the place everyone goes for how the team works
An integrated communications and engagement strand to drive adoption of the knowledge hub

The work was anchored in established team development frameworks, applied selectively. GRPI provided the lens for goals, roles, processes and interpersonal dynamics. ROCKET shaped thinking on execution and momentum. DISC supported self awareness and adaptive communication.

The delivery

Skills catalogue covering both core roles across three career stages
Facilitator led training sessions, refined between cohorts based on what worked in the room
A central hub built to a structured wireframe, populated with onboarding guides, process maps, FAQs and learning content
An adoption plan of practical actions to drive sustained engagement after launch
A quantified baseline against which future progress could be measured

The shift

A shared language for capability is now in active use, giving line managers and team members a common reference point for career conversations that previously had none.

Role boundaries are reported as clearer. A single hub has replaced scattered documentation, supported by a governance plan to keep it current. Practical role play was consistently rated the highest impact element of the training.

With the baseline in place, progress on decision clarity, shared success and constructive challenge is measurable rather than anecdotal.

The impact

What made the difference was design discipline. The programme was built by alterNOTION bespoke from the discovery findings, treated as a change programme from day one rather than a training rollout, with the hub wireframed before any content was written.

The future

For the Client, this changes how the team shows up in the wider business. Cross functional work moves faster because decision making is clearer. Onboarding is quicker because the environment is documented rather than tribal. Career conversations have substance, strengthening retention. The team's voice at senior tables is more credible, backed by a visible standard of how it operates.

A team that was already capable is now positioned to be relied on.

The AI pilot trap

Thu, 02 Apr 2026 13:34:20 GMT

Most organisations are measuring AI success on pilots, not people. That's the wrong way round.

A few weeks ago I sat in a steering committee for an AI rollout. The deck was the usual: green RAG, licence count climbing, prompts-per-seat trending in the right direction. Everyone was pleased.

I asked one question. What was actually different about how the work got done last month compared to the month before? The room went quiet. Nobody had measured it. Nobody had thought to.

The pilot was a success on paper. Underneath, nothing had moved.

The numbers we like to quote

The headline finding from the MIT NANDA Initiative's 2025 State of AI in Business report : 95% of generative AI pilots deliver zero measurable P&L impact. Most of the commentary uses the number to argue that AI is overhyped, the technology isn't ready, or that boards are wasting money.

Useful number. Wrong conclusion.

The pilots aren't failing because the technology doesn't work. They're failing because we're measuring the rollout instead of the shift.

AI doesn't arrive as a transformation

We know how to measure whether change has landed. On any major transformation, whether digital, ERP, or agile, we put readiness surveys in place. Pre and post. We track sentiment, capability, behaviour change. Not perfectly, not always honestly, but the infrastructure is there. We've understood for decades that the rollout and the change are different things.

AI is different. It usually arrives as a pilot rather than as a transformation programme. And pilots inherit pilot logic: deployment, usage, time saved per task in the controlled environment. The readiness work we'd do as standard on a transformation usually isn't there.

So we end up with something transformational in scope, changing how knowledge work gets done, who does it, and what skills matter, being measured like a tool deployment.

Kotter wrote about this kind of failure in 1995 . Around 70% of transformations fail, and the reason is almost always the same: organisations skim the human side because the structural side is easier to project-manage. Even where readiness surveys are in place, the discipline to act on them often isn't. AI pilots usually don't start with the surveys at all.

What the dashboards count

Pull up the steering pack for any AI programme and you'll see roughly the same metrics:

Licences activated
Active users this month
Prompts run per seat
Time saved per task in the controlled pilot
Pulse scores from the pilot cohort

Deployment metrics. They tell you whether the tool got installed and whether people clicked on it. They tell you almost nothing about whether anyone is doing their job differently.

I've watched programmes hit every one of these targets and produce nothing that lasts. People log in once a fortnight, run a couple of prompts, get a passable output, and revert to the old way of working for everything that actually matters. The dashboard reports green. The behaviour underneath has not moved.

What the dashboards don't count

The harder things to instrument tend to get left off the slide:

Whether people trust the output enough to use it on work that matters
Whether they have the judgement to spot when it's wrong
Whether they're using AI on the parts of their job they care about, or only on the busywork
Whether the way they describe what AI is for has changed
Whether they're sharing what they've learned with colleagues
Where AI is conspicuously absent, and what that absence is telling you

Twenty-five years of organisational change work has convinced me of one thing above all: if you don't measure the human side, it isn't happening. Not because people are lazy or resistant, but because nothing else is signalling that it matters.

The perception gap

Here's the pattern that worries me most. Self-reported confidence in AI runs ahead of evidenced behaviour, often by a wide margin.

Ask a workforce how AI-ready they feel and you'll get one answer. Look at what they're actually doing with it day to day and you'll get another. Both are real data. The space between them is where the change work lives.

The leaders making decisions about the next phase of investment usually only see the first answer. The pilot dashboard shows adoption climbing. The pulse survey shows confidence rising. The board pack reports progress. And meanwhile, the actual capability shift, the thing that was supposed to make any of it worth doing, isn't happening.

A recent piece from Harvard Business Review frames it well: leaders mistaking silence for alignment, dashboards for behaviour, surface engagement for genuine shift. There's no deliberate self-deception. They're looking at the only data anyone is collecting.

The perception gap is what makes pilot metrics so dangerous. They flatter to deceive.

Why people success has to come first

McKinsey's research on large-scale transformations found that organisations achieving most of their people-oriented goals were twice as likely to sustain the change for more than three years. Their AI work points the same way. Companies seeing significant financial returns from AI are twice as likely to have redesigned end-to-end workflows before selecting the modelling approach.

That sequencing matters more than any other single thing.

If you start with the pilot and bolt people onto it, you get the 95% outcome. If you start with the people, the workflows, the judgement, the genuine capability shift, the pilot tends to land. The pilot becomes a downstream consequence of the people work, not a substitute for it.

I understand the resistance to working this way. It's slower. Harder to dashboard. Doesn't generate the kind of demo a CIO can show the board in March. But in twenty-five years, I haven't seen a transformation produce lasting value any other way.

Upskill the workforce, not just the cohort

The other thing AI rollouts tend to get wrong: training the pilot users, and stopping there.

McKinsey's work on capability building is consistent on the point. Transformations that sustain are the ones that upskill broadly across the organisation (leaders, middle managers, the wider workforce), not the ones that train a small cohort of early users on a single tool.

If you train only the pilot cohort, you've created a capability island. The rest of the organisation watches from the outside, often with mistrust or quiet resentment. When the pilot tries to scale, it scales into a workforce that has none of the same context, language, or comfort with the technology. Most of the time it stalls.

If you upskill broadly first, building genuine AI literacy, judgement, and confidence across the population rather than vendor-specific training tied to one tool, the pilot lands into something more capable. People who weren't in the cohort understand what's being attempted and why. They have the capability to absorb the change when it scales. They have opinions worth listening to.

Empower the workforce broadly and the pilot tends to stick. Train only the cohort and you've built an island. Islands don't scale.

Practical version

If you want to measure people success alongside (or before) pilot success, the move isn't exotic:

Measure evidenced behaviour, not just self-reported confidence. What people say they do and what they actually do are two different data sets. You need both.
Measure capability shift, not licence count. Can people use AI on harder tasks this quarter than last? Can they spot a bad output? Are they teaching colleagues?
Measure where AI is being used, not just how often. Use on low-stakes admin is not the same signal as use on judgement-heavy work.
Measure the absence. Where is AI conspicuously not being used? What does that tell you about trust, capability, or fit?

Build broad capability, not just pilot-cohort training. AI literacy, judgement, and confidence across the workforce. The pilot lands into something then, rather than onto an island.

None of that is new. The same kind of measurement we'd apply to any workforce transition. We just don't apply it to AI, because the technology has its own metrics and the technology team owns the rollout.

Which is how we keep ending up in the 95%.

The bit nobody puts on the dashboard

If your AI programme is technically on track but somehow not producing the shift you were promised, look at what you're measuring. The dashboard might be telling you the pilot is fine. The behaviour underneath will tell you something different.

That gap is where the work is. And until we treat it as the actual work rather than something to come back to after the rollout, the failure rate isn't going to budge.

alterNOTION works with organisations treating AI as a workforce transition, not a tool deployment. See how we approach AI adoption.

The missing middle: why the 'glue' between strategy and delivery makes or breaks change

Mon, 02 Mar 2026 12:39:50 GMT

The gap that kills more change programmes than bad strategy ever will

Here's a pattern I see over and over again: brilliant strategy at the top, solid project management at the bottom, and a gaping hole in the middle where the real work of change should be happening.

The strategy deck is polished. The project plans are detailed. The governance structure is in place. But six months in, nothing's really moving. People are going through the motions, but the change isn't taking hold.

What's missing? The glue. The bit that connects the big picture to the day-to-day reality of making it happen.

The theory gets it right (sort of)

Change management theory has been telling us this for decades. Kotter talks about creating urgency and building coalitions . The ADKAR model breaks it down into awareness, desire, knowledge, ability, and reinforcement. Bridges focuses on helping people through the emotional journey of transition.

All of these frameworks point to the same truth: there's a critical space between deciding to change and actually changing. But in practice, we often skip straight from strategy to implementation, treating this middle bit as administrative detail rather than the make-or-break moment it actually is.

I've lost count of how many times I've heard: "We've got the strategy sorted, now we just need to roll it out." As if rolling it out is the easy part.

What lives in the glue

So what actually happens in this middle space? It's where strategy meets reality. Where the neat PowerPoint slides bump up against the messy truth of how work actually gets done.

It's where someone has to figure out what "being more customer-centric" actually means for the person answering the phones on a Monday morning. It's where "agile ways of working" gets translated into "here's what your Tuesday will look like differently."

This is where we work out:

What exactly needs to change in people's daily experience?

Who needs to do what differently, and how will they know they're doing it right?

What's going to get in the way, and how do we help people navigate that?

How do we keep momentum going when the initial excitement wears off?

The human translation layer

The glue isn't just about project management or communications. It's about human translation. Taking the strategic intent and making it make sense in the context of real people's real jobs.

I remember working with a team that was supposed to "collaborate more effectively across silos." Beautiful strategy. Clear business case. But when we dug into it, nobody could actually describe what better collaboration would look like in practice. What meetings would be different? What decisions would get made by whom? What would change about how they started their day?

Without that translation, people default to what they've always done. Not because they're resistant to change, but because they literally don't know what else to do.

When the glue goes missing

When we skip this middle bit, we get what I call "zombie change programmes." They look alive from the outside—there are regular updates, RAG status reports, and milestone celebrations. But nothing's really different for the people doing the work.

The classic signs are:

Training gets delivered but behaviours don't shift
New processes exist on paper but the old ways persist
People can recite the vision but can't see how it applies to them
Early wins happen but momentum fizzles out

The theory warned us this would happen. Kotter's research showed that most change efforts fail because we don't create enough urgency or build broad enough coalitions. ADKAR tells us that knowledge without ability equals frustration. But somehow we keep acting surprised when it happens.

Getting the glue right

The organisations that get this right treat the middle space as seriously as they treat strategy development. They invest time in working out the human side of the equation. They prototype new ways of working before rolling them out. They pay attention to the stories people are telling themselves about the change.

This might look like:

Spending time with people in their actual work environment to understand what really needs to shift

Creating small experiments to test what the change feels like in practice

Building feedback loops so you can adjust course based on what's actually happening

Training managers to have conversations about change, not just deliver messages about it

Celebrating the right behaviours, not just the right milestones

It's not glamorous work. It doesn't make for exciting presentations. But it's where change actually happens.

The reality check

You can have the most brilliant strategy in the world, but if you can't translate it into something that makes sense in people's daily reality, it's just expensive wallpaper.

The glue between strategy and delivery isn't optional. It's not something you can outsource to the communications team or tick off with a training programme. It's the work of change itself.

If your change programme is technically on track but somehow feels stuck, look at your glue. Are you helping people understand not just what's changing, but how to actually live it?

Want to see how alterNOTION approaches this messy middle space? Our case studies show what happens when you take the human translation work as seriously as the strategy itself.

Why systems change needs a people approach

Mon, 02 Feb 2026 12:39:52 GMT

What I've learned from watching change programmes succeed and fail

Here's what I've learned after years of watching change programmes succeed and fail: the ones that crash and burn rarely do so because the strategy was wrong. They fail because somewhere along the way, we forgot that systems are just people doing things together.

I've sat in too many rooms where brilliant minds have crafted perfect models and frameworks, only to watch them gather dust because no one stopped to ask: "But how will Business Partners actually use this? What will it mean for the team in Manilla? How will this land on a Tuesday afternoon when everyone's already stretched thin?"

That's the gap where most change efforts die.

People aren't implementation details

When we're redesigning how an organisation works—whether that's a new operating model, rolling out agile ways of working, or bringing two companies together—we're asking human beings to change how they think, act, and feel about their work. That's massive.

Yet somehow we expect this to happen through email updates, process maps, and the occasional all-hands meeting. It doesn't work that way.

Real change happens when people trust the process and the people leading it. It happens through actual conversations, not one-way communications. It happens when people can see themselves in the future you're describing and believe they can get there from where they are now.

The changes that stick are the ones people live

I've watched beautifully planned programmes fall apart because no one thought about what it would actually feel like to be the person trying to make it work. And I've seen messy, uncertain journeys succeed because the leaders were honest about what they didn't know and clear about what they did.

This isn't about throwing out good planning. It's about planning with the people who'll be affected, not just for them.

Being people-focused isn't being soft

Let me be clear: putting people first doesn't mean avoiding hard decisions or moving slowly. It means understanding what motivates people, what worries them, and what they need to succeed. When you get that right, you actually move faster and with far fewer nasty surprises.

The questions I find myself asking are:

What story is running in people's heads about this change right now?
What new behaviours do we need to see, and what's going to make those feel impossible?
How do we make this feel like something people can actually do, rather than something being done to them?

What this actually looks like

In practice, this means things like involving the people most affected in shaping the change from early on. It means using visual tools that help people engage with complexity rather than be overwhelmed by it. It means working with teams to figure out what good looks like in their world, not just on paper.

It means leaders who show up and stay engaged, not just at the launch event. And it means creating real space for people to push back, ask questions, and help make course corrections along the way.

This isn't a checklist to work through. It's a different way of thinking about how change happens.

The reality check

You can't transform systems if you ignore the humans who make them work. And you can't create lasting change unless people are genuinely willing and able to make it happen.

If your strategy makes sense but nothing's really moving, maybe it's time to look at it through a different lens. Start with understanding your people—really understanding them. The rest has a much better chance of following.

That's what I've learned, anyway. And it's why alterNOTION exists.

Beyond broadcast: why knowledge hubs are the unsung heroes of change communications

Fri, 02 Jan 2026 13:42:13 GMT

I've been in too many change programmes where communications feels like shouting into the void. Beautiful newsletters, polished videos, carefully crafted emails—all sent out into the organisation with the hope that somehow, the right information will reach the right people at the right time.

Spoiler alert: it rarely does.

Then someone asks a perfectly reasonable question in week six of the programme, and you realise they've completely missed three crucial pieces of information that were "clearly communicated" in previous updates. Or worse, they got the information but couldn't make sense of how it applied to their specific situation.

That's when I learned the hard truth about change communications: broadcasting information isn't the same as creating understanding.

What the theory tells us about information flow

Change management theory has been trying to tell us this for years. Kotter emphasises the need for communication that's not just frequent, but also accessible and relevant to people's daily experience . His research shows that transformation efforts fail when people can't connect the dots between the big picture and their own role.

The ADKAR model is even more specific about this. It breaks down the knowledge component into knowing what to change, how to change, and why change is needed. But here's the thing—people don't need all of that information at once, and they certainly don't need it in the same format or at the same time.

Nudge theory adds another layer to this. It shows us that the way information is presented and accessed dramatically affects whether people actually use it.

Small changes in how we make information available can have huge impacts on behaviour.

Yet most change communications still follows the old broadcast model: we decide what people need to know, package it up, and send it out. Job done, right?

The reality of how people actually consume information

Here's what I've learned from watching people navigate change: they don't consume information linearly. They don't read everything in order. They don't remember details from that email three weeks ago when they suddenly need them on a Thursday afternoon.

What they do is search. They ask colleagues. They try to piece together fragments of information to answer the specific question they have right now. And when they can't find what they need quickly, they either make it up or give up.

I remember working with a team going through a major system change. Despite months of communications, people were still unclear about basic processes. When we dug deeper, we found that the information existed—it was just scattered across dozens of emails, buried in slide decks, or sitting in documents people couldn't find.

The breakthrough came when we created a simple knowledge hub where people could actually search for answers to their specific questions. Suddenly, the same information that had been ignored in emails became genuinely useful.

What makes knowledge hubs different

A proper knowledge hub isn't just a document repository. It's a living, searchable resource that's designed around how people actually look for information when they're trying to get things done.

The best ones I've seen have a few things in common:

Information is organised around people's questions, not organisational structure
Content is written in plain language that actually makes sense
There's a search function that works the way people naturally think about problems
Popular questions are easy to find without searching
It's updated regularly and clearly shows what's new or changed

But the real magic happens when you treat it as a conversation starter, not a conversation ender. When people can find most of what they need but also know where to go for the things that require human input.

The ripple effect of getting this right

When people can actually find the information they need, something interesting happens. The quality of questions gets better. Instead of asking "What's changing?" they ask "How do I handle this specific situation differently?"

Managers stop feeling like human search engines, constantly answering the same basic questions. They can focus on helping people work through the trickier aspects of change—the stuff that requires judgement and context.

And here's the bit that surprised me: people actually start engaging more with the change itself. When information is accessible and useful, they're more likely to take ownership of understanding their role in making it happen.

Beyond FAQs: making knowledge work

The temptation is to create a fancy FAQ section and call it done. But the knowledge hubs that really work go deeper than that. They anticipate the questions people don't even know they should be asking. They provide context, not just facts. They show examples of what good looks like, not just what the policy says.

I've seen teams create video walkthroughs for complex processes, decision trees for common scenarios, and even simple flowcharts that help people figure out which bit of information applies to their situation.

The key is thinking like the person who needs the information, not the person who has it.

The human side of information architecture

This isn't just about technology or information design. It's about understanding that in times of change, people's relationship with information gets complicated. They're often dealing with uncertainty, cognitive overload, and competing priorities.

A good knowledge hub recognises this. It doesn't just store information—it makes information genuinely useful for people who are trying to navigate unfamiliar territory while still getting their day job done.

The reality check

You can have the most compelling change story in the world, but if people can't find the practical information they need to act on it, you're stuck.

Change communications isn't just about inspiring people or keeping them informed. It's about enabling them to actually do something different. And that requires information that's not just available, but accessible, relevant, and useful in the moment they need it.

If your change programme has great messages but people are still confused about the basics, it might be time to look at how information actually flows in your organisation. Are you broadcasting, or are you building understanding?

What happens when people can actually find the answers they need

Something quietly powerful shifts.

People stop feeling wrong for not remembering an email from three weeks ago. They stop second-guessing themselves. They stop interrupting their day, or their manager’s, to ask questions they suspect they should already know the answer to.

Instead, they get on with the job.

When information is easy to find and easy to understand, confidence goes up. Not the loud, chest-beating kind. The practical kind. The kind that shows up as fewer workarounds, better decisions, and calmer conversations. You see it in small moments first. A new starter who finds the right process without asking. A manager who uses a shared decision guide rather than inventing a local rule. A team that spends its meeting time solving problems instead of clarifying basics. None of this makes headlines, but it is exactly what progress looks like.

The incremental value

From an organisational point of view, the benefits compound. Support tickets drop. Inbox traffic slows. Subject-matter experts get their time back. Change teams stop playing whack-a-mole with the same questions dressed up in slightly different words.

More importantly, trust improves. When people can reliably find accurate, up-to-date answers, they start to believe the organisation has thought this through. That it respects their time. That it understands how work actually happens.

And that is where engagement really comes from. Not from another beautifully designed broadcast, but from the quiet reassurance that when you need to know something, the answer is there, it makes sense, and it helps you act.

At alterNOTION , this is why we put as much effort into information architecture as we do into change narratives. Because the story might spark intent, but it is accessible knowledge that turns intent into action. If you want people to change how they work, start by making it easier for them to find out how.

alterNOTION Blog

Crafting what's next

The challenge

The approach

The delivery

The shift

The impact

An organisation already performing well is now positioned to sustain that performance through significant leadership and operating model change.

Built to land

Restructuring a finance function without losing what makes it work

The challenge

The approach

The delivery

The shift

The impact

Capability by design

From execution to enterprise impact

The challenge

The approach

The delivery

The shift

The impact

The future

The AI pilot trap

The numbers we like to quote

AI doesn't arrive as a transformation

What the dashboards count

What the dashboards don't count

The perception gap

Why people success has to come first

Upskill the workforce, not just the cohort

Practical version

The bit nobody puts on the dashboard

The missing middle: why the 'glue' between strategy and delivery makes or breaks change

The gap that kills more change programmes than bad strategy ever will

The theory gets it right (sort of)

What lives in the glue

The human translation layer

When the glue goes missing

Getting the glue right

The reality check

Want to see how alterNOTION approaches this messy middle space? Our case studies show what happens when you take the human translation work as seriously as the strategy itself.

Why systems change needs a people approach

What I've learned from watching change programmes succeed and fail

People aren't implementation details

The changes that stick are the ones people live

Being people-focused isn't being soft

What this actually looks like

The reality check

Beyond broadcast: why knowledge hubs are the unsung heroes of change communications

What the theory tells us about information flow

The reality of how people actually consume information

What makes knowledge hubs different

The ripple effect of getting this right

Beyond FAQs: making knowledge work

The human side of information architecture

The reality check

What happens when people can actually find the answers they need

The incremental value

Curious about how we approach knowledge sharing in complex change programmes? Contact us today .