Sharper, Not Smaller: The Business Analyst in the Age of AI
- Folayemi Tee
- 3 days ago
- 5 min read
Day 2 |What to Hand to AI (The Safe List)

Yesterday I drew one line: artefact versus accountability. Today I want to make it practical, starting with the side you can give away. Most analysts are carrying work they do not need to carry. It feels like the job because it has always been the job. But a lot of it is scaffolding, not skill, and scaffolding is exactly what AI is built for.
I want to name the feeling that comes up here, because it stopped me for a while. There is a quiet pride in doing the whole thing yourself. It feels like craft. But pride in the wrong place is expensive, and a lot of what we do by hand out of habit is not craft at all. It is just time spent. Here is the test I use. If a task mostly turns information you already have into a tidier shape, and a competent stranger could check the result in minutes, it belongs on the safe list. If the task requires you to decide what is true, what matters, or who to trust, it does not. Keep that question in your head as you read.
The safe list
First drafts of documentation. Not the final word, the rough clay. Give the tool your notes and a structure, and let it produce a first pass you then shape. Starting from a blank page is the slowest part of writing, and it uses none of your real skill. Start from a draft instead and spend your energy on what the draft gets wrong.
Summarising long inputs. Workshop recordings, call transcripts, sprawling email threads, sixty-page vendor responses. AI is strong at pulling the shape of a long document into something you can scan in two minutes. You still read for what it missed, but it gets you to the real reading much faster.
Reformatting and restructuring. Turning a messy list into a table. Converting requirements into a consistent template. Rewriting a paragraph into plain language for a non-technical audience. This is mechanical reshaping of content you have already decided on, and it eats hours when you do it by hand.
Generating first-pass test cases and acceptance criteria. Hand the tool a user story and ask for the obvious scenarios. It will give you the standard happy path and the common edge cases quickly. Your job is to add the strange, project-specific cases it could never know about, but the routine 90% is a fine starting point.
Initial data exploration. Ask it to describe a dataset, suggest what to check, or sketch the questions worth asking. It will not understand your business, but it will save you the setup time of working out where to point your attention.
Naming and wording options. Stuck on a heading, a field label, a way to phrase a tricky sentence in a stakeholder email? Ask for ten options and pick the one closest to right. Low stakes, fast, genuinely useful.
Drafting questions for discovery. Before a workshop, ask it to generate the questions a thorough analyst would ask about a process. You will know your context better, but it is a good prompt against your own blind spots.
Notice the shape of this list. Every item takes existing information and turns it into something more useful. None of them asks the tool to decide anything that matters. That is not an accident. That is the test doing its work. When you hold a task up against it, the safe ones almost sort themselves.
Why handing this over is not lazy
Some analysts feel a flicker of guilt about this as though good work has to be slow and done entirely by hand to count. Let that go. Nobody admires a carpenter for refusing to use a power drill. The skill was never in the turning of the screw. It was in knowing what to build and whether the result is sound. The same is true here. The value was never in you personally typing the first draft of a requirements section. The value is in the requirements being right, complete, and defensible. The drill does not make the carpenter less skilled. It makes them faster at the part that was never the point.
When I moved this work off my plate, two things happened. My week opened up, and the quality of my real work went up, because I had more attention left for the parts that needed it. Let me give you a real number from my own week. I used to set aside the better part of a day to turn a long discovery session into clean, structured notes. Recording, replaying, typing, tidying. Now a tool gives me a first-pass summary in minutes, and I spend perhaps forty minutes correcting it, adding the context it missed, and flagging the moments that need a follow-up. The notes are better than they used to be, because I am reading for meaning instead of straining to transcribe. The hours I saved did not vanish. They went into the conversations that actually needed me.
The one trap to avoid
There is a catch, and it is the same one that embarrassed the junior analyst from yesterday. Handing over the production of an artefact is safe. Handing over the judgment inside it is not. Every item on this list produces a draft, not a decision. You read it, you correct it, you own the result. The safe list is not a list of things you stop caring about. It is a list of things you stop typing from scratch. You still own every word that goes out under your name. You are just no longer doing the slow, mechanical first 90% by hand.
A simple habit makes this safe. Never send AI output onward without reading every line as if you wrote it, because as far as the room is concerned, you did. If you cannot defend a sentence, cut it or rewrite it until you can. This is also where a quiet professional standard separates strong analysts from careless ones. The careless analyst treats the draft as the finish line. The strong one treats it as the start line. Same tool, completely different outcome, and the difference is entirely in the human who picks the draft up.
Try this today
Look at your calendar for the past week. Find the single task that took the most time and used the least judgment. That is almost certainly your first safe-list candidate. Run it through a tool once, properly. Give it good input, take the draft, and finish it by hand. Time both the old way and the new way. The gap will tell you, more convincingly than I can, how much of your week you have been spending on scaffolding. Do this honestly, and the result usually surprises people. The task you dreaded most, the one you kept pushing to Friday afternoon, is often the one that frees the most time the moment you stop doing it by hand. Start there. The momentum from one good handoff makes the next one easier.
Tomorrow we cross the line. We look at what must never go on this list, no matter how good the tools become, because that is where your real value lives.
Go out and be successful.
Oluwatosin Ogunkoya | Flotog BA Insights | www.flotogbainsights.com
TOMORROW: What to Never Hand Over
The parts of the role that must stay in your hands no matter how good the tools get, and why they are about to be worth far more than they were.



Comments