I don’t normally post press releases on this site. Too much corporate speak. But I make an exception in this case. Regular readers will know that for the last three years I have been playing with the possibility of using open data for people to make choices about their future jobs and careers – whether it be moving to a new area to seek work, changing careers or selecting a university or college course. For the past two years we have been working with Warwick University and Raycom on the UK Commission for Education and Skills sponsored LMI for All project. the project has developed a database and APi providing access to a range of Labour Market Information. The work has proved challenging in terms of negotiating access to different data sets, ensuring the data is non disclosive and cleaning the data and in developing the technical infrastructure to provide easy access but at the same time ensuring the security of the data.

The beta vesrion of the APi was released in June this year. Whilst we provide access to a web based data explorer we do not provide apps. Instead the idea os to  Over the autumn we have been upgrading the infrastructure and adding more datasets including the US O*Net data. Whilst we provide access to a web based data explorer we do not provide apps. Instead the idea to encourage third party developers, including careers web sites, to themselves develop web and mobile applications based on the API.  And yesterday UKCES, working together with together with Loudsource have launched a CareerHack competition for apps based on the API.

The press release says:

A NEW competition launched today is calling on developers from across the globe to create an app to help people hack into a new career and win a share of £20,000 in the process.

The CareerHack contest, run by the UK Commission for Employment and Skills (UKCES), is asking developers to find innovative and inspiring ways of using data made available through its LMI for All data site. This is a unique portal containing Labour Market Information (LMI) on employment, skills and future job market predictions, which for the first time makes the different sources of information compatible with each other and available in the same place.

The winner will be given £10,000 to spend as they wish, with £5,000 going to the runner-up.  A special £5,000 prize is available to college students aged 16-24, giving the opportunity for the tech-leaders of tomorrow to showcase their talents and skills.

Michael Davis, Chief Executive of UKCES said:

“We wanted to find a way to allow as many people as possible to benefit from our open data approach to careers and jobs intelligence. An open innovation contest for developers is the perfect solution and we’re delighted that there is a special category for young people studying in college. I’m looking forward to seeing the creativity of app developers from across the world.”

The LMI for All data portal brings together extensive careers intelligence providing a single point of access to the data needed to answer common career questions such as how many people currently work in a particular job, average salaries and the skills needed for certain careers or roles.

While LMI for All information is already being used in various ways by a number of websites, organisers hope the CareerHack contest will open the resource up to creative individuals from around the world – uncovering new and innovate ways to use data to help people map out their future career.

To help illustrate the ways in which the information can be used a Career Trax website has been created by the UKCES – highlighting just one of the ways the LMI for All data can be used.

All entries must be submitted with a brief YouTube video, showcasing how the app works and illustrating its potential. A panel of judges, including representatives from Google and Ubuntu, Further Education institutions and business leaders, will then pick the overall winner next February.

Both individuals and teams are eligible to enter.  You will need to be capable of developing a workable app using LMI for All data. For more information, please visit the contest website at http://careerhack.appchallenge.net

The closing date for entries is 5pm on Friday the 21^st of February 2014.

I have just read an interesting blog post on mobile learning (via the useful ADL mobile learning email list). Donald H Clark says:

Training Magazine’s annual survey of US L&D professionals shows that just 1.5% of training was delivered via mobile devices. That’s right, after about 7 years of hype and discussion we’ve reached 1.5%. That’s not leaping. That’s trench warfare.

And yet of course we use smart devices for learning all the time.

Every time we Google something, check a map for our location, quiz friends and colleagues for the answer to a question we are operating exactly in the sweet spot of L&D: we are learning something, or using a performance aid.

Of course we don’t call it that.

We call it ‘finding something out’, or ‘doing our job’. The learning is almost invisible because it is embedded in our daily lives; it didn’t require us to go somewhere special, to do anything special. It happened at the best possible time – when we had a need for it, and were attuned to be receptive to new information.

I agree. And in the Learning Layers project we are focusing on the everyday learning that take place with mobile devices. Our focus is on Small and Medium Enterprises. Donald Taylor goes on to say:

