There’s plenty of frustration amongst social media commentators about the steadfast attitude of many enterprises towards the adoption of social tools. More specifically, accepting the philosophy of Enterprise 2.0.

Ross Dawson of Future Exploration Networks and Stephen Collins of AcidLabs amongst others have often commented in detail on this topic. They have pointed to some great successes and I also hear their frustrations. There is language, thinking and approaches around social tools that simply don’t fit into the corporate culture of old. Barriers need to be broken down to give people free open access to these tools, sometimes rules need to be put in place and even some situations call for access to be restricted during work hours. There isn’t a clear and general solution for all enterprises be they large or small.

I’m an advocate for open access for enterprise knowledge workers, as we do in Saasu. We’ve even built connections to social platforms from our online accounting web finance engine. We are building Enterprise 2.0 capabilities into our products and services. However I also hear the frustration of business owners and management teams who believe they are losing productivity due to Facebook and Myspace.

The main factor causing slow adoption by enterprises is productivity fear. Decades of workhorse enterprise culture has left management in fear of productivity declines from social tools. Just as SMS, Instant Messaging systems were perceived to be slowing productivity so are social networks at this early stage of their technology cycle.

Naturally they jump to no access for anyone. Well, they are totally justified to have this fear, but not to apply it to everyone unilaterally. If in managing the flow of information in tools like Facebook can only be served by blocking certain users and allowing others then that’s justified but far from ideal. Many roles in organisations may not be well served by these tools until either a self managing culture or a social communication workflow system is firmly in place that understands or controls acceptable versus unacceptable use.

I talked about restricting access to social tools some time ago in my post about Facebook in the workplace. I’ve witnessed first hand productivity costs in an enterprise environment. I still advocate restrictions and policy around access based on a role by role basis. Access to social networks should be no different to any other communications or knowledge tools used to generate productivity. Any approach to this which is not analytical and scientific in it’s assessment is simply decision making based on poor business intelligence.

Even in the Saasu business we are careful what each new system is that we adopt. It’s not about a free for all, an unequivocal license to explore for all employees. That’s nice, but an analogy springs to mind. If all the scientists choose to go out into the field because it’s fun then none of the lab work gets done.

Most importantly I’m committed to scientific rigor on the adoption of any tool in an enterprise. Anecdotal, emotional and social benefits are all important but what do the numbers also say about the social tool being employed. This is where enterprises should look at the usefulness in numbers and not just jump to conclusions. There is no substitute for at least some rough scientific checks being applied to any system, business or otherwise.

Many managers witness staff spending time working their personal Brand in Facebook. Plain and simple it often about entertainment, events and niche interest groups. So a manager in that situation adds that anecdotal evidence to their bag of reasons and moves on. That evidence is then pulled out of the bag when a decision is being made to block a tool or if thought leaders like Ross or Stephen happen to be giving advise and encouragement on adoption. The argument no doubt becomes tough in the face of this. My approach would be to:

1. Demonstrate why social tools are an opportunity and not a time waster in many circumstances.
2. Get them to adopt an Enterprise 2.0 framework with metrics or that connects to a system that has metrics.
3. Get the social flow managed via culture, tools and procedures.

The reality is that some jobs simply become less productive while others benefit. The job specs for a production line worker, retirement home salesperson or waste removal person probably don’t call for it. However, there is an argument that even people in those roles gain job satisfaction, get better communication with colleagues and possibly better access to management when using social platforms.

Knowledge workers should always be given access to platforms. I’ll leave it to Ross and Stephen to communicate this. Read their blogs, they are the experts.

It’s old now, but you simply can’t watch this video too many times.

http://video.google.com/googleplayer.swf?docid=-6909078385965257294&hl=en

It was strange for me moving from a trading environment to the software as a service industry (SaaS). One of the biggest differences I noticed straight away was how sparse web pages were. Even the early web tools like online banking and broking portals were so inefficiently designed. They failed to optimise screen real estate and forced users to scroll, mouse, search, yada yada yada.

