Internal Journey Mapping and Capability Building
The challenge
The support organization was running on institutional memory and informal workarounds nobody had written down. Leadership wanted to find automation opportunities, but you can't automate a process you don't understand. Before any technology decisions, someone needed to map what was actually happening, not what the org chart said was happening.
What we did
The client wanted to find automation opportunities inside their internal support operations. That was the stated goal. But what made this engagement stick was what happened alongside the research.
While mapping workflows and interviewing 19 support team members, we built the client's internal research capability at the same time. By the end of the engagement, the team knew how to identify problems, structure studies, and keep digging on their own without bringing in outside help.
For teams weighing whether to hire a fractional researcher or invest in internal capability, this project is a good example of why that's a false choice. You can do both at once.
What changed
By the end of the engagement, the support team had documented their own workflows for the first time. Leadership had a clear picture of where automation could actually help versus where it would create new problems. The team also had the research skills to keep investigating on their own. The engagement built capability, not just a deliverable.