Rollout by AIP
The system AIP uses to design and run your newsroom transformation.
Eighteen modules, one live programme, every figure counted from the records beneath it. Built for the people running the change, not for the people building software.
Built and operated by As If Pictures. Not sold separately.
$23.5M in annual savings.
178 roles freed up.
One engagement.
The Monday After Go-Live
Your news transformation shouldn't run on spreadsheets.
A transformation is not finished when the new system is installed. It is finished when someone can describe the Monday after.
Who is on shift that Monday?
Nobody is quite sure yet.
Who may do what in each system?
There's a spreadsheet somewhere.
What does a story cost to move through the cloud?
Ask finance next quarter.
What are the job titles even called now?
Good question.
We run transformations for broadcasters including BBC, Sky News, RTL, Nine Entertainment, TV2 Fyn, GB News, Wall Street Journal, TV Globo and Asharq, and we could never find a tool built for the job. So we built Rollout for ourselves.
Why a System, Not a Spreadsheet
Most transformation programmes are run in spreadsheets.
Three things a spreadsheet cannot do.
3,500%
of staff trained, according to one broadcaster's spreadsheet planner. Nobody noticed for a while. A spreadsheet does not say when it has stopped making sense. Rollout does.
01
Keep the method where it is maintained
A workbook is copied, forked and quietly diverges. In Rollout the plans and the calculations run on AIP's server, kept current by the people who wrote them, so every programme has the latest method.
02
One live programme, not a chain of attachments
An emailed plan is as old as the last send. A Rollout programme is the same programme for the consultant and for you, at the moment either opens it, with its change trail beneath it.
03
Figures that cannot drift from the data
Every figure in Rollout is counted from the records beneath it, never typed in beside them. A number that cannot be right is refused where it is entered, with the reason, rather than carried into a total.
What a Programme Contains
Eighteen modules. Four groups. One programme.
Everything AIP plans for a broadcaster lives in one programme, in four groups.
Training rollout
6 modules
Plan and track the training rollout.
Who is on which team, and how those teams are built into training cohorts. Which sessions run when, with what capacity, and what the curriculum covers day by day, including breakouts for specialist teams and learner groups by future role. Who has attended and who still has not, counted from the attendance records themselves. And the whole rollout against its dates: move the go-live and you see immediately what no longer fits. Nothing left to chance, not even whether Jimmy got his laptop before training begins.
Team setup
Session planner
Curriculum
Cohort build
Timeline
Progress
Archive migration
3 modules
Migrate the legacy archive.
Take a filename like SPT_FIN_090614_CAM2.mxf. To the archivist who has been there twenty years, it says: sports desk, final edit, June 2014, second camera. To your brand new MAM, it says nothing at all. Rollout audits every field in the old archive, writes the rules that read meaning out of legacy filenames, and produces the translation file the new system imports. Not a report about the migration: the migration itself.
Archive audit
Archive inference
Archive translation
Future newsroom
8 modules
Design the future newsroom.
The shape of the working week after launch, with a minimum-viable-rota calculator that shows the smallest crew that still gets the bulletin out. The metadata schema your content will carry, and who may do what in each system. The future cloud setup, what it costs to run, and the technical standards it is held to, down to the camera formats. And the roles people will hold after launch, written as real job descriptions, down to the graphics principles behind them.
Shifts and rota
Metadata
Permissions
Cloud and cost
System design
Job descriptions
Technical standards
Graphics principles
Explaining the change
1 module
Explain the change.
Advisories written for staff, in plain words, about what changes for them and when.
Change advisories
One programme. Everyone on the same page.
The consultant and the broadcaster open the same live programme, at the same moment, with its change trail beneath it. No forked workbooks. No emailed attachments that are as old as the last send.
Step 1
Operations leads
Shifts and rota, permissions, cloud and cost.
Step 2
Training leads
Teams, cohorts, sessions and progress.
Step 3
Archive leads
Archive audit, inference and translation.
Step 4
Your staff
Change advisories in plain words.
In Numbers
What one programme holds.
5,798
records in one programme.
603
people planned across 38 teams.
13
sessions scheduled against a 10-day curriculum.
81
fields audited in the legacy archive, driving 291 migration rules.
1,551
individual software permissions mapped across two systems.
53
graphics templates specified.
Figures from the Meridian News demonstration programme.
$23.5M in annual savings.
178 roles freed up.
One engagement.
Part of how we run your change
Not a product you buy. The system we bring.
Rollout is built and operated by As If Pictures and is not sold separately. It comes with the consultants who run your change, and it holds the plans they build with you.
