Mobile learning in the classroom – Mark Howell/Meru. Developments in the school sector. Mobile taking over. Technology permeates the very fabric of the school – it’s in the DNA (Primary School). Smartphone & tablet installed base will overtake PCs this calendar year. Informational ubiquity. Multiple automatically WIFI connected devices per student – will HE WIFI cope? Martini learning – again – how many more times? And so, what? Apparently things will happen that we weren’t expecting. Heavens above.
Idea Street – creating a culture of change – David Cotterill, Cabinet Office. Deputy Director, IT Reform Government Digital Service. Idea Street -project at DWP. 100,000 staff – innovation team with 7 people. 3 great myths about innovation: don’t have time; don’t have resources; don’t have culture. But really all about prioritisation – culture key. Sounds familiar! Drucker: the culture ate the strategy. HR: will help, make innovation an objective in everybody’s performance plans – yeah, that’ll work. Economic and social bargains can be contradictory. Game dynamics are very influential – appointment dynamics, have to be there at certain times to do certain things, Farmville – more users than Twitter, have to obey the game. (Seth Priebatsch). Next dynamic – influence & status, desperate to be Level 10 etc. School is a game, just not very well designed – why not use game dynamics explicitly. Progession dynamic – like LinkedIn, only 85% complete. Great stuff. Another dynamic – voyage of communal discovery. Crowdsourcing approach to promoting innovation. Similar to OpenLivin – create buzz, vote, team etc – idea owners build the team to take the idea forward. Ideas marketplace. Final: people like doing fun stuff; the unit of delivery is the team; start with user needs.
Transformation of public sector services – Mike Bracken/Cabinet Office. Executive Director for Digital Government Digital Service. Spending a lot of time trying to get IT out of the way. What’s exciting is the users, not the IT. Digital by default. Fix publishing. Fix transactions. Go wholesale. Build services like Google & Amazon – iterative, agile, user-focused. How do we usually do it? Start with policy, requirements, development, end with user needs. Now: start with user needs, get it out there quickly – otherwise the world changes while the users are waiting. But: requires a level of user engagement/effort that we don’t usually get? Objective: digital services so good that people prefer to use them. Working on stuff that matters – IT doesn’t, user needs do.