Managing Products Across Commercialization and End-of-Life

My work covered two distinct product moments in Accela's service-request portfolio. SRM required commercialization strategy, roadmap work, and launch assets. PublicStuff, a legacy CRM product, required end-of-life program management while product quality and customer incidents still needed attention.

Keeping those moments distinct matters. Launch work and legacy operations demand different decisions, even when they sit in the same product domain.

For commercialization work, the focus was connecting product scope with a coherent roadmap and launch material. For the legacy product, the focus was deciding where limited attention belonged across lifecycle needs, defects, and incidents.

I use this case to show range across product maturity, not to invent one causal story that links launch work to a later financial or migration result.

The legacy work required defect prioritization, incident management, and coordination across customer-facing and delivery participants. The commercialization work required strategy, roadmap, and launch artifacts that made the newer product direction understandable.

Across both moments, my role was to make tradeoffs and product state visible enough for different teams to act on them.

The supported evidence is commercialization strategy, roadmap work, launch assets, end-of-life program management, defect prioritization, and incident management.

I do not publish customer counts, revenue, retention, feature counts, defect totals, incident totals, migration outcomes, or an orderly-transition claim that the current evidence does not independently support.