ReWork Rehashed

Arjen Vrielink and I write a monthly series titled: Parallax. We both agree on a title for the post and on some other arbitrary restrictions to induce our creative process. For this post we agreed to write about the 37signals book Rework. Each of us will write about the three things in the book that we already do, about three things we will do from now on going forward and about three things that we wish our employers would do from now on. You can read Arjen’s post with the same title here.

Rework
Rework

Jason Fried and David Heinemeier Hansson of 37signals and Ruby on Rails fame have just written a new book titled: Rework (you can download a free PDF excerpt). Reading it gave me an ambivalent feeling: these authors are obviously very good in what they do and they have managed to build a successful business monetizing different parts of their talents, but the book feels like a monetization effort too and the number of words per Euro are very low. Arjen Vrielink has written a quite damning review on Goodreads.

Nonetheless it has some interesting lessons to offer. It has about 100 pieces of advice for people starting their own business or working in a business. Some of the advice I already practice, some advice I will try to practice from now on and I wish that the company I work for would practice some of the advice going forward.

Three chapters about things I already do:

Build an audience (page 170)
Traditional PR and marketing is about going out and trying to reach people. The ubiquity of the Internet allows you to let people come to you instead of the other way around.

When you build an audience, you don’t have to buy people’s attention – they give it to you. This is huge advantage.
So build an audience. Speak, write, blog, tweet, make videos – whatever. Share information that’s valuable and you’ll slowly but surely build a loyal audience. Then when you need to get the word out, the right people will already be listening.

Emulate chefs (page 176)
In this chapter the authors make a case for sharing everything you know, something which is anathema in the business world. They use famous chefs as an analogy. The best chefs share their most valuable recipes in their cookbooks. Why? Because they know that their business as a whole cannot be copied. What better way to show you are an excellent cook, then by sharing your recipes?
I am convinced that there are only benefits to sharing everything I know about educational technology and innovation with anybody who is willing to listen. Doing this is the only way to take part in the incredibly valuable discourse on this topic and taking as much out of it as possible.

Forget about formal education (page 215)
Companies still over-value formal education from. I have personally decided to attend as little formal education as possible from here on further. The key qualities that somebody needs to have are curiosity and the ability to learn. If you combine these two, then there is a whole world out there from which you educate yourself. You don’t have to go and sit in a stuffy classroom and listen to some academic lecturing. Don’t get me wrong: academics are hugely valuable. It is just that you don’t have to join a university to engage with them.

Three chapters about things I will try to do from now on:

Embrace constraints (page 67)
This chapter starts as follows:

“I don’t have enough time/money/people/experience.” Stop whining. Less is a good thing. Constraints are advantages in disguise. Limited resources force you to make do with what you’ve got. There’s no room for waste. And that forces you to be creative.

This is a principle that I am already highly aware of (it is actually embedded in every introduction to any Parallax post on this blog). It is not something I am naturally good in though. I love gadgets and these things often create a lot of extra affordances and thus complexity. I need to tone this down to allow a better focus on things that really matter. First step: “downgrade” my current Ubuntu 10.04 setup which allows me a lot of flexibility (and gives me wobbly windows, that’s not me by the way) to the Ubuntu Netbook edition.

Focus on what won’t change (page 85)
This is probably advice that anybody tasked with working on innovation should heed to. Naturally we like to be focussed on the next big thing. The danger is that you will focus on fashion instead of on substance.

The core of your business should be built around things that won’t change. Things that people are going to want today and ten years from now. Those are the things you should invest.

I will try and use this advice while thinking about the next iteration of our learning landscape. Which aspects are lasting needs and wishes and which are just fads?

