Why structure the OPS team?
For a long time, the OPS team relied on knowledge shared orally or held by the most experienced people. This could work in a small team, but it showed its limits as Bill grew.
When a service expands, methods need to be standardized, information must be accessible and reusable materials become essential. Otherwise, onboarding new team members becomes harder, clients remain dependent on internal teams and some missions slow down simply because information is not available in the right place.
Four processes, one purpose
I mainly worked on four topics: onboarding with Zelty integration, the CSM process, team-led client onboarding and a self-guided onboarding path for clients.
These processes were different, but they served the same goal: making OPS methods clearer, easier to transfer and more efficient. The objective was to reduce errors, simplify the arrival of new team members and make future onboardings faster.
From idea to usable support
For each process, I followed a similar method. I started with an ideation phase in Miro or Figma to map the steps, stakeholders and possible blockers. This visual representation created a shared view of the path before anything was written.
I then turned this work into concrete materials: HubSpot conversational guides, BoldDesk articles, Loom videos or Guideflow interactive demos. After review by the teams involved, I refined what needed to be clarified or completed.
The internal onboarding process is the most advanced. I gathered knowledge from experience, structured the path in Miro, designed the conversational guide architecture and created the supporting training materials. The final guide was validated and is now used during onboardings.
What I learned
An effective process is not just a document. It must be clear, applicable, understood by the team and updated over time. Its impact is not always immediately visible, but these materials help the company grow better by saving time, training faster and making the service less dependent on individual knowledge.