Rather than concentrating on writing courses, we should be establishing good practice in our organisations for finding information and experts and for sharing information. Where necessary we should be setting up the systems and then letting people get on with using them. We need to use this opportunity to move from being the gatekeepers of knowledge to the facilitators of conversations and learning.

Once more I agree – to an extent. I think the real potential of mobile learning is to link learning that takes place in different contexts. That mean linking formal learning to informal learning. And to link learning that take place in vocational schools, in training centres and in work. But even greater is the possibility to link what we used to call learning (or training) to developing and using knowledge for work. In the past we have called this work process knowledge. In development term this means we need applications which can ;recognise the different contexts (and purposes) for which the mobile device is being used. Whilst there has been considerable academic research on mobile work based learning, there is only limited accounts of practice.

One barrier is the attitude of employers. A recent survey we undertook on over 500 construction apprentices in Germany found that whilst over 50 per cent said they used their mobiles for finding information related to their work or training, only 20 per cent said their employers allowed them to do so. They said that they used the devices in their breaks and lunch time. And in construction I would argue that mobiles are a working tool anyway. So part of  “establishing good practice in our organisations for finding information and experts and for sharing information”, is a task of awareness raising and capacity building with companies for them to realise the potential of mobile technologies for their organisation.

In the first  post of this series of blogs I indicated that we (the ITB team together with our Pontydysgu colleagues and the application partner Bau ABC)  are going through a transitional phase in our fieldwork for the Learning Layers  (LL) project. In the second post I looked back at the shifts of emphasis that had characterised our field visits and workshops in Bau ABC since the first ones in winter to the latest ones before and after the summer holiday break. In both postings I made the point that we had moved from preparatory measures to work in the context of a participative design process. In this posting it is time to consider the implications of such process for the design activities themselves and for the necessary training activities to be planned and carried out.

In principle, there has been an implicit agreement among the LL partner that our project is not a “technology push” project. Neither have we seen our application partners as clients in the supermarket – making choices between ready-made solutions that are on the shelf. Instead, the emphasis has been put on participative co-design processes. Yet, it has been quite a challenge to get such processes take off in the domains and in the locations where we want to carry out pilot activities.

In the case of the Rapid Turbine initiative Graham Attwell has given some insights into the first steps of the design work, into the plans to produce videos (the helmet camera) and into conceptual challenges (“closing the gap”). Much of this design work is still on the way and the demonstrators are yet to come. However, we already know that much of the messages of trainers and apprentices have been taken on board. The important thing is that the Pontydysgu colleagues try to provide real support for completing working and learning tasks without dropping the idea of self-organised learning. Thus, the web tools and the software solutions are there to enhance the learners’ awareness of their own learning. At the end of the exercise, the apprentices should have a picture what they can do, what the cannot do yet and what challenges they can meet in the next phase. This is being discussed between developers, trainers and us, the accompanying researchers.

This has also implications for getting the forthcoming Rapid Turbine designs work together with existing applications and software solutions (such as the Reflect application for the LL project and the software for the assessment procedures in Bau ABC). In this way the support for project-based learning of apprentices would be linked to a tool that enables audio recording of learners’ reports and trainers’ feedback – and to the assessment processes. This, as we understand, will take some time and requires further efforts in the design process.

Parallel to this we have made progress in our discussions, how to give shape for training activities that would support the Rapid Turbine initiative and enhance the general media literacy of trainers and apprentices. Whilst the design work and the discussion on appropriate workshops were firstly taking off as two different things, they seem to be getting closer to each other. It is obvious that the design of the Rapid Turbine gives rise to specific training activities. These can be seen as one part of a wider range of training options to be considered together with the application partners. Here, we are pleased to be able to share experiences with the EU-funded TACCLE projects that have a long experiences with such workshops for teachers to help them produce user-generated web content.

Here I need to stress that both the design work for Rapid Turbine and the development of the training concepts are at an early stage. Yet, we are carrying out this work via joint working meetings in which different parties are actively engaged. This, to me, is already aq good sign and I am looking for the next steps that are taken very soon.