Interruption is the enemy of productivity (page 104)
I work in an office with about 10 other colleagues (if everybody is in). During a working day I receive about 50 emails in my work Outlook inbox and have multiple instant messaging conversations. This means that I barely have a couple of minutes without any interruptions. I have to admit that I am probably the cause of many interruptions too, as I constantly share the things I find fascinating or funny with my co-workers.
This is definitely not beneficial for my ability to do work on things that require a bit more concentration and need me to be focussed. It takes a lot of time to write anything which is more than a page of two for example. Usually I can only do it if I work from home and I turn Outlook off. From now on I will try to block a couple of hours every week during which I will sit by myself, turn off my phones, IM and email, refuse to look at Google Reader and just work.
It is as the authors say:

Your day in under siege by interruptions. It’s on you to fight back.

Three chapters about things I wish my employer would do going forward:

Meetings are toxic (page 108, available in the free excerpt)
This one is pretty obvious, but we still have a complete meeting culture. Everybody knows that meetings are not very effective at what their intent is to do and still we have way to many. Some of the reasons the authors give for why meetings are this bad are:

  • They usually convey an abysmally small amount of information per minute
  • They require thorough preparation that most people don’t have time for.
  • They often include at least one moron who inevitably gets his turn to waste everyone’s time with nonsense
  • Meetings procreate. One meeting leads to another meeting leads to another…

If you still need to have a meeting I like their simple rules:

  • Set a timer. When it rings, meeting’s over. Period.
  • Invite as few people as possible.
  • Always have a clear agenda.
  • Begin with a specific problem.
  • Meet at the site of the problem instead of a conference room. Point to real things and suggest real changes.
  • End with a solution and make someone responsible for implementing it.

I think we are especially guilty of inviting too many people to meetings and I would love to meet at the site of a problem instead of a conference room, but am not sure how this is done with IT related issues.

Don’t write it down (page 164)
We spend an inordinate amount of time capturing everything everybody says, needs and wants. We have hundreds of Excel files containing lists of requirements, feature/enhancements requests, issues, etc. We probably spend more time managing these spreadsheets than working on the issues that these spreadsheets are an abstraction of.

There’s no need for a spreadsheet, database, or filing system. The requests that really matter are the ones you’ll hear over and over. After a while, you won’t be able to forget them. Your customers will be your memory. They’ll keep reminding you. They’ll show you which things you truly need to worry about.

Don’t scar on the first cut (page 260)

The second something goes wrong, the natural tendency is to create a policy. “Someone’s wearing shorts!? We need a dress code!” No, you don’t. You just need to tell John not to wear shorts again.

This is how bureaucracies are born according to the authors. They consider policies “organizational scar tissue”. I work for a company that, like most other I am sure, is very scarred. Let’s all stop scarring it more!

I have to admit that a list of three was severely limiting when it came to wishes for my employer. I would have like to have the opportunity to add: Ignore the real world (page 13), Illusions of agreement (page 97), Hire managers of one (page 220) and They’re not thirteen (page 255).

5 Things I Cannot Live Without

Arjen Vrielink and I write a monthly series titled: Parallax. We both agree on a title for the post and on some other arbitrary restrictions to induce our creative process. For this post we agreed to write about things we cannot live without. The restriction is that the things should have a hierarchical relationship where the lowest level of hierarchy is the microprocessor and the highest level is the Internet. Each thing should be described in 100 words. You can read Arjen’s post with the same title here.

Please don’t take the title of this post too literally: yes, even I realise that I will be able to live without these things. Instead consider this a tribute to these five things. Also be aware that the title is not “The 5 Things I Cannot Live Without”, there are many other things that I find way more useful and crucial (think bed, dishwasher, etc.).

So here goes, in a loose hierarchy from local to global:

Microprocessor
CC licensed by Flickr user Stéfan

1. The Microprocessor
What do you know about the microprocessor? If it as much as I used to, then it will be very little! Did you know that the first microprocessors appeared in the early seventies and that they were mostly used for calculators? Did you know that their capacity follows Moore’s law? Did you know that microprocessors not only integrated in computers, but also in cars, toasters, TVs, dishwashers (again!) and most other electrical equipment with some advanced functionality? Finally, did you know the Wikipedia article for Microprocessors needs additional citations and references? Why don’t you get to work and fix it?

