Version 1.0 and the Zombie Garden –
It is quickly dawning on everyone on this program that there are a lot of new ideas to get your head around in a short space of time. Two suggestions from the team at We are Open really helped with this.
Version 1.0 – Basically your first attempt at something does not need to be your final attempt. You can come back to things after your first attempt. As the program continues you may come across new ideas that change the way you think about something you have already covered. You can go back and make another version, Version 1.1, Version 1.2 and so on…
The Zombie Garden
This is a concept where you put ideas that interest you, but are low priority to one side to look at later.
The Data model from last week is one such idea I have put in the Zombie Garden to look at when I have more time.
By Visual Thinkery is licenced under CC-BY-ND
Open Working Support Workshop –
On Tuesday I attended a ‘Working in the open’ Work Shop run by the Open Working Lineup (OWL) where we learnt about the benefits of this way of working and ideas for how to work in the open.
Basically “Working in the open’ is as simple as sharing your work with others – inside or outside your organisation.
This can simply be done by writing publicly about your work at any stage within a project. This can be a blog, social media posts or as weeknotes which are like a diary where you reflect on what you have learnt over the week and make better decisions.
The Benefits of ‘Working in the open’
It makes you reflect on what you have learnt and process the information in order to share it with others. By doing these it helps you gain a better understanding and makes you think about how you can use this new information.
It invites interested parties to get involved and give feedback on your work. Negative feedback should be seen as a positive to aid learning and improve what you are doing.
You can learn from others that are working on similar issues and may already have solutions for the problems you are facing.
It may also attract potential funders, partners and collaborators.
Architecture of Participation
Although I will be the main WECIL staff member involved in the 10 week Digital Program it is important that the rest of WECIL are kept informed in what I am doing and feel like they can have their say and get involved. In this session we talked about the architecture of participation which is basically a simple set of ideas to keep wider teams informed and involved in a project and to manage the team when multiple people are involved to different levels.
cc-by-nc We Are Open Co-op
I am not sure in what direction this project is going, but I welcome the idea of involving others. I need to revisit this session as the project progresses.
Persona Spectrums & Journeys
Today we talked about identifying who the users might be of the digital services we are developing and the idea of using User Personas.
A Persona is where you identify key characteristics of a person including those that might impact the development of the digital solution. Such as Age, language, Access needs, technology familiarity, Devices used, how they become aware of the service.
We then talked about taking these and starting looking at ‘persona spectrums’ – identifying common characteristics across the different personas which can be used to help shape the digital solution you develop. For instance there is no point in developing a Phone App if none of your target users have mobile phones.
Initially I found creating Personas hard as WECIL provides so many services for such a wide range of people. However I eventually scaled the idea back to just People who are newly referred for Direct Payment support. I am starting to learn that I need to think small scale to make this Project work in 10 Weeks
Once you have your User Personas and Spectrums it is then useful for your planning to map their User Journeys. Both now and what you would like their journey to be following the introduction of your digital solution. Take them through the 4 stages of engagement
1)How does the user become aware of the service
2) First contact with the service
3) Building the relationship
4) Deepening engagement
This will help you understand requirements of the project and barriers and risks to the project.
In this session we explored existing tech and digital solutions and discussed the Build v Buy approach to finding Solutions.
In general the right Tools for the Job are already out there and we would be unlikely to need to develop our own tech for our digital solutions. This was reassuring as development can get very expensive. We also discussed that not all Digital solutions work out, so if you are going to spend lots of money developing something you better hope it works.
To demonstrate this we spent time exploring and reviewing the pros and cons of different existing Messenger Apps and Chat Apps.
Going off on a slight Tangent we discussed the use of Emails within organisations and how everyone finds Long emails time consuming.
We were then introduced to the five Sentence rule where you try to keep all emails and email responses to no more than five sentences. http://five.sentenc.es
I realised wherever possible I already try to do this, I just need to figure out how to get the rest of the world to adopt this idea!
22nd February to 26th February 2021 – Matt Young