Latest / The Operator's Manual with Fexingo: Daily Decisions, Tactical Wins, and Business Execution / How One Army Corps Cut Procurement Cycle 80 Percent With a Single Meeting
Transcript
- Lucas: So there's this procurement office in the U.S. Army Corps of Engineers — not exactly a place people think about for speed. But they cut the average procurement cycle from 90 days down to 18. One change. Luna: Eighty percent reduction. That's wild. What was the change? Lucas: A single weekly meeting. Thirty minutes. They called it the 'procurement huddle.' And it wasn't more people or more software — it was just forcing visibility into the process every seven days. Luna: If today's episode moves your own work forward — maybe you're dealing with your own approval bottlenecks — there's a simple way to keep these conversations ad-free and independent. It's buy me a coffee dot com slash fexingo. That's it. We appreciate the support, and it lets us keep digging into stories like this one. Lucas: Yeah, exactly. And if you've ever passed along an episode to a colleague, that helps too. Now back to the Corps of Engineers — let's get into the details of how the huddle actually worked. Luna: Walk me through the before picture. What was causing the 90 days? Lucas: Standard distributed process. A project manager would submit a purchase request — say for a pump part or a consulting contract — and it would land in someone's email inbox. That person might be out for two days, or they'd have 40 other things to do, so it sits. Then it moves to the next person. Each handoff adds three to five days of latency just from queue time. Multiply by six or seven approvals, and you're at 90 days. Luna: Right, no one is malicious. It's just that everyone has their own priority list, and someone else's request is at the bottom. Lucas: Exactly. So the procurement director — a guy named Jeff — decided to pull all the stakeholders into one room once a week. Every Tuesday, 10 AM, 30 minutes. The attendees: the project manager, the procurement officer, the finance rep, the legal reviewer, and the contracting officer. Luna: So basically everyone who touches a request. Lucas: Right. And the rule was: no phone, no laptop. Just a printed list of every pending request that had been waiting more than five days. They'd go down the list one by one — what's the blocker, who has the action, what's the expected resolution date. Luna: And that simple act — sitting in a room together — collapsed the cycle time from 90 to 18 days? Lucas: In about six weeks. The key mechanism is what the lean community calls 'shared attention.' When everyone knows they'll be asked about their piece in front of their colleagues on Tuesday, the work gets done by Monday. The requests don't sit in inboxes anymore because there's social accountability. Luna: It's like the Hawthorne effect — people behave differently when they know they're being watched. But here it's not being watched by a manager, it's being watched by peers. Lucas: Exactly. And the data backs it up. After the huddle was implemented, the average time for a request to move from one approval step to the next dropped from 3.8 days to 0.7 days. Most items were resolved within 24 hours because someone knew they'd have to explain a delay to the group. Luna: What about the outliers — the complex requests that genuinely need more time? Did the huddle help or hurt those? Lucas: Good question. They actually did something smart with complex requests — they'd flag them during the huddle and, if it needed more than 30 minutes of discussion, they'd spin off a separate working session. The huddle was only for visibility and quick resolution. Anything that required deep analysis got a separate slot later that week. Luna: So the 30-minute cap prevented the meeting from becoming a black hole. Lucas: Critical design choice. If the huddle had turned into a two-hour slog, people would have started sending deputies or skipping it. The discipline of keeping it short ensured attendance stayed high. Luna: What kind of resistance did they face when rolling it out? I can imagine some people saying 'I don't need another meeting.' Lucas: Oh, plenty. Especially from the legal reviewer, who was used to doing things asynchronously. But Jeff made the case that the huddle would actually reduce total meeting time, because instead of five different one-on-one follow-ups, you had one 30-minute touchpoint. And within a month, the data proved it — the procurement officer reported spending two fewer hours per week on email follow-ups. Luna: So the net time saved was positive. Lucas: Very positive. And the downstream effects were big. Faster procurement meant field projects started earlier, which reduced cost overruns. They estimated that each day of cycle time reduction saved about $3,000 in project delay costs. Multiply by 72 days saved per request, times hundreds of requests a year — it's a seven-figure impact. Luna: That's the kind of number that gets leadership's attention. Lucas: It did. The Corps expanded the huddle concept to other districts and even to their project management teams. Same structure — weekly, 30 minutes, printed list, no laptops. Luna: It feels almost too simple. Why doesn't everyone do this? Lucas: I think because it requires a few uncomfortable things. First, you need to surface all pending work — that can be embarrassing if a team has a big backlog. Second, you need to give up the illusion that email is enough. And third, you need someone with enough authority to mandate attendance across departments. Luna: That last one is often the biggest barrier. Interdepartmental meetings are hard to enforce unless there's a clear sponsor. Lucas: Right. In the Corps, Jeff had the backing of the district commander, which gave him the pull to require attendance. Without that, the legal reviewer might have opted out. But once the results came in, it became self-sustaining — people wanted to be there because it made their own work easier. Luna: So the playbook for any organization: identify the cross-functional handoff that's causing the longest delay, assemble the five or six people involved, set a recurring 30-minute huddle with a visible list of stuck items, and enforce a no-laptops rule. Lucas: That's it. And the beauty is you can test it in two weeks. You don't need a consultant or new software. Just a recurring calendar invite, a printed spreadsheet, and the willingness to be uncomfortable for the first few meetings. Luna: I'm thinking about where I've seen this work outside procurement. I know some hospitals use a 'daily safety huddle' to reduce medication errors — same idea, different domain. Lucas: Absolutely. The concept is domain-agnostic. We've covered episodes on checklists and daily checks, but the huddle is a layer above — it's about coordinating handoffs between people who don't share a boss. That's where most organizational friction lives. Luna: One risk I can see: the huddle could become a status update meeting where everyone just reads their list. How do you prevent that? Lucas: The Corps avoided that by making the list action-oriented. They didn't just report status — they asked 'what's the single next step to unblock this?' And they assigned a named owner with a date. If an item came back two weeks in a row with no progress, it escalated to the commander. That created a forcing function. Luna: So there's a teeth element. It's not just a talk shop — there's an escalation path. Lucas: Exactly. And that's the part most copycats miss. They replicate the structure but not the accountability. The huddle without follow-through is just another meeting. Luna: Any other implementation gotchas? Lucas: One: they had to train people to bring the right data. In the beginning, someone would show up without knowing the status of their items. So they created a simple one-page template — request ID, requester, date submitted, current step, days in queue, next action, owner, target resolution. That template became the agenda. Luna: Standardized format reduces cognitive load. Lucas: Massively. And it made the huddle accessible to a new person in five minutes. If you're the new procurement officer, you can walk in, look at the template, and understand exactly where every request stands. Luna: I like that this is a story about government bureaucracy being fast. Usually we think of the private sector as more agile, but the Corps beat most companies on procurement cycle time with a 30-minute meeting. Lucas: It's a great counterexample. The tool isn't technology or incentives — it's attention. When you force five people to pay attention to the same bottleneck at the same time, the bottleneck tends to disappear. Luna: So the takeaway for a listener who wants to try this on Monday: pick one process, identify the five people who touch it, book a recurring 30-minute slot, and bring a printed list of stuck items. Lucas: And don't let anyone bring a laptop. That's the secret sauce. Because when you're all looking at the same piece of paper, you're actually in the same room. Luna: Alright, I'm going to test this on our own podcast production cycle. See if we can get episodes out faster. Lucas: Now that's a meta experiment I'd love to hear the results of. For now, that's the story of how one weekly meeting saved an army — literally.