Skip to main content
Articles10 posts

Support & SRE articles

Practical perspectives on Support & SRE for founders, technology leaders, and engineering teams.

Infographic of an error budget gauge pointing to exhausted while a barrier stops a rocket launch, showing the budget overriding a release
FeaturedJune 09, 2026

Error Budgets Are a Management Tool, Not an Engineering One

Most error budgets die quietly because engineers introduced them with no authority behind them. The number only matters when it changes what leadership does. Here is how to wire budget burn into roadmap decisions, exec reviews, and feature-freeze conversations so it actually has teeth.

MD
Mikael Danielian
Read article →
More Articles
Three SRE organization models side by side: a centralized team, embedded engineers inside product teams, and a platform paved road
June 05, 2026 / Mikael Danielian

SRE Org Design: Centralized, Embedded, or Platform?

Centralized, embedded, or platform SRE? Each model solves a different problem and breaks in a different way. Here is how to pick one, and how to migrate when you outgrow it.
Split diagram contrasting a vertical L1 L2 L3 support pyramid with tickets flowing sideways between many teams at enterprise scale
June 01, 2026 / Mikael Danielian

L1/L2/L3 at Scale: Where the Tiered Support Model Breaks

The tiered support model works beautifully until it doesn't. At enterprise scale, tickets stop flowing up the tiers and start flowing sideways. Here's exactly where L1/L2/L3 breaks, and the three patterns that replace it.
Infographic contrasting the firefighter who saves the fire with the fire marshal who prevents it, the prevention badge marked correct
May 26, 2026 / Mikael Danielian

Your First SRE Hire Is Not Your Best Firefighter

The instinct is to take the engineer who saves every outage and crown them SRE. That instinct is wrong. The skills that make someone great at firefighting are often the same ones that keep your systems fragile.
Split infographic contrasting an L1 team that forwards tickets through many hops with one that resolves tickets directly at the first line
May 14, 2026 / Mikael Danielian

Building L1 That Resolves, Not Just Escalates

Most L1 teams become a forwarding service that adds latency and frustrates everyone. Here's what it takes to build a first line that actually resolves tickets — the tooling, the runbooks, and the incentives that produce real outcomes instead of gamed numbers.
Infographic of support and engineering teams separated by a gap but connected by a feedback loop bridge instead of a wall
May 08, 2026 / Mikael Danielian

When to Split Support From Engineering (Without Losing Context)

Somewhere between 20 and 150 engineers, most companies split support out of engineering and quietly break the feedback loop that made them good. Here is how to split without building a wall.
Infographic of a four-section runbook recipe card with symptom, confirm, fix, and prevent steps linked from an alert to a resolved checkmark
April 27, 2026 / Mikael Danielian

The Runbook Habit: How to Make Engineers Document While They Fix

Engineers fix the same thing three times because the knowledge evaporates after every incident. Here's a runbook habit that survives contact with reality—built into how you resolve incidents, not bolted on as a chore.
Diagram of one startup engineer handling all three kinds of support work: first response, investigation, and deep fixes
April 21, 2026 / Mikael Danielian

L1/L2/L3 Doesn't Exist at a Startup — But the Work Does

Your 8-person startup doesn't have support tiers. But the work those tiers represent still exists and still needs an owner. Here's how to handle it now and track it so you can split it cleanly when you grow.
Hub diagram of a generalist first support hire owning documentation, triage, and customer communication
April 10, 2026 / Mikael Danielian

Your First Support Hire Should Be a Generalist, Not a Specialist

Most founders hire a career L1 support agent for their first support role and wonder why it doesn't scale. Here's why a curious generalist who can write docs and talk to engineers beats a ticket-closing specialist — and how to find one.
Flow diagram of scattered customer channels funneling into one shared inbox handled by a weekly engineer rotation
April 02, 2026 / Mikael Danielian

You Don't Need a Support Team Yet. You Need a Shared Inbox and a Rotation.

Hiring a support person before you have 20 engineers is usually a mistake. Keep your engineers close to your customers, run a simple rotation, and learn to read the signals that tell you when it's finally time to hire.