Source · OIDA Cloud

# Meeting 001: Project Kickoff **Date:** September 8, 2025 **Location:** ClearPath Solutions Inc., Florence office, Conference Room A **Attendees:** Marcus Webb (Lead, Meridian Labs), Nora Chen (Co-lead, Meridian Labs), Thomas Reed (CEO, ClearPath), Priya Anand (Head of Operations, ClearPath), David Park (CTO, ClearPath) **Duration:** 90 minutes (10:00–11:30) --- ## EXTENDED SMALL TALK & OPENING (10:00–10:12) [10:00] Marcus: Good morning, everyone. Thank you so much for having us. We're really looking forward to this engagement. *sets down briefcase* Before we dive into anything formal, I have to say—the traffic getting here from the station this morning was... well, let's just say Florence keeps things lively. [*light laugh*] [10:01] Thomas: Ha! Yeah, you picked a good day. Usually it's worse on Thursdays. How was the commute from your hotel? Are you staying near the Duomo area? [10:02] Marcus: Actually, yes—we are. It's a lovely neighborhood. I have to confess, I spent half the night just walking around. I think I know Florence a bit from... a few years back. Qualche anno fa, my family and I spent a month here one summer. Never really left my memory. [10:03] Thomas: *leans back* No kidding? Really? Because—I grew up partially in Florence. My mother's family is from here. I spent every summer in the Oltrarno district. Where did you stay? [10:04] Marcus: Near the Ponte Vecchio, actually. Not the most original choice, but— [10:05] Thomas: *interrupts, smiling* That's brilliant. My grandfather had an apartment just off the Piazza della Signoria. We used to have gelato almost every evening. [*chuckles*] Strange to come back here for work. [10:06] Nora: *while setting up laptop* I have to say, the view from upstairs is gorgeous. You can see—is that the Arno? [10:07] Priya: Yes, that's the river. And in better weather, you can actually see out to the hills. We took these offices about three years ago, and honestly, the location was half the selling point. Nice environment for the team, you know? It matters. [10:08] Nora: It really does. I've worked in some basement offices in London that just—*makes a face*—they suck the life out of you. This is the opposite. [10:09] Priya: *stands* Actually, after the meeting, if you want, I can give you both a quick tour. It's not massive, but it's efficient. We've tried to set up the space so teams can collaborate but also have focus time. [10:10] Marcus: That would be wonderful. We're always interested in how the physical space reflects the organizational culture. [10:11] Thomas: Priya, did you manage the coffee order? Marcus, Nora—espresso okay, or do you need the longer version? We have a decent coffee machine, but honestly, for the good stuff, you have to go out. [10:12] Nora: Espresso is perfect. Thanks. [10:12] Marcus: Very kind. I appreciate it. *sits down, pulls out a leather notebook* --- ## MARCUS PRESENTS MERIDIAN LABS METHODOLOGY (10:12–10:27) [10:12] Marcus: So, as you know, Meridian Labs specializes in operational process review and organizational transformation. We've had the opportunity to work with several firms in the compliance, documentation, and financial services space, and we're genuinely excited to bring that experience to ClearPath. But let me walk you through our methodology, because I think this matters—how we actually work is as important as what we deliver. [10:14] Marcus: Here's how we think about this engagement. We believe that most organizations operate in two realities simultaneously. There's the formal reality—the org charts, the documented procedures, the policy manuals. And then there's the actual reality—how people really work day to day, what they really prioritize, where the informal networks actually make decisions. Our job is to map both of those realities and understand not just where they diverge, but why they diverge. Because that gap? That's where you'll find your biggest opportunities. [10:16] Marcus: We do this through structured observation, which sounds fancy but is actually pretty straightforward. We embed ourselves in your operations. We sit with teams, we watch workflows, we take notes on what actually happens versus what the procedures say should happen. We're not auditors—we're not looking for violations. We're anthropologists, in a way. We're trying to understand the logic of how things actually work. [10:18] Marcus: The second pillar is interviews. We talk to people at every level—frontline staff, middle management, leadership. And we use a methodology called triangulation, which means we ask the same questions in different ways to different people and look for patterns. If five people tell us the same thing independently, we know it's real. If everyone tells us something different, we know there's either confusion or misalignment, which is itself very informative. [10:20] Marcus: The third piece is document analysis and systems review. We look at what people are actually using to do their work—your processes, your templates, your systems, your outputs. We trace work as it flows through the organization. All of this together gives us a 360-degree view. [10:22] Marcus: As for timeline, we structure this in three distinct phases, each with clear deliverables. Phase One is discovery—roughly two to three weeks. We're here, we're embedded, we're collecting data through observation and interviews. Phase Two is analysis and synthesis—about two to three weeks. We take everything we've gathered and we create a comprehensive diagnostic picture. What's working, what's not, where are the bottlenecks, where are the redundancies, where are the quick wins. [10:24] Marcus: Phase Three is recommendations and roadmap. We give you prioritized actions—short-term wins you can hit in 30 days, medium-term structural changes, longer-term transformations if necessary. Critically, we also map dependencies. What has to happen first? What's contingent on what? And we quantify resource implications as much as we can—how many people, what skill sets, what timeline. We're not giving you pie-in-the-sky recommendations. Everything is grounded in reality. [10:26] Marcus: The deliverables vary slightly by client, but typically you get a written diagnostic report—usually 40 to 60 pages, which sounds like a lot but isn't once you have process maps, flowcharts, data tables. You get an executive summary for board-level communication. And we usually do a series of presentations—one for senior leadership, one for teams, one for the board if that's relevant. The goal is that everyone understands not just what we found, but why it matters and what we're asking them to do about it. [10:27] Marcus: Questions on that so far? --- ## THOMAS ASKS SUBSTANTIVE QUESTIONS (10:27–10:35) [10:28] Thomas: Yes, actually. Three things. First—how do you handle it when teams are resistant to being observed? Because I'll be honest, I know some people on my team, and the moment they know someone's watching their workflow, they're going to behave differently. So how do you actually get authentic data when people are, you know, on their best behavior? [10:30] Marcus: That's a great question, and it's real. We account for it in a few ways. First, we build in observation time. People normalize our presence relatively quickly—usually in about a week or so, they stop performing. We're just... there. We become part of the background. Second, we don't announce that we're doing detailed workflow observation in the first week. We do a fairly soft introduction—"Marcus and I will be around, we'll be talking to people, we're trying to understand how ClearPath works." By the time people realize we're documenting their actual workflows, they've already stopped caring because it's become routine. Third—and this is important—we're very transparent that we don't care about individual performance. We tell people explicitly: we're not evaluating you, we're not reporting to anyone about what *you* specifically do. We're looking for system-level patterns. That actually disarms a lot of the resistance. [10:33] Thomas: *nods slowly* Okay, that makes sense. [10:34] Marcus: And frankly, in my experience, the initial resistance usually isn't about people being difficult. It's about fear of the unknown. Once they understand that we're not here to get them in trouble, and once they see that our observations actually lead to changes that make their work easier, they tend to become allies. Some of our best insights come from people who were skeptical at first. [10:35] Thomas: Fair enough. Second question—what happens if we discover that the problem isn't process? What if we discover that the problem is people? Like, what if I have someone in a critical role who's just... not performing? Do I find that out in your report? [10:37] Marcus: *thoughtful pause* That's a delicate one. Here's my honest answer: if there's a systemic people problem—meaning the role itself is poorly designed, or the person is in a role that doesn't fit their skills, or they don't have the support they need—we'll flag that. We might say something like, "This role needs clearer authority, or better training, or different reporting structure." What we don't do is provide personal performance evaluations. That's not our job, and frankly, it's dangerous territory. However—and this is important—if we observe that someone is actively undermining process or creating blockages, and it's clear, then yes, we'll flag it. We'll say it as professionally as we can, but we'll say it. [10:39] Thomas: But not like, "Thomas, you need to fire David," kind of thing. [10:39] David: *looks up from phone briefly, somewhat startled* What? [10:40] Thomas: *laughs* I'm just checking the parameters here. [10:40] Marcus: *smiles* Exactly. We might say, "The CTO role needs more structured time for strategic planning," or "There's a gap in technical documentation that's creating bottlenecks." But we're not HR consultants. We're not performance coaches. You understand? [10:42] Thomas: I do. Last question—have you done this for companies our size before? We're about 120 people, mostly here in Florence with a small Milan satellite. Are we big enough to be interesting, but not so big that it becomes unmanageable? [10:44] Marcus: We've worked with organizations ranging from 50 to 500 people. The dynamics change a bit as you scale, but 120 is actually in a sweet spot. You're big enough to have real process complexity—you can't just do everything ad hoc—but you're still small enough that a single engagement can actually move the needle. We did a similar engagement with a firm about your size—similar revenue, similar structure—about a year and a half ago in London. They were in financial services compliance. Six months post-engagement, they'd cut their turnaround time by 35% and reduced redundant work by significant margin. So yes, this is the scale we know how to work at effectively. [10:47] Thomas: *nods* Good. Okay. I think that answers my main concerns. --- ## PRIYA RAISES THE EXCEL TEMPLATE PROBLEM (10:47–11:00) [10:47] Priya: *leans forward, slightly animated* Okay, so before we move on, I want to flag something that I think is probably going to jump out at you guys pretty quickly, and I'd rather just... acknowledge it upfront. So—the spreadsheet situation. [10:48] Nora: *looks up* The spreadsheet situation? [10:49] Priya: *laughs a little, stressed* Yes. So we have, like, dozens of operational templates that live in various places. Shared drives, email attachments, individual hard drives, some in our project management system. The problem is, there's no real master version. Every team has essentially created their own version of core templates—client tracking, project intake, budget tracking, even onboarding checklists. Some of these are slightly different, some are very different. [10:51] Priya: And—this is the part that drives me crazy—some of them have broken formulas. I'll get a spreadsheet from someone in the Milan office, and I can see that the sum function is just... wrong. Or it references columns that don't exist anymore. Or there are duplicate rows that nobody's deleted. I've spent hours trying to clean up after the fact, just to get consistent data to report on. [10:53] Marcus: *making notes* How many of these templates are we talking about? Roughly? [10:54] Priya: I'd say there are maybe a dozen that are truly critical—the ones that affect how we track clients, revenue, capacity, quality metrics. And then there are probably another 30 or 40 that are used by individual teams but don't necessarily feed into reporting. The big challenge is that I don't even have a complete inventory. Because people keep creating new ones. Just last week, I found out that the project management team had created an entirely new intake form that nobody told me about. Nobody told *them* it already existed. [10:56] Marcus: *still taking notes* So there's no governance around template creation? [10:57] Priya: Not really, no. I mean, IT is supposed to manage our shared drive, but there's no active curation. And people are busy—they need something fast, so they grab something that sort of works, modify it, and off they go. Which is understandable from a day-to-day perspective, but it creates this... *waves hand* chaos in the background. And when I try to pull data to report to Thomas—and Thomas needs good data for the board—I'm constantly in a position where I'm either spending days validating and fixing, or I'm presenting data that I'm not 100% confident in. [11:00] Marcus: *looks at Nora* This is exactly the kind of thing that gets invisible in normal operations, but it's actually a massive efficiency drain. Priya, when you say you're spending hours—is this a weekly thing? [11:01] Priya: It's more like weekly, yes. At minimum. Sometimes it's more if we have a reporting deadline coming up. And it's not just my time—it's also David's people, they sometimes have to troubleshoot things on the system side. It's just... it's not a disaster situation, but it's a slow leak of productivity. [11:03] Marcus: And has anyone tried to consolidate or standardize? [11:04] Priya: *sighs* I've brought it up. Qualche settimana fa I sent out a request for everyone to use a standard template. You know what happened? People used it for like two weeks, then drifted back to their own versions because they said it didn't fit their process. And maybe they were right—I don't know yet. Which is why I'm actually really glad you're here, because this might be something where an outside perspective helps. Like, are we being too rigid in trying to standardize? Or are the teams being too freelance? Or is the answer something in the middle? [11:06] Marcus: *nods* That's the kind of thing we'll dig into. We'll talk to the team leads, we'll look at what each template is actually used for, we'll see if there are legitimate operational reasons why they differ or if it's just inertia and habit. And then we'll make a recommendation that's actually grounded in how you actually work. [11:08] Priya: *visibly relaxes slightly* Thank you. I feel like I've been carrying this in the background, and it's good to know it's going to get some attention. --- ## DAVID PARK ARRIVES LATE & DISENGAGED (11:08–11:15) [11:08] *David Park enters quietly, about 5 minutes late, with an apologetic look* [11:08] David: Sorry, sorry—I had a call with our vendor in London that ran over. I didn't mean to miss the beginning here. [11:09] Thomas: No problem. We were just talking through the approach. Marcus, did you want to do a quick recap for David, or are we good? [11:09] Marcus: *gestures welcoming* David, you're the CTO, right? Technical side? [11:10] David: Yes, that's me. David Park. [11:10] Marcus: Right, we talked briefly in an initial call. I was just explaining our methodology—the observation, interviews, analysis, recommendations framework. Nothing you need to catch up on fully right now. We'll get into systems access stuff in a moment. [11:11] David: *nods, pulls out phone to check something* Okay, sure. I was just worried I was going to miss some critical requirement or timeline. [11:12] Thomas: No, we're basically just getting on the same page here. One thing that did come up, though—Priya flagged the template issue again. [11:13] David: *glances up from phone briefly* Oh, right, the Excel thing. Yeah, I know about it. IT's aware. It's on the roadmap to address. [11:14] Nora: *studying David* When you say "on the roadmap," do you mean— [11:14] David: *slightly distracted, looking back at phone* I mean, we know it's a problem. It's not an immediate priority, but we've flagged it. I've got a bunch of other things on my plate with the cloud migration project. *pauses* Sorry, I'm being rude. I'm listening. [11:15] Priya: *gently* David, this might actually be connected to the migration, though. Like, if we're moving data around, this is the time to fix the template problem, right? [11:15] David: *sits up slightly* Yeah, no, you're right. Fair point. Okay, it's on my list. *puts phone down, makes a note in his laptop* --- ## DISCUSSION OF SYSTEMS ACCESS & METHODOLOGY (11:15–11:25) [11:16] Marcus: Let me actually come back to the methodology piece, because this connects to what David just mentioned. We'll want access to key systems to understand the actual flow of work. Not to audit the technology itself—that's not really our remit—but to see how your processes map onto the tools you're using. Because sometimes a process problem looks like a system problem, and sometimes it's the opposite. David, from your perspective, what systems should we be looking at? [11:18] David: *more engaged now* You've got the main ones—our project management system, which is still somewhat basic. Our CRM. The client portal, which is aging. Financial tracking system. And then there's all the Google Drive stuff where people just... keep things. Email, obviously. [11:20] Nora: And you can give us access to those, or do we need special credentials? [11:21] David: I can set you up. I'll probably give you guest accounts on most of it, just for read-only access. I want to keep it locked down a bit just for security reasons. [11:22] Priya: We can arrange system access. I'll need to work with David and IT on what makes sense from a security standpoint, but I think we can make something work. [11:23] Thomas: Full access. Tell Marcus and Nora what they need. This is important enough. [11:24] Priya: *pauses noticeably* Yes. Okay. Though we should probably... *glances at David* let me just flag that some systems have what I'd call sensitivities around access. Especially anything touching client data. [11:26] Nora: What kind of sensitivities? [11:26] Priya: Oh, nothing unusual. Client confidentiality agreements, that sort of thing. The standard stuff. Totally manageable. I'll draft a protocol with David. We have NDAs we use anyway, so we can expand those. But I do want to make sure we're not opening doors that create compliance issues. [11:28] David: Yeah. We can do it. I'll work with Priya to set up a clean environment, probably sandbox access for anything really sensitive, so you can see the process and structure without seeing the actual client information. [11:30] Marcus: That sounds perfect. We're used to working under NDAs and access restrictions. We'll be discrete and professional about it. And honestly, understanding the process matters more to us than seeing the actual data. [11:31] Thomas: Good. Let's move on to logistics. --- ## SCHEDULING & PLANNING SECTION (11:25–11:35) [11:32] Thomas: So—when do you want to start the interviews? And who do I need to tell to cooperate? [11:33] Nora: Sooner is better. We'd like to kick off Phase One next week if possible. Starting Monday, September 15th. And yes, you'll need to send a communication to your team explaining that we're here, that this is collaborative, and that we'll be requesting time from various people. [11:35] Marcus: The communication should emphasize that we're not here to evaluate individuals. We're trying to understand systems. That distinction matters for people who are naturally going to be a little defensive. [11:36] Priya: I can draft something. And we should probably include a brief bio of you both so people know who you are when you show up in their office. [11:37] Marcus: *smiles* Thank you, that's actually very helpful. I'll send you some background on both of us and on our firm. And I'd suggest the communication explains that the goal is to identify improvements that will make everyone's work easier. Not all process change is painful, but we want people to know it's coming. [11:39] Thomas: Fair enough. I'll review it and send it out by end of week. Priya, coordinate with Marcus on the template. [11:40] Priya: Will do. And we should block calendar time for the steering committee meetings. How often were you thinking? Weekly? [11:41] Marcus: I propose bi-weekly, for about 45 minutes. Thomas, you, me, Nora, David if possible. Just to keep on track, surface issues early, and maintain alignment. Does that work? [11:42] David: *nods without looking up* Yeah, I can do that. [11:42] Thomas: Bi-weekly works. Priya, get that on the calendar. And Marcus, I want those findings to be complete enough that I can present something to the board by... let's say mid-November. November 15th at the latest. Can you do that? [11:44] Marcus: November 15th is feasible. We'll have a draft narrative summary by then, and we can do a full presentation by end of month if you need it. Will the board presentation happen here in Florence? [11:45] Thomas: Yeah, here. Unless things change, but I don't expect them to. [11:46] Nora: One other thing—are there any other locations or operations we should be aware of? Just to scope this correctly? [11:47] Thomas: Here in Florence is the primary office. We've got that small team in Milan—what, Priya, about 8 people? [11:48] Priya: About 8, yes. They're mostly client-facing. The operational infrastructure is here. [11:48] Thomas: Right. So Milan is more of a satellite. I mean, at some point maybe Milan comes into scope, but let's start with Florence. [11:49] Marcus: *making final notes* Got it. So Florence is our primary focus. Okay, I think we have a good frame here. Let me summarize: Phase One discovery kicks off Monday, September 15th. We'll conduct interviews, observe workflows, and document existing processes. Bi-weekly steering meetings starting September 22nd. We'll develop findings through October, synthesize analysis in early November, and present a comprehensive roadmap and recommendations by November 15th. Does that capture it? [11:51] Thomas: That works for me. Anything you need from me in the meantime? [11:52] Marcus: Just one thing—keep an open mind. Sometimes the things that feel obvious to you as a CEO aren't obvious to your team. And sometimes your team has insights you might not have picked up on. That's where a lot of the value comes from. We're just creating a space to surface all of that. [11:53] David: And if you find something we should know about immediately, you'll tell us, right? Not wait until the final report? [11:54] Nora: If it's critical—like, if we see something that's creating immediate risk or serious dysfunction—yes, we'll flag it. Otherwise, we hold findings for the steering committee to respect the integrity of the analysis process. We don't want individual conversations distorting the overall picture. [11:56] Priya: That sounds fair to me. --- ## EXTENDED CLOSING (11:56–12:05) [11:57] Thomas: *stands slightly* Alright. I think we're good here. Marcus, Nora—welcome to ClearPath. Let's make this a good engagement. [11:58] Marcus: *stands, extending hand* Thank you. We're looking forward to it. Priya, I'll follow up with you tomorrow about logistics for next week. And we'll send you our standard confidentiality and access request forms. [11:59] Priya: *stands* Perfect. I'm here to make this easy. And honestly, this conversation has already been helpful. It feels like we're going to have some good clarity here. [12:00] Nora: *gathering laptop* One last thing—what's the food situation around here? *smiles* We're going to need fuel for the next few weeks. [12:01] Priya: *laughs* Oh, you're in the right city for that. There's a great little place just around the corner—Osteria da Ruggero. It's family-run, not fancy, but the pasta is genuinely excellent. And they're used to people coming in for quick lunch during the work day. [12:02] Thomas: *adds* There's also Gabriele's, which is just a couple of blocks away—more of a café, but they do sandwiches that are actually good. That's where I grab coffee. [12:03] Marcus: Excellent. Thank you. We'll scout around. There's also—since you mentioned Florence earlier—I remember a little place near the Ponte Vecchio that had amazing food. I can't remember the name, but I'll have to find it. [12:04] Thomas: *laughs* Let me know what you find. I'm always looking for new places. [12:05] *everyone gathers bags and begins moving toward the door* [12:06] Priya: Oh, and seriously, if you want that office tour before you go, I can do it in five minutes. It might actually help you understand the space better. [12:07] Nora: *to Marcus* Should we? [12:07] Marcus: *to Priya* That would be great, actually. Thank you. [12:08] *group moves toward the conference room door* [12:09] Priya: *as they walk* So the main team is on the second floor, and I'll show you the collaboration space we've set up... [12:10] *meeting adjourns; informal conversation continues through the office tour*

Meeting 001 — project kickoff

What was taken from it