Skip to article

Workflow Clarity Comes First: Fixing Broken Processes Before Adding AI

Bloomberg's CTO described a process drawn as five boxes. Each box was a team, and the arrows were tickets.

By Jacqueline V. TwillieNovember 20, 20264 min readGuide
Quick answer

Automating a process nobody has mapped keeps its delays. Before you add an AI agent, map the workflow on one page: the trigger and goal, the inputs, the steps and the definition of done. If the boxes on your page are teams and not steps, you have a redesign project to finish before any automation.

A slow process invites a quick fix, and an AI agent looks like one. Plugged into an unclear workflow it has no written steps to read.

An AI agent struggles inside an unclear process

People inside a messy process fill the gaps themselves. They know which spreadsheet is out of date and which manager has to sign off, and none of it is written. An AI agent has only what you gave it. BNEDai's published guidance says an AI agent follows instructions literally, including the parts you left out.

If three account managers prepare for an executive call three different ways, the instructions have to pick one. Choosing is the work. The AI agent can't do it for you.

Bloomberg's CTO described a process made of teams

Shawn Edwards, Chief Technology Officer at Bloomberg, said getting new data ready for their systems went from two to three months down to realistically a week. He said one of his leaders came back with a diagram of five boxes. Each box was a team, and the arrows between them were tickets. His example was a ticket sent back to someone who is on vacation for two weeks.

Instead of automating each team's steps, Bloomberg built a data design studio, an AI-assisted modeling tool that a subject matter expert uses to do those steps. It's self-service, which freed other teams to work in parallel. Edwards added a caveat: "I can't say that we replicated that 100 times." It's early, he said, with a couple of other examples.

BNEDai's own note, apart from what Edwards said: draw your own process as boxes and arrows before you automate any of it, and count the arrows that are tickets.

Four questions map a workflow before you add AI

Neither speaker proposed these four questions. Answer them with the people who do the work, and write the answers on half a page.

  • Trigger and goal. What starts the workflow, and what decision or deliverable should exist at the end?
  • Inputs. Which documents, notes or data does it need, and where do the current versions live?
  • Steps. What happens first, second and third, and where does the work pass from one person to another?
  • Definition of done. What does the output have to meet before someone calls it finished?

These line up with two questions in the AI Readiness Index: whether each AI workflow had a one-sentence goal written down before it was built, and whether the judgment criteria, such as thresholds, filters and tone, are written down and not carried in one person's head. BNEDai teaches the same order for building: goals first, then how many AI agents you might need and what you delegate to each, then the workflows.

Look at the boxes to tell a redesign from an automation project

Look at the boxes. When each box on your page is a step one person or one AI agent can do, you have an automation project. When each box is a separate team handing a ticket to the next, as in the diagram Edwards described, the wait is in the structure, and automating one team's steps leaves it there. That is BNEDai's reading of his account.

An AI agent fits where the process is clear

Where the inputs are named, the steps are written and a person can check the result. BNEDai's Agent Lab builds a Meeting Prep AI agent that has one job, a known input in the calendar and the last thread with each attendee, and an output a person reads before trusting it. The AI agent drafts, and the person decides.

Pick the slowest step of your mapped workflow that has those three traits, and start there. What Should I Do on Paper Before I Build an AI Agent? has the order. When you're ready, the AI Readiness Index shows how many of your rules are written down.

Frequently asked questions

What should I map first?

The slowest recurring workflow your team runs. Write its trigger and goal, its inputs, its steps and its definition of done on one page.

How do I know whether to redesign before automating?

Check whether each box on your map is a step or a team. If the boxes are teams passing tickets, redesign comes first.

Does the AI agent decide how the work should run?

No. The steps and the definition of done come from the people who do the work. The AI agent drafts, and a person decides.

Source: remarks by Shawn Edwards, Chief Technology Officer, Bloomberg, at an online enterprise AI summit, November 12, 2026.

Reviewed on November 20, 2026.

More on Real Workflows for Corporate Executives