How to avoid the AI fizzle
In the 1990s, Business Process Reengineering (BPR) was the Big Bet. Companies launched tightly controlled pilot programs with hand-picked teams, custom software, and executive backing. The results dazzled on paper.
But when it came time to scale? Reality hit. People weren’t ready. Systems didn’t connect. Budgets dried up. The pilot became a cautionary tale, not a blueprint.
We’ve seen this before with Lean, Agile, even digital transformations. Now it’s happening again with AI, only this time, the stakes are different. Because we’re not just implementing a new solution, we’re building into a future that’s unfolding. Technology is evolving faster than most organizations can learn, govern, or adapt right now. That uncertainty doesn’t make transformation impossible, but it does make it easier to get wrong.
And the dysfunction is already showing up, just in two very different forms.
Two roads to the same cliff
Today, we see organizations falling into two extremes. Most companies are either overdoing the control or letting AI run wild.
Road 1: The free-for-all
Everyone’s experimenting. Product teams are building bots, prompting, using copilots. Finance is trying automated reporting. HR has a feedback chatbot in the works. Some experiments are exciting. Most are disconnected. There's no shared vision, no scaling pathway, and no learning across the enterprise. It’s innovation by coincidence.
Road 2: The forced march
Leadership declares an AI strategy. Use cases are approved centrally. Governance is tight. Risk is managed. But the result? An impressive PowerPoint, a sanctioned use case, and very little broad adoption. Innovation is constrained before it ever reaches the front lines.
Two very different environments. Same outcome: localized wins, system-wide inertia.
The real problem: Building for optics, not for scale
Whether you’re over-governing or under-coordinating, the root issue is the same: designing efforts that look good but aren’t built to scale.
Here’s the common pattern:
- A team builds something clever.
- It works in their context.
- Others try to adopt it.
- It doesn’t stick.
- Momentum dies. Energy scatters. Or worse, compliance says no.
Sound familiar?
It’s not that the ideas are flawed. It’s that they’re built in isolation with no plan for others to adopt, adapt, or scale them. There’s no mechanism for transfer, no feedback loops for iteration, and no connection to how people actually work across the organization.
So, what starts as a promising AI breakthrough (a smart bot, a helpful copilot, a detailed series of prompts, a slick automation) quietly runs out of road. It works for one team or solves one problem, but without a handoff or playbook, there’s no way for others to plug in. The system stays the same, and the promise of momentum fades, lost in the gap between what’s possible and what’s repeatable.
We’ve seen this before
These aren’t new problems. From BPR to Agile, we’ve learned (and re-learned) that:
- Experiments are not strategies. Experiments show potential, not readiness for adoption. Without a plan to scale, they become isolated wins; interesting, but not transformative.
- Culture is the operating system. If the beliefs, behaviors, and incentives underneath aren’t aligned, the system breaks, no matter how advanced the tools.
- Managers matter. Without their ownership and support, change stalls.
- Behavior beats code. Tools don’t transform companies. People do.
Design thinking promised to bridge this gap with user-driven iteration and empathy. But in practice? Most efforts skip the hard parts. We tinker, test, and move on, without ever building the conditions for adoption.
AI and the new architecture of work
Many organizations treat AI like an add-on—as if it’s something to bolt onto existing systems to boost efficiency. But AI isn’t just a project or a tool; it changes the rules of how decisions are made, how value is created, and what roles even exist. It’s an inflection point that forces companies to rethink how work gets done.
Companies making real progress aren’t just chasing use cases. They’re rethinking how their organizations operate, end to end. They’re asking:
- Have we prepared people to reimagine how they work with AI, not just how to use it?
- Are we redesigning workflows, decision rights, and interactions—not just layering new tech onto old routines?
- Do we know what success looks like when it’s scaled and sustained, not just when it dazzles?
If the answer is no, whether you’re too loose or too locked down, you’re not ready.
The mindset shift AI demands
AI isn’t just a tech rollout. It’s a mindset shift that asks leaders to reimagine how value gets created, how teams operate, and how people grow. But that reimagination isn’t about the tools. The tools will change—rapidly. It starts with new assumptions, new stances, and a new internal leader compass.
Here are three essential mindset shifts every leader must make, not just to keep up with AI but to stay relevant in a world being reshaped by it:
1. From automation to amplification
Old mindset: AI automates tasks and cuts costs.
New mindset: AI expands and amplifies human potential, enhancing our ability to think strategically, learn rapidly, and act boldly. The question isn’t what AI can do instead of us, but what it can do through us—helping people make better decisions, move faster, and focus on higher-value work.
2. From efficiency to reimagination
Old mindset: How can we use AI to make current processes more efficient?
New mindset: What would this process look like if we started from zero with AI as our co-creator, not a bolt-on?
3. From implementation to opportunity building
Old mindset: Roll out the tool. Train everybody. Check the box.
New mindset: AI fluency is a core human capability that creates new realms of curiosity, sophistication in judgment, and opportunity thinking. Soon, AI won’t be a one-time training. It will be part of how we define leadership, collaboration, and value creation.
From sparkles to scale
In most organizations, the spark isn’t the problem. Good ideas are everywhere. What’s missing is the ability to translate those isolated wins into something durable, repeatable, and enterprise-wide.
Too many pilots are built to impress, not to endure. They dazzle in one corner of the business but aren’t designed for others to adopt, adapt, or sustain. The result? Innovation that stays stuck in the lab—or dies.
Designing for scale means thinking beyond the “what” to the “how”:
- How will this spread?
- What behaviors and systems need to change?
- Can this live in our whole world, not just my sandbox?
It’s not about chasing the next use case. It’s about setting up the conditions that allow innovation to take root, grow, and multiply, without starting from scratch every time.
Here’s how to make that shift:
1. Test in the wild, not just in the lab
Skip the polished demo. Put your solution in the hands of real users, in real conditions, with all the friction that comes with it. Use messy data. Invite resistance. That’s where the insights live, and where scale begins. If it only works in ideal settings, it doesn’t work.
2. Mobilize managers
Executives sponsor. Front lines experiment. But it’s team leaders who connect and spread. Equip them as translators and expediters, not blockers. Every leader is a change leader.
3. Hardwire behaviors, not just tools
The biggest unlock in AI is not the model—it’s the muscle. Invest in shared language, habits, and peer learning that support new ways of working. Focus on developing behaviors that scale, such as:
- Change readiness: the ability to spot opportunity, turn obstacles into possibilities, and help teams pivot.
- Coaching: getting the best out of your AI “co-workers” just like human ones.
- Critical thinking: applying human judgment where it matters most—context, nuance, and ethics.
4. Align to a future-state vision
To scale beyond one-off wins, people need a shared sense of where they’re headed. A clear future-state vision acts as an enduring focus, allowing everyone to innovate in concert. That alignment doesn’t stifle innovation. It multiplies it, turning a thousand disconnected pilots into a coherent transformation.
5. Track adoption, not just “wins”
Don’t mistake a shiny, clever prompt for progress. A great experiment means nothing if it can’t be repeated by many people. From day one, design with scale in mind: Can this be adopted elsewhere? What would need to change for it to work across teams, roles, or regions? Build for transfer, not just applause.
The real opportunity
AI will not fail because the tech wasn’t good enough. It will fail because we mistook experiments for solutions, or because we governed innovation into paralysis.
You don’t need more control. You don’t need more chaos. You need design for scale, not just scale in hindsight.
Let’s stop chasing sparkles. Let’s build systems that spread.
Related content
Most sales meetings don’t fail.
They just don’t lead to a decision.
And that’s where value is lost.
Today’s customers are more informed, more selective, and more time-poor.
They don’t need more product pitches.
They need conversations that help them prioritize, decide, and move forward.
And yet, 58% of sales meetings fail to create real value.
Not because sellers lack capability, but because conversations are not designed to move decisions forward.
“Customers don’t act on every need they recognize.
They act when something becomes a priority.”
In this short executive brief, you’ll discover:
- Why most conversations inform… but don’t drive action
- What actually makes customers prioritize and move
- How to create urgency without damaging trust
- The shift from presenting solutions to enabling decisions
- What separates conversations that stall from those that accelerate momentum
If your teams are experiencing stalled deals, delayed decisions, or slow pipeline movement, this brief will help you understand why, and what to do differently.
Download the Executive Brief and learn how to design conversations that actually move decisions forward
Global spending on AI is forecast to reach $2.52 trillion by 2026, a 44% year-over-year increase, according to Gartner. At the same time, only about 10% of AI pilots scale beyond proof of concept.
What’s the disconnect?
Why aren’t most organizations seeing the ROI they hoped for, despite making such large investments?
It’s not because the technology isn’t ready. And it’s not because the use cases are unclear.
The disconnect exists because many organizations are investing in AI as a technology upgrade and expecting a business transformation in return.
The tools are advancing at breathtaking speed, and most organizations already have AI in motion. But the work itself often stays the same. AI gets layered onto existing tasks instead of being used to rethink workflows end to end. Adoption metrics go up, while decisions, operating models, and value creation remain largely untouched.
When teams first start using AI, they do what makes sense. They try to recreate today, just faster. Can it help me write this? Analyze that? Save a bit of time?
That’s a smart place to begin. But it’s not where ROI, or reinvention, actually shows up.
Getting over the hump
Real returns begin when teams experience what we often call “getting over the hump.”
This is the moment when two things click at once:
- AI can fundamentally change how work gets done.
- People don’t need deep technical expertise to make that change happen.
When teams see weeks of work compress into hours, or watch an end-to-end workflow suddenly run in a new way, something shifts. Confidence replaces hesitation. Curiosity replaces caution. The questions change, from “How do I use this tool?” to “What’s possible now?”
That shift matters, because ROI doesn’t come from using AI more often, it comes from using it to work differently.
Why ROI stalls as AI scales
As AI initiatives expand, many organizations discover that the limiting factor isn’t the technology itself. It’s the environment surrounding the work.
ROI shows up when teams are able to explore and redesign workflows, not just automate steps. That requires clarity on outcomes and guardrails, but also room to experiment, learn, and iterate. When AI is tightly controlled or narrowly deployed, pilots stay pilots. When people are trusted to rethink how work happens, value starts to compound.
Organizations that unlock ROI don’t chase perfect use cases upfront. They focus on learning faster and applying those insights where they matter most.
The early signal that ROI is coming
Long before AI shows up in financial results, there’s an earlier indicator that organizations are on the right path.
People are energized by the work.
You see it when teams start sharing experiments, when ideas move across functions, and when learning becomes visible rather than hidden. Progress feels owned, not imposed.
That energy isn’t accidental. It’s a signal that people feel trusted to rethink how work happens, and that trust is essential to turning investment into impact.
Reinvention happens closer to the work than most expect
AI reinvention rarely starts with a sweeping rollout or a multi-year roadmap. More often, it begins with one meaningful workflow, one team close to the work, and a willingness to ask a different question.
With the right support, that team gets over the hump. What they learn becomes reusable. Patterns emerge. Over time, those insights connect, creating enterprise-wide impact and sustained ROI.
That’s how organizations move from isolated pilots to real returns.
What this means for AI investment
No organization feels fully “caught up” with AI, and that’s true across industries.
The organizations that will realize ROI aren’t waiting for certainty or the next breakthrough tool. They’re reinvesting their AI spend into new ways of working that scale human potential alongside technology.
Handled thoughtfully, AI doesn’t distance people from the work. It brings them closer - to better decisions, stronger collaboration, and better outcomes.
For many organizations, that’s where the real return begins.
Technology choices are often made under pressure - pressure to modernize, to respond to shifting client expectations, to demonstrate progress, or to keep pace with rapid advances in AI. In those moments, even experienced leadership teams can fall into familiar traps: over-estimating how differentiated a capability will remain, under-estimating the organizational cost of sustaining it, and committing earlier than the strategy or operating model can realistically support.
After decades of working with leaders through digital and technology-enabled transformations, I’ve seen these dynamics play out again and again. The issue is rarely the quality of the technology itself. It’s the timing of commitment, and how quickly an early decision hardens into something far harder to unwind than anyone intended.
What has changed in today’s AI-accelerated environment is not the nature of these traps, but the margin for error. It has narrowed dramatically.
For small and mid-sized organizations, the consequences are immediate. You don't have specialist teams running parallel experiments or long runways to course correct. A single bad platform decision can absorb scarce capital, distort operating models, and take years to unwind just as the market shifts again.
AI intensified this tension. It is wildly over-hyped as a silver bullet and quietly under-estimated as a structural disruptor. Both positions are dangerous. AI won’t magically fix broken processes or weak strategy, but it will change the economics of how work gets done and where value accrues.
When leaders ask how to approach digital platforms, AI adoption, or operating model design, four questions consistently matter more than the technology itself.
- What specific market problem does this solve, and what is it worth?
- Is this capability genuinely unique, or is it rapidly becoming commoditized?
- What is the true total cost - not just to build, but to run and evolve over time?
- What is the current pace of innovation for this niche?
For many leadership teams, answering these questions leads to the same strategic posture. Move quickly today while preserving options for tomorrow. Not as doctrine, but as a way of staying adaptive without mistaking early commitment for strategic clarity.
Why build versus buy is the wrong starting point
One of the most common traps organizations fall into is treating digital strategy as a series of isolated build-vs-buy decisions. That framing is too narrow, and it usually arrives too late.
A more powerful question is this. How do we preserve optionality as the landscape continues to evolve? Technology decisions often become a proxy for deeper organizational challenges. Following acquisitions or periods of rapid change, pressure frequently surfaces at the front line. Sales teams respond to client feedback. Delivery teams push for speed. Leaders look for visible progress.
In these moments, technology becomes the focal point for action. Not because it is the root problem, but because it is tangible.
The real risk emerges operationally. Poorly sequenced transitions, disruption to the core business, and value that proves smaller or shorter-lived than anticipated. Teams become locked into delivery paths that no longer make commercial sense, while underlying system assumptions remain unchanged.
The issue is rarely technical. It is temporal.
Optimizing for short-term optics, particularly client-facing signals of progress, often comes at the expense of longer-term adaptability. A cleaner interface over an ageing platform may buy temporary parity, but it can also delay the more important work of rethinking what is possible in the near and medium term.
Conservatism often shows up quietly here. Not as risk aversion, but as a preference for extending the familiar rather than exploring what could fundamentally change.
Licensing as a way to buy time and insight
In fast-moving areas such as AI orchestration, many organizations are choosing to license capability rather than build it internally. This is not because licensing is perfect. It rarely is. It introduces constraints and trade-offs. But it was fast. And more importantly, it acknowledged reality.
The pace of change in this space is such that what looks like a good architectural decision today may be actively unhelpful in twelve months. Licensing allowed us to operate right at the edge of what we actually understood at the time - without pretending we knew where the market would land six or twelve months later.
Licensing should not be seen as a lack of ambition. It is often a way of buying time, learning cheaply, and avoiding premature commitment. Building too early doesn’t make you visionary, often it just makes you rigid.
AI is neither a silver bullet nor a feature
Coaching is a useful microcosm of the broader AI debate.
Great AI coaching that is designed with intent and grounded in real coaching methodology can genuinely augment the experience and extend impact. The market is saturated with AI-enabled coaching tools and what is especially disappointing is that many are thin layers of prompts wrapped around a large language model. They are responsive, polite, and superficially impressive - and they largely miss the point.
Effective coaching isn’t about constant responsiveness. It’s about clarity. It’s about bringing experience, structure, credibility, and connection to moments where someone is stuck.
At the other extreme, coaches themselves are often deeply traditional. A heavy pen, a leather-bound notebook, and a Royal Copenhagen mug of coffee are far more likely to be sitting on the desk than the latest GPT or Gemini model.
That conservatism is understandable - coaching is built on trust, presence, and human connection - but it’s increasingly misaligned with how scale and impact are actually created.
The real opportunity for AI is not to replace human work with a chat interface. It is to codify what actually works. The decision points, frameworks, insights, and moments that drive behavior change. AI can then be used to augment and extend that value at scale.
A polished interface over generic capability is not enough. If AI does not strengthen the core value of the work, it is theatre, not transformation.
What this means for leaders
Across all of these examples, the same pattern shows up.
The hardest decisions are rarely about capability, they are about timing, alignment, and conviction.
Building from scratch only makes sense when you can clearly articulate:
- What you believe that the market does not
- Why that belief creates defensible value
- Why you’re willing to concentrate risk behind it
Clear vision scales extraordinarily well when it’s tightly held. The success of narrow, focused Silicon Valley start-ups is testament to that.
Larger organizations often carry a broader set of commitments. That complexity increases when depth of expertise is spread across functions, and even more so when sales teams have significant autonomy at the point of sale. Alignment becomes harder not because people are wrong, but because too many partial truths are competing at once.
In these environments, strategic clarity, not headcount or spend, creates advantage.
This is why many leadership teams choose to license early. Not because building is wrong, but because most organizations have not yet earned the right to build.
Related content
¿Se puede cambiar la cultura de una organización?
Hoy en día, hay pocas organizaciones que no se encuentren inmersas en uno (o varios) procesos de transformación cultural. Nuevas formas de trabajar en organizaciones más planas y adaptativas, mejoras en la cultura de seguridad, orientar la organización hacia sus clientes, transformaciones de las áreas comerciales, mejora de la excelencia operativa, por citar algunas.
Y es aquí donde viene una de las grandes preguntas:
¿se puede cambiar la cultura de una organización? Y, si es así, ¿cómo se hace?
Para ayudar a responder a estas preguntas, que a menudo nos hacen nuestros clientes y sobre las que hay mucho escrito, me gustaría compartir lo que en BTS hemos aprendido en los últimos 38 años sobre qué funciona y qué no (hasta ahora, que en esto de los cambios culturales uno nunca deja de aprender).
La buena noticia es que la respuesta a la pregunta de si se puede cambiar la cultura de una organización es sí.
La dificultad viene al responder a la segunda: ¿cómo se hace?
¿Un proyecto? ¿Una iniciativa?
Un punto importante a considerar es que los procesos de cambio o transformación cultural no son un proyecto con un inicio y un fin; es un proceso en constante evolución. Y esto es algo que en ocasiones genera tensión en las organizaciones, a menudo acostumbradas a un enfoque basado en proyectos.
¿Qué es crítico y a menudo se suele ignorar?
Hay una serie de elementos que, si se tienen en cuenta y se utilizan adecuadamente, harán que los esfuerzos de transformación sean mucho más eficaces. Desafortunadamente, muchas veces se ignoran.
Estos elementos críticos son:
- Involucrar a la gente. Cuanto más se hace partícipes de la transformación a las personas (a todos los niveles), más altas son las probabilidades de que implementen los cambios requeridos.
- Para entender el cambio hay que tangibilizarlo y experimentarlo. Consiste en conectar el marco teórico con acciones del día a día. Explicar la foto completa con transparencia es clave.
- Todos los cambios traen consigo cosas positivas, pero también tienen impactos negativos. Explicar la foto completa con transparencia es clave.
- Cambiar la cultura implica tiempo y requiere identificar y cambiar los “mindsets” y las estructuras diarias (símbolos) que definen cómo se hacen las cosas en la organización.
- La cultura debe estar fuertemente conectada con la estrategia.
¿Cómo recomendamos estructurar los procesos de cambio cultural?
Nuestro enfoque se compone de cuatro etapas: establecer resultados, crear líderes de cambio, incrustar cambios clave y sostener las nuevas formas de trabajo.
1. Establecer resultados
El primer paso en cualquier proceso de transformación es establecer resultados claros. Es crucial identificar los impulsores de la transformación y definir los resultados deseados de manera que se logre un verdadero alineamiento a nivel ejecutivo. A medida que se avanza, hay que conectar los puntos entre el propósito y la visión, entendiendo de dónde se viene, dónde se está y hacia dónde se quiere avanzar. Además, es esencial conectar la transformación con los objetivos organizacionales.
Algunas acciones relevantes de esta fase son:
- Recopilación de información (entrevistas, focus groups, visitas a operaciones,…)
- Diagnósticos culturales
- Definición de expectativas (Leadership Profiles
2. Crear líderes de cambio
En BTS creemos que todos los líderes son también líderes de cambio. Adoptar una mentalidad de “líder de cambio” requiere que los líderes experimenten y vean lo que se espera de ellos. Desde el inicio, es vital impulsar a la acción con ‘trabajo real’, como establecer nuevas prioridades y comunicar de forma transparente y eficaz.
Hay que comprometer (emocional y racionalmente) a los líderes con el cambio y hacerles ver cómo pueden impactar en la cultura a través de acciones concretas en el día a día.
Por último, es necesario proporcionar apoyo continuo para los cambios de mentalidad y comportamiento más difíciles y recoger retroalimentación sobre lo que funciona y lo que no en esta etapa.
Algunas acciones relevantes de esta fase son:
- Elaboración de Playbooks para roles críticos
- Despliegue de programas de liderazgo y cambio
- Feedback loops con los niveles ejecutivos
3. Incrustar cambios clave
Para lograr un cambio significativo, es esencial identificar los modelos mentales actuales y ofrecer nuevos que apoyen el estado deseado. Crear rutinas y símbolos que refuercen el cambio, así como identificar procesos, prácticas, eventos o normas ancladas en las viejas formas de trabajar, es crucial.
Cocrear nuevas formas de trabajo para su activación inmediata ayuda a cimentar estos cambios. A medida que se avanza, cambiar los sistemas y procesos que soportan y refuerzan los cambios cruciales es fundamental para el éxito a largo plazo.
Algunas acciones relevantes de esta fase son:
- Coaching a líderes
- Montar Sprints culturales
- Cascadear el cambio al resto de la organización
- Assessments para medir cambios de comportamientos
4. Sostener las nuevas formas de trabajo
El cambio no es solo un esfuerzo individual, sino también un fenómeno social. Por ello hay que proveer de las redes sociales necesarias para apoyar los cambios de mentalidad y comportamiento. Intervenir con apoyo individual para roles críticos y períodos específicos, así como incorporar nuevas formas de trabajo, asegura la continuidad del cambio.
Por último, hay que utilizar datos para analizar lo que funciona y lo que no, permitiendo crear el siguiente conjunto de intervenciones y apoyo necesarios.
Algunas acciones relevantes de esta fase son:
- Integración de los Playbooks en el ciclo de talento de la organización
- Practica de los nuevos comportamientos en el día a día con bots potenciados por IA
- Diseño de una oficina para monitorizar el cambio y definir nuevas acciones
- Diseño y lanzamiento de Comunidades de Práctica (CoP)
La importancia de ser paciente e impaciente a la vez
Los procesos de transformación cultural son uno de los elementos más retadores, ya que nunca existe una receta única.
Ser estratégicamente paciente (teniendo claros esos resultados deseados y evitando dar bandazos), pero tácticamente impaciente (realizando acciones en las fases expuestas anteriormente y viendo qué funciona y qué no, para pivotar y corregir) es clave en los procesos de transformación.
El enfoque de las 4 fases ayuda a ello, posibilitando que estos viajes se conviertan en una experiencia enriquecedora para la organización, y no en un dolor de los que dejan cicatriz en la memoria colectiva.
Este es solo un resumen.
Si quieres profundizar en el enfoque completo, ejemplos y claves prácticas:
Descarga el PDF completo y accede a todo el contenido.
En todos los sectores, la seguridad está experimentando un cambio estructural. Lo que antes se gestionaba principalmente como una función de cumplimiento o una métrica de desempeño se entiende cada vez más como un reflejo de cómo las organizaciones están diseñadas, lideradas y mejoradas de forma continua.
En entornos complejos y de alto riesgo, la seguridad no se logra únicamente mediante un mayor control o programas adicionales. Surge de la interacción entre el comportamiento del liderazgo, el diseño operativo, los entornos de decisión y la capacidad de la organización para aprender y adaptarse.
Basándonos en la ciencia global de la seguridad, el enfoque de Human & Organizational Performance (HOP), la investigación sobre seguridad psicológica y nuestra experiencia en transformación en múltiples industrias, identificamos ocho cambios clave que están definiendo la próxima evolución de la cultura de seguridad.
1. La seguridad como valor organizacional central
La seguridad está dejando de tratarse como una prioridad cambiante. Las prioridades compiten. Los valores guían.
Cuando la seguridad se convierte en un valor central, influye en la toma de decisiones, en los compromisos bajo presión, en la planificación operativa y en la asignación de recursos. La seguridad pasa a ser una consecuencia natural de cómo funciona el sistema, en lugar de una iniciativa añadida a la producción.
Este cambio también redefine el rol de las funciones de seguridad: de supervisar el cumplimiento a habilitar un desempeño seguro y sostenible.
2. El aprendizaje como disciplina operativa
Las organizaciones están integrando el aprendizaje continuo en las operaciones diarias. En lugar de centrarse solo en lo que falló, exploran señales débiles, casi accidentes, fricciones operativas y adaptaciones exitosas.
El aprendizaje se convierte en una capacidad clave que acelera la generación de insights, fortalece la resiliencia y mejora la calidad de las decisiones.
3. Responsabilidad del liderazgo en todos los niveles
La cultura de seguridad se reconoce cada vez más como una capacidad de liderazgo, no solo como responsabilidad del área de HSE.
- Los directivos marcan la dirección y el tono.
- Los mandos intermedios traducen las expectativas en decisiones operativas.
- Los supervisores configuran el entorno de decisiones del día a día.
Las organizaciones exitosas convierten las expectativas de seguridad en comportamientos concretos de liderazgo y rutinas diarias, generando claridad y alineación entre niveles.
4. La seguridad psicológica como infraestructura
Una cultura de seguridad sólida depende de entornos donde las personas se sientan seguras para hablar.
Cuando los empleados perciben seguridad psicológica, las señales débiles emergen antes, los riesgos se discuten abiertamente y el aprendizaje se acelera.
La seguridad psicológica es una infraestructura operativa, no un tema “blando”.
5. Amplificar lo que funciona
Existe un reconocimiento creciente de que la mayor parte del trabajo se realiza de forma segura, a menudo en condiciones variables.
Estudiar el éxito revela la capacidad adaptativa y fortalece la resiliencia. Esto complementa el análisis tradicional de incidentes al reforzar la experiencia y la confianza.
6. Alinear el trabajo “imaginado” con el trabajo “real”
Los procedimientos y planes rara vez capturan perfectamente la complejidad operativa.
Las organizaciones líderes reducen la brecha entre políticas y realidad operativa incorporando la perspectiva del personal de primera línea y empoderando la autoridad para detener el trabajo.
El objetivo es una mejor alineación entre diseño y ejecución.
7. Diseñar para la toma de decisiones humana
Los incidentes suelen derivarse de sesgos cognitivos predecibles como la normalización de la desviación, el sesgo hacia la producción, el exceso de confianza y el sesgo retrospectivo.
Reconocer estas trampas en la toma de decisiones desplaza el enfoque de culpar a las personas hacia fortalecer los entornos de decisión.
8. La evolución cultural como capacidad a largo plazo
Una cultura de seguridad sostenible requiere integración en lugar de reinvención, desarrollo estructurado de capacidades en lugar de programas puntuales y medición del impacto conductual en lugar de métricas de actividad.
Las organizaciones que tienen éxito:
- Integran la seguridad en los sistemas existentes de liderazgo y operación
- Diseñan itinerarios de aprendizaje que apoyan la aplicación en el día a día
- Miden el cambio de comportamiento y los resultados operativos
- Refuerzan el progreso de manera consistente en el tiempo
La evolución cultural es un compromiso sostenido con la alineación del sistema y el desarrollo de capacidades.
Conclusión
La evolución de la cultura de seguridad trata menos de añadir controles y más de fortalecer sistemas.
La seguridad es algo que las organizaciones producen: a través de la claridad del liderazgo, el diseño operativo, la seguridad psicológica y el aprendizaje continuo.
Quienes integren estas capacidades de forma consistente no solo reducirán riesgos. Construirán organizaciones más resilientes, sostenibles y de alto desempeño.
Sources & references:
- WorldSteel Association. Safety Culture & Leadership Fundamentals.
- Norsk Industri (2025). Safety Leadership and Learning: A Practical Guide to HOP.
- D. Parker et al. / Safety Science 44 (2006). Development of Organisational Safety Culture
- Hollnagel, E. (2014). Safety-I and Safety-II: The Past and Future of Safety Management.
- Hollnagel, E. (2018). Safety-II in Practice: Developing the Resilience Potentials.
- Conklin, T. (2012). Pre-Accident Investigations: An Introduction to Organizational Safety.
- Edmondson, A. (2018). The Fearless Organizations
- Reason, J. (1997). Managing the Risks of Organizational Accidents.
- Resilience Engineering research (Hollnagel,Woods, Leveson and others).
Across industries, safety is undergoing a structural shift. What was once managed primarily as a compliance function or performance metricis increasingly understood as a reflection of how organizations are designed, led and continuously improved.
In complex and high-risk environments, safety is notachieved through stronger enforcement or additional programs alone. It emerges from the interaction between leadership behavior, operational design, decision environments and the organization’s capacity to learn and adapt.
Drawing on global safety science, Human & Organizational Performance (HOP), research on psychological safety, and our cross-industry transformation experience, eight key shifts are shaping the next evolution of safety culture.
1. Safety as a Core Organizational Value
Safety is moving beyond being treated as a shifting priority. Priorities compete. Values guide.
When safety becomes a core organizational value, it shapes decision-making, trade-offs under pressure, operational planning and resourceallocation. Safety becomes the natural consequence of how the system operates,rather than a campaign layered on top of production.
This shift also redefines the role of safety functions, from compliance policing to enabling safe and sustainable performance.
2. Learning as an Operating Discipline
Organizations are embedding continuous learning into everyday operations. Rather than focusing only on what failed, they exploreweak signals, near misses, operational friction and successful adaptations.
Learning becomes a core capability, accelerating insight, strengthening resilience and improving decision quality.
3. Leadership Ownership at All Levels
Safety culture is increasingly recognized as a leadership capability, not solely an HSE responsibility.
Executives define direction and tone.
Middle managers translate expectations into operational decisions.
Supervisors shape the daily decision environment.
Successful organizations translate safety expectations into concrete leadership behaviors and daily routines, creating clarity and alignment across levels.
4. Psychological Safety as Infrastructure
A strong safety culture depends on speaking-up environments.
When employees feel psychologically safe, weak signals surface earlier, risk trade-offs are openly discussed and learning accelerates.
Psychological safety is operational infrastructure , not a soft topic.
5. Amplifying What Works
There is growing recognition that most work is completed safely, often under variable conditions.
Studying success reveals adaptive capacity and strengthens resilience. This complements traditional incident analysis by reinforcing expertise and confidence.
6. Aligning Work-as-Imagined and Work-as-Done
Procedures and plans rarely capture operational complexity perfectly.
Leading organizations reduce the gap between policies and operational reality by inviting front line input and empowering stop-work authority.
The goal is better alignment between design and execution.
7. Designing for Human Decision-Making
Incidents often stem from predictable cognitive biases such as normalization of deviance, production bias, overconfidence and hindsight bias.
Recognizing these decision traps shifts focus from blaming individuals to strengthening decision environments.
8. Cultural Evolution as a Long-Term Capability
Sustainable safety culture requires integration rather than reinvention, structured capability journeys rather than one-off programs, and measurable behavioral impact rather than activity metrics.
Organizations that succeed:
- Integrate safety into existing leadership and operational systems
- Design earning journeys that support day-to-day application
- Measure behavioral change and operational outcomes
- Reinforce progress consistently over time
Cultural evolution is a sustained commitment to system alignment and capability building.
Conclusion
The evolution of safety culture is less about adding controls and more about strengthening systems.
Safety is something organizations produce — through leadership clarity, operational design, psychological safety and continuous learning.
Those who embed these capabilities consistently will not only reduce risk. They will build more resilient, sustainable and high-performing organizations.
Sources & references:
- WorldSteel Association. Safety Culture & Leadership Fundamentals.
- Norsk Industri (2025). Safety Leadership and Learning: A Practical Guide to HOP.
- D. Parker et al. / Safety Science 44 (2006). Development of Organisational Safety Culture
- Hollnagel, E. (2014). Safety-I and Safety-II: The Past and Future of Safety Management.
- Hollnagel, E. (2018). Safety-II in Practice: Developing the Resilience Potentials.
- Conklin, T. (2012). Pre-Accident Investigations: An Introduction to Organizational Safety.
- Edmondson, A. (2018). The Fearless Organizations
- Reason, J. (1997). Managing the Risks of Organizational Accidents.
- Resilience Engineering research (Hollnagel,Woods, Leveson and others).