Tutorials, real-world applications, and plain-English explanations — for people who use AI at work but don't want to read a research paper to understand it.
You don't build an agent, you configure one, and it comes down to four decisions, none of which involve programming. The fourth is the one nobody mentions and the one that keeps you out of trouble.
A short AI workshop where everyone builds one real thing, the agenda, why each block is that long, and the fifteen minutes of scope-cutting that decides whether it works.
The safest way to use AI on a spreadsheet is to never let it hand you a number. Ask for the formula instead: it's auditable, it recalculates, and it's the one thing decades of spreadsheet research says actually catches errors.
Google mapped 14.7 million AI conversations to real occupations. AI showed up in 68% of them, but in the median job, it touched just 21% of the tasks. Here's what that gap actually means for your week.
In one week this month, Anthropic put Claude Cowork on phones and OpenAI shipped ChatGPT Work. Both do multi-step jobs with little supervision. Here's how to pick the first task to hand over, and the one to keep.
40% of workers got hit with 'workslop' last month, AI output that looks finished but isn't. Each piece took nearly two hours to clean up. Here's how not to be the person sending it.
47% of U.S. employees say their company has integrated AI, but only 15% use it daily. That gap isn't a training problem or a tool problem. It's an ownership vacuum, and there's a two-hour-a-week fix.
Over 80% of enterprise AI projects fail, twice the rate of normal IT projects, and it's almost never the technology. It's that companies buy the licenses and skip the training. Here's the gap, and what the survivors do differently.
Most people use Claude like a chatbot and never touch the four built-in capabilities that do the real work: file creation, Projects, Artifacts, and web search. A plain-English tour of what each does, when to reach for it, and where each one bites.
AI cuts professional writing time by about 40%, but the study that found it used tasks with no real context and no relationships. Here's how to close that gap and get replies that actually sound like you wrote them.