7 Steps to create value from Kubernetes, fast..

I’ve advised countless organizations 6-9 months into their Kubernetes projects. It’s stalled, complicated & not delivering value. Here’s 7 steps I’d take if they brought me in at the start.

Most large-scale modernisation efforts stall.

Here’s a few common reasons.

+ They treated Kubernetes like ‘1 project’
+ The scope was too ambitious
+ No proof of early value
+ Skill curve shock
+ Tooling overload

The smartest teams don’t go big first. They start small, prove value fast, and build a rhythm that lasts.

Here’s what that looks like in practice…

1. Start Small
Focus on one problem, one environment. Big, abstract initiatives fail because no one can see progress. Starting small lets you prove value fast and build momentum. Choose something important enough to matter but contained enough to control.

2. Solve Real Problems
Abstract goals sound strategic, but they don’t drive change. Real problems do. Pick something your team actually complains about, such as a deployment bottleneck, poor visibility, or manual patching. When you fix a pain that people feel, adoption follows naturally.

3. Use the Team You Already Have
External help can be useful, but outsourcing early wins kills internal capability. The team that’ll run the system should own the pilot from day one, their learning becomes your foundation for scale.

4. Don’t Wait for Perfect Infrastructure
Perfect conditions never come. Waiting for ideal tooling or a full redesign only delays progress. Start where you are, with the clusters, networks, and workflows already in place. Improvement inside constraints builds confidence, and confidence builds momentum.

5. Prove Value Quickly
Long programs lose momentum. Quick wins earn trust. Set a 90-day goal with measurable outcomes that matter to both engineers and leadership.

6. Document and Replicate What Works
Without documentation, every success becomes a one-off. Record how you configured access, networking, and monitoring. Turn that into a repeatable pattern before you scale,

7. Build Rhythm, Not Revolution
Modernisation isn’t a one-off project. It’s a rhythm. Prove, document, improve, repeat until it becomes how you operate, not what you chase.

That’s how transformation sticks.

The incremental value compounds, and leads to organisational momentum.

Have you done a smaller ‘problem solving’ Kubernetes project?

How did it go?

Neil

If you want to see what this looks like in the field, I unpack it in Kubernetes Without Illusions, stories from real teams who’ve done it, scars and all. Available in my bio.