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).

Summary of and Reflections on “Learning in 3D”, Chapter 1

The first chapter of Learning in 3D titled “Here Comes the Immersive Internet” consists of three parts. The first part gives an overview of the three “Webvolution Waves”, the second part focuses on four convergence points that all lead to a next-generation Immersive Internet architecture and the chapter closes with a short analysis of what this might mean for the enterprise.

Three Webvolution Waves
The web browser arrived in 1993 and was used to connect “to” the information that was available on the web. The web grew fast and businesses helping people with getting on the web (Internet Service Providers like AOL) or finding the information on the web (e.g. Yahoo and Google) where the clear winners of the first wave.

In the early noughties companies like Google and Amazon truly started to leverage “the aggregated behaviour of many users to differentiate their [..] offerings”. This insight combined with the increased ability of people to participate in the web by uploading their own content became the core of “Web 2.0“, characterised by the authors as connecting “through“.

Allegedly the next phase of the web will be about connecting “within” and immersive 3D  experiences will be a fundamental part of that. Kapp and O’Driscoll give a couple of examples, mainly from MMORPGs. In games like World of Warcraft people come together in a (semi-) three-dimensional worlds and collaborate as teams to battle other team. There is real economic value in these games as the practice of gold farming clearly shows.

The description of this third phase obviously has much less clarity than the first two phases: we are now in this “webvolution” and we are not sure which of these points are the most salient aspects. I don’t think that “immersiveness” is the only candidate to be at the heart of the next generation of web technology. It could still be that the semantic web will have more impact on social practice. Or alternatively it could the social graph which will be the all pervasive aspect of the new web. In that latter case Facebook seems to be in prime position to be the next Google with their recently announced Graph API. I am sure these trends reinforce each other, but I am not sure that 3-dimensionality will be as important as this book seems to think it will be.

Four Convergence Points
The authors think there are four current technologies that are integrating with each other, creating four convergence points in the process. All these points converge to the immersive Internet. I don’t want to steal their diagram (you can find it on page 18 of the book), so I’ll describe it here.

  • 2D synchronous learning and knowledge sharing spaces are combining to create immediate networked virtual spaces.
  • Knowledge sharing spaces and web 2.0 technologies are integrating into intuitive dynamic knowledge discovery.
  • Web 2.0 technologies and virtual world technologies are coming together in interactive 3D social networking.
  • Virtual world technologies and 2D synchronous learning together can create immersive 3D learning experiences.

I really like this model as it provides four clear spaces in which you could look at technology. The problem for me is that in my job I do indeed see immediate networked virtual space and am starting to see intuitive dynamic knowledge discovery, but I do not see the two 3D convergence points yet. This could be my lack of knowledge and experience of what is out there, in which case I would gladly see some examples and demonstrations!

What does this mean for business?
The web has had a profound impact on the way we do business and organise ourselves. I want  to address the points that I thought most interesting by quoting three passages from the book. The first quote is about information abundance and the subversion of hierarchy by networks:

As the Internet continues to pervade society, the scarcity paradigm that undergirds most modern economic theory is being challenged. Unlike currency, information is non-appropriable, which essentially means that it can be shared without being given away. Today, information no longer moves in one direction, from the top to the bottom or from teacher to student. Instead, it has a social life all its own.

The second quote is about how the web allows people to come together without needing formal organisations to do it:

As communication costs have decreased and the quality of web-based interactivity has increased, communities of co-creators no longer need to rely on a formal organization to become organized. Rather than employing an enterprise infrastructure to plan ahead of time, they leverage the pervasive and immersive affordances of the web to coordinate their activities in real time.

The above is one of the most important points (and actually the subtitle) of Clay Shirky’s wonderful Here Comes Everybody and I think this reading group is an example of how this can work.

And finally a quote about how companies have to innovate faster and how this affects the role of the learning function in the enterprise:

For change to occur it is a precondition that learning take place. [..] In the case of the centralize hierarchies, [organizations] must unlearn all that brought it success in the pre-webvolution era and quickly learn how to leverage the Immersive Internet to reconfigure its resources and capabilities to achieve sustainable competitive advantage in a world gone web. […] The perennial challenge of the learning function within the enterprise is to ensure that human capital investment yields a workforce capable of innovating faster than the competition and work processes that allow the organization to adapt to changes with minimal disruption. This suggests that the learning function should become increasingly strategic to the enterprise.

