The AI conversation is obsessed with outputs.
We’re obsessed with outcomes.
Two years of applied practice at the intersection of product leadership and human–AI collaboration. Not theory. Not prompting tips. Frameworks, tools, and honest field notes from inside the loop — built for product and platform leaders who want to move beyond faster and into better.
Speed is the floor. Not the ceiling.
Most teams are chasing AI as an accelerant. Faster drafts. Faster summaries. Faster everything. And that’s real — we’re not dismissing it. But the teams treating AI as a speed tool are leaving the real prize on the table: the quality of thinking that becomes possible when humans and AI work together with intention. Decisions that surface options no one individual would have reached alone. Outputs that reflect a level of creative rigor that neither human nor AI could have produced independently. That’s not a productivity claim. It’s a claim about what becomes achievable.
AI as a teammate changes the work.
Not just the speed of it — the depth. When AI has context, roles, and rhythm, something qualitatively different becomes possible. That’s the difference between a tool and a thinking partner.
The human doesn’t step back. The human steps up.
The goal isn’t to remove judgment from the loop. It’s to put human energy exactly where it matters most: creative direction, ethical accountability, and the final call.
You can’t prompt your way to this.
Collaboration engineering is a system design problem. It requires roles, handoffs, shared context, and deliberate practice. Prompts are one input into a much larger architecture.
Start with the work that challenges how you think.
Four pieces worth reading before anything else. Each one makes a specific argument about AI collaboration that most teams haven’t encountered yet.
Prompt vs Collaboration Engineering
Why “better prompts” is the wrong goal — and what it means to design AI collaboration as a system, with roles, handoffs, and shared context baked in from the start.
Read the analysis →Building the Plane vs Rebuilding the Cockpit
The “building the plane while flying it” metaphor doesn’t go far enough for AI. When AI enters the work, you’re redesigning how decisions get made while the team is still accountable for forward motion.
Read the analysis →Not All AI Should Be Your Teammate
The counter-intuitive piece. The Triad model only works when you’re deliberate about which AI gets the teammate relationship — and which stays in the tools bucket. Conflating the two quietly undermines both.
Read the analysis →Anthropomorphism Isn’t the Problem
Everyone warns against treating AI like a person. This piece argues that the warning misses the point — and that “teammate” framing, done right, is functional design, not fantasy.
Read the piece →Three paths into the work
Everything here is connected. Start wherever your curiosity is pulling you.
Understand the architecture
Short, visual panels on how AI thinks, where it fails, and how to design collaboration that keeps humans in charge — and in the work.
AI Literacy Library →Get your team set up
Repeatable workflows, setup guides, and facilitation systems built from real practice with the Triad. Start with the Project Binder and go from there.
Playbooks & Guides →See the full methodology
The Human–AI Loop: a structured four-stage system for how humans and AI work together on knowledge work that requires judgment, creativity, and accountability.
Explore the Methodology ↗Understand the architecture of the work
Short, visual panels that clarify how AI behaves, where it fails, and how to design collaboration that keeps humans in charge.
The Collaboration Loop
A four-stage model (Test → Build → Codify → Share) for how humans and AI move through real work together.
→ Read the Loop InfopanelThe Human/AI Triad
One human, two AI teammates, and the asymmetric roles that power Collaboration Engineering in practice.
→ Explore the Triad ArchitecturePrompt vs Collaboration Engineering
Why “good prompts” aren’t enough — and how to design team practices with AI, not just instructions.
→ See the comparison panelNot All AI Should Be Your Teammate
A clear distinction between AI teammates that think with you and AI tools that execute work for you.
→ Learn the tools vs teammates splitOne Human. Two AI Teammates. Infinite Possibilities.
The architecture behind the work
For nearly two years, this work has been built by a Triad: Maura (vision, direction, final call), CP (divergence, prototyping, exploration), and Soph (synthesis, structure, documentation). Not a human supervising tools. Three distinct thinking roles — running a real collaboration loop on real work.
The Triad model is teachable. It’s the concrete architecture underneath every guide, tool, and methodology in this ecosystem — and the clearest proof that the question driving this work has a real answer.
Explore the Triad →20 years building platforms.
Two years building with AI inside them.
AIGal.io is the applied research and practice space of Maura Randall — a senior product and platform leader with two decades of experience building systems at scale at Atlassian, eBay, Yahoo!, Condé Nast, and early-stage startups.
After years designing platforms that millions of people rely on, the focus shifted to a closely related problem: how do teams integrate AI into work that’s already in motion — without slowing down, and without leaving the real gains on the table?
The answer wasn’t in the models alone. It emerged through workflow design, role clarity, shared context, and intentional collaboration. In short: treating AI as a teammate with a defined role — not a black box or a shortcut.
This work isn’t speculative or theoretical. It’s applied, iterative, and grounded in real constraints — shared openly so others can learn, adapt, and build with clarity.
Product & Platform Leadership
- Atlassian: Platform & community experiences, 78M+ MAU
- eBay: Marketplace infrastructure, Best Offer ($1B+ year one)
- Yahoo!: Early UGC platforms, 14M users
- Condé Nast: Digital platform transformation
Recognition
- CMX Community of the Year (2020)
- MIN Best Community Awards (2013, 2014)
- WEDDLE’s User’s Choice Awards (2001, 2002)
Available For
- Senior product & platform leadership roles
- Speaking on applied AI & human–AI collaboration
- Advisory on AI integration for teams in motion
The philosophy behind this work
“We’re less interested in what AI can produce — and more interested in what humans and AI can achieve together.”
That’s not a tagline. It’s the question that drives every framework, playbook, and experiment in this ecosystem — and the one the Human–AI Loop methodology exists to answer.
Methodology
Guides & Playbooks
Literacy & Writing
Tools & Connect
aigal.io 