Pilot Governance Taskforce and plan
Source: deck slides 18–20 · WPP MEDIA · PRIVATE AND CONFIDENTIAL
Wrike AI Agent Pilot Governance Taskforce#
Bring the business perspective into validation, Pilot governance and the design of controlled Rollout. · Slide 18
8–12 certified admins
Objective#
- Validate risks and controls, agree the Pilot/Rollout/GA approach, govern the Pilot and co-own the wider Rollout recommendation.
Membership#
- Business administrators and representatives, supported by Global Wrike Team - Support, Implementation, Integration and AI CoE/Security advisers (if needed)
Business validation#
- Validate all 21 risks against real business scenarios
- Challenge whether controls are practical and proportionate
- Identify market, client, workflow and operational dependencies
- Agree where manual or compensating controls are acceptable
- Confirm accountable business actions and representatives
Pilot governance#
- Review and approve every Pilot submission
- Approve scope, actions, limits, ownership and expiry
- Confirm Delete is disabled and write actions are bounded
- Review monitoring evidence, incidents and exceptions
- Modify, suspend, disable, escalate or retire agents
Rollout co-ownership#
- Agree controls required for Pilot, Rollout and GA
- Define business conditions for progressing beyond Pilot
- Shape use-case priorities and the up to 30 agent approach
- Own actions within represented business areas
- Champion controlled adoption and communications
Outputs: validated risk and control matrix, agreed staging model, approved Pilot approach, business-validated use cases, Pilot evidence, Rollout conditions and a jointly owned recommendation.
Technical capability delivery remains with the relevant product, integration and platform owners.
3 Stages: jointly shape, test and agree the approach#
A gate-based plan combining business validation of the framework with controlled Pilot execution and Rollout design. · Slide 19
Stage 1: Validate and agree the framework#
| Week | Activity |
|---|---|
| W1 | Confirm Taskforce authority, Pilot scope and validation approach |
| W2 | Validate the 21 risks, proposed controls and accountable owners |
| W3 | Agree Pilot, Rollout and GA requirements and compensating controls |
| W4 | Approve the Pilot operating model, artefacts and readiness gate |
Stage 2: Assess, configure and activate#
| Week | Activity |
|---|---|
| W5 | Review business use cases, value, risk and ownership |
| W6 | Configure and test approved agents and boundary scenarios |
| W7 | Close readiness gaps and confirm scope, limits and expiry |
| W8 | Activate approved agents and begin daily monitoring |
Stage 3: Learn, refine and co-own Rollout#
| Week | Activity |
|---|---|
| W9 | Operate the Pilot and run weekly business assurance reviews |
| W10 | Validate controls using write, bulk, incident and change evidence |
| W11 | Revalidate risks, controls and staging using Pilot evidence |
| W12 | Joint recommendation, Rollout conditions and accountable actions |
Readiness gate: progression pauses until the Taskforce validates the evidence and agrees that mandatory controls or documented compensating measures are sufficient.
Joint outcome: approve or revise the framework, confirm Rollout conditions, assign accountable actions, progress selected agents, remediate gaps or pause.
Management support and decisions required#
Enable the Taskforce to act as the business validation and co-ownership body for controlled adoption. · Slide 20
| # | Decision | Description |
|---|---|---|
| 1 | Endorse the validation mandate | Authorise the Taskforce to validate and challenge the 21 risks, controls, owners and Pilot/Rollout/GA stage requirements. |
| 2 | Back business participation | Release certified administrators and business representative to bring real business scenarios, make timely decisions and own actions. |
| 3 | Confirm shared accountability | Taskforce co-owns business suitability, Rollout conditions and adoption actions; Product, Integration and AI CoE/Security retain technical control delivery. |
| 4 | Sponsor a gate-based Rollout | Require a joint Taskforce and management recommendation before expansion, with unresolved product or architecture gaps remediated, constrained or formally accepted. |
Decision required: endorse the Taskforce mandate, confirm business representation and accountability, and authorise the gate-based Pilot-to-Rollout approach.