Owning a production help-center platform
Owning a platform means being answerable to two different clocks: the roadmap's quarters and production's right now. The job was holding both.
§1 The situation
A customer-facing help-center platform — a primary route for customers to resolve questions and understand complex product and financial-planning workflows. Someone had to own both where it was going and whether it was healthy right now, across content operations, cross-functional dependencies, and customer-facing reliability.
§2 What I did
Owned the roadmap and production-health responsibilities for the platform, and stayed hands-on alongside collaborators: application work, integration, testing, release-readiness, and troubleshooting. Prioritization and delivery weren't separate jobs so much as the same job on different days.
§3 Result
A production knowledge platform customers could rely on while it kept evolving — roadmap priorities set, production health watched, releases made ready, problems chased down. Working sources describe the platform's audience at a scale this site doesn't publish until it's confirmed; the ownership and the hands-on work stand without it.
§4 Difficulty & judgment
The role combined strategic prioritization with technical delivery, and the tension between them is the actual work: a roadmap is a theory about the future, production health is a fact about the present, and the platform needed somebody accountable to both at once.
§5 Not claimed
Deliberately left unclaimed
- The platform's audience size — a figure exists in working sources, but it's time-sensitive and unconfirmed, so it doesn't appear here.
- Sole creation or initial authorship — the role was owning and improving a platform built with others, not building it from nothing.
- A formal Software Engineer title — the hands-on engineering work was real, and is described as exactly that: hands-on work, not a title.
§6 The same work, other lenses
- Business systems
- Roadmap and operational health for a customer-facing knowledge platform connecting content, support, analytics, and release workflows.
- Engineering
- Application, integration, testing, troubleshooting, and release work on a collaborative production web platform.
- Operations leadership
- Roadmap priorities coordinated with production health, contributors, stakeholders, and release readiness.