The rise of the AI project manager

Slack project management isn’t a category anyone sat down and designed. It’s what you get when the work moves into chat and the plans stay in a tool nobody opens. Most teams now run on the gap between those two things, and most of them know it.

There have been three eras of this. The third one is the interesting one.

The old world

Twenty years ago, project management meant a person. On anything big enough to matter somebody got assigned, and they kept the Kanban board, built the plan, and walked around every week asking what had changed.

The walking around was the actual job. Everyone remembers the plan. Fewer people remember that a plan is only ever as current as the last person who went and chased it. Take that person away and the document sits there being confidently wrong.

It worked. It just didn’t scale, because people don’t. One project manager holds one portfolio. Anything under a certain size got nobody at all, which in practice meant it got managed by whoever happened to remember.

Then the work moved

Chat arrived properly around the mid-2010s and companies stood up Slack to talk across offices and time zones instead of dialling into a bridge. The plans didn’t go anywhere. The work did.

Notes, decisions, somebody agreeing to own a thing by Friday. All of it moved into threads. The plan turned into a summary written afterwards by whoever had read enough of the channel to reconstruct it.

You already know the failure. A task gets agreed on Tuesday, in a thread. It’s real, it has an owner, and everyone in that thread understood it perfectly. It also exists in exactly one place, which is a conversation that has since scrolled away. The board still says green.

Why Slack project management matters

If your process assumes somebody will type the work into a system, your process is already behind the work. That’s the whole thing in one sentence, and it’s the reason Slack project management is worth treating as a discipline rather than as chat being a place where real work leaks out of the real tools.

Two things fall out of it.

Capture has to happen where the agreement happened. Not later, not in a Friday tidy-up. The moment you put a step between “yes, I’ll do that” and the record of it, you have built a process that fails hardest on your busiest people, who are also the people agreeing to the most.

Then somebody has to chase. This is the unglamorous half and it’s where the whole thing usually dies. A captured task nobody ever asks about is a tidier way of forgetting. Chasing is what the old project manager actually spent the week doing, and it’s what quietly eats managers who were never given the title.

What makes Slack specifically hard

Chat isn’t a worse filing cabinet. It’s a different medium, and several of its properties work directly against follow-through.

Threads bury. A thread is a side conversation the channel stops surfacing once it scrolls, so the reply where somebody actually took something on is the reply nobody sees twice.

Huddles are worse. The fastest way for a team to decide something leaves no record that they decided it.

Then there are DMs, which are invisible to everybody except two people. A surprising amount of real work gets agreed in DMs.

And time zones quietly break the assumption that anyone was watching. The person who most needed to see it was asleep, and by the time they weren’t, the channel had moved on.

None of this is people being careless. The medium just doesn’t hold the work.

The multiplayer era

Generative AI opened something up in the 2020s that we’re only part of the way into. What if the next version of this has an AI project manager on the team as a contributing role, instead of only humans managing human work?

That’s the shift, from managing projects by hand to delivery that gets driven for you. It stops being a question about which board you use.

Picture a thread between a CRO and their sales leads about pipeline. Somewhere in the fourth reply somebody takes something on. Historically that survives only if a human notices and writes it down.

With Pondros it’s captured as a task, chased with the right person, and closed by an AI project manager running its own agentic workflows.

Nobody switched windows. Nobody maintained anything.

What Slack project management looks like in practice

Three verbs, and they’re the same three whether a person or an agent is doing them.

Capture. The task gets recorded from the thread it was agreed in, with an owner and a date, without anybody leaving the conversation. How capture works.

Chase.The owner gets asked, in Slack, before it’s late. Then asked again if it slips. How chasing works.

Close. Somebody checks the work actually landed, and done means done rather than assumed. How the agent closes the loop.

We’re opinionated about that last one. Marking something complete because its due date went past is how boards start lying to you, and a board that lies is worse than no board, because people trust it for another quarter before they find out.

An AI project manager isn’t a better board. A board is somewhere to put things. This is the layer that does the asking.

Which makes the usual comparison a strange one. It isn’t really this against project management software, because software doesn’t chase anybody. It’s against what the role costs, which is a different conversation and the one we’d rather have. We’ve written up that comparison properly.

Where this leaves us

The old world managed human work with humans and it worked, at human scale. The Slack era moved the work into threads and left the plans behind, and most teams are still living in that gap.

We think the third era mostly means every project gets a project manager, including the small ones that were never going to be given a person. We might be wrong about the shape of it. We’re fairly confident about the gap.

The product tour walks the whole loop if you want to see it before deciding anything.