A finance manager at a manufacturing company built a scheduling app in Power Apps to help her team track machine downtime. It worked well enough that three other departments started using it. Then she left the company. Nobody knew the app existed, let alone who owned it or how to fix it, until it stopped syncing correctly and half the plant floor lost visibility into equipment status for a week.
IT wasn’t angry at her for building it. They were angry that nobody had ever asked the obvious question while it was being built: who’s responsible for this once you’re gone?
Governance isn’t about stopping people from building things
A framework for citizen developer governance often gets misread, especially by the people it’s meant to serve, as a way of slowing down the exact energy that made low-code tools appealing in the first place. That’s backwards. The point isn’t to stop a finance manager from solving her own problem. It’s to make sure that solution doesn’t quietly become critical infrastructure with nobody accountable for it.
The companies that get this right build a simple tiering system early. A tool used by one person, for one task, with no sensitive data involved, gets almost no oversight. It’s a personal productivity hack, and treating it like an enterprise deployment wastes everyone’s time. But the moment an app touches more than a handful of users, or connects to a data source with anything remotely sensitive, or starts making decisions that affect other departments, it needs a named owner, a basic security review, and a plan for what happens if that person leaves. That single tier change would have caught the manufacturing company’s problem months before it became one.
What actually works in practice is lightweight registration, not heavy approval gates. A shared list where builders log what they’ve made and who else relies on it takes five minutes to fill out and saves someone a very bad week later. Making that step mandatory rather than optional is really the entire governance program, more often than people expect.
The parts nobody thinks about until later are the parts that matter most
Most first-time builders focus on what the app does. Almost nobody thinks about who maintains it, what happens if the underlying data source changes structure, or how it gets decommissioned cleanly if the team it served gets restructured. Those questions feel unnecessary at build time because everything’s working. They become urgent exactly when the person who’d know the answer isn’t around to ask.
This is oddly similar to a completely different kind of maintenance question, the sort that shows up outside rather than in a server room.
A driveway asks the same question a citizen-built app does
Anyone researching types of driveway sealer options runs into the same tension almost immediately. Acrylic sealers go on easily, look good fast, and cost less upfront, which makes them the obvious first choice for a homeowner who just wants the job done this weekend. The tradeoff shows up eighteen months later, when the surface starts wearing thin from UV exposure and needs reapplication far sooner than expected. Asphalt-based sealers hold up longer against oil stains and general wear, but they take longer to cure properly and cost more per gallon. Coal tar sealers used to dominate the category for durability, though restrictions in a growing number of states have pushed a lot of buyers toward other options, often for good reason given the environmental concerns involved.
None of these choices is wrong, exactly. Each one is a different bet about how much attention you’re willing to give the surface later versus how much you want to spend or wait right now. The homeowner who picks the fast, cheap acrylic option isn’t making a mistake if she knows she’s signing up for more frequent reapplication. She’s making a mistake if she picks it without realizing that tradeoff exists at all.
Both problems come down to the same avoidable gap
A citizen-built app and a sealed driveway fail for the same underlying reason when they fail: someone made a reasonable choice for the moment without accounting for what the choice would demand later. The finance manager didn’t do anything wrong building her app. She just never got asked, or asked herself, what happens to this in a year. The homeowner who picks the cheapest sealer without understanding the maintenance cycle isn’t lazy. She just wasn’t given the framing that would have made the tradeoff obvious at the time of purchase.
The fix in both cases is ridiculously unglamorous. Ask the maintenance question at the start, not after something breaks. It’s a five-minute conversation that most people skip entirely, right up until skipping it costs them a lot more than five minutes.