2. My iPhone
I don’t think I have yet waxed lyrical about my iPhone. First of all I am late to the party: I have only bought one last December. This is because I resisted buying a closed down Apple product for as long as possible. I really really wanted to buy an Android phone, but all the ones that I tried were seriously less capable than the iPhone. So why is it that much better? Because thought has been put into every single element of the software and hardware design. Nothing is accidental, everything is considered. No other company is there yet.

3. Xs4all
My Internet provider is XS4ALL. There are a couple of reasons why this will be the case for the foreseeable future (even though their price/speed ratio is not competitive):

4. Google Services
Over the last couple of years I have come to rely more and more on Google’s services. So much so that it has become increasingly hard to even list all the Google services that I have an account for or use regularly otherwise. As an excercise I have used this Wikipedia page to list all the products I use regularly (on Ubuntu or iPhone): Chrome, Sketchup, Gears, Calendar, Gmail, Product Search, Reader, Apps, Feedburner, Youtube, OpenSocial, Maps, Aardvark, Alerts, Translate, Groups, Image Search, Scholar, Web search, Analytics, Gapminder, Trends and Zeitgeist. Couldn’t be bothered to link them all: Google them!

5. The Internet
It is a cliché to call the Internet a “game changer”. However, it cannot be denied that it is the most disruptive technology out there. It creates feasibility spaces for social practice (thank you Benkler) and it forces you to rethink traditional ways of doing things. In the field of educational technology for example it has led to, among other things, new course paradigms, an Edupunk movement and deep critiques of the learning function. We cannot fathom what the near future of the Internet will look like as the pace of change is continually accelerating. I cannot wait for it!

P.S. This post was inspired by Techcruch’s Products I Can’t Live Without.

My New Job Title: Innovation Manager Learning Technology

Innovation
Innovation by Flickr user theonlyone, cc-by-nc-nd licensed

My employer has gone through a restructuring exercise in the past couple of months. This means that from today onwards I will have a new job in the company.

I used to be Blended Learning Advisor in the global learning design and development team, now I will be Innovation Manager in the IT department of the Human Resources function.

I will be managing the innovation funnel for learning technology. I am very aware that this is a perilous job! As Machiavelli wrote in The Prince (via Rogers’ Diffusion of Innovations):

There is nothing more difficult to plan, more doubtful of success, nor more dangerous to manage than the creation of a new order of things…. Whenever his enemies have the ability to attack the innovator, they do so with the passion of partisans, while the others defend him sluggishly, so that the innovator and his party alike are vulnerable.

I doubt the writing in this blog will change much (I see this change as a continuation of what I was doing before), but do expect some posts on innovation management pretty soon.

The Proactionary Principle as a Corporate Attitude Towards Technology

Proactionary Principle
Proactionary Principle

Through h+ magazine I encountered the Proactionary Principle. This principle emerged as an alternative to the Precautionary Principle during the Vital Progress Summit in 2004 and is written up by the extropian thinker Max More. Let’s start with the precautionary principle:

The precautionary principle has been used as a means of deciding whether to allow an activity [..] that might have undesirable side-effects on human health or the environment. In practice, that principle is strongly biased against technological progress so vital to the continued survival and well-being of humanity. […] The precautionary principle [..] inherently biases decision making institutions toward the status quo, and reflects a reactive, excessively pessimistic view of technological progress.

The proactionary principle tries to overcome this problem, by nine component principles (liberally reworded from the original article):