Traders Reuters/Bloomberg terminals and their spreadsheets were nearly always set to the smallest font size you could find (or read). You would use efficient fonts like Arial Narrow to try and squeeze a few more prices into the screens that surrounded you. You didn’t have the luxury of whitespace (actually it was blackspace). The vast majority of traders went for black background designs. This was interesting in itself.

In a way I miss that, it was extremely time and information efficient. It was also easier on the eyes and clearer for the mind. You had all your information laid out in front of you. It can be likened to ‘chess boarding’ your desk with all your paperwork so that you would know exactly where everything is and be able to grab it instantly.

You could see the markets and the world events unfold in realtime. You could be efficient, no transition costs, such as the need to navigate a clumsy mouse, tab through browsers, scroll down screens, drag and drop or refresh web content. Screen real estate was prime real estate. No cares for font-type, white space pixel counts and the finest navigation effects. Just jam it in was the approach so you don’t have to do a single thing except read it.

It dawned on me when I first came into the web applications space that financial markets traders had actually evolved their own designs. The result was quite different to web applications as we know them. Here’s some of my observations.

Traders designed and built their own screens

Traders designed their screen themselves, or ex-traders working for Bloomberg or Reuters helped them. Extremely user centric design, they got exactly what they wanted. There was no lost-in-translation, lost-in-budget or lost-in-design-ego issues to contend with.

Traders built their screens like engineers and not like designers would

Traders are generally left brain logical types which could be described as ‘engineering like’. So their screens were very matrix like. Information was given the best screen real estate if it was the most financially sensitive. Really important financials received the mega-font treatment.

Traders were bad designers, but did it matter?

Web designers and now usability designers tend to come from right-brain imaginative and creative backgrounds (in my experience). The traders didn’t care much for good looking screens. This wasn’t a male thing. There were plenty of female traders in the organisations I worked for and it made no difference. Design extended to font colour and that was it. A non-black background was an outlier in this crowd. Traders seemed to naturally design for screen real estate optimisation and minimal navigation choices (no navigation), so there was an element of design in usability.

I thought I’d write this post to highlight something which has influenced keeping features a click or two away in our Saasu application. It has been extended further in our next Saasu.com release with the new one-click menu.

Photo credit: Matt Seppings

Twitter is a community website where users post publicly or privately what they are doing during their day in succinct comments (140 characters).

In my opinion, the magic 140 characters and getting a feel for peoples day to day lives are the biggest reasons for it’s success. It keeps communication precise, moving it away from long emails and IM ping-pong.

Twhirl is a great app for getting your twitter feeds. Why? I work a fine balance of communicating with people and getting some coal face work done on Saasu.com. This productivity dilemma of being “fuzzy” versus “bundy-clock” in my work style is improved with the right tools like Twhirl. Twitter, Facebook, LinkedIn all require time to keep track so when a tool comes along that will at-a-glance give me the updates I need, then I’m on board. Thanks to @alegrya and @jodiem at BarCamp Sydney who pointed it out.

To learn more about what the fuzzy worker concept is read Stephen Collins acidlabs blog.

I’m at BarCamp Sydney 2008, get there if you can, lots of great people and content – a perfect storm. Clearly no-one has it nailed on what Web 3.0 will look like, including me.

The discussion turned to; web privacy, OpenSocial, OpenID, which device, on vs. off-line and semantic web. So many views and they all felt right to some degree but none felt clearly and independently correct. The one point of clarity was that Web 3.0 isn’t any one thing.

The discussion and comments just added evidence to my view that the organism or entity that is evolving out of the primordial Web 2.0 soup is so much bigger than the sum of it’s parts. It can’t be observed, it has a life of it’s own, we can’t comprehend it. Just as the flea doesn’t know it lives on a dog. We are building all the components, the cells in it’s body. Being many specialist cells, we don’t have the ability to conceptualise the whole entity yet. I’m increasingly convinced Artificial Intelligence is going to be a major component. If the web enabled applications are the cell specialisation using frameworks then the nervous system is probably somewhere in the region of AI engines and the semantic web. The cell nuclei or the distributed brain if you like.

Picture credit: Mike Licht