Triad-in-Slack · Human AI Loop

The future of teamwork isn't human vs AI.

It's human + AI — working inside the same system.

What happens when AI isn't a tool… but a teammate?

Follow a sprint planning session inside a shared workspace — with humans and AI working together in real time.

02 / 12
A standard product team

Nothing about this team is unusual.

Human Members
PMDirection
Engineering LeadBuild
DesignerDesign
Where they work
Sprint planningSlack
Stories & estimatesBacklog
DependenciesCross-team

The only difference?

AI teammates are present — with defined roles.

AI isn't bolted on. It's part of the team.
03 / 12
Clear roles, shared system

AI has responsibilities —
not just responses.

Convergence AI
Identifies risk
Surfaces gaps, inconsistencies, and blockers before they become problems.
Synthesis AI
Maintains state
Captures decisions, updates the shared workspace, creates artifacts.

Just like human teammates:

Different strengths
Same workspace
04 / 12
Familiar workflow

The team starts planning the sprint.

Stories
Reviewed
Estimates
Discussed
Sizing
Slack polls
Nothing new. The tools are the same. The primitives are the same. The workflow is the same.
AI augments the ritual — it doesn't replace it
05 / 12
Same tools, new intelligence

AI doesn't replace the poll —
it interprets it.

The team votes. AI reads the distribution.

Poll: Story #14 estimate
2 pts
1
3 pts
2
5 pts
3
8 pts
1
AI · "No convergence yet — recommend quick clarification before locking."
Vote distribution: 3 / 5 / 5 / 8 — no majority
Slack primitive → AI insight
06 / 12
What humans miss

AI surfaces what's not being said.

"

Story #14 has no owner. It overlaps with another component. Recommend resolving before sizing.

AI (Convergence) · unprompted
No prompt required.

A tool responds to prompts. A teammate notices things. The difference is initiative — and this is what it looks like.

07 / 12
Hidden risk

AI tracks what spans beyond the room.

"This story depends on the API team. That dependency hasn't been discussed."
AI (Synthesis) · context not lost
Current Sprint
Story #14
depends on
External Team
API Platform

Context is not lost.

08 / 12
Control stays human

The system doesn't decide.
The human does.

PM · Direction Decision moment
"Pause — we're not ready to lock. Let's resolve dependencies first."
PM pauses the sprint. Redirects the team.
↺ Re-loop initiated
Context preserved
Prior votes retained
This is the moment the Loop is designed for. The human doesn't just approve or deny — they redirect the entire team. AI holds the context. Work continues from where it left off.
09 / 12
Back to flow

Work continues —
without losing momentum.

✓
Votes
Converged — Story locked at 5 points (4/5 aligned)
✓
Ownership
Assigned — no ambiguity
✓
Dependencies
Acknowledged — API team notified
AI (Synthesis) · Estimate recorded · Sprint plan updated · Shared state current
10 / 12
Decision captured

The sprint is committed.

Sprint Plan · Locked
Estimates
Finalized
Ownership
Assigned
Dependencies
Noted
Blockers
0 remaining
📄 Artifact created and pinned to channel
11 / 12
Work doesn't stop

The system carries
the team forward.

System · Scheduled
Next Ritual
Backlog Refinement
Scheduled · 72 hours
Add tickets
Vote on priorities
Flag dependencies

No context lost between sessions. No reconstruction overhead. The team picks up exactly where they left off.

12 / 12
The shift

AI isn't replacing teamwork.

It's making it more complete.

Less lost context
Faster decisions
Clearer ownership
Work that neither could produce alone.

AI isn't replacing teamwork. It's making it more complete.

This is a simulated prototype based on real workflows. Built to explore how human and AI teammates operate together inside existing systems.

thehumanailoop.com/methodology