The leave-request app it shut down, and what came after
An HR operations manager at a 400-person logistics company got tired of the email chains. Leave requests bounced between employees, supervisors, and payroll, and at least one got lost every week. Over three weeks, using the company’s low-code platform, she built a simple app to replace them. Within a month, 300 employees were using it.
Then IT found it. The app stored notes about medical leave, and every manager in the company could see every employee’s notes. IT shut it down for a week. She hadn’t broken any written rule, because there weren’t any.
That story repeats in companies everywhere, and the fix is rarely to stop people from building.
Where Citizen Developers Come From
Women hold roughly a quarter of computing jobs in the US. They’re much better represented in HR, finance, and operations, which happen to be the departments where people most often start building their own tools, because those teams live with clunky processes every day and rarely get engineering time to fix them.
For many, the first app becomes a career turn. Builders who start with a leave tracker or an invoice approval flow often move into business analyst, automation, or product roles. Companies that recognize this work grow technical talent from inside. Companies that only notice it when something breaks tend to lose those people to employers that value them more.
Governance That Keeps Builders Building
The instinct after an incident like the leave app is a blanket approval process: nothing goes live without IT sign-off. In practice, that pushes builders toward spreadsheets, personal accounts, and tools IT can’t see at all.
A better framework for citizen developer governance sorts apps by risk.
Personal productivity tools, like a tracker only you use, need no review. Team apps need a light checklist: a named owner, a backup owner, and a note about what kind of data the app holds. Apps touching sensitive data, such as health information, payroll, or customer records, or anything used outside the company, get a real IT review, with a promised turnaround of something like five business days so builders aren’t left waiting for weeks.
Make the safe path the easy one. Provide approved templates with access controls already set, so a new HR app starts with permissions limited by role. Offer a list of approved data connections. Keep an inventory of every app above the personal tier. And have IT run regular office hours where builders can ask questions before launch instead of apologizing afterward.
The Writing Half of the Job
People who build internal tools spend a surprising share of their time writing: requirements, user instructions, training guides, release notes, emails explaining why the old process is going away. AI writing assistants speed this up considerably.
Teams evaluating Grammarly alternatives, or any writing tool, should look past the quality of grammar suggestions. Start with data handling. Does the vendor use your text to train its models? Are there administrator controls, and can you sign an agreement covering confidential data? An HR builder pasting medical leave policies with employee examples into a consumer writing tool creates the same kind of exposure the original app did.
Next, check whether the tool can enforce your company’s own terminology and style guide. Consistent names for systems and processes help employees far more than polished sentences do. Finally, confirm it works where your builders actually write, inside the app platform, documents, and email, and compare cost per seat across the people who’d actually use it.
What Speeds Up and What Doesn’t
AI drafting tools are good at producing a first version of a user guide from an app’s fields and workflow, turning rough notes into clear release announcements, and rewriting instructions at a simpler reading level for frontline staff. A builder still needs to check every step against the real app.
What they don’t speed up: getting supervisors to agree on how approvals should work, testing with actual employees, and training the payroll team that’s used to the old way. Those still take the time they take.
The leave app came back after four days of IT review, with permissions limited by role and medical notes visible only to HR. Its builder now co-hosts the monthly office hours with IT, helping other employees build their first tools. The most useful outcome of the shutdown turned out to be that someone finally wrote the rules, and asked a builder to help write them.
