Posterous theme by Cory Watilo

Filed under: technology in the workplace

The Intranet Imperative (2005)

I wrote this in June 2005. The history of intranets is one of a slow burn of adoption (or innovation, if you like). But the pace of technology change is increasing, email is being challenged... is it time now to dust off the intranet imperative and think about about where we go next?

What exactly is an intranet?

The nature of intranets is changing. In fact the term intranet itself is rapidly losing meaning as the Internet interpenetrates organisations through a mixture of business-to-business marketing, extranets, hosted application services and of course personal use of the Web at work. The traditionalist view of intranets, one that concentrates on static information built around an impregnable information architecture, creates a risk for organisations that may be oblivious to the rise of collaborative and dynamic “application-nets” that connect users to people, places and things.

Consider for a moment - what exactly is an intranet? The most simple or basic definition defines it as a restricted, private computer network that uses TCP/IP (Internet) network protocols to facilitate data transmission and exchange within an organisation. But when we look at modern intranets (and extranets), this definition raises more questions than answers – for example:

  • Restricted or private to whom – does this include business partners or even customers?
  • What is the computer network - does it end at the PC on your desk, the mobile phone in your pocket or a kiosk on the shopfloor?
  • Does data include self-service systems, rich media, access to Web - and video conferencing and business intelligence tools that empower staff to get their work done?

Clearly the potiential demands placed on intranets are moving well beyond their original scope of simple access to information and documents. In fact paralleling other changes in our working environments, intranets now need to support always on, always connected access and provide flexibility and interactivity on demand. The technologies to do this already exist and the key challenge for many organistions is how to manage the evolution of an intranet into a multifaceted application-net in a controlled manner.

Of course while you can choose to ignore this imperative, be aware that technology has a habit of winning. You may find your users taking the path of least resistance (like returning to the dreaded network drive) or they will pick their own user-driven tools that will ensure they can get the job done.

The Strategic View of Intranets

Organisations need to control how their intranets will evolve into application-nets. The right approach for achieving this control is a management response that starts with developing a strategic view of their intranet. This strategic perspective does not prescribe the exact future form of the intranet as an application-net, but it provides the basis for creating a system architecture that will facilitate it. The critical point of difference between this new architecture and the old approach is that the intranet imperative forces us to broaden our horizons in order to understand more fully the fit between people, places and things.

This new strategic view should be built from understanding four key elements:

  1. People and Process - understand who the current and future users of system will be, where they are located and what work activities the system must support;
  2. Content - not just documents and information, but the collection of applications and other data in the system;
  3. Infrastructure - The basic technical structure or features of the system (e.g. servers, networks, content management software, etc) and also the human support functions (e.g. helpdesks, trainers, technicians, etc); and
  4. Governance -– the management controls (standards, committees, etc) that deal with the form of the infrastructure and the nature of the content in the system to ensure it meets the needs of the organisation and its users.

But like any type of strategic planning, the application of this strategic view must take into account the overall context of the organisation. Steps for understanding the strategic context and incorporating it into the design of the new architecture include:

  • Business and Technology Analysis - Develop a strategic understanding of the intranet and how this technology, at its most fundamental level, relates to the overall strategy objectives of the organisation;
  • System Audit and Gap Analysis - Complete a review of the people, processes, technology and content that already exists within your organisation to identify the gap between where you are and where you want to be;
  • Manage expectations - Negotiate performance outcomes with your stakeholders to link the evolution of the intranet to the organisation's objectives; and
  • Innovation - Look outside the organisation to learn from leading practices, understand the different options that are available in the market, and emerging trends.

These steps take us beyond simply asking how users will contribute and access information in the intranet and instead make us focus on the bigger picture, resulting in an architecture that is better aligned to the needs of the organisation.

From imperative to action

The intranet imperative is driven by unstoppable technology advances that affect how people work with and use information technology in the workplace. These include:

  • Blurred lines between people, places and things - the distinction between intranets, extranets and Internet sites is changing;
  • Rich media and interactive content - the scope of content has expanded to includes more than static documents, text and images;
  • Always on, always connected - the working environment and intranets need to be delivered through new channels, such as mobile phone, wireless PDAs, voice and kiosks on the shop floor;
  • Next generation networks - awareness, presence and locality will be built in; and
  • User-driven software - users will take the path of least resistance and will pick less sophisticated tools if they get the job done.

