“Bring one real task from your own work” is easy to say and quietly difficult to do. Asked cold, most people either reach for the hardest problem in their business - too big to build in a day - or something so trivial that automating it proves nothing. The task you choose decides what you walk away with, so it is worth choosing deliberately.
Five tests, in the order they matter.
1. You do it repeatedly
A workflow pays back every time it runs, so frequency beats size. The monthly board summary, the weekly pipeline review, the supplier update you assemble every Friday - each is worth more than a one-off, however painful the one-off is. If you do it once a quarter or less, save it for your second build.
2. It runs on words and documents
Agentic workflows are strongest where the raw material is text: notes, emails, reports, transcripts, spreadsheets exported to something readable. If your candidate task starts with “first I read through…” or “I pull together the…”, it is probably right. If it starts with a system only you can access from one locked-down screen, or with a conversation only you can have, it will fight you all afternoon.
3. You can check the output at a glance
The first build succeeds when you can look at what came out and know immediately whether it is right. Summaries, drafts, structured lists and comparisons all have that property - you have done the task yourself a hundred times, so your eye is already calibrated. A task whose output you would need an afternoon to verify is a poor place to learn, because you cannot tell whether the workflow is working.
This matters because the pattern you are learning has a review step built in: a stage that checks the draft against a stated standard before you see it. To write that standard down, you have to know what good looks like. On a task you know well, you do.
4. It is annoying enough to care about
You will hit a snag at some point - everyone does - and the difference between pushing through and drifting off is whether you actually want the result. The task that makes you sigh when it comes round again is the right raw material. Mild irritation is a better fuel than ambition here.
5. Getting it wrong is affordable
The first task should be one where an imperfect output costs you a correction, not a client. Decisions about people, anything with personal data your organisation has not approved for the tools, and outputs that go straight to someone important without review are all wrong for a learning build - not forever, just first. You are learning to build the check; do not pick the one task where a missed check is expensive.
The tasks to leave alone, permanently
The five tests above are about picking a safe first build. There is a separate question that never goes away, and it is the one that separates people who get value from this from people who automate their way into a mess: not every task is worth automating, and some should not be. Working out the difference is most of the skill.
Three kinds are worth protecting.
The ones where doing it is the thinking. Some writing exists to work out what you believe. A strategy note, a difficult piece of feedback, the argument you are still forming. Hand that to a pipeline and you get a document without the thinking that was the actual output. You have not saved an hour; you have skipped it.
The ones you do rarely. A workflow takes real time to build and a little to maintain. Something you do twice a year almost never repays that, and a half-remembered pipeline you have to debug before each use costs more than doing the job by hand.
The ones where a person has to stand behind the output. Not because a workflow could not produce it, but because when someone asks “why does it say this”, the answer has to be a person who decided, not a process that ran.
None of this is squeamishness about the technology. It is the same judgement that decides what you delegate to people, applied consistently - and the reason the reclaimed hours are worth having is that they go back into exactly this kind of work.
What this looks like in practice
Put together, the tests point at a familiar shape: the recurring assembly job. The report built from the same sources every time. The meeting notes that become minutes and actions. The inbound enquiries that need triaging into three piles. The draft that always starts from the last version. Dull, frequent, text-based, checkable - and collectively hours of your week.
Bring one of those, and by the end of a build day you have it running: a pipeline against your own task, a review step that checks the output, and a written recipe so you can rebuild and extend it afterwards. That is the deal at the Oxford Agentic Bootcamp, and the choice of task is the half of it you can get right before you arrive.