The Operational Transition:
change management
cross-functional architecture
strategic risk mitigation
“You have a proactive approach that I find beneficial. You ask the questions I don’t know to ask and name the tasks up ahead I don’t always realize I should be thinking about.”
I was brought in to architect a vendor transition within four months for a call center operation that had just lost institutional knowledge through a company-wide reorganization.
My role was to transform organizational anxiety into structured progress by creating end-to-end workflows, establishing cross-functional workstreams, and building the operational playbooks that enabled business continuity despite the knowledge vacuum.
The Problem
The client needed to migrate their call center to a new vendor while simultaneously redesigning how cases would be handled: changing activity flows, data exchanges, and coordination between the vendor and internal teams. The challenge was compounded by timing: the project launched one month after a massive reorganization that had eliminated the people who understood how the old system worked. The remaining team faced a rigid four-month deadline with no documentation, no clear understanding of current processes, and mounting anxiety about what they didn't know. Without institutional knowledge to build on and no established baseline to work from, the team couldn't articulate what needed to change, let alone how to implement it.
The Solution
I started by creating clarity about what was changing and why it mattered, connecting the vendor transition and program redesign to business objectives so the entire cross-functional team understood the purpose behind the timeline pressure. Rather than pretending we had all the answers, I mapped out the envisioned operational model and deliberately highlighted the gaps and unknowns, making the missing pieces visible so the team could see where to focus their effort. This transparency shifted the conversation from paralyzing anxiety to collaborative problem-solving. I then organized the work into focused workstreams with clear ownership, breaking down overwhelming complexity into parallel investigation tracks that teams could tackle independently while I tracked interdependencies separately. As questions emerged across workstreams, I built comprehensive end-to-end workflows illustrating how all the pieces would fit together — the new processes, data handoffs, system triggers, and touchpoints. These workflows became the single source of truth for both technical teams (internal IT reconfiguring the CRM, vendor IT building APIs) and operational teams designing the human processes. To centralize fragmented knowledge, I drafted the Standard Operating Procedures (SOPs) and Business Rules Document (BRD) that gave stakeholders something concrete to react to, enabling focused problem-solving and uncovering previously unknown complexities through collaborative refinement.
Core Skills Leveraged
-
While my formal remit was project management, I quickly recognized that the team's real struggle wasn't tracking timelines—it was identifying what needed to be done and understanding the ripple effects of program changes across the organization. No one had a clear view of second-order impacts. By consistently probing one level deeper in conversations ("Then what happens? Who takes it from there? What do they do with it?"), I surfaced critical dependencies that had been invisible.
This questioning revealed that changes to the call center workflow would affect sales processes, analytics reporting, finance reconciliation, and other downstream functions that hadn't been part of the initial planning conversations. I brought in additional internal stakeholders for input, informed more departments about upcoming changes, and co-created new processes in anticipation of the transition. This strategic foresight prevented what would have been painful surprises during implementation and ensured the organization was prepared across functions, not just within the immediate project scope.
-
The project was divided into ten workstreams, and I was one of the few people attending all meetings. This positioned me to serve as connective tissue, piecing together how decisions in one area would impact work happening in others. I relayed information across teams promptly, which accelerated decision-making by giving people the cross-functional context they needed to move forward confidently. I built this connectivity into the weekly dashboards I created for workstream leads, explicitly flagging critical interdependencies that would create bottlenecks if not coordinated.
When I noticed teams across workstreams struggling to grasp the full scope of changes, I created detailed workflows mapping every key action, touchpoint, and data transfer. These visual maps became essential infrastructure: the internal IT team and vendor's technical team could now align on exactly when APIs would push or pull information and which status changes would trigger downstream actions. Both technical planning and human operational design relied on these workflows to ensure the pieces would actually connect when the transition went live.
-
This project unfolded in a high-anxiety environment shaped by both recent reorganization and an aggressive timeline. The institutional amnesia created by losing the legacy knowledge holders meant we were rebuilding operational understanding from scratch while also trying to innovate.
My challenge was building a bridge between the old way of working (which no one could fully articulate anymore) and a half-formed vision for the redesigned program. I centralized fragmented knowledge by drafting baseline documentation — SOPs and Business Rules — that gave scattered insights a home. These documents weren't perfect, but they were concrete enough that stakeholders could engage productively: they could add questions, suggest edits, and surface concerns, which consistently led to richer discussions that uncovered complexities no single person had anticipated.
By creating artifacts that invited collaboration rather than presenting finished solutions, I turned the documentation process itself into a mechanism for knowledge-building and alignment across a fractured organization.