Unfortunately for the average intranet manager or management team these changes will of course increase the complexity of dealing with already existing document-centric challenges such as information architecture, effective search and content quality. For example, expert designed information architectures will need to co-exist with those created by user communities. In practice what this means is that we will see organisations embrace different degrees of control, standardisation and integration in order to align their application-nets with the strategic goals of the organisation. For example, centralised authoring will live along side self-publishing systems such as wikis and blogs because it makes business sense rather that isolated decision to choose one over the other.

What may be worse still for some teams is that the technology of the intranet will no longer be isolated from other parts of the organisation. Under these circumstances the system architecture becomes even more critical as both a plan but also as a process for engaging with the rest of the organisation, both in terms of needs but also to create the right operational linkages. So, applying strategic thinking and designing a system architecture for your next generation intranet represents more that just a nice theoretical step but is instead a critical success factor.

Summary

We now understand that the nature of intranets is changing. Unless you use strategic thinking to broaden your concept of what constitutes an "intranet” into a next generation application-net, then you risk losing control as technology leaps ahead without you. You can prepare for this challenge by:

  • Understanding why the nature of intranets is changing;
  • Analysing the strategic context of your intranet today and what will be needed moving forward; and
  • Designing a new system architecture that will facilitate this change so it is progressive, evolutionary and beneficial rather than chaotic, revolutionary and disruptive.

 

RN Future Tense: The Changing Nature of Work

What impact are new design practices and changing technology having on not just the physical office but also on the way we think about work itself? Is the idea of the individual office a thing of the past? In this program we explore the physical, social and cultural trends affecting the changing nature of the office and the way we work in the 21st century.

Another great episode from Future Tense. I was recently talking about activity based workplaces (ABWs) and this podcast provides a good overview of Macquarie Bank's Shelley Street building and the overall trends in open plan office spaces. Again, the role of technology is highlighted as a key factor but balanced by the need for the new leadership skills in the workplace, particularly as workplace demographics change. The show also discusses the impact on worklife-balance and our relationship with the people we work with.

Trying to fix how people use email can backfire

Some attempts to limit email haven't gone as planned. One client of Christina Randle, a workplace productivity expert with the Effectiveness Edge in Austin, tried remedying employees' email overload by banning staff from sending messages on Fridays. It backfired. Employees just stored outbound messages and sent them all Monday morning. "Instead of getting 100 messages on Friday, [people] got 200 in their inbox on Monday morning," she says.

If you want to fix email in the workplace, you've got to treat it as a systemic problem.

Quoted in the SMH about the benefits of enterprise microblogging

Microblogging is great for maintaining a cohesive work environment among geographically dispersed offices, says James Dellow from the social business consultancy Headshift.

"With access to microblogs, executives can be in touch with what's going on across the whole organisation. In a virtual sense, the CEO is sitting next to the employee."

In the future, Dellow says enterprises will be using data analytics to pick up issues, trends, and opportunities from microblogging conversations.

I was quoted in the SMH, in an article by Cynthia Karena who was looking at the benefits of enterprise microblogging with tools like Yammer, Chatter and tibbr.

Nicholas Carr: Flame and filament

Cleaner, safer, and even more efficient than the flame it replaced, the light bulb was welcomed into homes and offices around the world. But along with its many practical benefits, electric light also brought subtle and unexpected changes to the way people lived. The fireplace, the candle, and the oil lamp had always been the focal point of households. Fire was, as Schivelbusch puts it, “the soul of the house.” Families would in the evening gather in a central room, drawn by the flickering flame, to chat about the day’s events or otherwise pass the time together. Electric light, together with central heat, dissolved that long tradition. Family members began to spend more time in different rooms in the evening, studying or reading or working alone. Each person gained more privacy, and a greater sense of autonomy, but the cohesion of the family weakened.

Yes, even apparently small technology innovations can have a massive impact on society.

The Rise of the 3rd Generation Organisation

