Lisa Karlin Curtis, incident.io
Service catalogs promise a lot of things: powerful automations, insights into your technology estate.
But over the last few years, many of us have learned that setting up and maintaining a service catalog is really hard.
Building out a catalog from a standing start can take months, or even years. Too many people get stuck in a chicken-and-egg situation, where you can’t deliver value because you don’t have the data in your catalog, and you can’t convince anyone to spend time helping you because the catalog doesn’t do anything yet.
But there is another way...
Lisa Karlin Curtis, incident.io

Lisa started out as a consultant working with HMRC and then smart meters, before accidentally becoming a developer. She was a founding engineer at incident.io, building tooling to help your whole organization manage incidents better. She loves building stuff, but is also really interested in how people interact with each other in a work environment - particularly in software engineering. Having seen the 'old way' at Accenture (large-scale waterfall projects), she's now looking at taking the lessons from that environment to the start-up scene.

author = {Lisa Karlin Curtis},
title = {Why {You{\textquoteright}re} (Probably) Doing Service Catalogs Wrong},
year = {2024},
address = {Dublin},
publisher = {USENIX Association},
month = oct
}