DevDay 2026 Champion launch resources
Connect DevDay release to work your teams want to improve.
Start with your role
Do First: Confirm which DevDay capabilities are available and configure approved setup with source-system owners.
Hand off: Pass enabled capabilities, access boundaries, and support contact to Transformation Leaders.
Do First: Choose a pilot team and priority workflow; name the workflow's owner, success measure, and review date.
Hand off: Coordinate the support the workflow owner needs. Bring evidence and requests for capacity or wider investment to the Exec Sponsor.
Do First: Test new capabilities on one recurring team task with approved sources, intended users, and a named reviewer.
Hand off: Give the Transformation Leader a reusable workflow, instructions, results, and a recommendation to expand access, revise the workflow, or pause deployment until named conditions are met.
Do First: Back the pilot, protect time for teams to test, and test and model a useful leadership task with the new capabilities.
Hand off: Align with the Transformation Leader on priorities, capacity, and decisions on investment or cross-team constraints.
Best practice: Name the workflow owner
Each shared workflow needs a named person accountable for its business outcome, human review, and maintenance. An Agent Activator may hold this responsibility, or hand off this responsibility after introducing a proven workflow. State responsibilities and product permissions clearly.
See the new release guides section below for specific setup guidance on DevDay releases.
New release guides
Define the outcome, provide the right context, and agree when to check progress. Keep personal delegation distinct from a workflow other people need to own or run.
Keep an offsite plan and deadlines on track (guide with example) →
Organize shared files, Pages, and context so a team can continue its work. Check membership, sharing, and permissions for connected sources.
Space sharing and permissions →
Build a shared project plan in Space (guide with examples) →
Admin-managed connections let shared assistants and Team Tasks use an approved account for company tools.
Admins lead setup with the source-system owner: confirm the account, permissions, audience, and permitted actions.
Agent Activators identify the sources and actions their workflow needs, then test access with intended users.
Transformation Leaders coordinate priorities across teams.
Bring a shared assistant into a familiar team conversation.
Admins confirm the approved app and access setup.
Agent Activators lead a small team trial and help colleagues use it. Agree what needs review with the workflow owner.
Transformation Leaders plan wider introduction and support.
@ChatGPT setup and troubleshooting →
Turn a team discussion into a draft update (guide with example) →
Give repeatable work a shared home and a named owner. These are Teams in ChatGPT; Microsoft Teams is the separate collaboration app above.
Agent Activators lead design and testing with the workflow owner: define the trigger, result, reviewer, and when to pause or ask.
Admins confirm required permissions and connections.
Transformation Leaders coordinate rollout and ongoing support.
Start with a small tracker, hub, or app. Review publishing permissions with your admin, choose the right audience, and name who will maintain it. Sites is in beta; connected-app access is read-only and requires admin enablement.
Sites publishing and data access →
Build an issue-tracking dashboard with connected apps (guide with example) →
Workspace-approved plugins can add sidebar apps, interactive panels alongside conversations, and viewers for supported file types.
Start with one plugin that supports a useful team task. Admins confirm approved access; Agent Activators test the workflow and review the result.
Available features vary by plugin and where you use it.
Champion rollout guidance
Start with one workflow. Choose a recurring task your team already understands. Begin with a small group and a result someone can review.
Choose one task and who will use the result. Agree with the workflow owner on what should improve and how to measure it. Confirm the priority with the Transformation Leader.
Partners: Workflow owner, intended users, Transformation Leader.
Define your workflow’s scope and success measures (guide and worksheet) →
Learn how to scope a workflow in Activator Labs (recording) → (Academy sign-in required)
Set up the access and connections the test needs. Work with the owners of the connected tools to check permissions. Ask the workflow owner to name a reviewer and decide which actions need approval.
Partners: Workflow owner, owners of connected tools, reviewer.
Document access, approvals, and reviewers for your test (template) →
Test with intended users, including cases with missing or conflicting information. Track corrections, review time, and usage or cost. Share the results and your recommendation with the workflow owner and Transformation Leader.
Partners: Workflow owner, intended users, reviewer.
Review the results with the workflow owner and decide whether to proceed, revise, or stop. Agree who will use and maintain the workflow. Involve business function leaders or an Exec Sponsor when expansion needs their approval, people, or budget.
Partners: Workflow owner, business function leaders, Exec Sponsor as needed.
Assess whether the workflow is improving the work (article) →