0%
Chat
← Back to all posts

Invest in a Culture of Curiosity in Infrastructure and Operations

Infrastructure and operations teams are built to keep things running. Stability is their mission, change is their biggest risk, and a mistake can take down systems the whole business depends on. Unsurprisingly, many I&O cultures become deeply risk-averse.

That instinct protects uptime, but taken too far, it also blocks learning. New technologies are adopted late or not at all. Knowledge stays locked in the heads of a few experts. Talented engineers feel stuck and leave. And the team spends its days reacting to problems it never has time to prevent.

This article outlines how to invest in a culture of curiosity in I&O: encouraging continuous learning, safe experimentation, and knowledge sharing — while keeping production stable.

Symptoms of an Incurious Culture

Internal surveys in the organization behind this business case painted a clear picture:

  • Only 20% of I&O employees took part in formal training each year, and 70% said they felt stagnant in their roles.
  • Teams operated with a "zero-failure" mindset; fewer than 10% of projects included a pilot or proof of concept, and 60% of employees named fear of negative consequences as the main reason they avoided experimenting.
  • Only 30% of teams regularly shared insights with other departments, and half of employees said critical knowledge was concentrated in small groups.
  • Employee engagement stood at about 60%, and leaders saw the culture itself as a barrier to strategic goals.

Curiosity and Reliability Aren't Opposites

The best-run operations organizations are often the most curious ones. Site reliability engineering, for example, treats incidents as learning opportunities, uses error budgets to balance change against stability, and invests heavily in automation and experimentation. The trick is to make experimentation safe, not to avoid it.

Three Pillars

1. Continuous Learning

  • Protected learning time in every engineer's week or month, not just "when it's quiet".
  • Personal learning budgets and access to courses, certifications, labs, and conferences.
  • Learning paths aligned with where the organization is heading — cloud, automation, observability, security, AI.
  • Mentoring and rotations across teams to spread skills and perspectives.

2. Safe Experimentation

  • An innovation lab or sandbox where teams can try new tools and ideas without touching production.
  • A lightweight process for pilots and proofs of concept, with clear success criteria and time limits.
  • Blameless post-incident reviews that focus on systems and learning, not on finding someone to blame.
  • Recognition for well-run experiments, including ones that "failed" but produced useful lessons.

3. Knowledge Sharing

  • A central knowledge platform with runbooks, architecture decisions, lessons learned, and how-tos.
  • Communities of practice around topics such as automation, cloud, and observability.
  • Regular demo days, lunch-and-learns, and internal tech talks.
  • Documentation as part of done: a change isn't finished until the knowledge is captured.

The Role of Leaders

Culture follows behavior. Leaders who ask questions, admit what they don't know, share their own learning, and respond to failures with curiosity instead of blame set the tone faster than any program.

Choosing the Scope

The business case compared three options:

  1. Status quo: no formal initiatives — no cost, but continued inefficiency, missed opportunities, and turnover.
  2. Incremental improvement: a modular training program, a small innovation lab for selected teams, and a basic knowledge-sharing space. Lower cost and risk, but limited impact on deep-rooted issues such as fear of failure and siloed knowledge.
  3. Full cultural transformation (recommended): a comprehensive learning and development framework, a structured experimentation program, and a knowledge-sharing platform, backed by leadership commitment and changes to incentives and processes.

Managing the Risks

Risk Mitigation
Experiments affect production Sandboxes, change controls, and error budgets
Learning time gets squeezed by operational pressure Formally protected time, backed by leadership
Initiatives seen as "HR programs" Tie learning and experiments to real operational problems
Knowledge platform goes stale Ownership, documentation as part of done, and regular reviews
Change fatigue Start small, celebrate early wins, and build momentum

Measuring Success

Metric Baseline Target
Employees participating in training 20% 80%
Projects using pilots or the innovation lab Under 10% 50%
Teams actively using the knowledge platform 30% 90%
Employee engagement 60% 85%
Annual cost of lost productivity $1.2M $500K
Annual cost of staff turnover $300K $100K

Conclusion

The technology landscape changes too quickly for any I&O team to rely only on what it knew five years ago. Teams that keep learning, experiment safely, and share what they discover adopt better tools sooner, prevent more incidents, and keep their best people.

A culture of curiosity isn't a luxury for quiet times. It's what allows operations teams to move from keeping the lights on to actively improving how the lights are kept on.