Talk

AI and How Work Changes

A practical talk on how AI changes everyday work: choosing repeatable workflows, keeping people in review, and what changes when AI can plan and act.

Direct answer

Direct answer: AI and how work changes

This talk explains how AI actually changes work without forecasting that everyone will be replaced. It starts from the recurring tasks people already do, shows how connected and reviewable AI workflows return time, and explains in plain language what changes when a model can plan, call tools, and keep state. Audiences leave knowing which work to start with, where people must stay in review, and the questions leaders should ask before scaling.

The question

“We need a practical talk on how AI changes work without hype about replacing everyone. What is the audience takeaway?”

Who it is for

Business conferences, professional bodies, company all-hands and leadership events, and internal AI adoption programmes.

Abstract

What the talk covers

Most people have tried an AI assistant, and most weeks still look the same. The gap is rarely the model. It is the absence of a repeatable workflow with clear inputs, a reviewable output, and someone responsible for checking it. This talk starts from the recurring work people already do—email, meetings, research, reports, task tracking, spreadsheets—and shows how connected, reviewable AI workflows return time without removing judgement. It then explains, in plain language, what changes when AI moves from generating text to planning, calling tools, and keeping state: authority, review, and accountability become the questions that matter. The session avoids forecasts about replacing everyone. Instead it gives the audience a way to choose the right work to start with, keep people in review, and measure whether the change is useful. Leaders leave with the decision questions to ask before anything scales.

The audience leaves able to

  • →How to pick recurring tasks where AI can return time with a reviewable result
  • →Where people must stay in review, and why that is a design choice rather than a limitation
  • →What changes when AI can plan, call tools, and keep state
  • →Which ownership, data, and measurement decisions leaders should make before scaling

Audiences

Business Operations Leadership AI adoption

Formats

  • Keynote
  • Conference talk
  • Panel
  • Webinar
  • Podcast
  • Workshop variant

What you leave with

Audience-specific abstract, workflow examples, and leadership decision questions.

  • 01 An abstract tailored to the audience’s sector and roles
  • 02 Workflow examples drawn from email, meetings, research, reports, task tracking, and spreadsheets
  • 03 A short list of leadership decision questions to use after the session
  • 04 Short and long speaker biographies from the speaker kit

How it runs

Structure and format

Duration
30–45 minutes as a talk or keynote; 90 minutes to a full day as the “Build Your Automated Week” workshop
Delivery
In person in the UK, travel by agreement, or remote
Participants
Business professionals, managers, operations teams, and leadership audiences; no technical background required
01

From occasional prompts to connected work

Why one-off prompting rarely changes how a week is spent, and what a repeatable workflow looks like.

02

Choosing the right work

How to pick recurring tasks with clear inputs, a reviewable output, and a measurable time or quality change.

03

From generative to agentic

What changes when a model can plan, call tools, and retain state, and why authority and review become the central questions.

04

Decisions for leaders

Ownership, review points, data boundaries, and how to measure whether the change is useful rather than merely busy.

Audience assumptions

  • →No technical background is assumed
  • →For a workshop variant, participants need access to the AI tools their organisation permits

Evidence

What this draws on

Published book

AI for Everyday Automation (Packt, 2026)

Seven connected workflows for email, meetings, research, reports, task tracking, spreadsheets, and professional communication, each with people kept in review.

Read more →
Open teaching material

GenAI and Agentic AI Playbooks

21 open chapters in ten languages under Apache 2.0: a business-leader guide to GenAI adoption followed by an engineering and operating guide to agent systems.

Inspect the source ↗
Workshop catalogue

Hands-on workshop formats

Four defined formats (governed agents, agent reliability, multi-agent coordination, and an automated working week), each built around a participant artefact rather than slides.

Read more →

Scope and limits

What this is not

  • —The talk does not forecast headcount effects or promise a specific number of hours saved for any organisation.
  • —Workflow examples are illustrative patterns from the book; results depend on the organisation’s tools, data, and review practices.
  • —It is a talk, not a staff enablement programme; changing how a team works day to day is separate work.

If the need is different

Common questions

Answers before you commission

Is this a “future of work” keynote?+

It is a practical one. It focuses on the work people do this month, how AI can change it with people kept in review, and what leaders must decide, rather than long-range predictions.

Does it say AI will replace jobs?+

No. It treats AI as a change to tasks, review, and responsibility, and leaves workforce decisions to the organisation, with questions that help leaders make them deliberately.

Is it based on the book?+

Yes. It draws on AI for Everyday Automation (Packt, 2026) and the open GenAI and Agentic AI Playbooks.

Can attendees build something during the session?+

Yes, in the workshop variant “Build Your Automated Week”, where each participant maps one recurring task and builds a reviewed AI-assisted workflow for it.

Related

Next step

Invite Dipankar

A short written brief is enough to establish fit. I reply personally, and say plainly when the work belongs elsewhere or is not worth commissioning.

Talk, panel, or event workshop: what to include

  • →Event name, organiser, and website
  • →Audience: size, roles, and technical depth
  • →Preferred topic or the problem the audience faces
  • →Format and length (keynote, talk, panel, podcast, workshop)
  • →Date, time zone, and location or remote
  • →Fee, travel, and accommodation arrangements
  • →Recording, publication, and reuse terms
  • →AV and lab environment, if a workshop