Log in to Claude.ai via SSO
Go to claude.ai, click Continue with Google, use your @samba.tv account. You're already provisioned — no request, no wait.
What's available, who's leading it, where to ask, where to plug in.
If you've never opened Claude, start here. The first useful thing you'll do is small — that's the point.
Go to claude.ai, click Continue with Google, use your @samba.tv account. You're already provisioned — no request, no wait.
Pick something tedious you do every week — formatting a deck, summarizing a long thread, cleaning a CSV. Ask Claude. Don't overthink the prompt; just describe what you want.
Share what you tried. Working or not, both are useful. The channel is where Champions answer questions and where good prompts get circulated.
All seats are paid for. All training is open. All Champions are reachable.
Chat for one-off questions. Cowork for projects with shared context. Claude Code and Cursor for engineering. What to pick when, and how to access each.
TrainingLive sessions across NA, Taipei, Sydney, EU. Recordings of every past session. Cohort kickoffs throughout Q2.
ChampionsChampions sit inside every region and most divisions. They answer in Slack, run local sessions, and triage real problems faster than the help desk.
Chat is great for one-off questions — quick answers, quick rewrites, quick lookups. But that's where most people stop, and that's where the leverage stops too. Every conversation starts from zero. Nothing compounds.
Cowork is collaborative — shared context, persistent projects, multi-step work that builds on itself. Code (Claude Code, Cursor) is where engineers move from autocomplete to actual delegation, shipping changes that used to take days. Both surfaces multiply leverage instead of consuming it one prompt at a time.
The breadth number — 84.5% adoption across 336 seats — is real. People are logged in. The Q2 push is depth: moving the median user from "I asked Claude a question this week" to "I built something with Claude this week." That's the shift Cowork and Code unlock, and it's where we're concentrating training, Champions, and cohort time for the rest of the quarter.
Day-to-day execution and exec coverage — that's the whole accountability stack.
Lead AI Product Manager · AI Task Force
Day-to-day owner of the Task Force. Runs the program, builds the tooling, answers the hard questions, ships the cohorts. If something's broken or unclear, this is the line of accountability.
Office of the CEO · AI Adoption
Owns Lunch & Hacks coordination across the four regional cohorts. Connects the program to exec priorities; the path runs through her if a manager has a concern.
Numbers refresh weekly from Anthropic admin reports + internal champion roster. Source of truth for every page on this hub.
Adoption isn't a marketing problem. It's five operational levers, pulled in concert.
Embedded experts in every region and most divisions — first line of help, local advocates.
Weekly informal sessions where people demo what they built. Low pressure, high signal.
Newsletter, Slack, all-hands moments. Steady drumbeat so AI stays top-of-mind, not novelty.
QBR-tracked metrics, Champion check-ins, manager visibility into team-level adoption.
Cohorts, office hours, recordings library — depth-focused programming for the next stage.
Public dates for newsletters and regional cohort kickoffs. Add the ones relevant to your region to your calendar.