Forum Discussion
Behavior design for reaching adoption objectives
Hi Phil.
Thanks for sharing your experience with Tiny Habits. Indeed, I think many of us find that it is difficult to come up with generic Tiny Habits for Office 365 and the digital workplace. Together we might break the barrier and come up with some good tools, though. :)
Did you have the chance to join BJ Fogg's free 5 day program (http://tinyhabits.com/join), by the way? That's a very good way for learning about the method. On my side, I have been doing quite a number of these free programs since I first came in contact with Tiny Habits method. I find that it is an excellent way to keep the skill fresh and uncover more aspects on the method.
And I like the 2 tiny habits you share, and they show that productivity is much more than just knowing how to use the technology. Which is maybe why it is difficult to make them generic in the first place. But it ought to be possible to make the method generic, at least. I'll try to work on such a method over the coming weeks, and I will be happy to share my results with you.
For example, there's a method taught at the Tiny Habits Academy (where I'm in the process of getting certified in the Tiny Habits method) for coming up with the tiny habits that will make you succeed with a specific desired outcome, called Focus Mapping. I think through the use of Focus Mapping, it is easier to make sure that one does not get stuck.
Another aspect that I think of is the importance of mapping out the potential anchors/triggers. What behaviors do you already do in your digital workplace? With that awareness it gets easier to come up with potential good behaviors during the day.
One tiny habit for Office 365 that I am performing myself the past months is to create a notes page for the meeting in OneNote each time I create a meeting invite in Outlook. I think that is a good generic one (that is similar to your own meeting habit).
I will keep on designing more tiny habits for Office 365, and I'm planning to launch a weekly newsletter focusing on one habit per week. I think organizations would need help to keep up the work of adopting Office 365, and why not as a weekly challenge ("Will you be able to perform this tiny habit for a week?").
Cheers, Magnus
Magnus
Whilst I truly support the idea of Tiny Habit methods of change I wonder if the fundamental issue is around the vast potential of Office 365 and its flexibility for the end user. With this amount of flexibility then trying to find a common set of habits becomes the problem.
I am currently looking at how enough information can be collected from a sizable portion of the business (and not just a few stakeholders) so that a campaign can be created around users selecting from a list of habits.
For example, changing the method of communications with externals to say Microsoft Teams rather than emailing document might be a great Tiny Habit for Sales and Marketing department but not for Research and Development department because of a compliance policy where their management has restricted any external sharing for that department. So, the habit for the sales team is about placement of the shared content whilst for the R&D department it is probably around the classification of the data.
My thought is to develop a 'group of habits' campaign so that users can select which best works for them, and then working with their managers to track the specific change. I realise that this is a bigger piece of work, but everyone works different so a sweet shop approach needs to be taken so they take a ‘Tiny Habit‘ that works for them but allow the change team to focus on a number of changes across the business.
All this depends upon collection information from the business, but then the more information collected the better decisions on how Office 365 can be applied and governed for the business.
Steve Dalby
Hello Steve Dalby,
Definitely agree with you on the need to target the "Tiny Habits" or use cases per department.
And definitely agree on the challenges to get enough feedback from different parties across the organization.
One question we asked ourselves a while back is : Do we need to address all departments at the same time? Depending on your company culture and operating countries, the answer might be no.
If this is the case, you can consider a program phased per department (1 department / month for example). We are currently doing the following:
- Individual interviews of people in the department to get their personal feedback on collaboration needs;
- Followed by group workshops to prioritize/brainstorm on the most critical and urgent use cases via a gamified approach;
- We then select a group of ambassadors in the department and are in the process of coaching them on the basic functionalities of Office 365 to produce quick wins (where the Tiny Habits could be really interesting!);
- We hope to turn these experimentations into success stories and share them in an internal productivity library (a bit like the one of FastTrack which is a good start but not relevant enough for our environment);
- We will then communicate throughout the department on the success stories and start some more coachings based on the incoming leads generated.
- And then iterate the process with another department (duplicating the generated quick wins from previous departments if applicable in the context of the function).
If anyone went through a similar process, I am more than happy to share experiences!
Hope that is of any interest!
