Source · OIDA Cloud

# Meeting 003: Interim Review & Findings **Date:** October 15, 2025 **Location:** Video call (Meridian Labs Florence office and ClearPath Florence office) **Attendees:** Marcus Webb (Lead, Meridian Labs), Nora Chen (Co-lead, Meridian Labs), Thomas Reed (CEO, ClearPath), Priya Anand (Head of Operations, ClearPath) **Duration:** 60 minutes (10:00–11:00) --- [10:01] Marcus: Good morning, everyone. Thank you for making the time. This is still early in the engagement, but we wanted to do a substantive midpoint check-in with you before we move into the final analysis and synthesis phase. We're at about seventy percent of our discovery work now, and I wanted to give you a clear sense of what we're seeing, where patterns are emerging, where there are still unknowns, and how we're thinking about the sequencing of recommendations. This is also an opportunity for you to flag anything we might be missing or misinterpreting before we lock our findings into the formal report. [10:03] Thomas: Good. I appreciate that. I've got about thirty more minutes after this, so— [10:04] Priya: *faintly* You've got back-to-back today. [10:05] Thomas: *laughs* As always. But this is important, so let's make good use of the time. [10:06] Marcus: We'll keep this focused. So, we've conducted structured interviews with your team leads, completed observational walkthroughs of both the operations and administrative workflows, reviewed a sample of current process artifacts, and we've run preliminary metrics against your stated baseline. I want to walk you through the headline findings and the data we've gathered so far. [10:08] Nora: Let's start with onboarding, since that was flagged as a priority area. You told us the official timeline is six weeks from hire date to completion. Our observation, based on shadowing and interviews, is that the actual time to meaningful autonomy is longer—we estimate closer to six and a half to seven weeks, sometimes longer depending on role complexity. [10:11] Thomas: Seven weeks? That's significantly different from what I'm seeing on paper. Where's the gap? [10:12] Nora: The formal "onboarding complete" milestone is when someone finishes the final training module, which happens at the six-week mark. But in practice, people are still asking questions, still getting informal supervision, still not confidently handling their full responsibility set for another one to two weeks after that. We're seeing a real tail of supervision that isn't captured in your current metrics. [10:15] Priya: That actually... yes. I think that's accurate. We measure onboarding completion when the formal training program ends. But you're right—the handoff to full independence happens later. That's something I've seen anecdotally, but we haven't quantified it. [10:18] Marcus: Right. And here's what's interesting from the data—based on our observation of the four team leaders across both operational tracks, we're seeing significant variance in how long that tail extends. In some cases, it's a week. In other cases, it's nearly three weeks. The average we estimate is around ten days of post-training supervision, but the distribution is wide. [10:20] *note: Marcus said four team leaders. This contradicts observation-005, which will later identify six. The discrepancy is not caught or corrected during this meeting.* [10:21] Thomas: So where does the variance come from? Are the leads not coordinating on the structure of onboarding? [10:23] Priya: *slight pause* We have four team leads. They do coordinate on the formal program—we have a documented curriculum. But each team handles different client types, different levels of complexity. So there's some variation in how they interpret the program in their own context. [10:26] Marcus: And here's the nuance—that variation isn't necessarily a problem. It's contextually appropriate. You can't train someone working on high-stakes regulatory work the same way you train someone on standard reporting. But the issue we're seeing is that the variation isn't intentional, it's not documented, and it's not consistently explained to people joining the organization. It's evolved organically. So we have an opportunity here to be deliberate about it. Document what's working well in each track, standardize the core components that apply universally, and explicitly allow flexibility where it's justified by context. [10:30] Nora: Moving to the second major area we've focused on—the audit queue. We've been watching that carefully because it was cited as a significant constraint. What we found is that it's not fundamentally a capacity problem. You have enough people. It's a process design problem. [10:33] Thomas: What do you mean? [10:34] Nora: The way the workflow is structured right now, junior consultants complete their audit work, and then it goes into a queue waiting for a senior person to do a review. While it's sitting in that queue—and we're seeing queues of fifteen to twenty items on average—the junior consultant is idle. They can't take new assignments because they're waiting for their work to be reviewed and have feedback. This creates a bottleneck that then cascades. The queue grows, wait times extend, and you see reduced throughput on the junior consultant side. [10:37] Priya: But we do need that review step. It's a compliance requirement. We can't skip quality gates. [10:38] Nora: Absolutely. We're not suggesting you skip review or compromise quality. We're suggesting you change the mechanism. Instead of a hard serial bottleneck where everything funnels through one review stage, there are parallel approaches that maintain rigor and actually strengthen it while accelerating throughput. [10:41] Thomas: Such as? [10:42] Marcus: Several options. One is structured peer review—instead of only senior staff doing review, consultants at similar levels review each other's work against a detailed checklist, and senior people do spot checks and quality audits on a percentage of items rather than reviewing every single one. You maintain quality through the rigor of the checklist and the spot-check sample, but you remove the serial bottleneck. Another approach is to partition the review gates. Instead of one big review at the end, you have smaller review points at different stages. That way feedback happens earlier, rework is smaller, and the final gate moves faster. There are other variants too. We'll want to get your compliance team involved to validate that these approaches meet your regulatory requirements, but I'm fairly confident there's substantial room to improve here without taking on additional compliance risk. [10:48] Thomas: Okay. I'll definitely want to see detailed options and trade-offs in the final report. [10:49] Nora: Third area—IT infrastructure and systems. You're underprovisioned relative to your actual operational demand. [10:51] Thomas: Underprovisioned? We have a decent IT budget. [10:52] Nora: It's not about budget. It's about strategic allocation. You're investing in some systems that don't align well with your actual workflows, and you're underinvesting in areas where delays are creating real friction. For instance, access provisioning is slow. We watched someone wait four days for their system credentials after being hired. That's a procedural bottleneck layered on top of any technical issue. New hires are literally sitting idle waiting for access to the tools they need to do their jobs. [10:56] Priya: That's usually IT's issue. David handles that. We'll need to talk to him about prioritizing it. [10:58] Thomas: I can loop David into this. That should be fixable. What else on systems? [11:00] Marcus: We're still assessing the balance of your infrastructure spend, but the access issue is the most acute pain point we've measured so far. And along that line—la settimana scorsa we noticed some unclear handoffs between operations and the admin side. Information gets passed inconsistently, sometimes late, sometimes not at all. It creates confusion downstream. We need another week to understand whether that's a fundamental design problem or more of a communication and documentation issue, but it's something to watch. [11:05] Nora: Can I push a bit on the onboarding numbers, though? Marcus, you said we estimate six and a half to seven weeks based on our observations. But how many people did we actually shadow through the full onboarding process? [11:08] Marcus: We did direct observation with eight people across the two tracks, and we did retrospective interviews with another twelve. So sixteen total data points on the timeline question. [11:11] Thomas: Okay, so these aren't exact measurements. They're based on observation and people's recollection. [11:12] Marcus: Correct. That's an important caveat. What we're saying is that based on our sample and our interviews, the evidence suggests a longer tail than six weeks. But you're right to flag that this isn't instrumented data. This is observation plus reported retrospective timelines. To really lock down the actual numbers—to know with certainty that the average is six weeks, six and a half, or seven weeks—you'd need ClearPath to instrument the process. Right now, you don't have automated tracking of when people actually reach autonomy versus when they finish training. So we can say with confidence that there's a gap between your formal timeline and your operational reality, but the exact size of that gap... we're estimating. [11:17] Thomas: So for the board presentation, if I cite six and a half weeks, I need to caveat that it's an estimate? [11:19] Marcus: I'd say, yes. Or we could frame it differently. You could say, "Our formal process is six weeks, but our observation suggests we should review our operational metrics to understand the true time-to-productivity. We've commissioned analysis that indicates there's likely a longer tail, and we're moving to better instrumentation so we can measure this consistently going forward." That's honest, it doesn't oversell the findings, and it positions ClearPath as being deliberate about improving measurement. The recommendations we'll make will help you get actual data to confirm these estimates. [11:23] Thomas: Fair enough. I appreciate the rigor there. So let me ask—of all the things we're looking at, which is going to have the fastest return? Which one should we prioritize? [11:26] Nora: The audit queue redesign. If you change that process, you probably see ten to fifteen percent throughput improvement in audit capacity within weeks, not months. It's a process fix, not a capital project. You can pilot it with one team. [11:29] Thomas: And onboarding? [11:31] Marcus: Onboarding is important for retention and employee satisfaction, but the throughput impact is smaller unless you're rapidly scaling hiring. It's a medium-term investment. The infrastructure access issue is quick and low-cost—that's a no-regret move. The bigger architectural work around handoffs and process integration—that's longer timeline but higher ultimate impact. [11:35] Thomas: Got it. So we're looking at a phased approach. Quick wins, then medium-term efficiency, then structural redesign. [11:37] Nora: Exactly. [11:39] *pause; Thomas's video briefly freezes, then unsticks* [11:40] Thomas: Sorry, connectivity blip. So, one other thing—I know Florence is the focus here, but we should probably think about including Milan at some point. Not as part of this engagement, necessarily, but it's worth factoring into how you design the processes. Milan is mostly client-facing and business development, but they're growing quickly, and they'll eventually need to plug into the same operational infrastructure as Florence. Just something to keep in mind. [11:45] Marcus: Understood. We can design with scalability to a second office in mind. We won't require detailed Milan data, but we can structure our recommendations so they could expand. [11:48] Priya: I think Milan is more of a future thing. For this engagement, Florence is really the primary focus. [11:50] Marcus: That's what we'll plan for then. If Milan becomes in-scope, we can add that as a follow-on phase. [11:52] Thomas: Perfect. So timeline-wise, where are we on the full report and board presentation? [11:54] Marcus: We're on track. You'll have a complete written report by November 10th. We can do a live presentation to the board by November 18th or 19th—whichever works better for your calendar. [11:57] Priya: The board meets the third Thursday of every month, so November 20th would actually be ideal. [12:00] Nora: November 20th works for us. [12:02] Thomas: Great. And I'll want something visual for the board. Not just slides full of text. Something that tells a story. I need them to understand not just what we found but why it matters operationally. [12:05] Marcus: Understood. We'll structure it as an executive summary with visuals—process flow diagrams showing current state and recommended state side by side, quantified opportunity metrics showing where the ROI is clearest, and then a detailed recommendation section with sequencing, rough resource estimates, and success metrics for each phase. We'll make it visual and narrative-driven. [12:09] Thomas: That's exactly what I need. Okay, I think we're in really good shape here. Priya, anything from your end before we wrap? [12:11] Priya: I think we're good. Marcus and Nora have been really thoughtful in how they're approaching this. My team feels heard and collaborative. I'd say the process is going smoothly from our side. [12:14] Nora: That's great to hear. One logistics note—over the next two weeks, we'll be interviewing some of the newer hires to get their perspective on the onboarding experience from a fresh viewpoint. You'll probably get a calendar request from Yuki, who's helping us coordinate. [12:17] Priya: That's fine. I'll make a note and flag the team that Yuki will be reaching out. [12:19] Marcus: Thank you. I think we've covered the major ground here. Thomas, we'll send you a detailed summary of this call by end of day. You'll have it in writing. Then we'll sync with you and Priya at the steering committee meeting—which is? [12:23] Priya: October 29th. [12:24] Marcus: Perfect. October 29th. That gives us two weeks to complete the final interviews, nail down our recommendations, and be ready to discuss them with you before we lock them into the formal report. Thank you all for the time, and for being so open to this kind of scrutiny. It's what makes this kind of work productive. [12:28] Thomas: Thanks, Marcus. I'm looking forward to seeing what you come up with. And I like the approach—we're building on solid data and real observation, not guessing. [12:30] Nora: We'll see you October 29th. [12:31] Priya: Thanks, everyone. [12:32] *call ends*

Meeting 003 — interim review and findings

What was taken from it