Why gamified DevOps
The work that keeps your cloud up deserves to be seen.
When the cloud is up, nobody notices. The patch, the renewed certificate, the alert answered at 3 a.m.: all invisible. Opsburg turns that work into a city that grows every day it stays in the air, so the whole team can see it, share it and want to do it.
Animated scene: a clocktower stands alone on a floating island. Every day the cloud stays up, a lamp on the island's rim turns green and a new building rises in a puff of steam. On the seventh day an airship dock is built, an airship lands, fireworks go up and the airship sails off with the next release.
Running a cloud is invisible work
Dashboards tell you what is wrong right now. They don't make anyone want to do the boring things that keep it from going wrong.
Success looks like nothing
When the cloud is up there is nothing to see. The work behind it only shows up the day it fails.
Chores get postponed
Upgrades, patches, renewals and clean-ups always lose against the next feature, until one of them turns into an incident.
Incidents are rehearsed live
Most teams practise recovery for the first time during the real outage, at night, with everyone watching.
Knowledge lives in a few heads
The map of what runs where sits in a wiki nobody reads, or in the head of whoever is on call.
What a game does better than a dashboard
Games are very good at one thing: making people care about a system and come back to look after it. That is exactly what keeping a cloud up needs.
A picture anyone can read
A city shows at a glance what is healthy, what is under pressure and what is broken. A new hire learns the platform by walking through it.
A goal you can feel
A streak turns “nothing happened today” into something worth protecting, and a storm weathered fast into a save, not a failure.
Small, clear steps
Missions split the chores into things you can finish today, each with a reason, an owner and a visible result.
Practice without the pager
Storm drills let the team rehearse an incident on purpose, in daylight, so the real one finds everyone ready.
Credit for the quiet work
Every finished mission adds to the city. Whoever patched the vault or renewed the seal gets seen by the whole team.
Play is the real thing
There is no separate game to keep up to date. Every move in the city is an action on your stack, with the same approvals.
Every mission is a real task
The game word never hides the real one. Each mission shows the task, the resource it touches and the change it makes.
| The real work | The mission in the city |
|---|---|
| Renew a TLS certificate before it expires | Reseal the Lightning Spire |
| Patch a base image with known vulnerabilities | Reline the boilers |
| Add a replica before a traffic peak | Fire up a reserve boiler |
| Remove an environment nobody uses | Dismantle an empty island and save the coal |
| Rehearse an incident on purpose | Call a storm drill |
| Write the notes after an incident | Log the storm on the telegraph tape |
What it is not
Gamification done wrong is surveillance with badges. These are the rules we build by.
Not a leaderboard of people
The streak belongs to the city, which means the team. Nobody is ranked, and nobody is blamed for the storm.
Not points for busywork
The city grows with outcomes: up, patched, cheaper. Commits and closed tickets earn nothing on their own.
Not a simulation
When a mission is done, a real certificate was renewed or a real replica added. The game is the interface, the cloud is yours.
Keeping it up is the game
Streaks, missions and storm drills are in the workshop, not playable yet. Follow the build on GitHub, and tell us which chore your team keeps postponing.