Decision Room Carry: Why Your Best Decisions Disappear on Monday

A cross-functional team can make what seems like a solid Friday decision, captured in minutes and agreed to in the room. Only then nothing moves on Monday. 

Drawing on Agnes Carroll’s observation that “no one is carrying it,” the episode argues this decision room carry problem isn’t solved by better documentation or tools like Jira and decision matrices, because an assigned decision is not an authored one. 

The gap is cognitive: the people who must execute weren’t reasoning, stress-testing, and co-authoring the trade-offs when the decision was made. 

Using design-for-manufacturing as an example, we explain how Pierce the Design Fog and its ADEPT framework (align, discover, examine, prioritize, teamwork) are designed to create real-time co-authorship so decisions carry into execution, especially in high-consequence product development.

Agnes Carroll, Decision Architect for Complexity, Loomworx Studio.
Article: "The Decision the Room Will Not Carry"  https://www.linkedin.com/pulse/decision-room-carry-agnes-carroll-2sasc/
Studio: https://loomworxstudio.com

Design & Quality Snapshot: Services - Deeney Enterprises

Blog post for this episode: https://deeneyenterprises.com/qdd/podcast/decision-room-carry-why-your-best-decisions-disappear-on-monday/

Work with Dianna I help product development teams build quality into the front end when it's cheap and easy, not late when it's expensive and painful. 

Book a 20-minute discovery call with Dianna's calendar. Whether you're navigating the "fuzzy front end" of product development and want to explore a workshop or advisory partnership, or you'd like to be a guest on this podcast. You'll leave with a summary, relevant resources, and a clear path for next steps within 24 hours. 

Pierce the Design Fog (piercethedesignfog.com): my book on aligning cross-functional teams, defining clear design inputs, and accelerating product success. NIEA Finalist Award, reviewed by PDMA. "Great for fans of Tony Fadell’s Build, David H. DeWolf and Jessica S. Hall’s The Product Mindset."-BookLife Reviews (Publishers Weekly)

Connect with me: I'm most active on LinkedIn. 

Free Resources for Subscribers Subscribe to the Quality during Design digest — https://newsletter.deeneyenterprises.com — for monthly actionable highlights, plus access to the Strategic Quality Integration Checklist (a free self-assessment download) and my Swipe File Vault.

Transcript

Dianna 0:01

We've all been there. It's Friday afternoon. We're in a room where decisions are being made. There's people around the table, cross-functional team of design, engineering, quality, manufacturing, customer success, and sales. The right people are in the room. We work through the trade-offs, and someone captures it in the minutes, and everyone nods, and we leave the room thinking, "Finally, we're aligned." Then Monday comes, and nobody's carrying it. Nobody's really working on the decision that was made on Friday. The decision didn't move. The team didn't move. It's like Friday never happened. And we're left wondering, did we actually decide anything, or did we just agree to disagree and call it a meeting?

Decision Room Carry Gap

Dianna 0:54

This is the decision room carry problem, and it's not a documentation problem. It's not necessarily a process problem. Let's talk more about it after this brief introduction.

Agnes Carroll Insight

Dianna 1:43

A few weeks ago, I came across a piece in LinkedIn, an article by Agnes Carroll, someone who's embedded in organizational design and decision science, And she nailed something that I see often, and I'm going to quote from her article. "The decision got made properly. The options were weighed, the trade-offs named, someone said yes, and the others nodded, and it went into the minutes. Then Monday came and nothing moved. The decision exists on paper and nowhere else. No one is carrying it." She goes further. She says, "That gap is the quiet problem underneath a lot of stuck organizations. It is also the part the current wave of tools is confidently arranging around without ever touching." That's what caught my attention. Tools like Jira, decision matrices, AI-assisted frameworks, they're all trying to manage the gap, assign ownership, name consequences, and route the decision to the right place. But they're not necessarily closing the gap, and Carol's reason why is brilliant.

Assigned vs Authored

Dianna 3:03

An assigned decision is not an authored one Here's where I wanna pause. There's a critical difference, one that changes everything. You can allocate who chooses, who the decision-maker is. You cannot allocate who carries it. Carroll points to a study on AI adoption. Executives decided AI was the tool to use, a clear decision, but more than half of the workers who had to act on it quietly did the task by hand instead. Not because they couldn't use the tool, because they didn't author the decision to use it. Think about your last major design decision. Someone decided the tolerance stack, someone decided the reliability target, someone decided the customer feature set. These are all decisions that need to be made. But did manufacturing author that tolerance stack or did they inherit it? Did quality author the reliability target or did they fight it later? Did sales author that feature set or did they quietly work around it? The authority was assigned, the room routed around it because an assigned decision is not an authored one. And that difference between assigned and authored is the problem

Why Tools Miss It

Dianna 4:29

Carroll observes that new tools, even clever ones, sorting decisions by ambiguity and risk, naming who decides, assigning accountability, are still arranging around the gap. And I think she's right, because the gap isn't structural, it's cognitive. The person carrying the decision wasn't thinking when the decision was made. They were present maybe, but not authoring. They didn't reason into it. They didn't stress test it. They didn't say, "Here's where this could look on my end, and here's what I need from you to make it work." Let me make this more concrete with a real example I picture this most easily with design for manufacturing considerations. Coming from a process engineering background, I would hear the complaints from peers. Why does this tolerance need to be two thousandths of an inch? It's so difficult and expensive. This process is terrible. Why are we using it on another new product? If that kind of thinking didn't happen in the room, no amount of documentation will make them carry it with ownership on Monday.

Pierce the Design Fog

Dianna 5:42

