The first stage of getting started with Process Bliss is to map one process - just one. In the software we refer to processes (the instructions of how to do something) as templates. This is what the template editor looks like:
You map your process by listing the steps that make up that activity, one by one. On each step you can add a description of how you perform that step, assign it to a specific person, set date rules, change the importance and add files and links.
When it comes to a point where the next step in the process depends on a decision being taken, you add a decision step to define the different scenarios. For example:
Written as a question, decisions let you define different routes through the process, so the whole workflow is clearly mapped in one place.
As well as yes and no answers, decisions also let you deal with multiple 'branches' at the same time, for example:
Here, we've used the 'simplified view' (accessed from the left hand panel in the template editor) so we can see how the steps link together in a more compact layout.
Using decisions also allows you to loop back to a previous step in the process. Let's imagine that you're writing a process for writing a blog article. You might have an approval step that determines whether the article is ready to be published, or needs redrafting. You could set this up like this:
The above image also shows how you can stop the process if a certain condition is met, in this case if the article shouldn't be published at all. This is represented by the tick in the blue circle on the right hand side, and is called termination.
Once you've mapped the outline of a process, you can share it with colleagues and refine it so there's a common understand of how the process should be run.
If you'd like more help getting started mapping your processes, sign up for one-on-one training or a consulting discovery call here.
Next up: execution - creating checklists so that processes are performed the same way, every time, and you can track the progress through them.