Day 1 · 18:00–18:05

Welcome and ground rules

RECORD onSHARE deck

Welcome. Over three evenings this week and two more for the technical group, you will learn to do real work with Claude, not watch me do it. Keep your camera on and your mic muted. Put questions in the chat at any moment. The pattern for every block is simple: ten minutes of method, ten minutes of me doing it live, then you do it on your own screen while I watch.

Day 1 · 18:05–18:15

Pre-assessment

STOP sharePAUSE 10 minPOLL done?

Before we start, a short baseline. Twenty questions, ten minutes, the link is in the chat. Nobody fails this. The same questions come back at the end so we can both see what changed.

Day 1 · 18:15–18:40

How Claude works

SHARE claude.aiDEMO new chat, attach a file, switch model

Claude is a model that writes the next words from everything you put in front of it. That is the whole trick. It knows what is in this chat and the files you attach, nothing else. It does not see your inbox or your ERP unless a connector is switched on. Three models: the strongest one for hard analysis, the middle one for daily work, the fast one for sorting. We will choose between them all week.

Day 1 · 18:40–19:25

Prompt engineering: the four-box brief

SHARE demo: shift handover summarySTOP sharePAUSE 20 minPOLL paste your best prompt in chat

A good prompt is a good brief. Four boxes: who Claude is, what it needs to know, what you want, and how you want it laid out. Add a constraint and one example and the quality jumps. Now you. Take a request you really send at work, write it badly first, then rewrite it in four boxes, and compare the two answers.

Break

Break

BREAK

Ten minutes. Back at seven thirty-five.

Day 1 · 19:35–20:20

Verification: trust but check

SHARE demo: ask for sources and a check tableSTOP sharePAUSE 20 minPOLL how many errors found?

Claude can be wrong with full confidence. So every output gets three questions: where did this come from, what did you assume, and show me a check table. I have planted five errors in a water-quality summary. Find them against the source CSV. Then we agree the verification checklist you will sign off on.

Day 1 · 20:20–21:00

Document analysis

SHARE demo: compare two PDFsSTOP sharePAUSE 25 minPOLL one takeaway in chatSTOP record

Now documents. Drop in a contract, a procedure, a forty-message email thread, and ask for the comparison, the extraction or the reply. Procurement people, compare the two supplier term sheets. HSE people, pull every action and owner from the incident report into a table. Everyone else, pick the one closest to your work.

Day 2 · 18:00–18:45

Excel and CSV analysis

RECORD onSHARE demo: production-log.csvSTOP sharePAUSE 25 minPOLL worst day?

Tonight we start with numbers. Upload the production log, tell Claude in one line what each column is, then ask the questions a manager asks: what moved, why, and what should I look at first. Insist that every figure traces back to a cell. Your task: find the three worst days for energy per cubic metre and explain them.

Day 2 · 18:45–19:25

Reporting, slides and Artifacts

SHARE demo: Artifact dashboardSTOP sharePAUSE 20 min

An analysis nobody reads is wasted. Ask for a one-page management note, then a six-slide outline. Then ask for an Artifact: a live dashboard with the charts, that you can edit and share. Build both from the analysis you just did.

Break

Break

BREAK

Ten minutes.

Day 2 · 19:35–20:20

Projects, Skills and Memory

SHARE demo: create Project, add files, write SkillSTOP sharePAUSE 30 minPOLL Skill name in chat

Stop pasting the same background every time. A Project holds your department's procedures, glossary and tone once. A Skill is a recipe for a task you repeat: the weekly dispatch summary, the lab trend note. Memory keeps what matters between chats. Build your department's Project now and write one Skill for a task you do every week.

Day 2 · 20:20–21:00

Research, Cowork and scheduled tasks

SHARE demo: schedule a taskSTOP sharePAUSE 20 minSTOP record

Three features that do work while you are not there. Research reads many sources and cites them: benchmark RO energy use from public data. Cowork runs a chain of steps from one instruction. Scheduled tasks deliver on a timer. Set up one weekly brief that lands in your inbox on Sunday morning without anyone asking.

Day 3 · 18:00–18:45

Claude in Excel and Chrome

RECORD onSHARE demo: Excel add-inSHARE demo: Chrome extensionSTOP sharePAUSE 25 min

Tonight Claude moves into the tools you already use. In Excel, the add-in cleans data, writes formulas and summarises without leaving the workbook. In Chrome, the extension reads the page you are on and acts on it. Clean the maintenance tickets in place, then turn one supplier product page into a comparison row.

