A guide to documenting business processes by embedding standard operating procedures directly into task management software. This approach increases adoption because people follow the steps where they already work, rather than hunting through separate documents.
If you're creating a business process but people aren't using it, odds are they're not worked into your templates. Let me show you what I mean. Let's say you define a process for how you want to organize customer complaints. Maybe you even take the time to write an sop, a standard operating procedure outlining all of the steps you want somebody to take if this event should happen. But despite creating this, people don't actually do it. Which makes this SOP and all the stuff you've just created pretty pointless. Or at least that's what it might feel like. It can be really easy to blame. You know, the process isn't good enough. I need to document more. Or my people just hate process. They can't possibly do it and blame your culture. But it may be a very simple fix. All you need to do is take what you've already created and work it into your task management software. So, for example, if this process is for every time a complaint is received, you need to do this step. Turn that into some kind of task template or checklist. And you guessed it, the first step of that checklist says, check the sop.
