The situation
The Technical Account Management team had developed strong expertise around a primary product. As the organization expanded the team's remit into adjacent platform services, the challenge was not to repair poor performance. It was to scale what already worked.
The team needed to support a broader customer journey and learn additional products without turning every TAM into a shallow generalist. We also needed a clearer way to evaluate the value of the TAM service itself.
Measuring the service on its own terms
Revenue was an imperfect measure of TAM performance because customer usage depended heavily on the market success of the customer's own product. A TAM could provide excellent technical guidance, incident leadership, and launch support without materially changing that external outcome.
I established a repeatable customer-satisfaction process focused on the quality and impact of the TAM service. We assigned customers to quarterly survey groups to create consistent relationship coverage while limiting survey fatigue, then added event-based feedback after significant service events, launches, and other major customer moments.
Turning feedback into action
The surveys were not intended to produce a score for reporting alone. We reviewed responses and converted them into account-level and team-level actions.
A customer that had previously offered critical feedback later described a substantially more positive experience after focused coaching and coordinated team action. The survey program also prompted several previously unresponsive accounts to re-engage and resume regular communication with their TAMs.
Broadening knowledge without losing depth
I developed knowledge management and competency assessment together using a V-shaped model. Every TAM needed beginner-level awareness across a broad set of products and related subjects. A smaller subset required deeper working knowledge, while each person developed strong technical expertise in one or two areas.
The model created a practical framework for coaching, self-directed learning, specialization, and future coverage decisions. Knowledge resources could be organized against clear proficiency expectations rather than accumulated as an undifferentiated library.
Creating a connected operating model
Customer input revealed where service practices needed to evolve. The competency model clarified the knowledge required to support a broader portfolio. Knowledge management gave the team a shared path for building that capability, while coaching converted both customer and competency evidence into individual development.
What this demonstrates
Scaling a technical customer organization requires a way to measure the service independently, learn from customer moments that matter, define appropriate levels of technical depth, and turn that evidence into team development. My role was to design those mechanisms as a connected system.