One objective per goal, three key results each. Leave a note in any box and hit Send — it lands with Claude for the next revision.
Source: AI Priorities sheet, pulled 2026-08-03 · 8 goals ranked 1-High · Drafted by Claude, awaiting Anthony's edits
Company — Adoption & Training
The through-line: Level 1 everywhere → verified by managers → buddies keep people climbing → Level 2 becomes measurable.
1. Everyone at EG AI Level 1
Objective: All 56 team members score at Level 1 or higher, and anyone who isn't has a named reason and a fix.
Owner: AnthonyIn progress
Key results
KR1: First scoring round complete — every one of the 56 names on the levels tracker has a score, no blanks.
KR2: Every person below Level 1 has a one-line blocker logged (access, training, time, resistance) plus a named fix owner.
KR3: 100% at Level 1, confirmed by each manager, not self-reported only.
Done when: the tracker shows 56/56 at L1+ with manager confirmation, zero "unknown" rows.
Sent ✓
2. A-Team verifies the self-assessments (L1 + L2)
Objective: Every department manager personally verifies their directs' self-assessments, so scores are real, not honor-system.
Owner: AnthonyUp next
Key results
KR1: Each A-Team manager gets a simple verification checklist (their directs + what "verified" means).
KR2: All 9 departments report back: every direct's assessment reviewed and confirmed or corrected.
KR3: Tracker gains a "manager verified" column at 100%, so the next scoring round is trusted by default.
Done when: every manager has attested to every direct, visible in one column.
Sent ✓
3. AI buddy with a power user
Objective: Everyone on the buddy list is paired with a power user (Jose, Anthony, or Brian) and meets on a weekly cadence to grow their AI skills.
Owner: AnthonyUp next
Key results
KR1: Pairing map approved (first draft below) and added to the levels tracker next to each name.
KR2: Every pair has a recurring weekly 30-minute invite on the calendar, and the first session has happened.
KR3: After 4 weeks, each buddy reports one concrete thing their person shipped or learned; levels tracker reflects movement.
Buddy map — first draft
Logic: department affinity first, existing working pairs locked, trios where the manager and their report share one session (same model the other departments use: manager + AI expert + learner). Load is balanced at 5-6 sessions per power user.
Person
Dept (Paycor)
Power user
Why
Brian — the A-Team + tool testers
Matt + EJ
Corporate / E-Comm
Brian existing
Already running; EJ learns from both.
Alie
Merchandise
Brian new
Tests Team Tool + Data Warehouse with him anyway.
Karlee
Planning
Brian new
Same — tester on both of Brian's builds.
Tess + Hannah
Marketing
Brian new
Trio: manager + report in one session.
Betsy
Creative
Brian new
Creative sits closest to Matt/Brian's product org.
Jose — ops, warehouse, marketplace
Lynette
Warehouse
Jose existing
Already running.
Patty
iHR Community
Jose new
Moved from Anthony per 8/4 note.
Maryanne
Merchandise (PH)
Jose new
Ops-flavored merch workflows, automation-heavy.
Alaine
Planning (PH)
Jose new
Planning data work pairs with Jose's spreadsheet automation.
Jun
Design (PH)
Jose new
Manager-to-manager; balances Jose's load.
Anthony — HR, CS, Finance orbit
Ross + L3s (Ardie, Joan)
CST
Anthony existing
Deep in the Pam work already; L3s join Ross's session.
Leonard + Josh
Marketplace
Anthony new
Anthony's call 8/4: working with Leonard on GEO, wants more face time; Josh joins as trio.
Camille
Finance (PH)
Anthony existing
Weekly AI meeting already exists.
Will
Finance
Anthony existing
Weekly AI meeting already exists.
Ara
Email Mktg + CRO (PH)
Anthony new
Load balance; influencer workflows fit Anthony's agent playbook.
Needs Anthony's input
"L2------"
?
unclear
CST L2 group or Warehouse L2 fulfillment? Name the people.
"?--------" and "---------"
?
unclear
Two placeholder cards with no name.
Updated 8/4 with Anthony's edits: Leonard + Josh moved to Anthony (GEO work with Leonard needs more face time), Patty moved to Jose. Camille and Will stay with Anthony; fresh perspective comes from a quarterly rotation instead of breaking working pairs. Still open: names for "L2------" and the two blank placeholder cards.
Sent ✓
4. Level 2 self-assessment for everyone
Objective: Every team member self-assesses against Level 2, managers confirm, and we get a company-wide L2 readiness picture.
Owner: AnthonyUp next
Key results
KR1: L2 self-assessment form built, mirroring the L1 form people already know.
KR2: 100% of team members submit it.
KR3: Managers review and confirm (same flow as Goal 2), and the tracker shows an L2-readiness score per person.
Done when: every name has a confirmed L2 readiness score — which also hands the buddy pairs (Goal 3) their curriculum.
Sent ✓
5. Every department head runs their own command center
Objective: Each department head owns one live command center they maintain themselves — graduated from the Power User command center.
Up nextOwner: TBD
Key results
KR1: A minimum command center template exists (what tabs, what data, how it self-updates) so nobody starts from scratch.
KR2: Two department heads pilot it and their feedback is folded back into the template.
KR3: Every department head is live, each updating their own center without Anthony or Brian doing it for them.
Done when: one command center per department, maintained by its own dept head for 2+ consecutive weeks.
Sent ✓
Power Users — Brian's builds
All three share the same pipeline: Power User → A-Team → Company. Same three key results, different testers.
6. Test the Team Tool
Objective: The Team Tool gets real daily use from its testers, bugs are worked to zero blockers, and it ships to the whole company.
Owner: BrianUp nextTesters: Alie, Jose, Anthony, Karlee, Matt
Key results
KR1: All 5 testers use it in real work weekly and log bugs/friction in one shared list.
KR2: Blocker-level bugs at zero; Brian confirms it's ready for strangers.
KR3: Shared with the entire company, with a one-page "how to start" so rollout doesn't need hand-holding.
Sent ✓
7. Test Workbench
Objective: Same pipeline as the Team Tool: real use, bugs fixed, shipped company-wide. (The "Replace Basecamp for personal use" goal is on hold and rides on this one.)
Owner: BrianUp nextTesters: Jose, Anthony
Key results
KR1: Jose and Anthony run real workflows in Workbench weekly, logging bugs in the shared list.
KR2: Blockers at zero; the personal-Basecamp replacement question gets a go/no-go answer from actual use.
KR3: Shared with the entire company.
Sent ✓
8. Build the Data Warehouse
Objective: The Data Warehouse gets built, its data validated by the people who know the numbers, and shipped company-wide.
Owner: BrianUp nextTesters: Alie, Leonard, Karlee
Key results
KR1: Testers validate the numbers against their own sources — the warehouse matches reality before anyone trusts it.
KR2: Each tester answers one real business question from it that used to take manual pulls.