Operational Discovery Report
“Four teams are running the same workflow and don't know about each other.”
Meridian Partners — Strategy & Implementation Consulting
47 people mapped · 36 workflows · 14 cross-team patterns · 3 agents scoped · Interviews conducted March 3–10, 2026
The map, in one paragraph.
Meridian Partners is a 200-person consulting firm operating across six practice teams. We interviewed 47 people and built a map of 36 distinct workflows, 14 cross-team patterns, and 23 pieces of institutional knowledge that currently live in individual people's heads. The single most revealing pattern: four separate teams are independently maintaining versions of the same client-status tracker. None of them know about the others. Partners have been reading four different versions of the same accounts in Monday meetings for years. The full map is visible at a private URL for the leadership team. This document is a static snapshot of it as of March 10, 2026.
The three patterns the map revealed first.
Four teams are maintaining the same tracker and don't know it.
The map revealed that the Healthcare, Financial Services, Public Sector, and Technology practice teams each maintain a weekly client-status spreadsheet. They have different names — ‘the pipeline doc,’ ‘the live tracker,’ ‘the Monday sheet,’ ‘the partner update’ — and slightly different columns, but they contain substantially the same information about substantially the same clients (there's significant cross-practice overlap on the top 30 accounts).
Each tracker takes between 3 and 5 hours per week to maintain, distributed across 2–3 people per team. That's roughly 14 hours a week of senior associate time spent producing four versions of a document that should be one document.
More importantly, the four versions disagree. We compared the four trackers as of March 7. On the 18 clients that appeared in more than one tracker, the status, next action, or owner conflicted in 11 cases. The partners reading these in Monday meetings are getting different stories about the same accounts depending on which deck they're looking at.
Nobody on any of the four teams mentioned this in their interview, because none of them know the other trackers exist. It only became visible when we put the transcripts side by side.
Estimated time recovered if consolidated: 12 hours/week. Estimated cost to build the unified version: low. Estimated political difficulty: medium — each team feels ownership of their tracker.
The proposal process has a 6-day shadow phase nobody talks about.
The map revealed that when a new opportunity comes in, the official proposal process is documented as taking 5 business days from intake to delivery. In practice, across the 12 recent proposals we reconstructed in interviews, the median time was 11 days. The extra 6 days are spent in what one senior associate called ‘the swamp’ — waiting for case studies to be located, waiting for the right partner bio, waiting for someone to find the version of the methodology slide that was used last time, waiting for legal to confirm a clause that's been confirmed eleven times before.
None of this work is hard. All of it is repeated. Every proposal team is rebuilding the same artifacts from scratch because there's no working system for retrieving the previous versions, and the institutional knowledge lives in three or four people's heads and inboxes.
Two of those people described being interrupted ‘constantly’ with proposal-related questions. One said it was the main reason they were considering leaving.
Estimated time recovered: 25–30 hours/week across the proposals function. Secondary effect: faster proposal turnaround likely improves win rate, though we can't quantify that from the interviews alone.
Your most senior people are doing your most junior work in one specific place.
The map revealed that six of the eight partners and principals interviewed described, unprompted, spending significant weekly time on expense report review, timesheet reconciliation, and approval routing. The median was 4 hours per week per partner. At partner-level billing rates, that's the most expensive 4 hours in the firm being spent on the lowest-leverage task in the firm.
When asked why, the answers clustered around two themes: the existing system requires partner-level credentials for certain approvals, and nobody has ever questioned the workflow because it's been that way for years. One partner said, with what we're fairly sure was dark humor, ‘I went to business school for this.’
This is the easiest thing on the list to fix and the one with the highest dollar-value-per-hour-of-effort to address.
Estimated time recovered: 32 partner-hours per week. Cost to address: trivial.
The eleven mid-tier patterns.
These are presented more briefly. Each was mentioned by multiple interviewees or surfaced as a pattern across teams.
Client meeting prep is being done from scratch every time.
Senior associates spend 30–90 minutes before each client meeting assembling background, recent communications, and account history. The same information is being assembled repeatedly for the same clients.
~18 hours/week recoverable.
The Friday partner update is taking 4 people most of Friday afternoon.
Three associates and one EA spend Friday afternoons collecting, formatting, and distributing the weekly partner update. Most of the underlying data lives in systems that could produce the update directly.
~14 hours/week recoverable.
Three different teams are manually copying data from Salesforce into Excel for analysis.
Because the Salesforce reporting layer is 'annoying' (mentioned in 9 interviews, exact word).
~9 hours/week recoverable, plus the analysis itself becomes more reliable.
New hire onboarding is a 40-hour drain on the team that absorbs the new hire.
The onboarding process is documented but not automated. Each new hire effectively costs their team a week of someone else's productivity. With 18 hires expected this year, that's 720 hours.
Significant recovery possible.
The case study library doesn't exist as a library — it exists as 200 PowerPoint files in 14 folders.
When someone needs a relevant case study, they ask in Slack and hope. Three people described this as 'the worst part of writing proposals.'
Connects to finding #2 above.
Meeting notes are being taken, written up, distributed, and then never read again.
Five interviewees described the post-meeting writeup as 'performative' — they do it because it's expected, not because anyone uses it. The notes contain valuable signal that's currently being lost.
Worth reframing rather than eliminating.
Invoicing has a 9-day delay built into it that nobody designed.
The delay comes from a chain of small handoffs, none of which take long individually, but which collectively push invoices out by more than a week. Direct cash flow impact.
Worth a separate analysis.
Two people are functioning as 'the person who knows.'
One in operations, one in client services. Both described being interrupted dozens of times a day with questions only they can answer. Both are flight risks. The knowledge they hold is recoverable into a system the rest of the team can query.
Urgency is high because of the flight risk, not the time recovered.
Recruiting screening is being done by people whose time is worth 4–6x what the task warrants.
Senior managers are doing first-round CV review.
Standard pattern, easy fix.
Status updates to clients are being written individually when they could be assembled.
Each project lead is writing weekly client updates from scratch. The underlying material exists in project management tools.
~11 hours/week recoverable.
There's a recurring 2-hour meeting on Wednesdays that 6 of the 11 attendees described as 'not useful for me.'
This isn't an automation finding — it's a finding the interviews surfaced because we asked. Worth raising with the meeting owner.
Not an automation, but worth knowing.
The agent blueprint.
For each high-value pattern, a specific AI agent to build — in the order we'd build them, with estimated hours recovered and the reason it sits in that slot.
Partner approval routing agent
Unified client tracker
Proposal asset retrieval agent
A note on what the map didn't reveal.
A few things worth saying, because documents like this tend to oversell.
We didn't find evidence that your client work itself is inefficient. The teams we interviewed are doing skilled judgment work that should not be automated and mostly couldn't be. The opportunities are in the layer underneath the client work — the operational scaffolding — not in the work itself.
We didn't find a single villain. No one team or system is responsible for most of the loss. It's distributed, which is why it's been invisible, and which is also why fixing it requires looking across teams rather than within them.
We didn't find anyone who seemed to be hiding their work or padding their hours. The people we interviewed were, almost without exception, trying to do good work inside systems that were making it harder than it needed to be. The findings in this report are not about your team. They're about the operational layer your team has been compensating for.
This is a snapshot. The real map is live.
This document captures the Plainsight map for Meridian Partners as of March 10, 2026. The live map is hosted at a private URL for the leadership team and continues to update as new interviews happen and patterns shift. If you are the leader who commissioned this map, your URL is in your email. If you are evaluating Plainsight, the closest thing to a live map view is in the three sample companies on our homepage.
This is what your company's map could look like.
Add your team and we'll start the interviews this week. You'll watch your map build in real time.