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 with your Dot.
Transformation Leaders and Exec Sponsors can start with one ongoing responsibility they personally own, such as keeping an offsite plan on track.
Best Practice: Use approved sources, name decisions that need your input, and review progress in Activity. Share a useful delegation example with colleagues, including what you corrected and how much review it needed.
Guardrails: Keep personal delegation distinct from a workflow other people need to own or run. Before encouraging wider use, compare the time saved with the corrections and review effort.
Keep an offsite plan and deadlines on track (guide with example) →
Organize shared files, Pages, and context so a team can continue its work.
Transformation Leaders can start with one active project whose decisions and handoffs are scattered.
Ask an Agent Activator (e.g. the project owner) to create a shared plan, name who keeps it current, and show colleagues where to find decisions and next steps.
Best Practice: Check membership, sharing, and permissions for connected sources. Test access to the page and its linked sources with intended collaborators.
Guardrails: Before extending this approach, check whether colleagues can pick up the work without asking someone to reconstruct the context.
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.
Transformation Leaders should prioritize one workflow that needs a shared account and bring its owner, a Platform Admin, and the source-system owner together.
Admins lead setup: confirm the account, permissions, audience, and permitted actions. Name who maintains the connection and resolves access failures.
Agent Activators should test approved reads and any permitted actions in that workflow with intended users. Check who can open generated files; a shared account may have different access from a participant.
Guardrails: Before reusing the connection across teams, review the trial’s access failures and support needs with the owners.
Bring a shared assistant into a familiar team conversation.
Transformation Leaders can start with one team and one recurring need, such as turning a discussion into a draft update.
Platform Admins work with Slack or Microsoft Teams admins to confirm the approved app, audience, and company connections. Review the connected account’s access for that audience.
Agent Activators lead the trial: share an example request, agree what the workflow owner reviews, and tell colleagues where to get help.
Best Practice: Test with intended participants. Replies are visible to the conversation’s participants; check access to any generated files separately.
Guardrails: Use corrections, review effort, and colleagues’ willingness to reuse it to decide whether to introduce it to more teams.
@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.
Start with one recurring output, such as a weekly project update. Agent Activators lead design and testing with the workflow owner: define the trigger, result, reviewer, and when to pause or ask.
Platform Admins confirm team membership, required permissions, and connections. Members can see earlier runs and generated files, so review what the pilot team should be able to access.
Transformation Leaders coordinate rollout and ongoing support: agree who monitors results, corrects failures, and maintains the task.
Guardrails: Review several runs for missed information, corrections, and ongoing effort before asking an Exec Sponsor to support wider use.
Start with a recurring task where colleagues need to find, compare, or act on information.
Agent Activators should review publishing permissions and the intended audience with a Platform Admin.
Best Practice: Choose a small, approved set of inputs and define what the Site should help someone do. Try it with a few colleagues in their real work, then decide whether it’s useful enough to maintain and share more widely.
Guardrails: For connected apps, keep the Site private to the workspace and test with each pilot user’s own account.
Note: Connected-app access is currently read-only and requires admin enablement.
Transformation Leaders should name a maintainer and collect feedback on task completion, time spent searching, and the help colleagues need to use it.
Sites publishing and data access →
Build an issue-tracking dashboard with connected apps (guide with example) →
Sites technical guide: hosting, storage, access, and secrets →
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, such as preparing a design or reviewing a supported file. Platform Admins confirm approved access and permitted actions; Agent Activators test the workflow and review the result.
Transformation Leaders should give the pilot group a worked example and a support contact.
Best Practice: Check whether the plugin reduces steps or rework, and what help colleagues need, before recommending it more widely.
Guardrails: Available features vary by plugin and where you use it. Confirm the feature is available on the web or desktop surface your team will use.
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) →