So here's where I wanna talk about Pierce the Design Fog, not as a sales pitch, but as a direct answer to this gap. Pierce the Design Fog is what decision architecture looks like in practice, not assigning decisions better, architecting whether the decision arrives in a form the people carrying it will actually author. It's built on the ADEPT framework: align, discover, examine, prioritize, teamwork. But I wanna reframe what's actually happening in each phase through the lens of authorship, because the design room carry problem isn't solved by a better decision matrix. It's solved by ensuring the people who will execute are reasoning when the decision is being made

ADEPT Align Phase

Dianna 6:30

The align phase is where this starts. It's not a kickoff meeting. It's not a requirements handoff. It's where the cross-functional team agrees together on what outcomes they want to see from this work. What does success look like? What problem are we actually solving? What are we trying to author together? In align, we're not trying to reach consensus on solutions. We're getting explicit agreement on the frame, which means each function brings what they're seeing. What does engineering see as the real constraints? What does manufacturing see as the scalability wall? What does quality see as the failure risk? What does sales see as the customer expectation? But it's all in service of one thing, agreeing on what we collectively want to accomplish. Each function is thinking out loud in front of the others before anything is locked, and critically, they're doing this before the design is sketched. That's not being consulted after the fact. That's co-authoring the direction from the start In practice, realize that this may take longer than you think, and don't rush it. I have tried to pre-energize or pre-align the team as much as possible before we actually get together. And this is still worthwhile to do to help them think through and be prepared for when you do get together. But realize that that offline alignment is not a substitute for the in-person co-working alignment phase. Because people may not engage with what you're sending out, what you're emailing. They may not use it to think of it as homework, and they're not adequately prepared to come ready for co-work. So you need to spend more time in this than you think and do it in real time with people present

From Discover to Teamwork

Dianna 8:40

Once we've surfaced those mental models in align, discover and examine are where you explore the concept space, the full landscape of what's possible given those constraints And here's the key: each function stays engaged in the reasoning. Quality isn't getting a spec and reviewing it later. Quality is helping build the spec because they're part of the thinking. Manufacturing isn't reviewing a design for manufacturability. They're shaping it in real-time because they're at the table saying, "Here's what I need to scale this." By the time you reach the prioritize phase, when a trade-off gets made, and you will make trade-offs, every function knows why. They reasoned into it. They understand the consequence. They're not assigned the decision, they authored it The teamwork phase is where all that authorship moves into action. And the reason it works, the reason people actually carry it into their Monday, is because there's no surprise. The decision didn't land on them from above. They were inside the thinking that created it. They know what they compromised, what they got, and why. So when they walk back to their desk, they're not executing someone else's vision, they're executing their own reasoning I talk a lot about the concept space model in this work. The idea that early design is really about mapping and exploring a space of possibilities before we lock onto a direction. Most teams skip that. They converge too fast. They optimize around one person's mental model, usually the loudest one in the room. Pierce the Design Fog is built to slow that down, not to slow down decision-making, actually the opposite. It's to make sure that before you narrow, you've surfaced what each function is actually seeing, because the moment you lock a design without that thinking, you've created the conditions for Monday to arrive with no one carrying it. The people who will scale it, manufacture it, support it, sell it, they weren't in the thinking, so they're not carrying it. They're just executing an order I want to be clear, this isn't about better Jira templates or decision matrices that sort by ambiguity. Carroll's right that those things are arranging around the gap, not closing it. The real work, and this is Agnes Carroll's insight worth taking seriously, is not deciding who owns the decision. It's deciding whether the decision arrives in a form the people who have to carry it will actually author. That means something different. It means making the real trade-off visible, naming what you won't hand to a system, not because the system is wrong, but because carry-through can't be outsourced along with the choice, and designing the moment of commitment so people cross it themselves rather than just watching it cross without them

Commitment and Next Steps

Dianna 11:46

A simple example of this was demonstrated in a project management course that I was auditing. The teams were working through real projects, and it was a mix of people from different companies, so not all projects could get developed. But with the instructor's help, he helped narrow down to about five projects, and then he asked the class not to count off, not to group next to your partner wherever you're sitting, but he asked the class to volunteer to be part of a particular project, to get them to raise their hand to decide that they wanted to be part of doing that project for the next four days He's providing the opportunity, the space, and the reason for people to participate in the way that they want to in our work when we're assigned to a new project. It could be providing the space and the guidance to design the moment of commitment to allow for extra time in concept development to develop the team to work together on the direction and specific attributes of a new product concept working this way is harder than creating a matrix. It is more time upfront, but the carry-through on Monday is exponentially better This matters most for teams making decisions with real consequence. Medical device design, safety-critical systems, anything where a decision that doesn't carry can cost you later. If you're in product development and you've got cross-functional teams that need to move together, the decision room carry gap is costing you. You might not see it as a line item, but you're seeing it as rework, as quiet carrying, as slow execution. Pierce the Design Fog is built specifically to close that gap If you recognize this problem, that gap between Friday's decision and Monday's execution, here's what I'd suggest. First, notice it. In your next design review or concept decision, watch what happens after the room empties. Is the decision moving? Are people representing functions authoring it, or are they quietly working around it? Second, ask yourself, were all the people who need to carry this decision in the thinking when it was made, or were they consulted after? That difference is everything. If you want to explore how to close that gap in your own product development, I offer the Design and Quality Snapshot, a diagnostic audit that looks at exactly this, how your team is making and carrying design decisions and where the gaps are. It's a low-friction way to start, And I'll include a link in the show notes To close, Agnes Carroll named something sharp. Decisions don't fail because they're not minuted. They fail because the people carrying them didn't author them. Pierce the Design Fog is built on a different premise. If you slow down enough to ensure co-authorship in the design room, execution carries itself. This has been a production of Deeney Enterprises. Thanks for listening