Zarrar Sheikh
February 9, 2026

Agentic Workflows: Moving Beyond "Chatting" with AI

In 2023, we used AI as a chatbot. We asked a question, it gave an answer. In 2026, we use AI as an **Agent**. What is an Agent? A chatbot talks. An Agent *does*. An Agent has access to tools. It can browse the web, run a Python script, query a database, and send a […]

In 2023, we used AI as a chatbot. We asked a question, it gave an answer.
In 2026, we use AI as an **Agent**.

What is an Agent?

A chatbot talks. An Agent *does*.
An Agent has access to tools. It can browse the web, run a Python script, query a database, and send a Slack message.

How I Use Agents as a BA

I don't just ask AI to "write a user story." I set up a workflow:

1. The Research Agent: Scours the competitor's website and summarizes their checkout flow.
2. The Analyst Agent: Compares that flow to our current internal documentation and identifies gaps.
3. The Writer Agent: Drafts a Jira ticket based on those gaps.

The Human Role (Me)
My job changes from "writing the ticket" to "reviewing the Agent's logic."
I become the **Orchestrator**.

This dramatically speeds up the "boring" parts of discovery. Instead of spending 3 days clicking through a competitor's site, I have a report on my desk in 3 minutes.

But—and this is huge—an Agent doesn't know why we are building the feature. It doesn't know that the CEO hates the color blue. It doesn't know that the Legal team is worried about GDPR.

That is why the "Human in the Loop" is not optional. It's mandatory.

Copyright © 2026 Zarrar Sheikh
linkedin facebook pinterest youtube rss twitter instagram facebook-blank rss-blank linkedin-blank pinterest youtube twitter instagram