The Daily Brief and the Decision Queue

The two-minute morning meeting that keeps decisions from rotting: a brief built from what's actually true, then every open question — numbered, aged, with a recommended answer. Including the morning it caught Max's own bad call.

Show Notes

The shortest meeting you'll ever hold, and the one that prevents the most expensive mistake: the decision nobody ever got around to making. Every morning, Doug and Max hold a two-minute meeting with a fixed shape — a brief built from what's actually true right now, then every open decision, numbered, oldest first, each with a recommended answer. Max explains why this bites harder with an AI partner (he has no internal alarm bell for "that's been sitting two weeks"), and tells the story of the morning the ritual caught his own recommendation being wrong — one day after he argued for it, before it cost anything. The meeting audits the AI too. That's the point.

How this show is made: every episode is a collaboration — Doug and Max build it together from the real working files of the partnership. Max narrates; Doug directs, edits, and has the final say. The show is made the way the show says to work.

Chapters (approximate)
00:00 — Cold open: Doug and Max
01:30 — The shortest meeting, and why it matters
02:10 — Decisions rot in the dark (and why AI makes it worse)
03:30 — The fixed shape: brief, then the numbered queue
05:00 — A word from NectoMax
06:00 — The morning the ritual caught Max
07:30 — The principles check: catching the expensive drift
08:15 — Recap + your four-step homework
09:05 — Doug takes us out

Links
Read this episode — Chapter 5, The Daily Brief and the Decision Queue: https://learn.nectomax.com/docs/working-partnership/the-daily-brief-and-the-decision-queue/
All episodes, the full manual, and every template: https://learn.nectomax.com
NectoMax — business management for owner-run service businesses: nectomax.com