To be continued …

PS. I have written this blog posting just before a series of working meetings with several LL partners and stakeholders that will bring these issues (and wider issues) further. As I will not be present in all these activities and since I will be travelling some time afterwards, it may take some time before we get updates. PK

Acknowledgements. This work is supported by the European Commission under the FP7 project LAYERS (no. 318209), http://www.learning-layers.eu.

Mind the Gap, says Geoff Stead referring to the gap between theory and practice in mobile learning. And it is this gap which is perplexing me as we attempt to develop an App (code named Rapid Turbine) for use by German construction apprentices.

Writing in a blog for last year’s MobiMOOC Geoff says:

There are a few academic frameworks that can be useful in evaluating, and reflecting on m-learning:

1. Laurillard’s Conversational framework (2002) – showing the different roles that technology can play in the process
2. Park’s Pedagogical Framework for Mobile Learning (2011) – offering a simple matrix to map the transactional and/or social closeness of a learning intervention
3. Koole’s Model for Framing Mobile Learning (FRAME) – 2009 – showing how the mobile learning is an interaction between the technology, the learner and the context.

FRAME model

The one that most connects with my own thinking is FRAME, because it is quite clear that you any theory about m-learning needs to engage with the technology itself (the device), AND the learner (who they are, what they want), AND their social context.

The reason the definition works for me is exactly the reason why I suspect m-learning has proved so problematic to define precisely. It just isn’t one thing. There may well be one core idea in the middle, but this is heavily influenced by factors that are different in different contexts.

Here are some examples, and contrasting ideas:

• while m-learning at work might be about performance support tools, and access to small nuggets of information; m-learning in the classroom might be more about exploring ideas together, and collaborating on a project
• while m-learning on a field trip might be exploring your environment (GPS / augmented reality / mapping / camera), m-learning in a lecture theatre might be about taking notes, and looking up references.
• while BYOD m-learning might be about sharing critical information via any device; a specific iPad activity will be rely on a specific app on a specific, named device

Folks, these are ALL m-learning, but because the circles in the Venn Diagram are filled with different questions, the resulting answer is different.

The core idea behind Rapid Turbine is that it brings teogther learning in different contexts – in the vocational school, in the industry training centre and in the workplace

Thus the pedagogic design of the App needs to be ‘mutable; to reflect these different designs. In the vocational school learning may be more formal and the app needs to scaffold and support apprentices in linking that formal knowledge to the work based learning gained in practice.

In the training centre the use of the App is focused on gaining practical work based knowledge and the presentation of learning materials and learning support needs to reflect that use. In the workplace, the App may be more needed to provide information and knowledge based on the other settings.

The different dimensions of the App should adapt to these different contexts of use. Collaboration, communication and data sharing will vary in each context of use. Thus a use case based on a single scenario or context will only provide us limited help.

Perhaps a dimension or scale lacking in these frameworks is that of depth and breadth, which can be seen as key in linking both the different kinds of knowledge and learning and the different resources which support scaffolded learning.

If we take a particular work task as the basis for an application (as Rapid Turbine does which is why it is high in authenticity and situatedness) then at some points apprentices will want to progress in more depth which perhaps brings in more theoretical learning and in other cases with more breadth which provides more contextual links to other work tasks (and arguably to more holistic work tasks).

The App needs to overcome not just a gap between theory and practice in mobile learning design but the gap between theory and practice in skilled construction work and the gap between informal and formal learning. And that is not easy

by Graham Attwell, Owen Gray and Martina Luebbing

We wrote in an earlier post about the Rapid Turbine app which we are developing through the Learning Layers project. Rapid Turbine is a prototype demonstrator, designed to show the potential of mobile devices to support learning by apprentices in the north German construction industry training centre, Bau ABC. Apprentices at Bau ABC learn through undertaking a series of practical projects, detailed in a paper based White Folder.

