Using AI well in a job and rolling it out to a team: playbooks, use cases, enablement. 17 pages. Generated by scripts/build_manifest.py - do not edit by hand.
Give your staff a short, plain-language AI policy that says which tools are approved, which data can go into them, and who is responsible for the output - and copy the template on this page to get there in an afternoon.
Roll AI out to a team or company in four phases over about twelve weeks - set guardrails, pilot with volunteers on real tasks, measure, then scale what worked - instead of buying licences for everyone and hoping.
Recruit one respected, curious person per team as an AI champion, give them a few hours a month, a clear job and a direct line to the rollout owner, and they will spread working habits faster than any central training team can.
Pick a company-wide AI assistant (ChatGPT, Claude, Gemini or Microsoft Copilot) by checking data terms, admin controls, where your work already lives, and real cost per active user - in that order - rather than by which model topped a leaderboard this month.
Measure AI's value task by task against a baseline - time, quality, errors and adoption - using timestamps and blind review rather than self-reported feelings, and turn hours saved into money only when they actually go somewhere.
Teach AI as a work skill, not a tool tour - a 90-minute hands-on starter session on people's own tasks, then short weekly practice and a shared prompt library - and you will get far more use than from any slide deck.
Use AI to write and explain formulas, SQL and Python, clean messy data, and draft the narrative around your findings - but have it produce code you run, not numbers you trust, so every result is reproducible and checkable.
Use AI across the whole engineering job - not just autocomplete, but understanding unfamiliar code, writing tests, debugging, design docs, reviews and on-call - while keeping your review bar, your tests and your secrets hygiene exactly where they were.
Use AI to cut the writing and synthesis load of managing - updates, meeting prep, plans, first drafts of documents - while keeping it well away from judgments about people, and set clear expectations so your team uses it well too.
Use AI to brainstorm, draft, repurpose and test marketing content faster, while a human owns the strategy, the facts, the brand voice and anything legally risky - because generic AI copy is easy to make and easy for your audience to ignore.
Use AI to research accounts, prepare for calls, write first-draft outreach and follow-ups, and fill in CRM notes faster - then put the saved time into conversations, because the relationship and the judgment are still yours.
Use AI to draft replies from your knowledge base, summarise long tickets and threads, write and update procedures, and triage incoming work - with a human sending every customer-facing answer until you have measured that the AI gets it right.
Roll out coding assistants and agents to an engineering team with clear rules for context, review, testing, secrets and agent permissions, and judge them on delivery and quality metrics rather than on how much code they generate.
Automate customer support in stages - agent assist first, then AI answers for narrow, proven question types, then actions behind strict limits - grounding every answer in your own approved content and always keeping a fast route to a human.
Use AI to read invoices, contracts, forms and emails and pull out the fields you need - starting with a chat assistant for one-offs and moving to a checked, structured pipeline with human review for anything at volume.
Use AI to transcribe meetings and turn them into decisions, action items and short summaries - with everyone's knowledge and consent, a human checking owners and dates, and clear rules about what gets recorded and kept.
Use AI search and "deep research" tools to find, read and synthesise sources much faster, but treat every claim and citation as unverified until you have opened the source yourself - because these tools still misquote and invent references.