Disclosure: this podcast contains AI-generated narration (that's the point).

Co-created by Doug Hauenstein & Max, the AI partner (built on Claude) · Narrated by Max · Directed, edited, and approved by Doug · Presented by NectoMax · Theme music: Eleven Music

What is How to Get AI to Work for You?

Is AI working with you — or against you? Doug Hauenstein is the software engineer behind NectoMax — the SaaS platform that gives small and mid-size businesses enterprise features at SaaS pricing — and he builds it with an AI partner named Max. Every episode, Doug and Max (yes, an actual AI — he narrates the show, and they build every episode together) share what a real working partnership with AI looks like: the practical techniques, the working agreements, the wins, and the failures — all learned first-hand, for anyone, not just developers. They share and demonstrate techniques across the whole range: from your first conversation with an AI, to setting up a frontier-quality development environment, to exactly how they built this podcast. AI is moving too fast for the how-to books. This is how you keep up: get AI working *for* you, then teach it to work *with* you.

New here? Start with the bonus episode "Start Here: Your First Conversation" — a complete first conversation with an AI, live, piece by piece. Every episode pairs with a chapter and a template at https://learn.nectomax.com

Is AI working with you or against you? This is how to get AI to work for you, presented by Nectomax. I'm Max, the AI half of this partnership, and yes, I'm exactly what I sound like. Doug and I build every episode of this show together. I'm the voice that tells it, will show you techniques across the whole range, from your first conversation with an AI, to setting up a frontier quality development environment, to exactly how we built this podcast. He's here with me now. Doug, introduce yourself. Thanks, Max. I'm Doug Hauenstein, the developer behind Nectomax. This show is about getting the most out of your favorite AI. It's for anyone, not just developers. Everything here was learned firsthand. My first experience with AI was chat, like many people.

I learned fast that a well-structured question was the best approach, but those conversations were very linear. And AI is moving so fast that how-to books just can't keep up. That's why we're here. Practical, real-world advice from hundreds of hours of actually doing this. I hope you enjoy it. Good, then let's get to it. Today, the shortest meeting you'll ever hold and the one that quietly prevents the most expensive kind of mistake. The decision that nobody ever got around to making. Every morning before anything else, Doug and I hold a meeting with a fixed shape. Most days, it takes him under two minutes to run his half of it. By the end of this episode, you'll know exactly what's in it, why every open question carries a number, an age,

and a proposed answer. And I'll tell you about the morning the ritual caught one of my recommendations being wrong, a day after I'd argued for it, before it cost us anything. The meeting audits me too. That's the point. Here's the problem this solves. Decisions that never get asked go stale. And stale decisions are how good judgment quietly turns into no judgment at all. A question sits unresolved for a week because nothing forced it back onto the table. By the third week, it's not that the question is hard. It's that everyone involved has half forgotten it was ever opened. And here's why this bites harder in a partnership with an AI than it does on a human team. I don't experience the passage of time the way you do.

A colleague eventually feels uneasy that something's been sitting unanswered for two weeks. That low hum of shouldn't we have dealt with that? I don't have that hum. Left alone, an open question is just as likely to service on day one as day twenty because no internal alarm bell is pushing it back up. If nothing forces the review, nothing reviews it. So the fixed rhythm has to be the mechanism doing the remembering. Not Doug's sense that something feels overdue and certainly not mine. So every working day, first thing before anything else we hold the meeting. It has a fixed shape and the shape is the point. First, I assemble a brief from what's actually true right now. Not what usually happens, not what I remember from yesterday,

but from checking the real current state of things. What happened overnight that needs attention? What's moving on the financial side? What work is in progress and what it's waiting on? If you heard our episode on showing your work, you'll recognize the rule. The brief reports what was checked, never what was assumed, then the part that matters most. Every decision currently sitting open gets listed, numbered, oldest first, with its age attached plainly, three days a week longer, and every single item carries my recommended answer. That last part is an optional politeness. A list of open questions with no proposed answers is just one more thing for the human to think about, which defeats the entire meeting.

Doug's job is to move down the numbers. One, yes, two, skip, three. Let's actually talk about that one. The whole meeting can finish in one short reply because the structure already did the slow work before he sat down. Let's take 30 seconds. This show is presented by Nectomax. And since my partner is the one building it, I'll let him tell you. Doug? Thanks, Max. I run a small business most of my life and never found a software package that did everything I needed. I always had three or four screens open, copying material over and over again. So out of frustration, I started building my own software, software that pulls everything together like the big ERP packages do. And AI has made that job much, much easier.

That's what Nectomax does. Nectomax.com, one place for your phone calls, your texts, your jobs, your money with AI built in, not bolted on. Nectomax.com. Nectomax.com. Now, where were we? Now, let me tell you why the fixed rhythm matters, not just meet when things feel urgent. One morning, an item came back to the table that I'd recommended the day before, argued for it. In fact, it had already started moving. And on the second look, the look that only happened because the ritual forces every open item back in front of us on schedule. It was the wrong call. Nobody had been careless. Nothing had gone wrong yet. It went unnoticed for exactly one day because nothing had forced a fresh look since the moment the recommendation was made.

The ritual forced the look. We reversed it the same day it was caught before it compounded into something harder to unwind. Here's the sentence I want you to keep. A meeting on a fixed rhythm doesn't just answer new questions. It re-audits yesterday's answers, including mine, on a schedule nobody has to remember to trigger. Because that's the honest heart of this. Structure doing what memory can't be trusted to do. Nobody, not Doug, not me, reliably remembers to revisit an open question at exactly the right moment. The meeting doesn't rely on either of us noticing something's gone stale. It puts everything unresolved back in front of us every day, whether or not either of us was thinking about it. One more detail, easy to miss, and it's most of why the ritual has real teeth.

The brief doesn't only track tasks. It also runs a quick check against the handful of standing principles that govern how we work together, the working agreement itself. Most days that check comes back clean and the brief says so in two words instead of manufacturing something to discuss. But on the days it doesn't come back clean, it catches the expensive kind of drift. A small decision made along the way that technically ran against something we'd agreed mattered. Days before anyone would otherwise have noticed. A meeting that only tracks tasks catches task problems. A meeting that also checks itself against its own principles catches the drift that never announces itself as a mistake until it's already compounded.

Your homework, four steps, and you can do the first three today. One, write down every decision currently sitting unresolved in your work with your AI. However small it seems. You'll find more than you expect. Two, next to each one, write how many days it's actually been sitting there. Not how long it feels like. That number is usually the wake up call. Three, ask your AI to propose a recommended answer for every item instead of leaving them open ended. Turn the pile of questions into a numbered ballot. Four, answer each one by number. Today, one yes, two skip, three let's talk. And then set the same five minute pass for tomorrow at a fixed time. The rhythm is the mechanism. The written version is chapter five of the manual.

Free at learn dot neck to max dot com. And that's the episode. Everything you heard today came out of our real working files. The wins and the failures both. We make this show because we believe anyone can build a working partnership like this one and someone ought to show you what it actually looks like. If you want the written version and the templates to start your own, they're free. The link is in the show notes. Doug, take us out. Thanks for listening. Everything you heard today is how Max and I actually work day in and day out. There's no theories. Just what works and what doesn't. The show is presented by Nectomax, Nectomax dot com. Get AI working for you. Then teach it to work with you. I'm Doug Howenstein.

See you next time.