The task sheets are used both outlining the tasks to be undertaken, the tools required, materials and health and safety concerns etc and for recording learning. Through developing a mobile app it is intended to make updating 0of tasks easier but most importantly to allow closer links between the learning apprentices undertake in the training centre, with their courses in vocational schools and with their work undertaken on construction sites.

The task we are developing for the prototype is called Rohrleitungsbau (pipe and sewer laying). Our main aims are to test the pedagogic approach and design of the app and to develop a work flow so that trainers can themselves produce mobile learning materials.

One of the key aims for the Learning Layers project is to encourage the development of peer produced learning materials. Peers might be apprentices themselves or trainers in the training centres. We are aware that a major barrier to the take up of technology for learning in Small and Medium Enterprises is the high cost of buying or commissioning the production of learning materials. Furthermore we are aware of the need for vocational expertise in the development of these learning materials, expertise we do not have as researchers and developers.

Although it is beginning to change, most traditional e-learning has been very heavily text dependent. This is not really suited to practical and wok based learning, especially using the mobile devices which can allow apprentices to access learning materials directly in the training centre or workplace.

Therefore we are keen to videos into the app related to the different tasks being undertaken. Once more, fairly obviously the trainers are the best people to make these videos. Originally we had thought of going to Bau ABC and filming these videos ourselves. But this would have been very time consuming and is not really sustainable. Our next thought was to use wearable video devices and we experimented with prototype smart glasses with video capacity. However, the quality was not great and the controls were difficult to use.

So our latest solution is to use an Go Pro camera, attached to a construction site safety helmet. The cameras are reasonably easy to use and importantly, having originally been designed for recording extreme sports,  are extremely rugged, and with the cover fitted, water proof and dust proof. They can also be controlled through a Wireless based phone app. We need more work to find out what makes a good short learning video to be accessed on a mobile device. We’re starting out trying to make a series of handy tips, based one each task, but will review this as we go. And we are encouraged that some of the trainers have already been making their own videos using an ipad. I suspect they will have more ideas than us.

The helmet mounted camera will be delivered to the training centre tomorrow and as soon as we have some videos we will shared them on this site.

I guess many of you are enjoying your holidays now. Here at Pontydysgu we’re ploughing ahead with our summer project, codenamed Rapid Turbine. Rapid Turbine is a spin out from the Learning layers project design group called Sharing Turbine.

The design idea has followed extensive discussion with Bau ABC, a large training organisation for the building industry in Lower Saxony and Bremen in north Germany. The apprenticeship system in Germany is based on a Dual System, with apprentices learning both within companies and within vocational schools. However in the construction trade there are three venues for learning, the company, the vocational school and the training centres.

Training in the training centre is organised around practical tasks which may take from one to three or four days to complete. The tasks are documented in something called the White Folder which is also used for reporting on work. This has a number fo problems – it takes time to update content and despite the use of colour photocopying has limitations in terms of media. Perhaps the biggest drawback is teh lack of portability, thus limiting the use of learning materials or of apprentices/ past learning in the company or the vocational school.

Thus the idea of Sharing Turbine is to produce a mobile app which can provide interactivity whilst undertaking workplace learning tasks. But the more we have looked at developing such an app – the more daunting it seems. Wireframes and diagrams have multiplied, with multiple use cases and endless meetings.

So Rapid Turbine has been designed as a rapid application project to get something out. And my thinking is until we have produced something, we will not really understand what we are doing. So we have taken just one task – Trench digging and pipe installation- and are trying to produce an app.

So far we have hit two big issues. The first is the pedagogic approach. We want to go further than just producing information on how to do the task – even with nice video. The mobile app should stimulate not just interactivity  but activity in the work process. And of course there are many real life artefacts which are used in that activity.

The second issue is establishing a workflow. Ultimately our aim is that our colleagues from Bau ABC will be able to produce the learning materials themselves. So far our workflow is fourfold. Firstly we are producing wireframes. Although we have used Balsamic in teh past, at the moment our designers, Owen Gray and Martina Luebbing are preferring to work on flipchart paper. then we need to generate the HTML, CSS, Javascrtipt etc. for the app. This we plan to do using Twitter Bootstrap and an html editor. And then we will use the Tribal m-Learning program to produce the App.

