Appendix · Schedule

Example 12-week
engagement schedule.

A practical cadence for the
initial 3-month project.

The project starts with clarity,
then moves into building.

This example schedule shows how the initial engagement moves from assessment and foundation work into personal-agent enablement, use-case discovery, one first team agent, and a final retrospective.

Example cadence
Month 1 · Assess and prepare
Week 1
Assessment

Two assessment workshops

Mon + Wed, 1.5h each. Data, context, current AI usage, and existing agents.

Fri: assessment report
Week 2
Decision

Discuss results and choose actions

Tue + Thu, 1h each. Review the assessment and decide the foundation actions.

Output: action list
Week 3
Foundation

Start selected actions

Improve access, structure, permissions, documentation, capture, or tool setup.

Work block: foundation
Week 4
Foundation

Complete selected actions

Finish the most important changes so agents can reach more of the right information.

Output: stronger foundation
Month 2 · Enable and discover
Week 5
Personal agents

Introduce personal-agent workflows

Two 1.5h employee workshops on practical personal-agent use and safe daily habits.

Output: employees start using agents
Week 6
Discovery

Run use-case discovery workshops

Two 1.5h workshops to surface workflows, pain points, and candidate team agents.

Fri: use-case backlog
Week 7
Selection

Select first use case and agent

Choose the first team-agent use case, define scope, ownership, and success criteria.

Output: build scope
Week 8
Build

Build the first team agent

Implement tools, instructions, permissions, workflow handoff, and evaluation criteria.

Output: first version
Month 3 · Deploy and improve
Week 9
Deploy

Deploy to the selected team

Onboard users, define feedback paths, and start using the agent in the real workflow.

Output: agent in use
Week 10
Iteration

Run the agent iteration loop

Evaluate performance, inspect failures, and adjust instructions and workflow fit.

Work block: improve agent
Week 11
Iteration

Continue iteration

Clarify boundaries, improve quality, and document what the team learned.

Output: improved agent + learnings
Week 12
Close-out

Retrospective and project ending session

Review outcomes, capture lessons, decide what continues, and identify next opportunities.

Output: next-step roadmap

Fixed Cadence

The schedule creates enough structure to keep momentum without pretending every organization needs the exact same actions.

Early Foundation

The first month focuses on what agents can access, because the later team agent depends on useful organizational context.

One Agent First

The build phase stays intentionally narrow: one selected use case, one team agent, and enough iteration to learn what works.