David Jenyns explains how to build a systems culture by documenting processes so work doesn't depend on one person. He shows how capturing discovery-call steps and project setup creates what he calls system certainty, and argues that systems only become culture when the whole team uses them, not just a few people.
You can have Asana or Monday and they can have the key steps. But again the problem you come into is when the staff member leaves, how do we do that step again? How do we run a discovery call? What are the questions that we're asking? How are we setting up the project? So system certainty comes from getting that documented and it's about not being person dependent and it's about having all of your departments covered. So that's ultimately where we're trying to really grow that system certainty. The second area is systems performance and system performance has to do with having the right software stack. It needs to be simple. You need to split out your project management from your SOP management. You need to have your entire team working on it. Particularly with systems. It's not enough to have it loaded in Google Sites and having one or two team members who work on it. Systems happen when it's part of the culture. This is the way that we do things here.
Remember me? Subscribe To My Channel For More Free Business Systems Content 📈
