helping make the network smarter

In what is likely the best example of my mantra that ‘work is learning and learning is the work’, Nokia’s Chairman Risto Siilasmaa describes how he learned about machine learning because everyone was talking about it but he still did not understand it enough to describe it. Frustrated, he was acting like many of his fellow executives

“I spent some time complaining. Then I realized that as a long-time CEO and Chairman, I had fallen into the trap of being defined by my role: I had grown accustomed to having things explained to me. Instead of trying to figure out the nuts and bolts of a seemingly complicated technology, I had gotten used to someone else doing the heavy lifting.” —HBR 2018-10-04

The result of what Siilasmaa learned is an excellent example of the integration of learning and work, a necessity in the network era workplace.

Read more

Learning to work smarter

Anne Marie McEwan’s Smart Working nicely summarizes the shift that is taking place in how we work. These shifts have happened before – when we developed agriculture, moved into cities, or created powered machines. Now we are becoming networked.

The term ‘smart working’ has in recent years been associated with flexible and mobile working, that is ‘anytime, anywhere’ ways of working enabled by communication technologies. Another view, broader than the narrow focus on location and time independence, is that smart working is about flexibility and autonomy in where, when and how people work.

In my view, smart working is the outcome of designing and putting in place systems, working environments and governance principles that are known to be associated with effective business performance, including workforce autonomy and self-determination, and which seek to maximise opportunities to use and develop people’s knowledge, skills.

I’m in the process of putting together several threads as a single article, and this is where I do my thinking in public.

In The Learning Age I said that business models and work practices are becoming networked and global, speeding the rate of time to implementation. The lines between work and leisure are blurring, as with work and learning. Today, about 16% of us can be described as hyperconnected but that is expected to grow to 40%, and I would say those people will be the main drivers of our economies and societies.

Effective knowledge sharing is essential for all organizations today but the mainstream application of knowledge management, and I would include learning management, over the past few decades has got it all wrong. We have over-managed information because it’s easy and we’re still enamoured with information technology. However, the ubiquitous information surround may put a stop to this. As enterprises become more closely tied to the Web, the principle of “small pieces loosely joined” is permeating our industrial walls. More and more workers have their own sources of information and knowledge.

At an individual level we need to make sense of the ever-increasing signals coming from our networks, while reducing the noise. This is why I developed sense-making with PKM which I am continuing to refine. Just yesterday I explained social bookmarks, feed readers and using Twitter as a search engine to a “digital immigrant” the same age as me. The light went on when I showed how she could connect with a worldwide cooperative community that shared several of her professional interests.

The power of micro-blogging with Twitter so far is quite impressive and I was one who adopted this medium with a fair bit of skepticism. I just noticed that in the past few months Twitter has replaced Google as the prime referring site for visitors here, surpassing Google.

With some individual skills in using social media, the next question an organization may ask is how to start an online community. Of course starting one doesn’t mean it will grow or be useful. Communication does not equal collaboration, and that is a challenge in “building” communities of practice (CoP). Just because the communication tools are in place does not mean that people will automatically collaborate.  You can’t really build a CoP, it has to emerge through practice; but you can put in systems and processes to support CoP’s.  You know you’re in a real community of practice when it changes your practice.

Taking advantage of social networks for business can give a temporary advantage (everything in business is temporary anyway) and help to develop disruptive business models. So that’s it – there are significant shifts in how we work which will require new skills and if used effectively can create new ways of generating wealth. The information age status quo isn’t the same for the learning age.

Distributed Work Rules

About ten years ago it was called computer supported collaborative work (CSCW) but today I would just call it getting things done using the Web. Most of my work is at a distance and I’ve been using Web collaboration tools since they became available. The Web has been around for the past 15 years or so, which means that for anyone under 35, it’s been part of the surround for most of their working lives.

I’ve been working as part of a distributed team that is composed mostly of people over 40 and as a result have accumulated several hundred e-mails on one project alone. I usually get maybe a dozen e-mail per day, but this month has required some serious triage of a hundred at a time. I guess this is how “normal” people work every day. Perhaps the next time I join a distributed team, I’ll ask everyone to accept certain ground rules. If not, I may decide not to play.

  1. Documents that are edited by more than one person must be created, edited and commented upon on a wiki or other collaborative web document such as Google Docs, Central Desktop, etc. (This graphic explains it quite well)
  2. The group must select a text chat method for small details that need to be discussed (Skype, MSM, Google Chat, etc). [Dozens of threads using “Reply All” saying things like, “well done” are a waste of the team’s time]
  3. Document formatting should only be considered/discussed once the content has been agreed upon, and then only one person/agency is responsible.
  4. E-mail should only be used for official correspondence that requires a date/time stamp for archival reasons. Contracts, acceptance of deliverables and official feedback would be examples.

Any other suggestions? Perhaps we need a Distributed Work Manifesto.