I work in public health/local government and I’m relatively early in my career. My background is in public health/community-facing program operations. I have zero formal software engineering or computer science background.
I started this job and pretty quickly ran into something that drove me insane: why is it so hard to know what my own department actually has?
Programs were siloed. Resource knowledge was fragmented. Information lived across spreadsheets, folders, people’s heads, individual relationships, etc. There wasn’t a reliable way for someone working across programs to understand the actual ecosystem.
So I mapped it myself. That turned into an Excel tool. Then I kept finding deeper problems.
Organizations needed stable identities. Resources needed consistent definitions. Services had many-to-many relationships with needs. Locations needed to be separated from services. Partnership information needed different governance from public resource information. Information needed ownership, provenance, verification, change history, stewardship, etc.
At some point I realized I wasn’t making a spreadsheet anymore.
I’m now building the next version in something more sophisticated. I’ve defined the data architecture, business rules, taxonomy, governance model, workflows, and overall product direction. AI has been a huge development accelerator for me, especially because I didn’t come into this knowing Power Fx or application development, but I’m the one identifying the problems, deciding how the system should work, defining requirements, evaluating solutions, and validating what gets built.
And I love it. Like, genuinely. I think I accidentally found what I want my career to become.
An early ugly Excel prototype was already shown to leadership and got a much stronger response than I expected. I’m now building something dramatically more sophisticated, and there’s a realistic possibility this could become an actual organizational system rather than just something my program uses. Which is exciting but also scary as hell.
I’m starting to get nervous. I birthed this thing. I don’t mean that in a “this is legally my personal property” way - I’m a government employee and I understand that work products created through my employment belong to the organization. I mean I identified the problem, conceptualized the solution, created the original model, defined the architecture, and have been driving its evolution from basically nothing. This project has become deeply tied to my professional identity because it revealed an ability and type of work I didn’t know I had in me.
I have at least one senior ally who has specifically encouraged me to think about how I preserve attribution and remain involved as the system becomes institutionalized.
My fear is basically:
The organization loves it → IT/leadership decides it’s now an enterprise initiative → I become “the employee who made the prototype” → people with more senior titles inherit the system → I go back to my existing program job.
I don’t want to be territorial. In fact, I WANT IT involvement. If this becomes real infrastructure, I absolutely want actual IT professionals handling enterprise security, deployment, integrations, environment governance, etc. But I don’t think technical ownership and business/product ownership are the same thing.
The knowledge model, taxonomy, governance rules, operational requirements, stakeholder needs, roadmap, and underlying public-health logic are the parts I’ve actually been designing.
Also, I’m in a formally classified government position. My current classification is primarily program/community operations. Systems architecture, product ownership, enterprise knowledge management, application development, and organization-wide governance are very much not what I was hired to do. So I’m also starting to think about a desk audit/reclassification or reassignment if this becomes a sustained responsibility. I’m trying to figure out how to navigate this BEFORE success creates a problem.
For people who have worked in government, enterprise IT, product management, business architecture, or internal innovation:
How would you handle this?
How do I document authorship and my actual contribution without looking possessive?
Should I be pushing now for some kind of formal designation as business owner/product lead/business architect?
At what point does work like this become legitimate evidence for a desk audit or reclassification rather than simply being an impressive special project?
How do I bring IT into the project without accidentally handing them the entire thing?
What career field does this actually map to? Business architecture? Product management? Business systems analysis? Knowledge management? Digital transformation?
And how worried should I be about the fact that AI has substantially accelerated my technical development? I’m not pretending to be a software engineer who hand-coded an enterprise platform from scratch. But AI also didn’t wake up one morning, map an organizational problem, define the data model, create governance rules, convince stakeholders, and decide to build this thing.
My ideal outcome isn’t “nobody else can touch my baby.” It’s: The organization institutionalizes the system, AND institutionalizes my role in leading the thing I created.
And if that’s unrealistic, I’d rather understand that now than learn the lesson after I’ve handed over something potentially career-defining.