The impact of the physical workplace on how we organise is a fascinating topic. For example the transformation of factories thanks to electricity and electric light changed how they operated. Modern offices, in the shape of skyscrapers, are an example of another development that has also affected how we manage. However, both the modernisation of factories and the creation of the modern office primarily depended on overcoming physical constraints to create physical structures. This in turn helped to define structures for work that we became familiar with in the developed world during the last century (lets call them 2nd Generation Organisations).

As the digital era continues, my impression is that intangible features are playing a greater role in defining the workplace environment and creating what I would call 3rd Generation Organisations. One trend that is starting to show what a 3rd Generation Organisation looks like is the shift towards Activity Based Workplaces (ABW):

As the name suggests the work space is organized by spaces designed to support specific activities… This loosely structured physical workplace is supported by work practices that facilitate it.

Note the relationship between space design and how work happens - this is more than simply creating a pleasant office space to work in and shouldn't be confused with hot desking or hoteling either. I recently had the opportunity to see Commonwealth Bank's Activity Based Workplace, built out on the edge of Sydney CBD. Its interesting to see how in practice IT plays a defining rather than supporting role in making their Activity Based Workplace possible.  In fact, urban planning consultants Urbis advise that:

During the 1990s, wi-fi didn’t exist, so flexibility was limited. Now, a successful [Activity Based] workplace must consider the IT environment to deliver productivity gains. ABW is fundamentally linked to technology and any ABW project will require significant investment in IT as well as the fitout.

The benefits of ABW appear to be a combination of soft and hard benefits:

  • Employee engagement (better collaboration and productivity).
  • Savings from more efficient use of space, less use of paper and lower building running costs.

Of course implementing an ABW is no easy task for a large organisation - it requires capital and motivation to make the change. Yet at the small end of town co-working spaces are becoming popular too, like Hub Melbourne. Just like their larger enterprise counterparts they are also enabled by access to mobile, social, Web-based and cloud information technologies.

It is easy to doubt the transformational impact of information technology in the workplace - including social software - but equally we shouldn't ignore the symbiotic relationship to the physical workspace. It is the combination of the two that will actualy create a deeper systemic change to how we organise and will allow 3rd Generation Organisations to emerge.

End of the viral adoption road for social business software?

Yesterday, social software maker Yammer announced it has raised $85 million, bringing its total funding to $142 million. Not shabby for a company with an estimated revenue run rate of some $30 million. The real questions though are what happens next, how does it compete with the likes of Chatter, can it remain as an independent software company or will what it does become part of the fabric of new software going forward?

Great post and analysis by Dennis Howlett (no, that's not a typo) where he talks to Adam Pisoni, co-founder Yammer, and discusses where Yammer goes next, which I think also has broader ramifications for all social business software vendors.

One of the big take aways is that there is clearly a big shift within Yammer from a company focused on promoting a viral adoption model towards one which is focused on a more sophisticated active change management and system integration. This has actually been evident for sometime, with lots of community management 101 content coming from the Yammer team and obviously plenty of add-ons appearing that enable better integrating with enterprise systems.

A try-before-you-buy model is perfectly reasonable and isn't entirely unique to Yammer, but while this approach does lower the barriers to entry in reality the software costs are only one part of running a successful pilot or proof of concept (and its worth considering that Jive, IBM Connections, Newsgator, Socialtext etc are being deployed to the enterprise without a freemium model). And as I'm sure Deloitte is finding, flicking the switch on 200,000 global users was the easy bit but replicating success at that scale is whole different order of magnitude from their initial deployment to their Australian practice.

However, overall this is a good thing and reflects my experience of working with organisations where the random, organic approach hasn't worked (regardless of the platform). But it should also be a wake up call for people who've been champions of the viral adoption approach who should realise this is actually quite damaging for some organisations.

Dennis also raises some good points about where solutions like Yammer sit from a vendor management and technical architecture stand point. Personally I think these questions are worth discussing although I don't believe we can jump to any conclusions just yet. After all, this is a different software marketplace (as we've pointed out).

To Dennis's points I would also add that I think the main danger to Yammer is that it becomes a bit like SharePoint, which is extremely popular but poorly deployed by many. I wonder if "Yammer Governance" will become a hot topic in the near future like "SharePoint Governance"?

What do you think?