Day 3 · 18:45–19:25

Microsoft 365 connectors

SHARE demo: Outlook and SharePoint connectorsSTOP sharePAUSE 20 minPOLL which connector first?

With the Microsoft connectors on, Claude reads your Outlook thread, finds the procedure on SharePoint and tells you what happened in a Teams channel this week. If IT has not enabled a connector yet, we do the same task by uploading the export, and you leave with the exact request to send IT.

Break

Break

BREAK

Ten minutes.

Day 3 · 19:35–20:35

Department labs

BREAKOUT 6 rooms, 55 minPAUSEPOLL back in main room at 8:35

This is the hour the week was built for. Breakout rooms by department. Each team brings one real task and finishes it tonight. I rotate between rooms every ten minutes. Before you leave the room, write the recipe down: the prompt, the files, the checks. That recipe is what you keep.

Day 3 · 20:35–21:00

Automation map and post-assessment

SHARE automation mapSTOP sharePAUSE 10 min assessmentSTOP record

Last block. Sort ten of your tasks into three boxes: rules, AI, or hybrid. Then each department names the next three things it will automate. Finish with the same twenty questions from Monday. Certificates and the completion report go to HR within three working days.

Day 4 · 18:00–18:35

Console, workspaces, keys and Workbench

RECORD onSHARE ConsoleSTOP sharePAUSE 15 minPOLL key working?

Welcome back, technical group. Tonight you move from the chat window to the platform. Create a workspace, issue a scoped key, set a spend limit. Run the same prompt on three models in the Workbench, compare, then export it as code. By the end of this block you have a key and you know what a call costs.

Day 4 · 18:35–19:25

Messages API: system prompts, multi-turn, streaming

SHARE terminal and editorSTOP sharePAUSE 30 minPOLL paste your first streamed line

The Messages API is one call: a model, a system prompt, a list of messages. You own the conversation history, so multi-turn means you append and resend. Streaming makes it feel instant. Build a small command-line tool that answers questions about a plant procedure, streams the answer, and remembers the conversation.

Break

Break

BREAK

Ten minutes.

Day 4 · 19:35–20:20

Python and TypeScript SDKs, long documents, caching

SHARE both SDKsSTOP sharePAUSE 25 min

Here is the same call in Python and in TypeScript. You work in Python; I show the TypeScript so you can port it later. Then long documents and prompt caching: load the sixty-page operations manual once and ask it twenty questions cheaply.

Day 4 · 20:20–21:00

Structured JSON output

SHARE demo: schema and tool-useSTOP sharePAUSE 30 minSTOP record

Business systems want JSON, not prose. Define the schema first, use tool-use so the model fills the schema, validate every record, and decide what happens when one fails. Your task: twenty supplier quotations into one validated JSON array, then a CSV you could hand to procurement.

Day 5 · 18:00–18:50

Claude Code

RECORD onSHARE terminalSTOP sharePAUSE 30 minPOLL change shipped?

Claude Code is Claude in your terminal with your repository open. It reads the code, makes the change, runs the tests. Tonight you open yesterday's extraction project and ask it to add an Excel export with a summary sheet. Watch what it asks permission for and why.

Day 5 · 18:50–19:25

Agents, Agent SDK and standard MCP servers

SHARE demo: MCP configSTOP sharePAUSE 20 min

An agent is a loop: think, act, observe, repeat. It beats a script when the steps are not known in advance. MCP is the standard socket that gives Claude tools and data. Connect a standard server to Claude Code and ask questions about last night's extraction results in plain English.

Break

Break

BREAK

Ten minutes.

Day 5 · 19:35–20:20

Custom MCP server

SHARE demo: write and run the serverSTOP sharePAUSE 30 minPOLL server answering?

Now you write one. Forty lines of Python, one function that returns today's plant output, and Claude can call it. Start from the template, run it, connect it, ask Claude for today's output. Once that works you know how to expose any internal system the same way.

Day 5 · 20:20–21:00

Integration concepts, administration, close

SHARE admin console walkthroughSTOP sharePAUSE 20 minPOLL post-assessmentSTOP record

Last block. Where does Claude sit in your systems: next to the ERP, the maintenance system, the SCADA exports, email and SharePoint. Batch or real-time, always logged, and a human approves anything that matters. Then the admin side: single sign-on, roles, approvals, retention, spend alerts. Finish by drafting a one-page proposal for one integration you would build first.

← Programme page