Use case
Transformation program governance: change requests, initiatives and delivery in one program
Transformation program governance keeps every change in the move of work to AI agents visible, owned and scheduled. Via (transformation planning) plans and governs each transformation as a program of change requests and initiatives, on Kanban boards and a Gantt timeline.
What goes wrong without program governance
Without one place for its changes, a move to AI agents splits into separate projects that nobody can see as a whole.
Changes without a status
A fix agreed in a meeting has no status, owner or date until someone records it somewhere everyone can see.
No line from problem to fix
A change loses its reason when nobody records the pain point, task or process it is meant to address.
Delivery nobody can see
Without a shared timeline, overlapping changes and slipping initiatives come to light late.
How does Via govern a transformation program?
Set up the program, log the pain points, raise change requests, group them into initiatives, then deliver them on boards, a timeline and a calendar.
Set up the program
Create a program with its own start and end dates. Every view in Via is then scoped to the active program.
Log the pain points
Record each problem against the task or process it affects, with its severity, so that every later change has a stated reason.
Raise change requests
Link each change request to its pain point, task, process and initiative. Give it an automation type, implementation and rollback plans, the systems it affects, a scheduled date, and one-time or recurring cost and savings lines.
Group them into initiatives
Group change requests into initiatives, each with an owner, effort, complexity, dates, estimated cost, business benefits and solution levers.
Deliver on boards, a timeline and a calendar
Move initiatives and change requests across Kanban boards, plan initiatives on a Gantt timeline and schedule changes on a change calendar. Each change request moves from Backlog through review and approval to Closed.
What you get: one governed program
You get one program that shows each change in the move to AI agents: its reason, its initiative and its scheduled date.
A pain-point log
Problems recorded against tasks and processes with their severity, including the ones that have no change request yet.
Change requests with plans
Each change with its status, automation type, implementation plan, rollback plan and scheduled date.
Cost and savings lines
One-time or recurring cost and savings lines on each change request, and delivery cost broken into role hours, overhead roles and non-labor cost.
An initiative portfolio
Every initiative in the program with its owner, effort, complexity, dates, estimated cost and business benefits.
Delivery views and exports
Kanban boards, a Gantt timeline and a change calendar for the whole program, with the data behind them exportable to Excel.
A record of changes
The server keeps each company's and department's data within its scope, and many changes are recorded with their before and after values.
Compare value against effort, and forecast against actuals
Via also compares initiatives on value against effort, and compares forecast savings with the actual savings your team enters each month.
Value against effort
Plot initiatives by their value against low, medium or high effort. The order of the initiatives stays your team's call, not a computed score.
Forecast against realized savings
Enter the actual savings each month, and Via compares them with the forecast. Via does not measure savings on its own.
Questions about transformation program governance
Program and transformation leads ask these questions about governing the move of work to AI agents in Via.
What is transformation program governance?
Transformation program governance is the set of records and routines that keep a transformation's changes visible, owned, approved and scheduled. Some teams call it digital change management, but here it covers changes to the work, not training or communications. Via holds these records as one program, from pain point to change request to initiative.
Does Via replace our project or service-management tools?
No: Via governs the change requests and initiatives of a transformation program, and it does not connect to other project or service-management tools. Your team enters changes in Via, or imports a whole program from a JSON file.
Is there a record of changes in Via?
Yes, for many changes: Via records them with their before and after values. The server also keeps each company's and each department's data within its own scope.
See a governed program in a demo
Request a demo and bring the changes you already have in flight. We'll set them out as change requests and initiatives on Via's boards and timeline.