Ali · Analyst
Observes the work and writes the brief.
Output: process, problem and acceptance criteria
NotionStrategyOwnership03 / 05
AI reaches every team.
Who owns the outcome?
The transformation team cannot own every department’s work. Company leadership sets priorities and resources. A shared team builds the capability. Departments retain ownership of outcomes and actual use. Connect these three layers.
Transformation team and responsibility mapSponsor and decision forum, transformation team, business owners and champions, with explicit decisions and handoffs.
NotionStarting team / three responsibilitiesILLUSTRATIVENotionNima · Builder
Builds the workflow, connections and tests.
Output: Activepieces workflow + evaluations
Claude CodeSara · Business owner
Commits the goal and team time; accepts the outcome.
Output: improve, adopt or stop decision
JiraAcross teams, responsibilities specialize.
The sponsor provides resources. A transformation manager coordinates priorities, an architect designs connections and authority, an evaluation engineer tests quality, and champions support daily use. Risk reviewers join according to data and impact.
FIELD, its figures, conversations and decisions are fictional worked examples.
Specialize responsibilities as more teams work in parallel.
The transformation manager coordinates priorities and teams. Analysis, architecture, implementation and evaluation can become distinct roles. Departments retain accountability for their own business outcomes.
COMPANY DECISIONS
Executive sponsor
Priorities, funding and escalation
COMPANY DECISIONS
AI decision forum
Portfolio, risk and investment decisions
COMPANY DECISIONS
Transformation manager
Team coordination, architecture and outcome review
Shared capabilities serving business goals
Business analyst
Observe work → brief
BriefObserveAcceptance
NotionAI architect
Context, tools and controls
System + Tools + PeopleKnowledge + MCPFilter → Structure → Gate
Claude CodeAgent engineer
Workflows, skills and integration
ap_build_flowap_validate_flowap_test_flowDraft; release requires approval
CodexEvaluations engineer
Tests, quality and evidence
R1 / R3 / R5 PASSR2 / Brand 3.6 / 5Target 4/5; iteration needed
LangfuseOutcome ownership and acceptance remain with each department
PhotoshopGrowthBusiness owner + champion
ZendeskSupportBusiness owner + championJiraProductBusiness owner + champion
Google SheetsFinanceBusiness owner + champion
ActivepiecesOperationsBusiness owner + championFIELD, its decisions and figures are educational examples. A company’s actual artifact requires its own data, owners and evidence.
Transformation team and responsibility map
These owners now define the company’s AI rules and approval decisions.
NotionWho hands what to whom?ILLUSTRATIVEBuildable brief
Current work, tools, people, inputs and acceptance examples; beyond “build an agent”.
NotionWorkflow + test results
Reviewable draft, approval route, behavior checks and quality scores.
ActivepiecesUse and improvement decision
Did work improve? What must be fixed? Who supports everyday use?
JiraFIELD, its figures, conversations and decisions are fictional worked examples.