De-centralising with tasks
How do we de-centralise our work through tasks in Wired Relations. And how do we move our organisation from reactive engagement to proactive engagement.
Introduction
One of the most important functions Wired Relations can serve, is to be the tool through which you succeed in de-centralising compliance and information security work.
While not every organisation is ready for, or interested in, de-centralising, it is a powerful method of ensuring long term success when it comes to compliance and information security.
Long term success comes from building an organisational culture that encourages responsibility and involvement in our work. This requires involvement and buy in from leadership, which is why not everyone chooses to pursue this.
Using tasks in your de-centralisation
Tasks is just one part of your de-centralisation effort. However they're probably the most important part.
Those of us who work with these things every day must recognise, that for most of our colleagues this all happens in the background, and is mostly a nuisance they have to deal with every once in a while.
Therefore it's important that we make it as easy as possible for them to get involved. Which is exactly what Wired Relations is designed to do.
Best practice
To involve your organisation more operationally in Wired Relations, requires making it simple for them to get involved. We do this by limiting their access, and making sure they only see what they need to see. Specifically by assigning them a limited access role
Read more about user roles and tasks.
To make a task as accessible as possible you should think about the following:
- Is it clear what I expect the user to do?
- Is it clear why this is important?
- Is there guidance in the description or attachment help them incase they get stuck?
- Are they fore-warned about their responsibilities and newly given access to Wired Relations?
- Should you create written or video material about how to use Wired Relations?
We recommend that you start small by de-centralising only a few tasks at a time.
What's the first thing you want the organisations involvement in?
Once you've figured that out, you can create a task template for that task. Look at the above bullets to think about what should be included in the template.
With the task template you're able to quickly mass-produce identical high quality tasks for your first users in Wired Relations.
Make sure to orient yourself and your users on how often they will receive email reminders about their tasks.
Reactive vs. proactive engangement
Reactive engagement
For the first while your users will only engage with Wired Relations reactively - meaning they'll only do something if externally reminded via tasks or something else.
This is only natural, since these responsibilities aren't core to their function in your organisation.
It's also why it's critical that we setup enough tasks, because your users won't do anything without a task reminding them to do it.
Proactive engagement
Ideally over time your organisational culture will mature, and your users/colleagues will begin proactively engaging with Wired Relations.
Eg. Adding a new system the moment they procure it, updating system information as it changes, or otherwise making changes in Wired Relations without being prompted to do so.
Proactive engangement is the essence of a sustainable program. And will dramatically increase the compliance and security level in your organisation. As every employee will be aware of their responsibilities, and actively engaged in securing we live up to our commitments.