The last sentence is the step-up to the rest of the book. I am looking forward to it!

Questions for discussion
Please participate in these two polls:

[polldaddy poll=3107820]

[polldaddy poll=3107841]

In the teleconference I would like to discuss the following questions:

  • In what way has your company or organisation changed because of the webvolution? How has this affected the learning function?
  • What are your thoughts about the convergence to an immersive web? Do you have examples of how 2D synchronous learning and web 2.0 combine with 3D virtual worlds?
  • What will change when we make the shift from a scarcity paradigm to an abundance paradigm for information.

We will discuss these questions in our weekly teleconference on Monday April 26th at 15:30 CET. Please contact me if you want to call in and don’t have the dial in details.

Learning in 3D: Please Join My Reading Group

Learning in 3D
Learning in 3D

My company is piloting serious gaming in the learning domain using an immersive 3D environment based on the Unreal engine. We are on the cusp of developing a game around hazard recognition scenarios that are based on real life experiences. Because of this I am reading up on serious gaming and game design in general. After finishing the brilliant The Art of Game Design by Jesse Schell (more about that book in a later post), I now want to tackle Learning in 3D, Adding a New Dimension to Enterprise Learning and Collaboration by Kapp and O’Driscoll.

I have decided to start a reading group which will read the ten chapters of the book in ten weeks (there is a preview of the chapters here). We will use blogs, Twitter, Delicious and a weekly teleconference to communicate around the book.

So how will this work?

Goal
The book provides principles for architecting 3D learning experiences (including a maturity model for immersive technologies) and has lessons on and examples of implementations in enterprise situations. The goal of the reading group is to actively internalise these lessons and see how they can be applied in our own organisation(s).

Participants
As I want this reading group to impact the learning function in my own organisation I intend for about 50% of the participants to work for Shell and for the rest to come from my network outside of Shell. The minimum number of participants is 5 (doing two chapters each) and the maximum is 40 (four people per chapter and incidentally the limit of our teleconferencing solution). Everybody will have to acquire their own copy of the book. (I used the Book Depository to buy this book, as they have free shipping, note that I will earn a small referral fee if you click this link and then buy the book).

Process
The reading group will have a weekly rhythm with a particular chapter of the book as the focus of attention. The following activities will happen every week:

  • One or more people will be assigned to write a summary of the chapter on their blog (if they don’t have a blog, they email me the summary and I will publish it on this blog). The summary ends with at least one multiple choice poll and a discussion question/proposition, both used as input for the teleconference.
  • All reading group participants will be tweeting questions and comments about the book (using a designated hashtag, see below).
  • Each participant will try to add at least one interesting link to Delicious (again with a hashtag) that relates to the chapter of that week.
  • At the end of the week (actually on a Monday), there is a teleconference where the summarisers for that week lead a discussion about the chapter, using the poll and the discussion question/proposition as input.

Hashtag and aggregation
All Delicious URLs, blogposts and Tweets should be tagged with the #Lin3DRG hash tag (stands for: Learning in 3D Reading Group). This will allow me to try some smart ways of aggregating and displaying the data using things like Yahoo Pipes or Downes’ gRSShopper. I promise to write another post on my aggregation strategies.

When and where?
It is going to be a virtual affair, co-creating on the web. We will start reading on April 19th, will have our first weekly 30 minute teleconference on Monday April 26th at 15:30 Amsterdam time and will close out on June 28th (so we will have 10 telcons on ten consecutive Mondays at the same time, it is not a problem if you miss one, we will record them).

Do  you want to join the reading group? Then please fill out a comment with your name, email address, blog URL (not required) and any comments or questions you might have at the bottom of this post. I will get back to you with your assigned chapter(s), some more information on the process and the call in details for the teleconference. You can put your name down until Monday April 19th.

I am really looking forward to it!

Book Review: Moodle 1.9 Teaching Techniques

Moodle 1.9 Teaching Techniques
Moodle 1.9 Teaching Techniques

Just over a year ago I reviewed four Moodle books published by Packt Publishing. Since then, a lot of new Moodle titles have been added to their catalogue. Richard Dias, Marketing Research Executive at Packt, has kindly sent me a copy of one of these new titles for review: Moodle 1.9 Teaching Techniques by William Rice and Susan Smith Nash, first published in January 2010.

William Rice has already published a couple of books with Packt. This book seems to be an effort by Susan Smith Nash to  build on an earlier version of the book by Rice. She adds some learning theory and instructional design essentials to the earlier text.

