FDLC Process

Activities, swimlanes, gates, in one view.

A side-by-side of the work as it runs today, and as it runs after the shift. Toggle the state. Layer in activities, gates, AI modes, and parallel work as you need them. Click any activity to open the detail; select more than one to compare side by side.

!
AI isn't structurally part of today's workflow. Individual contributors may reach for a chat tool now and then, but there's no shared discipline, no prompt library, no quality contract, and no role that depends on AI output to do its job. Every activity in this view is human-led by default.
The takeaway when you toggle

Today's process is sequential, hand-off heavy, and AI-absent. Every box is a person doing the work alone. Tomorrow compresses the phases, moves the POD into co-authorship at G2, applies AI deliberately by activity, and runs supporting work in parallel rather than after.

What you'll notice

Tech writing and Product Marketing move into Build rather than queuing behind it. QA tests are scaffolded from the spec at G2, not authored mid-Test. Customer Success and DS Team work continuously; they don't start and stop with the cycle.

From today to tomorrow

Change management runs alongside the shift.

Moving from the Today canvas to the Tomorrow canvas is its own delivery track. Below is the change-management work that has to run with explicit ownership for the framework to land.

Change management running alongside

The work that turns a framework into adoption.

A new workflow doesn't land just because it's documented. Change management runs as its own delivery track with explicit ownership, treating adoption with the same rigor as the work it supports.

Protected time for change Pilot Pods and rollout cohorts get explicit capacity for the shift, not "do this on top of the roadmap."
Companion file authoring Domain leads author design and engineering companions before their team's pilot or rollout window opens.
Skills & mindset development Spec authorship, prompt and context design, review craft, judgment under uncertainty. Invest in the muscles the new workflow uses.
Friction surfacing channels Adoption failure usually looks like silence. Surveys, retros, and the AI Ways of Working group keep friction visible.
Identity strain support Tell workflow friction apart from identity strain. They need different responses. Leadership reinforces that the shift changes what people do, not whether they belong.
Leadership reinforcement Permission to challenge legacy process. Endorsement of the framework as the org's reference model. Signal that pilot output is shaping the rollout.
Prompt library & templates Shared starting points so each team doesn't re-invent the same scaffolding. Promoted from the Activity Matrix.
FY27 OKR tracking Adoption tracked on the OKR scorecard: teams onboarded, gates exercised, outcome signal returning to the AI FDLC Review.