Session
The Two-Week Work-Redesign Sprint
Experiential learning to accelerate AI-native enterprise transformation
PAWorld26 San Francisco · 23–24 September 2026 · San Francisco
← Back to agenda
– · Work Design
About this session
Central teams can set tools, governance and support, but they cannot prescribe the right AI-enabled change for every workflow. A practical two-week sprint gives teams room to test changes in ordinary work while preserving accountability. Learn how to frame the problem, use midpoint review, assess what persists and decide whether the change deserves continued use or reuse.
Learning outcomes
- Design a bounded two-week sprint around a genuine workflow problem.
- Define responsibilities for team leads, champions and central support functions.
- Distinguish tool use from workflow change, persistence and business value.
- Judge experiments using evidence, quality, safety, ownership and persistence.
- Decide when to keep, adapt, stop or share a workflow change.
This session will explore
- Structuring a two-week sprint around one genuine workflow problem.
- Setting central guardrails while teams control local workflow experiments.
- Using midpoint review to adjust experiments before weak practice persists.
- Examining one workflow before, during and after AI experimentation.
- Capturing useful learning without turning local practice into enterprise standard.
Context
AI tools and training can spread faster than operating practices change. Central functions cannot understand every workflow, while unstructured experimentation can produce weak evidence, duplicated effort and short-lived practices. Organisations need a disciplined bridge between enterprise guardrails and team-owned redesign.
Speakers and contributors
Michel-Riyad NabtiPresenterSenior Director, Talent DevelopmentAutodesk