The fact that this is an update of a much older book, doesn’t work very well. Let me share some examples of where it goes wrong:

  • Chapter 2 used to be called “Forum Solutions”, now it has been retitled to “Instructional Material”. This is weird: Moodle’s core functionality and strongest pedagogical tool is first introduced as a way to clearly display course information and structure. Then on page 25 there is a paragraph titled “Creating a Separate Group for Each Student”. The context from the earlier book (you might want to do this to create private conversations with students) is omitted, making it a confusing set of pages.
  • Chapter 4 has a section that explains how you can exclude quiz grades from a particular quiz in the grade book. The screenshots and explanations are taken from an earlier version of Moodle and do not relate to Moodle 1.9. Moodle 1.9 has a completely different grade book (and has been released since March 2008). It is unforgivable for a book that is published in 2010 to get this wrong. I don’t understand how the reviewer missed this. Hopefully a corrected version will be published as an erratum.
  • The introduction to the book explains that  a basic level of Moodle understanding is assumed for the reader as it wants to focus on learning theory. However it then spends more than 5 (of its 193) pages on explaining what an IP address is and how it can be used to restrict access to a quiz. It gets the Linux part on how to see your IP address wrong (another one for the errata).

The book doesn’t really make optimal use of the new and advanced functionality that Moodle 1.9 has on offer. Two examples:

  • The concept of “groups” is used in the book in some descriptions of course activities (although not enough to call for its own spot in the index), but the concept of “groupings” isn’t mentioned anywhere. If I were to teach a course with Moodle tomorrow, I would definitely use this functionality as it allows you to be much more flexible in your course design.
  • Ever since Moodle 1.7 it has been possible to play with roles and capabilities in Moodle. That functionality is relatively hard to understand and needed some maturation. It is much more usable now in Moodle 1.9. This functionality is only used once in the book (during the discussion on forums) and isn’t explained well enough to my taste.

Does the book have some valuable things to offer? It is not all bad:

  • Some of the introductions to learning concepts are theories are good starting points for further exploration. For example, I liked the reference to Bruner’s “scaffolding” concept and spent some time reading the Wikipedia article on instructional scaffolding.
  • The pages on basic chat etiquette and wiki etiquette are quite useful. They describe rules you can agree on with your students to make the online learning process more pleasurable.
  • The ways of using the choice activity have been slightly expanded compared to the earlier version of the book.
  • The last chapter has a nice example of a capstone project assignment that you could adapt for your own teaching. To use the workshop module as the basis for this project assignment is a bit risky, as I would not recommend anybody to use the workshop module in its current state (Moodle 2.0 should solve that problem).

All in all I would not recommend anybody to get this book. If you have 30 euros to spend on a Moodle book (this book isn’t cheap!) choose one of the ones I recommend here. If you have a basic understanding of Moodle and are looking for generalised teaching techniques for online courses you are much better served by Gilly Salmon‘s work on e-moderation (see E-moderating and E-tivities).

Hopefully I can be more enthusiastic about the next Packt title I get to review…

The Influence of a Workspace On Performance

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 influence of a workspace on performance. The discussion should build on the ideas set forth in a previous parallax post Planning your Career or the Boundary between Private and Professional life. You can read Arjen’s post with the same title here.

I have written before about the direct influence of our environment on our behaviour. I think learning professionals can learn a lot from people like Hans Monderman. This traffic engineer looked with a fresh eye at how people and technology relate to each other. This led to some ground-breaking traffic concepts (quote from Wikipedia):

His most famous design approach is Shared Space, also known as designing for negotiation or Shared Streets. Monderman found that the traffic efficiency and safety of urban streets improved when the street and surrounding public space was redesigned to encourage each person to negotiate their movement directly with others. Shared Space designs typically call for removing regulatory traffic control features (such as kerbs, lane markings, signs and lights) and replacing intersections with roundabouts.

The Architecture of Happiness
The Architecture of Happiness

Our surroundings change who we are. I was therefore delighted to learn that Alain de Botton has written a book about exactly this topic, applying it to the architectural domain: The Architecture of Happiness. In it he writes about one of my favourite architectural topics: Le Corbusier and his plans for the Radiant City:

By building upwards, two problems would be resolved at a stroke: overcrowding and urban sprawl. With room enough for everyone in towers, there would be no need for cities to spread outwards and devour the countryside in the process. ‘We must eliminate the suburbs,’ recommend Le Corbusier, whose objection was as much based on his hatred of what he took to be the narrow mental outlook of suburbanites as on the aesthetics of their picket-fenced villas. In the new kind of city, the pleasures of the town would be available to all. Despite a population density of 1,000 per hectare, everyone would be comfortably housed. Even the concierge would have his own study, added Le Corbusier.

There would be ample green space as well, as up to 50 per cent of urban land would be devoted to parks – for, as the architect put it, ‘the sports ground must be at the door of the house.’ What was more, the new city would not merely have parks; it would itself be a vast park, with large towers dotted among the trees. On the roofs of the apartment blocks, there would be games of tennis, and sunbathing on the shores of the artificial beaches.

Simultaneously, Le Corbusier planned to abolish the city street: ‘Our streets no longer work. Streets are an obsolete notion. There ought not to be such things as streets; we have to create something that will replace them.’ He witheringly pointed out that the design of Paris’s street plan dated from the middle of the sixteenth century, when ‘the only wheeled traffic consisted of two vehicles, the Queen’s coach and that of the Princess Diane.’ He resented the fact that the legitimate demands of both cars and people were constantly and needlessly compromised, and he therefore recommended that the two henceforth be separated. In the new city, people would have footpaths all to themselves, winding through woods and forests (‘No pedestrian will ever meet an automobile, ever!’), while cars would enjoy massive and dedicated motorways, with smooth, curving interchanges, thus guaranteeing that no driver would ever have to slow down for the sake of a pedestrian. [..]

The division of cars and people was but one element in Le Corbusier’s plan for a thoroughgoing reorganisation of the life in the new city. All functions would now be untangled. There would no longer be factories, for example, in the middle of residential areas, thus no more forging of iron while children were trying to sleep nearby.

This rational (at first sight) design for cities has an intuitive appeal. It is therefore not surprising that many municipalities have created whole neighbourhoods according to Le Corbusier’s principles. I have worked in one of these neighbourhoods for many years: the Bijlmer. The Bijlmer can be considered an urban design failure. Its giant apartment flats have mostly been demolished or rebuilt within the first 30 years of their existence.

Urban planners could (should?) have known better. Jane Jacobs wrote The Death and Life of Great American Cities in 1961, delivering a damning critique of Le Corbusier’s idea of separating the different functions of a city. De Botton writes it down very elegantly too (apologies for another long quote, I think they are worthwhile though!):

Ironically, what Le Corbusier’s dreams helped to generate were the dystopian housing estates that now ring historic Paris, the waste lands from which tourist avert their eyes in confused horror and disbelief on their way into the city. To take an overland train to the most violent and degraded of these places is to realise all that Le Corbusier forgot about architecture and, in a wider sense, about human nature.

For example, he forgot how tricky it is when just a few of one’s 2,699 neighbours decide to throw a party or buy a handgun. He forgot how drab reinforced concrete can seem under a grey sky. He forgot how awkward it is when someone lights a fire in the lift and home is on the fourty-fourth floor. He forgot, too, that while there is much to have about slums, one things we don’t mind about them is their street plan. We appreciate buildings which form continuous lines around us and make us feel as safe in the open air as we do in a room. There is something enervating about a landscape neither predominantly free of buildings nor tightly compacted, but littered with towers distributed without respect for edges or lines, a landscape which denies us the true pleasures of both nature and urbanisation. And because such an environment is uncomfortable, there is always a greater risk that people will respond abusively to it, that they will come to the ragged patches of earth between their towers and urinate on tyres, burn cars, inject drugs – and express all the darkest sides of their nature against which the scenery can mount no protest.

In his haste to distinguish cars from pedestrians, Le Corbusier also lost sight of the curious codependence of these two apparently antithetical forces. He forgot that without pedestrians to slow them down, cars are apt to go too fast and kill their drivers, and that without the eyes of cars on them, pedestrians can feel vulnerable and isolated. We admire New York precisely because the traffic and crowds have been coerced into a difficult but fruitful alliance.

A city laid out on apparently rational grounds, where different specialised facilities (the houses, the shopping centre, the library) are separated from one another across a vast terrain connected by motorways, deprives its inhabitants of the pleasure of incidental discoveries and presupposes that we march from place to place with a sense of unflagging purpose. But whereas we may leave the house with the ostensible object of consulting a book in a library, we may nevertheless be delighted on the way by the sight of the fishmonger laying out his startled, bug-eyed catch on sheets of ice, by workmen, hoisting patterned sofas into apartment blocks, by leaves opening their tender green palms to the spring sunshine, or by a girl with chestnut hair and glasses reading a book at the bus stop.

