Session 2 aimed to build on the prototype of the first week by adding more detail and establishing the meta data fields. In plain English, what this means is to work out which search and browse terms to use and to ensure that they make sense to the group as this will impact on how the community uses the tool and whether it is sustainable.
Unfortunately, due to it being the summer holidays, two group members Maboobeh and Leah couldn’t be present and Sara could only be there for half a session. In addition, Tommy another facilitator from the CAN Do IT course joined the group. This meant that the sessions we planned had to be condensed and we had to bring Tommy up to speed with the project. First key learning point of the day: As a trainer flexiblity is a must – sometimes you have to be willing to change your plans at the last minute in order to meet the needs of the group.
With a bit of thought we found a way of reflecting on and evaluating the previous session which helped to cement our learning and re-visit the design decisions from last week whilst also introducing Tommy to the project. We asked the group some questions and recorded the resulting discussion…
We then moved quickly on to doing a rough sketch of four key elements of the site: ‘List, browse, search, details’. Due to the acceleration of the session this proved to be a bit confusing! For those of us who had never designed a website before, we weren’t sure where to start. There was also a lack of clarity about the difference between ‘list view’ and ‘detail view’ which became apparent when we fed back our quick designs to the rest of the group. Much of the confusion dissipated when we looked at the ‘OER Commons’ repository for guidance. This gave us a much clearer idea of the different possibilities but also raised some interesting questions in relation to our learning: Would it have been better to show us model repositories at the beginning before we did a rough sketch or was all that confusion an important part of the learning process? How much would a showing a model repository beforehand affect our own designs?
In the afternoon session, we visited Schema.org – a website which offers a collection of schemas to improve the search-ability and browse-ability on websites. By going through a list of suggested meta data terms and choosing which ones to keep and which to replace we began to design the ‘detail’ view of the website. The process of choosing which words to use and which we should replace with other terms that had more meaning to us, prompted discussion on who we are as a community of practice and what language has meaning and relevance to us. This is really important to get right if we are to create a tool which is owned by the community and reflects its needs.
Unfortunately we ran out of time and were unable to focus on the other aspects of the site. Mick has taken away the designs we have already and is in the process of creating a prototype for testing. The group re-convenes on 20th August for another 3 sessions which will allow us to test the site in its current form and make suggested revisions.
Session 2 was more challenging than session 1. Some of the group were unable to attend and we had to accelerate the session. It felt that rushed and that there was little time for explanation. This is partly down to the time of the year that the sessions are being held – many people are taking annual leave at this time.
Holding the sessions at the place of work of the participants is also potentially problematic. Some times we are interrupted because staff have to respond to urgent matters. Holding sessions at a different place might allow people to focus more easily.
When we were asked to do a quick design for the 4 elements on the website: list, browse, search, details, I felt ill equipped to do it because I had no prior experience of designing a website, particularly when others in the group do this work for a living. For me there was a divide between the myself, the novice and the experts. This was a barrier to my participation.It would be interesting to explore this further and to find out whether these perceptions exist for other people in this setting, whether they have experience in other participatory processes and what they did to overcome this perception and support people to contribute.
hilaryct wrote a new post, Week 1: Intro, What’s in the Bag & The Big Picture, on the site Duct Tape Uni 5 years, 7 months ago
Whilst in Bristol at the first of the Jisc SOSI events, the Duct Tape Uni team took some time to think about how to evaluate the co-design process. Understanding the co-design process, its strengths and weaknesses and how it impacts on the development and the effectiveness of the tool is as important to the project as the tool itself.
During initial discussions with our mentor Peter Chatterton we agreed that the evaluation should be integral to the process and that we should therefore be evaluating and reflecting on the process from the beginning of the project.
The cyclical process of ‘Plan, do, check, act’ encapsulates this idea and helps to keep the process simple.
We decided it would be useful to keep a project blog to map the critical moments and to record the overall process and that we could gather information, capture exciting moments and document feedback from stakeholders through using audio, video and photography.
Although we were pretty clear on the ways we could gather information, we still weren’t sure about what kinds of questions we should be asking as part of the evaluation so Peter suggested that we speak to Sara Knight, one of the experts from Jisc.
Sara suggested that a simple and effective way of evaluating the process would be to ask three key questions:
1. Have the initial aims of the project been met?
2. Is there evidence that it will be used or that it is needed?
3. How did we experience the project process and how has it developed our skills?
So why is the co-design process as important as the final tool and who does it actually benefit? We highlighted a 3 key points in support of co-design when we pitched our idea to mentors, experts and students at Bristol SOSI: Firstly, the co-design process for Duct Tape Uni will facilitate professional development and the sharing of best teaching/training practice as well as the sharing of resources and a space for reflection on teaching practice.
Secondly, it benefits staff and students by enabling them to share resources whilst also allowing students to evaluate and provide feedback on resources. Thirdly, learning and reflection from the co-design process could provide Universities with a framework to engage with wider communities and to develop communities of practice which bridge the gap between Universities and wider community settings.
We reflected that the process of co-design and its participatory, user-led focus within a tech context is intrinsic to the way in which people and organisations aim to work in community contexts and that lots could be learned through encouraging dialogue and the sharing of skills between these two sectors.
There was a choice of hack-streams to attend at the Birmingham event.
The one on design seemed the most appropriate for our project, with its focus on creating design focus, user stories and techniques for sketching wireframes for products.
As part of the session, Mick recorded three interviews with the facilitators. These are available with a Creative Commons BY – SA licence.
London was the last event of the SOSI production process and had a focus on communicating your idea. Mahboobeh prepared a video outlining the Duct Tape University process show below.