Freedom to innovate – our freedom to innovate technologically is so valuable that the burden of proof should be with the nay-sayers.
Objectivity – use a decision process that is objective and make decisions based on science and not on emotions.
Comprehensiveness – consider all reasonable alternative actions.
Openness/Transparency – be open to input from all possible affected parties and keep the decision process transparent.
Simplicity – don’t complicate things unnecessarily.
Triage – give precedence to known risks over hypothetical risks.
Symmetrical treatment – treat technological risks in the same way as natural risks and make sure to fully account for the benefits of technological advances.
Proportionality – only consider restrictive measures if the bad impact of the technological impact is probable and severe, also take into account the benefits of the technology and make sure that all restrictive measures are proportional to the extent of the probable effects.
Prioritize – give priority to risk to human and other intelligent life over risks to other species.

These principles were written with large social and environmental issues in mind. I think some of the philosophy inside these principles can be very useful in a different context: the acceptance and implementation of new technology inside large corporations. Very often these corporations have a very conservative look towards using technology in the workplace. In my field of work, learning technology, this shows itself through an over-focus on integration, excessive rationalizing towards a single platform and only trying out new technology after a long process in which governance has to be negotiated between HR, IT and legal.

Corporations and institutions focus on the problems and risks of new technology without taking full account of the benefits of using it and the opportunity cost of not using it. So here is my resolution: whenever next I am trying to defend the use of some innovative technology I will call on the proactionary principle to try and win the argument.

Let a thousand flowers bloom! By all means, inspect the flowers for signs of infestation and weed as necessary. But don’t cut off the hands of those who spread the seeds of the future.

Learning 2008: Mashups & Widgets are the Future of the LMS

“Mashups & Widgets are the Future of the LMS” was the title of the talk by Bryan Polivka of the Laureate Higher Education Group. This is a group that runs 36 universities over the world. All of these universities have different methodologies, styles and cultures. It is Bryan’s challenge to find solutions that work for all of these universities.

Bryan outlined his problem for us: The learning model is determined by how content connects to students connect to faculty connect to assessment. Their universities are still in the traditional LMS paradigm. This is a problem because we now have all these new things like podcasts, mobile phones, 3D worlds, social sites, etc.

His solution to this problem is to go back to the basics. What is the core of what they want to do with learning technology? According to Bryan they decided that Content – Students – Assessments form the core interaction. This is what should be supported by the LMS, the rest can be flexible and can be set up in multiple ways.

He then went on to highlight the widgetisation of the web (his example was Pageflakes). It used to be the case that the Internet was laid out according to the physical metaphor of the web page: a virtual location. You moved from place to place by switching web pages. That infrastructure is in the process of being broken up: you now have the possibility to pull in data from all over the web and display it in a single location (look at popurls as an example).

An LMS should support this through its architecture. Bryan gave a quick demo of Asiatrac Learning Studio. This LMS is created in Thailand and allows embedding of all of its contents as a widget on another site.

The courses in the Laureate group’s universities are designed through a very solid design process. This allows them to have a lot of high quality content (much video and audio) in their repository of digital assets. The repository allows for tracking and can display its assets in an LMS, but also in a Facebook app or through the iTunes university. All they need is to make sure the student authenticates. The university is now in control of what options they will give their students and they can experiment with having the content only available in Blackboard, or sharing it more widely capitalising on the site that is currently en vogue with their students.

I find this a very interesting strategy and love how Bryan managed to conceptualise his whole presentation very clearly. It would be great for current LMS’ to have more of an architecture that would support its contents being displayed elsewhere. However, I do see two issues that could use some more thought:

  • Content is seen here as broadcasted material (audio, video, interactive e-learning modules, etc.) and not as pedagogically designed activities. Where is the student as a constructor of knowledge in this story? How do you facilitate and moderate student interaction and collaboration?
  • How do you ensure that the learning experience doesn’t become too fragmented? The British Open University has explicitly chosen a strategy in which all the learning takes place inside the LMS (or as they call it: the VLE, compare Niall Sclater). This way they have full control over the design of the learning experience and are able to optimally facilitate their learners with a unified and clear interface.

I would love to explore this topic further. Does anybody have any pointers?