Engineers used to be the only people who could build. What happens now that everyone can?
retained text
I have been thinking about this a lot lately. With AI coding tools, a marketing manager, finance analyst, sales ops person, or product manager can now build a surprisingly useful internal tool without involving Engineering. And honestly, I think that's great. But I am curious how Engineering teams are dealing with the organizational problem this creates. Let's say someone in Finance builds a small internal application that saves the team 10 hours a week. It's not really an Engineering project. So do you just let Finance own it? Now imagine that six months later: * 40 people are using it * It has access to company data * It has become part of a business process * Nobody really knows how it works except the person who built it * And suddenly it breaks on a Sunday At what point does Engineering say, "Okay, this is now our problem"? And what if Engineering already has a tool that does 80% of the same thing? Do you ask the business team to stop using theirs? Do you bring their tool into Engineering and support it? Do you just provide infrastructure, security and guardrails while letting the business own the application? Or do you create some kind of internal "citizen developer" model where business teams can build whatever they want within certain boundaries? I am curious about how Engineering leaders as well as Business stakeholders are thinking about this. **Are you trying to keep Engineering as the owner of all corporate tools, or are you moving toward a world where Engineering provides the platform/guardrails and the business owns more of the actual tools?** And if you have already implemented a model for this, what does it look like?
document fetched 2026-09-26 00:21 · canonical https://reddit.com/r/ClaudeAI/comments/1wq88q8/engineers_used_to_be_the_only_people_who_could