Knowledge gap
Targeted training
01
Hypothetical operating strategy case study
STRATEGOS
Turning institutional knowledge into a scalable Customer Success operating system.
90 Days5 Operating Capabilities1 Continuous Improvement System
This is a hypothetical strategy exercise showing how I would approach the challenge - not work claimed to have been implemented at a prior employer.
The scenario
Scale the expertise without losing the judgment.
You inherit responsibility for a small, growing Customer Success team supporting a specialized SaaS product. As the team grows, success needs to become repeatable rather than dependent on individual knowledge.
The team knows its customers. Experienced employees understand the product. Problems get solved. But critical institutional knowledge remains concentrated among a few people, making the model increasingly difficult to scale.
How do you preserve the judgment and expertise of a small team while creating a Customer Success operation that can grow beyond the people who built it?
The operating principle
Build a system capable of learning.
Customer interactions generate signals. Those signals reveal process, knowledge, training, and product gaps. Improvements strengthen playbooks, documentation, enablement, and the customer experience.
STRATEGOSLearn &
improve
01Customer interactions02Signals & insights03Gaps identified04Improvements05Playbooks & enablementimprove
The Strategos operating system
Five connected capabilities. One scalable customer experience.
- 01
Customer lifecycle
Define what customers need at each stage - and what Customer Success owns.
- 02
CSM playbooks
Turn recurring moments into repeatable approaches without scripting judgment.
- 03
Knowledge system
Make institutional knowledge searchable, current, owned, and available in the flow of work.
- 04
Team enablement
Develop readiness through application and demonstrated competency - not attendance.
- 05
Measurement & improvement
Use customer and team signals to improve process, training, knowledge, and product.
Customer experience → Insight → Improvement → Enablement → Better customer experience
Start with the customer
Map the lifecycle before writing the process.
The first step is not creating SOPs. It is understanding what the team is responsible for helping customers accomplish.
01Implementation handoff02Onboarding03Activation04Adoption05Ongoing success06Expansion07Risk management08Renewal
At each stage, Strategos defines the customer objective, success criteria, CSM responsibility, trigger, and measurement. That lifecycle becomes the foundation beneath the playbooks, training, documentation, and measurement system.
Playbook example
Consistency without eliminating judgment.
01
TriggerOnboarding is complete, but usage remains materially below the expected adoption level.
Workflow mismatch
Configuration or process intervention
Technical barrier
Support or Product escalation
Stakeholder disengagement
Relationship and executive alignment
Unclear value
Reconnect usage to desired outcomes
The playbook guides the diagnosis. The CSM still exercises judgment.
Knowledge as infrastructure
Documentation should support work - not become work.
Customer lifecycle
How Customer Success operates.
CSM playbooks
What to do when something happens.
Product knowledge
How the product works.
Customer resources
What helps customers succeed.
Owner→Last reviewed→Review cadence→DependenciesHelpfulNeeds updateMissing information
AI-assisted knowledge maintenance
Keep knowledge fresh without surrendering control.
As more information becomes available, an LLM-connected workflow would use curated prompts to search approved sources, compare new signals with existing documentation and CSM playbooks, and surface evidence-backed recommendations for expert review - including opportunities to deepen adoption or expand value across the customer organization.
Product releasesSupport themesCustomer feedbackCall summariesApproved documentation
- 01→
Monitor
Review trusted sources on a defined schedule.
- 02→
Evaluate
Use curated prompts to find gaps, conflicts, repeated questions, and emerging risks.
- 03→
Recommend
Draft a structured update with evidence, confidence, urgency, and an owner.
- 04→
Review
Route the recommendation to a subject-matter expert to approve, revise, defer, or reject.
- 05
Publish
Record approved guidance with its sources, owner, review date, and change history.
Curated evaluation
What the workflow looks for
- Outdated or conflicting guidance
- Missing information and repeated questions
- New situations without a playbook
- Steps that conflict with current product guidance
- Patterns behind successful and unsuccessful responses
- Playbook deviations that may reveal a process gap
RECOMMENDATION · 014
HIGH CONFIDENCEExpansion play identified
- Detected pattern
- Strong adoption within one customer team, but limited usage across other eligible groups
- Affected content
- Adoption and Expansion Playbook
- Recommended action
- Add a value-review trigger that prompts the CSM to validate outcomes with the successful team, identify additional eligible users or departments, and create a phased expansion plan with the customer sponsor
- Evidence
- Usage trends, customer feedback, success-plan goals, and recurring themes from customer conversations
- Owner
- Customer Success Operations + Account Leadership
AI keeps knowledge moving.People keep it trustworthy.
AI never publishes operational guidance on its own. Subject-matter experts remain accountable for accuracy, context, privacy, and final approval.
Train for judgment
Readiness is demonstrated, not attended.
01Learn→
02Observe→
03Practice→
04Demonstrate→
05Own
What has this employee demonstrated they are ready to own?
Progression separates time employed from demonstrated capability - and makes coaching needs visible.
CompetencyLearnPracticeDemonstrateIndependent
Product fundamentals✓✓✓✓
Customer lifecycle✓✓✓✓
Onboarding✓✓✓✓
Adoption diagnosis✓✓✓
Customer communication✓✓✓
Escalation management✓✓
The first 90 days
Discover. Build. Operationalize.
Discover & design
Listen before standardizing.- ✓ Shadow customer interactions
- ✓ Map the customer lifecycle
- ✓ Inventory institutional knowledge
- ✓ Establish baseline measures
OUTPUTCustomer journey · Gap assessment · Playbook backlog
Build & pilot
Solve the highest-value problems first.- ✓ Develop priority CSM plays
- ✓ Establish knowledge architecture
- ✓ Build the competency framework
- ✓ Pilot with the people using it
OUTPUTPlaybook v1 · Knowledge system · Readiness framework
Operationalize & improve
Make the system the way the team works.- ✓ Incorporate pilot feedback
- ✓ Launch coaching and assessments
- ✓ Assign documentation ownership
- ✓ Create the improvement backlog
OUTPUTOperating model v1 · Dashboard · Next-quarter priorities
What success looks like
Six months later, the difference is visible.
Answers are findable
A new CSM can find an answer without knowing who to ask.
Strong work is repeatable
Two CSMs facing the same situation follow a consistently strong approach.
Managers can coach
Leaders spend less time answering repeat questions and more time developing people.
Value creates growth
CSMs connect demonstrated customer outcomes to appropriate opportunities for broader adoption and expansion.
The Strategos principle
Process should create leverage - not bureaucracy.
The goal isn't more documentation. It's creating a system where a growing team can deliver a consistent customer experience while making institutional knowledge accessible, repeatable, and scalable.