The addition of shops and offices adds a degree of excitement to otherwise inert, dormitory areas. Contact, even of the most casual kind, with commercial enterprises gives us a transfusion of an energy we are not always capable of producing ourselves. Waking up isolated and confused at three in the morning, we can look out of the window and draw solace from the blinking neon signs in a storefront across the road, advertising bottled beer or twenty-four-hour pizza and, in their peculiar way, evoking a comforting human presence through the paranoid early hours.

All of this, Le Corbusier forgot – as architects often will.

This is a very long pre-amble to the topic at hand: how the workspace can affect performance.

Shell's Learning Centre in Rijswijk
Shell's Learning Centre in Rijswijk

Most of my time I work in an office in Rijswijk that has been designed by David Leon. The longer I work there, the more impressed I have become by the attention to detail of its indoor design. The designers obviously have a very deep understanding of how people work nowadays and have created a work environment that enables people to get the best out of their day. How is this done?

  • The office space is open (no cubicles), but permanent storage areas and desks have been placed in such a way that privacy is ensured.
  • There are a multitude of different flexible rooms available: cockpits for one person (ideal for when you need to concentrate on getting something done), small rooms with two low chairs (great for having an informal chat), rooms with a table and a cornered bench (excellent for small brainstorms) and bigger rooms with oval meeting tables (sometimes with video calling facility). We even have rooms with wacky furniture to get the creativity going.
  • Connectivity in each room and at each desk. There are docking stations everywhere and each room has a speaker phone.
  • There is a lot of transparency: doors are made of glass and most meeting rooms are like semi-fishbowls with one or more walls completely done in glass.
  • The finishing is meticulous and natural. The orange colour is relaxing, cupboards have a wood finishing and in the heavy traffic areas (where carpeting can’t work) there are beautiful black natural stone tiles.
  • The overall layout allows small work communities (10-20 people) to form naturally. These work communities then share elevators, toilets, kitchen areas, allowing for broader networking too.

There are many similarities with the post I wrote about planning your career. Many of the things that keep you in the “Hooray!” zone on a career (macro level) are also relevant on the micro level when it comes to doing day-to-day work. Transparency, flexibility, the opportunities for networking and the use of technology are what make my office great.

People, Place, Process
People, Place, Process by David Leon

My company seems to understand this too. There is a reason why they hired David Leon, who write on their website:

Innovation depends on bright people. These people cost more and are far more valuable than the buildings they occupy… but it is a proven fact that the environment in which they work has a major impact on their effectiveness.

For that reason we design workplaces and buildings round the needs of people and the business aims of their organisations.

It is therefore stupefying that I am forced to use a locked down version of Microsoft Windows 2000 with Internet Explorer 6 as a primary workspace every single day of my working life (currently all employees are migrating to a locked down version MS Vista, this should be finished by the end of the first quarter). I think this is a big mistake and know that many people are not as productive as they could have been because of this.

I estimate that I am about 50% more productive on a laptop that is exactly configured to my specifications. The ability to use the applications that I want on the operating system that I prefer (that would be Ubuntu) would make a huge difference. It is the small details that make all the difference. I can’t use my normal keyboard shortcuts, I don’t have access to the command line to do things in batch, I don’t have a decent browser, I cannot edit images; I could go on much longer.

Many of the sites I need to look at don’t even work on IE6 anymore. The other day I browsed to drop.io from work and got the following message:

drop.io IE6 message
drop.io IE6 message (click to enlarge)

Embarrassing right?

So, here is my recommendation to all companies:

At all times allow your employees the freedom to use the technology they want

Yes, this means that you cannot standardise on hardware and software.

Yes, this means you have to allow access to your network from the device that your employee chooses.

Yes, this means you will have to support open standards so that people with a Mac or running Linux can access your applications.

Yes, you will need more bandwidth because you will have to allow YouTube and Facebook.

Yes, you will have extra costs because of all this.

But these extra costs will easily be offset by the extra productivity that your employees can deliver for you. In a couple of years it might actually become difficult to find employees that want to work for your company if you don’t heed to this recommendation.

Is your productivity affected by your workspace? Does your company allow you to choose your hardware? Can you install the software that you want and/or need? I look forward to any comments.