So far so good. We are still at the wireframe stage. I will update you on how it all goes.

plugin by rob

We are spending a lot of time at the moment designing a mobile e-learning application for apprentices in the construction industry in Germany. There are many issues – but we seem to be getting on top of the technology. Much more difficult is the pedagogic approach. I like this slideshow by Geoff Stead, recently joined Qualcomm to lead their m-learning initiatives. He says there is no single, correct answer.  The reality is complex, messy and diverse!

Reflect is a free Android App for phones and tablets developed by students from Hochschule Karlsruhe (Karlsruhe University of Applied Sciences) for Pontydysgu as part of the Learning Layers Project.

The app is presently in closed beta but will be open for use by everyone in August 2013. If you would like more details please email graham10 [at] mac [dot] com.

We demoed the App at a workshop jointly hosted by the UK National Health Service developers network Handi and the Learning Layers project in Bradford last month and share here the report we produced on the feedback.

Aim:

• To elicit user feedback from developers and healthcare professionals
• Evaluate potential of the App
  

Background and Key Idea:

The original idea came from talking with a doctor in the UK at a Learning layers workshop. He explained how little time he had to reflect on his ongoing learning. The most time he had, he told us, was when he was in his car between meetings and visiting patients.

The Reflect App was originally designed to make the recording of learning, both formal and informal, easy.

The App is voice controlled and translates voice recordings into text.

Users can build a ‘stack’ of questions by typing them into a simple form on a web interface. Then they can use an Android Phone App which reads them the questions. They can skip to the next question, resubmit their answer or ask for help. The answers are automatically converted to text and can be downloaded to their own computer or tablet.

What we hoped to learn:

We were concerned to get feedback about:

a)    The general idea and potential interest in the app

b)    Usability and UI

c)    Ideas for further development

Feedback from developers and healthcare professionals:

Negative feedback:

• GPs are concerned about the level of security, regarding sensitive data.
• Developers were concerned about quality of voice recognition and difficulties with background noise

Questions that were raised:

• What is the maximum recording time?
• Where does the voice recognition processing take place?
• Is an off-line mode possible?
• could Reflect be integrated into other systems (e.g. NHS)
• What are business models for future sustainability?

Positive feedback and further potential:

• Reflect could be a good tool to report back the first impressions on meetings
• A future approach could be to develop an APi to allow use with other systems
• Domains for groups to work together
• Reflect could be used for research purposes e.g surveys
• Learning tasks could be created for students (microanalysis)
• Link to Evernote
• Reflect provides strong support for scaffolding learning

Suggested Business Models:

• Advertising
• Premium domain accounts
• Develop market ins tacks of questions for different occupations / domain and license under revenue sharing model

What Next?

We are continuing to test the App on a closed beta and are working on an open beta release for Reflect.

We are hoping to get further developer support for:

a)    Exploring off line potential

b)    Developing a API

c)    Porting to iOS

Evaluation of the activity:

From our point of view we were delighted with the critical and positive feedback. We especially noted the concern from external developers that there is a strong business model and suggest that this should be noted by other Learning layers development teams / design groups.

The workshop was very well organised. Whilst it would have been useful to have more health care professionals, the opportunity for engagement with so many developers and with commercial companies was extremely valuable.

In my previous post I indicated that our current phase of fieldwork is preparing the grounds for participative co-design processes “for the users, with the users and by the users”. So far, we have had quite a lot of activities with the training centre Bau ABC and made also a lot of experiences with different workshops. Here, the blessing for us has been that we have had a chance to have joint workshops with groups of apprentices (during their stay at the centre) and with full-time trainers (at the time slots when apprentices have been working independently with their projects). Below some remarks on our workshops and on our learning experiences about their ways of making the workshops their events in which they address their own issues, concerns and initiatives.

