Doefinitions and documentations havepproven to be a backbone of automation in RevOps, as it helps the entire team align and also can be an easy reference point for teams, when in doubt.
While there were systems in place when I joined the team, the definitions and documentations of lead stages were not up to date. They were mostly head knowledge, which made it difficult to pass around from team to team, or to new joiners as well.
I took up this project and carefully defined, set up new stages and documented it for public view.
Here are the core things I had to set:
✔️ Accurate stage naming
✔️ Detailed definition of each stage criteria
✔️ Clear entry and exit conditions for each stage
✔️ Identifying the responsible teams for each stage and the required action