8/31/10

10 drastic changes in the world of work in the next 10 years

1. De-routinization of WorkThe core value that people add is not in the processes that can be automated, but in non-routine processes, uniquely human, analytical or interactive contributions that result in words such as discovery, innovation, teaming, leading, selling and learning. Non-routine skills are those we cannot automate. For example, we cannot automate the process of selling a life insurance policy to a skeptical buyer, but we can use automation tools to augment the selling process.
2. Work SwarmsSwarming is a work style characterized by a flurry of collective activity by anyone and everyone conceivably available and able to add value. Gartner identifies two phenomena within the collective activity; Teaming (instead of solo performances) will be valued and rewarded more and occur more frequently and a new form of teaming, which Gartner calls swarming, to distinguish it from more historical teaming models, is emerging. Teams have historically consisted of people who have worked together before and who know each other reasonably well, often working in the same organization and for the same manager. Swarms form quickly, attacking a problem or opportunity and then quickly dissipating. Swarming is an agile response to an observed increase in ad hoc action requirements, as ad hoc activities continue to displace structured, bureaucratic situations.

3. Weak LinksIn swarms, if individuals know each other at all, it may be just barely, via weak links. Weak links are the cues people can pick up from people who know the people they have to work with. They are indirect indicators and rely, in part, on the confidence others have in their knowledge of people. Navigating one's own personal, professional and social networks helps people develop and exploit both strong and weak links and that, in turn, will be crucial to surviving and exploiting swarms for business benefit.

4. Working With the CollectiveThere are informal groups of people, outside the direct control of the organization, who can impact the success or failure of the organization. These informal groups are bound together by a common interest, a fad or a historical accident, as described by Gartner as “the collective.” Smart business executives discern how to live in a business ecosystem they cannot control; one they can only influence. The influence process requires understanding the collectives that potentially influence their organization, as well as the key people in those external groups. Gathering market intelligence via the collective is crucial. Equally important is figuring out how to use the collective to define segments, markets, products and various business strategies.

5. Work Sketch-UpsMost non-routine processes will also be highly informal. It is very important that organizations try to capture the criteria used in making decisions but, at least for now, Gartner does not expect most non-routine processes to follow meaningful standard patterns. Over time, we believe that work patterns for more non-routine work will emerge, justifying a light-handed approach to collecting activity information, but it will take years before a real return on investment for this effort is visible. In the meantime, the process models for most non-routine processes will remain simple "sketch-ups," created on the fly.

6. Spontaneous WorkThis property is also implied in Gartner’s description of work swarms. Spontaneity implies more than reactive activity, for example, to the emergence of new patterns. It also contains proactive work such as seeking out new opportunities and creating new designs and models.

7. Simulation and ExperimentationActive engagement with simulated environments (virtual environments), which are similar to technologies depicted in the film Minority Report, will come to replace drilling into cells in spreadsheets. This suggests the use of n-dimensional virtual representations of all different sorts of data. The contents of the simulated environment will be assembled by agent technologies that determine what materials go together based on watching people work with this content. People will interact with the data and actively manipulate various parameters reshaping the world they’re looking at.

8. Pattern SensitivityGartner has published a major line of research on Pattern-Based Strategy. The business world is becoming more volatile, affording people working off of linear models based on past performance far less visibility into the future than ever before. Gartner expects to see a significant growth in the number of organizations that create groups specifically charged with detecting divergent emerging patterns, evaluating those patterns, developing various scenarios for how the disruption might play out and proposing to senior executives new ways of exploiting (or protecting the organization from) the changes to which they are now more sensitive.

9. HyperconnectedHyperconnectedness is a property of most organizations, existing within networks of networks, unable to completely control any of them. While key supply chain elements, for example, may be "under contract," there is no guarantee it will perform properly, not even if the supply chain is in-house. Hyperconnectedness will lead to a push for more work to occur in both formal and informal relationships across enterprise boundaries, and that has implications for how people work and how IT supports or augments that work.

10. My PlaceThe workplace is becoming more and more virtual, with meetings occurring across time zones and organizations and with participants who barely know each other, working on swarms attacking rapidly emerging problems. But the employee will still have a "place" where they work. Many will have neither a company-provided physical office nor a desk, and their work will increasingly happen 24 hours a day, seven days a week. In this work environment, the lines between personal, professional, social and family matters, along with organization subjects, will disappear. Individuals, of course, need to manage the complexity created by overlapping demands, whether from the new world of work or from external (non-work-related) phenomena. Those that cannot manage the underlying "expectation and interrupt overloads" will suffer performance deficits as these overloads force individuals to operate in an over-stimulated (information-overload) state.

Additional information is available in the Gartner report "Watchlist: Continuing Changes in the Nature of Work, 2010-2020." The report is available on Gartner's website at http://www.gartner.com/resId=1331623.

is this really something for teamwork?




When you begin to work in an agile way, you work much more in a team than before. Things you did alone before are now done in a team, and you rely on each other to get things done. While I find teamwork something very helpful in 80% of all cases, in some cases I can not help to think - before we start working in a cycle - "well, is this now really something for teamwork? Wouldn't it be easier if someone sat down and just figured this out?"

Today I had such a moment again. We were asked by todays product champ to come up with a system that would allow all people working for the company to sell our products and to make it in a way that would be transparent and corresponding to the agile principles (so, for instance, to make it in a way that would allow different people to work on the same client account and sharing responsibility).

My immediate response was: "Well, I know a lot about sales and about systems, so shouldn't I just sit down and write the concept?" But the other team members convinced me that it was a good thing to do this task as a team and so we started deciding on the best way to do this.

The other team members started by brainstorming on all the questions they might have about selling our products, while I came up with a basic suggestion of the structure and system. Then, we swapped the results, and the team members started to improve my system (they actually changed it completely, which was totally beneficial to the result :-) ) and I started taking their questions and formulating "how to's" and checklists to answer all the questions.

After only half a day we had a basic system in place with all the manual and checklists to go with it. In the afternon we then started testing our system together and improved it a great deal  over the course of the next three hours.

At 4.15 we had a review with our product champ and presented him the results. At 5, we all went home, feeling a great sense of accomplishment. Wow. I am starting to become a true believer in teamwork (needless to say, I am already a fervent advocate for agile).

8/30/10

The role of google docs in our agile structure

One of the principles of agile working is to make all your content public to all people involved. As we needed something that would work from the onset and would cost virtually nothing, we decided to go with google docs.

Although this decision has had it's disadvantages, the advantages are way more important in my opinion. The downside of google docs is, of course, that we could not use our fonts and basically our Corportate Identity became inexistent with google docs, or, to put it differently, we will need to work a lot on our design to make it work with google docs. But as our focus at the moment is not on creating beautiful things but rather things that work (agile principle again) we just chose to ignore this.

The advantages of google docs are many:

  • Working in the same document at the same time by as many people as you choose to invite
  • No endless search for document versions - everything is in one document and can be accessed by exactly the people you want to
  • No mailbox full of attachments
  • Realtime editing in groups
  • Easy structuring thanks to shared folders
  • sharing inside and outside the organisation 
  • Changes are available everywhere in real time
  • etc.
Before using google docs and before working in an agile way, we already had used information sharing and knowledge management tools, for instance an intranet or a company wiki. These were much less easy to use and to maintain than what we have now and I feel that google docs has already helped us a great deal in our journey of becoming an agile company (a journey which has only recently started).