Firstly, on the workshop concepts with which we worked: We firstly had conversational workshops with one group of apprentices (from different trades) in the morning and with a group of full-time trainers (Lehrwerkmeister) in the initial training plus the coordinator of continuing vocational training programmes. These workshops were supported by some pre-given guiding questions (Leitfragen) but they were run as relatively free conversation to let the participants address their issues with their own accents and their own voice. As a result, the apprentices spoke very freely of what they saw a needs and possibilities for improvement regarding the training in the centre (vis-a-vis advanced practice in the companies). They also emphasised their interest to have joint projects with apprentices from  neighbouring trades. The trainers gave positive comments on the views expressed by apprentices – however, they drew attention to rather inflexible boundary conditions for accommodating the apprentices’ training periods in the centre. Thus, there is very little room for manoeuvre for meeting the wishes of apprentices re joint projects or more flexible timing of periods in companies and in the centre. In addition, the trainers started giving thoughts, how they could use digital media and web appsa more effectively in informing themselves of new developments in the trade and on advanced practice in companies. Here, it seemed that something that was discussed in initial training was already in practice in the continuing vocational training activities.

In the next phase we organised a storyboard workshop that was based on group work to make storyboards of exemplary working days of apprentices (in the morning) and trainers (in the afternoon). The two parallel groups of apprentices had different tasks: one was invited to portray a day in the training centre whilst the other was asked to portray a day in the company and in the construction site. The group that worked with a day in the centre presented a spatial journey with drawings of different locations  at the Bau ABC sites and only after completing this started to give thoughts on eventual problems and how they could be taken into account in the phase of giving instructions. The group that focused on working at construction site portrayed the work flow (and the daily journey) from the company office to the site, setting the site and carrying through the process (drilling the holes for the well to be built) and in completing the task. Here, the apprentices drew attention to eventual obstacles and needs to star again or to give up if no water is found. Thus, they highlighted key problems in the work process – in which however the availability of web tools made very little difference. At the end of this session the joint plenary discussion started top trigger ideas of new apps to extend the learning effect and to draw attention to good practice  (e.g. the Maurer-App) and comments on the (limited) usability of existing apps.

The trainers gave very positive comments on the storyboards of apprentices and gave some thoughts of the possible usability of existing apps as a basis for the proposed Maurer-App. In their own group work phase they presented two parallel storyboards of trainers work at the centre. One story focused on a relatively homogeneous group of apprentices in the initial training whilst the other illustrated the growing complexity when there are apprentices from different phases of their training and eventual visiting groups in continuing training (with visiting trainers) to be supported at the same time. Altogether, the storyboards drew much more attention to the complex social and organisational processes to be managed alongside the key training functions  (instruction, supervision, monitoring, assessing and giving feedback). In the plenary sessions a lot of thoughts were given on the possibilities to offload the trainers with digital solutions in the assessment and in giving feedback. A major issue was the access to norms, standards and regulations in which context new copyright problems had emerged. As a result, a list of several design ideas and issues was drafted to be included into the workshop report (to take into account the issues arising from initial and continuing training).

Here I have emphasised the workshop dynamics rather than particular ‘results’ to be listed as apps or solutions that would have attracted most attention. In the preparation phase our colleagues suggested different techniques to get feedback on particular ‘use cases’ or wireframes drafted on the drawing boards elsewhere. As I have illustrated it above, when the users got control of their workshops, they addressed concerns, how to improve their working and learning processes on the whole. When getting their messages into discussion we then could use  some time to illustrate some of the use cases and emerging wireframes as possible responses to their concerns. In this context the powerpoint slides and the presentation of Martin Bachl (Hochschule Karlsruhe) worked very well.

As I understand it, we are going through similar collaborative learning processes as the earlier Work and Technology projects that couldn’t successfully transplant new technologies into companies as ‘gifts that fall  from Mt Olympus that are parachuted upon users’ but had to discover the possible needs for innovations and benefits for users in iterative processes that took their own time. Yet, after these experiences we have the feeling the we are making progress.

To be continued …

Acknowledgements. This work is supported by the European Commission under the FP7 project LAYERS (no. 318209), http://www.learning-layers.eu.