Bagels helped me come to an epiphany about developer experience recently during a client call.

I love a good, boiled bagel—even learned how to make my own during quarantine. In Portland, my favorite is Spielman Bagels. When I go to their store, which sometimes includes a long line, I stare around at their signage.

(That may be a hazard of being a professional communicator)

One of their most visible signs at the front says

WE ARE OUT OF:

and then they add flavors to the board as they run out.

If you go early enough, this sign will be empty. They have every flavor available. I understand it’s easier to keep that board up than take it down in this blank state. But it’s always seemed like a waste.

But now I’ve figured out the purpose it serves.

On a client call, we were discussing their lack of status page. It’s important to communicate API status. You want a place to share any downtime or other errors with developers. In moments of crisis, developers want accurate communication about issues. They want to confirm what their monitors tell them and ensure that you know what’s happening.

Assuming your service is reliable, that status page will nearly always show the system as available—the equivalent of Spielman starting the day with full buckets of bagels.

That sign at the bagel shop is important, even at the beginning of the day. It tells people that this isn’t the sort of place that will let you stand in a line to find out your favorite bagel is sold out.

Your status page isn’t just to show downtime. It tells developers you’re the sort of company that is transparent about service interruptions. You’re prepared to give them the details they’ll need in those frustrating moments of downtime.