Asking the question: GOOD; asking it over and over: BAD – where social engagement in the workplace fails.

same_tune

Using social tools within the enterprise is a valuable thing. It lets people ask questions to a bigger audience than just those sitting within hearing distance of their desk.

I’ve discussed this in earlier posts (ESS (Enterprise Social Software) – user adoption, and Let’s share!). It’s incredibly valuable to be able to draw on the knowledge of others. That’s why it’s good to be able to ask questions. The answer given helps not just the asker, but can help others, and at the same time, others can add to the answer creating even more value.

Where I feel this all falls down though is that, often, there is no real way to capture that knowledge that came about from the questions asked. Continue reading

Better Knowledge-Sharing: Fill The Dry Knowledge Well With These Practices

The post below was written by Sebastian Francis in 2010 for OilandGasInvestor.com.
At that time Sebastian worked for SAIC.

It’s an excellent article that describes describes some major concerns with knowledge management (including the capturing of tacit knowledge) along with making that knowledge retrievable and useful.
I’m grateful that Sebastian has given me permission to reproduce it here.

————————————————————————–

Better Knowledge-Sharing: Fill The Dry Knowledge Well With These Practices

a Guest Post by Sebastian Francis

Here are a variety of quick and easy ways to share important business information each generation needs to know.

Today, a popular need of organizational leaders is how to quickly identify, capture and reuse information from employees who are retiring, or about to do so, for these people have industry expertise and can make it quickly available to those who need it.

The ability to quickly access the right information can improve competitive position, promote innovation, reduce rework and errors, and increase the speed to identify new opportunities.

Unfortunately, searching for information (such as proven practices, lessons from prior unsuccessful attempts, tips and techniques, documented procedures and, most important, experience and intuitive expertise locked in the heads of individuals) can take far too much time.

As the crew shift change continues—Baby Boomers retire in mass and few Generation X and Y talent enter the oil and gas industry—leaders have an opportunity to manage this shift by leveraging the latest information-sharing technologies and methods. To meet business strategy, many leaders crave the ability to “google like Google.” They desire to create a deep reservoir of information that replenishes itself and deploy methods and tools that will enable each generation to find the right information within a few clicks.

Too often, organizations rely on only one method, such as launching communities of practice, conducting after-action reviews, and promoting the use of best practices. Or, they use a limited number of technologies such as social networking tools, content repositories and search engines, and use the same solution across the board. This tends to produce dry knowledge wells.

A savvy strategy begins with understanding the needs of the internal talent group: Who has the information and who needs it? Next is meeting unique requirements by implementing several methods and technologies to create custom solutions. Characteristics of the solution should emulate popular knowledge-sharing practices that occur outside the organization.

Understanding generational issues

“What we’ve got here is a failure to communicate.”
–Strother Martin, Cool Hand Luke, 1967 film starring Paul Newman

Communication problems are as old as human history. Bridging gaps is a continual challenge, and industry leaders need to know how to capitalize on overcoming those gaps.

Within the oil and gas industry (as well as in other industries), there are four generations of talent: Traditionalists (birth years 1925-1945), Baby Boomers (1946-1965), Generation X (1966-1980) and Generation Y (1981-2000). Since the 1990s, professional journals have alerted oil and gas leaders that the Baby Boomers, now the largest percentage of the workforce, are exiting the workforce at an alarming rate. The potential consequences include: 
Increased competition for talent. Due to the decrease in skilled talent following the retirement of the Traditionalists and Baby Boomers, competition for workers with required professional degrees and experience will increase. 
Shifting geography. Technology enables talent to work from anywhere and teleworking is becoming more commonplace; therefore, organizations will be able to source talent globally. This shift will affect organizational communication, strategy and business processes.
Shifting generation. The corporate leaders of tomorrow will most likely be talent from Generations X and Y. Currently, organizations are balancing the activities of retiring two groups and preparing the organization for two others, while not neglecting any.
Aging workforce. A majority of Baby Boomers are predicted to exit the workforce by 2015 and are followed by a much smaller group of talent, Generation X. In addition, the next generations of talent have different learning styles, communication preferences and work/life balance requirements than their predecessors. To recruit, retain and develop the next generation of talent, organizations must recognize and adapt to these styles.
Lost information and tacit knowledge. As Traditionalists and Baby Boomers exit organizations, some for the last time, so will their communal know-how—their tacit knowledge—especially if it has not been adequately identified, captured, codified and stored in corporate knowledge repositories.
Preparing and training talent. The fact that Traditionalists and Baby Boomers are retiring does not mean that they will not re-enter the workforce in some capacity, such as starting a new career, or working as a consultant or part-time employee. In some cases, organizations will be able to leverage veteran expertise in this way. As a result, organizations will need to update the skills of these workers, or train them along with other new hires. Thus, learning/training departments may simultaneously have to train several generations, each having distinctly different learning styles. This can perplex learning organizations that do not understand the needs of each generation.

Bridging generational gaps to improve knowledge management

“When you’re 17 years old, green and inexperienced, you’re grateful for any guidance and direction you can get.”
–Christina Aguilera, pop singer

Leaders who recognize and respond to generational communication and learning commonalities and differences, can bridge gaps and prepare for the future.

Different generations favor different learning styles. Traditionalists and Baby Boomers usually prefer face-to-face, classroom and instructor-led training activities. In contrast, Generations X and Y may resist formal training sessions and prefer to connect to people informally and quickly search all information sources. Technology tools, such as handheld devices and social-networking sites, facilitate their fast connections to information.

Traditionalists and Baby Boomers tend to communicate using formal and personal methods, such as writing e-mails, meeting face to face and holding conference calls. In contrast, Generations X and Y usually like just the right amount of information, when and where they need it, such as sending abbreviated text and instant messages, and meeting via online chat sessions.

When information exchange is effective, employees seeking information receive what they need—a knowledge gem. Unfortunately, during communication, valuable information is often lost because the organization does not have an easy-to-use method of identifying and systematically collecting and depositing gained knowledge into a repository.

Capturing critical knowledge

“Any customer can have a car painted any color he wants, so long as it is black.”
–Henry Ford

Because the talent of today and tomorrow is multi-generational, a one-size-fits-all approach to information capture, collaboration and reuse does not work. What works are multiple approaches that consider each member of the audience.

Now that the typical characteristics of each generation group is understood, the next step is to understand the two phases of information flow: capturing it and accessing it for re-use. Let’s explore two key steps to capturing it.

— Step One: Understand and identify knowledge that fuels the organization.
What information, knowledge and expertise is valuable to the organization? Some businesses are uncertain and attempt to capture all information regardless of value. A better practice is to identify critical business processes and their associated performance targets across the organization’s value chain. In other words, identify the most important business activities that yield success, are vital to avoid failure, and identify where information gaps exist.
Analyzing key processes, creating knowledge maps and interviewing stakeholders will lead to key process identification. The output will assist leaders in understanding where the information is located, who has it and the prerequisites for information capture.

— Step Two: Capture what’s important.
Information and know-how are scattered throughout an organization in e-mails, individual and networked hard drives, binders containing operating procedures and training manuals, SharePoint or other Internet sites, conversations around water coolers, and within people’s heads.

Knowledgeable organizations use a variety of capture activities such as on-the-job team learning processes before, during and after major activities and are supplemented, when relevant, through a series of individual interviews.

“Learning before doing” is supported by a peer-assist process, which targets a specific challenge, imports knowledge from people outside the team, identifies possible approaches to address obstacles and new ideas, and promotes sharing of information and knowledge with talent through a facilitated meeting.

A U.S. Army technique called After Action Reviews involves talent in “learning while doing” by answering four questions immediately after completing each key activity: What was supposed to happen? What actually happened? Why is there a difference? What can we learn from it?

At the end of a given project or accomplishment, a process called a Retrospect encourages team members to look back at the project to discover what went well and why, with a view to helping a different team repeat their success and avoid any pitfalls.

A critical component of capture technique requires an effective method to record information that is comfortable for the information providers and appeals to the information seeker. For example, a Baby Boomer’s preferred sharing method could be a written report. In contrast, a Gen Y would have no interest in such and would ignore it.

This issue raises the importance of using a variety of communication methods as well as an opportunity to emulate information and knowledge-sharing practices that occur outside the organization.

Social-networking sites such as Facebook, Wiki sites such as Wikipedia, and video-sharing sites, such as YouTube, are popular tools for capturing information, connecting with people, sharing ideas, searching for information and viewing content. Such sites are popular, free and used by each generation. Instead of inventing something new, organizations can transfer popular features from public sites into the design and functionality of corporate tools. 

For example, attaching a webcam to a laptop or using a smartphone instantly equips anyone with just-in-time ability to capture information, especially dialogue and images that are challenging to document. A handheld production studio allows for ad hoc or planned capture of interviews with experts, after-action reviews, safety procedures, an equipment repair procedure, etc.

Uploading multimedia files (sound bites and video clips) to a knowledge repository creates a powerful capture and sharing opportunity. The “YouTube” approach makes it possible for any employee to post a video to a corporate site so that any team member can watch it instantly. “Nu-tube” is the name of a concept that a nuclear energy company gives its effort.

Launching pop technology is “hip” when end-users are engaged, needs are understood and the solution meets their requirements.

Make Information Accessible Quickly and Easily

“I try to learn from the past, but I plan for the future by focusing exclusively on the present. That’s where the fun is.” 
–Donald Trump

With a plan now for perpetually capturing valuable information, people must be enable to access and use it. Two steps help to achieve success here. The first is to leverage technology to visually present information. The second is to involve end-users in the design of the sharing process. The following case study describes these two steps in action.

Recently, a U.S. pipeline service company realized that critical information trickled throughout its business unit. The increasing inability of talent to readily tap information sources sharply diminished the value of stored resources. The service company encountered several challenges to make information available.

The overwhelming amount of information to capture, organize, store and manage caused employees to spend days (then) versus minutes (now) searching data.

A document repository contained unmanaged versions and uncontrolled copies of files scattered in network file shares, laptops, intranet sites, CDs, flash drives and filing cabinets.

Other challenges were increasing regulatory constraints, litigation and business-continuity issues, and the rising need to capture “know how” from retiring staff.

Considering generational changes as an opportunity to plan for the future and social-networking tools as an opportunity to innovate, leaders acted. The result is “e-discovery,” a solution that increases the speed to find reporting information from across disparate business units, regulatory-compliance improvements and business-performance enhancements.

Solution highlights include preserving content on an enterprise level versus only at an individual level, implementing a self-service information portal, facilitating contextual and “smart” search, and reducing administrative costs of managing paper records.

The method of designing this solution contributed to its success. The e-discovery design team:
— Identified the valuable information needed to comply with legal requirements,
— Understood learning, technology and communication preferences of each generation,
— Devised methods to allow users to share and access information in multiple formats and
–Designed a tool that emulates features of popular social-networking sites (easy, visual presentation of information, collaboration, smart search and dashboards).

The e-discovery impact on the pipeline business segment includes preparing litigation-status reports in one step versus multiple steps; retrieving archived documents in minutes versus days; eliminating risks associated by damage to paper-based files; reducing employee frustration of not finding who or what they need; and serving as a solution model for re-use within the enterprise.

And most importantly this method helped all generations of talent quickly find the right information when they needed it, so that they can perform their job.

“Diamonds are forever.”
–De Beers ad

Information can be a valuable organizational asset when people can quickly recall where it is stored.

Fortunately, organizations have an abundance of internal information sources: documents, expertise, lessons learned, best practices and the like. Unfortunately, waves of experts are leaving or retiring, usually without depositing their rich knowledge or revealing the location of information “gems” critical to performing business processes.

Leaders can respond by providing a variety of communication and learning methods, leveraging popular social-networking technologies, and embracing the uniqueness of each generation. The impact for the organization can be a rich field of valuable information that continuously replenishes itself.

Note – this article can also be downloaded here.

Working with Global Teams: Not all in the same room

This is part of the Working with Global Teams series

Previous Post: Working with Global Teams: Pesky Time Zones Revisited

———————————————

A friend of mine,Shoaib Ahmed, has an excellent blog on Agile, and Project Management. 

He’s based in New Zealand, and as New Zealand is literally so far away from “the rest of the world” (said with a cheeky wink), he has a pretty good idea of some of the challenges that are met when working in a globally dispersed group.

Shoaib’s latest post goes into this in more detail. He mentions things such as time difference, culture, and reporting lines. Click here to read what he says.

Related posts:

 

  • 8 Tips for Teaming Across Time Zones (openforum.com)

Different Systems and Different Silos – A Real-life Disaster

What follows is a post that was recently published on AIIM’s site as an “Expert Blogger”. (The original can be read here)

———————————————————————–

Different Systems and Different Silos – A Real-life Disaster

Discussions had been going on for months. Plans had been drawn up. Even though the main tasks had been itemized, there was agreement that these would still have to be refined further into the project.

Nothing had been done to assign owners to the tasks, but there was a mutual agreement that whoever could, would work on each task as they saw appropriate.

In any case, the goal, and the timeline, was clear. There was no disagreement there.

Over the weeks, considerable time and resources were committed to working through the various items that made up the project task list, and the necessary information was diligently recorded, and documented.

Progress was regularly reported to the various parties involved. This was done verbally. It involved the person who took ownership of the task describing what had been done, along with what else had to be done, and any impediments that they had encountered. If they felt it was necessary the task “owner” could describe a plan of action to overcome the impediment. The other parties involved could ask for more information, or give suggestions.

Communication was informal, but each party were confident that they were apprised of task activities, and that they knew the status of the project.

Then, one day, everyone involved, got together to “walk through” the progress of the project. This involved visiting the various locations where the tasks were done. It was, essentially, an internal, informal “audit”, and a complete day was scheduled. As is necessary for such an event, all “distractions” were removed. Everyone was asked to turn off their mobile phones, Blackberries, or similar handheld devices. An extended dinner was planned. Everyone had been working hard, and this would allow them to relax, and discuss the results of the audit, as well as talk about whether the project goal was still valid, or whether it needed to be modified.

The walk through of the first task went well. The recorded information was double-checked (obviously by someone other than the task “owner”). Everything looked good. Everyone was happy. The walk-through of the second task (identifying potential candidates for future sub-tasks) also went well.

But then, major issues were starting to appear. And these were not to do with the actual data, or even with the tasks themselves.

It turned out that each party had used their own system for recording information. This meant that the data, although present, was stored in two different systems. And in each case, the data had been recorded in a way that “suited” the person entering it. This meant that there was no “common” structure, and different metadata. And there was no way to simply “merge”, or import, the data from one to the other.

Further to this, because there was no real management of the tasks (as mentioned, it was a very informal process), it turned out that there was a duplication of activities. It appeared that some of the “unassigned” tasks, had been worked on by one party without knowing that others were also working on them. Result – a duplication of data. And, with the data recorded in two disparate systems.

To fix the “problem” would involve deciding which system would be the “master” system, and then manually entering all the data, from the unwanted system, into it. It was going to be a big job, and there was a lot of tension. The elaborate dinner that was planned was called off.

At this point, I turned to my wife, and suggested that the next time we were going to move house we need to make sure that we write everything down on the same notepad, instead of each of us having our own…

Based on true-life events.


Why Virtual Events Matter – a post by Daniel O’Leary

I have started watching the presentations from the AIIM Virtual Social Business Conference. Even though I was not able to “attend” the conference live, AIIM are making all the sessions available for a limited time.

Thanks to a twitter feed that was running at the conference, I saw that Daniel O’Leary, an “AIIM Capture Expert Blogger” had written an excellent post on the value of Virtual Events.

Here is a link to his post…Why Virtual Events Matter

 

  • I’ve just signed up for…The AIIM Social Business Virtual Conference (markjowen.com)

The Use of Collaborative Software in Virtual Teams

I was delighted to discover a whitepaper by Eike Grotheer’s on “The Use of Collaborative Software in Virtual Teams”.

I’m interested in how “virtual teams” operate and work together, and so started reading his work. Then I realised that I had actually been part of his research. To gather data for his thesis, Eike had sent out  requests to participate in a survey in May 2010. (Google still has a cached copy of the survey). In November 2010, he sent out the results of his research. And I never looked at it!  (Kicking myself now, though!)

As I read Eike’s work I got even more excited – his research not only involved communication in virtual teams, he had used TAM (Technology Acceptance Model) to determine the effectiveness of the software.

(If you are not familiar with TAM (Technology Acceptance Model please check out my earlier posts: Predicting User Acceptance; and Applying (loosely) the Technology Adoption Model to a Real-Life situation)

Eike had used some pretty advanced statistical techniques to analyze his findings (Spearman’s rank correlation coefficient; Kruskal–Wallis one-way analysis of variance), and I won’t go into those in detail.

Survey Results Summarized
  • 265 people responded to the survey,
  • There was also a very large variety of tools in use (Microsoft Outlook, SharePoint, Microsoft Project Server, Lotus Notes, Lotus Sametime, Lotus Quickr, and Google Apps were all listed, along with other collaborative applications).
  • Most of the features that are frequently used can be split into two categories:
      • Tools for sharing and managing information (e.g.  document, content and knowledge management)
      • Tools for direct communication between team members

User Satisfaction and the Use of Collaborative Software in Virtual Teams

OK – this is where it started getting interesting. Eike rightly states that

the use of information systems can only provide a benefit to an organization if users first of all have interest in using them and then actually make use of them.

To try and explain this the Technology Acceptance Model was devised (refer earlier mentioned posts for more detail). It states that the a user’s intention to use a system is influenced by the perceived usefulness and  the perceived ease-of-use.

Eike analyzed these two determinants (perceived usefulness and perceived ease-of-use) to determine their impact on the use of collaborative software. (He points out that, as everyone who responded to the survey is already using collaborative software, the intention is already known, and that the use is measured.) 

Again, I won’t go into too much detail. In the survey there were 4 statements that were related to the perceived usefulness, and 4 statements that were related to perceived ease-of-use.

Performing a bivariate correlation analysis on the data from the survey, Eike was able to show that there was a positive correlation between the perceived usefulness and the actual use. This effectively proves (statistically) that the more users perceive collaborative software to be useful within a virtual team, the more they will use it. (Sounds logical, but then this fact means that the TAM can be verified).

Tackling the other determinant of the TAM, Eike did a bivariate correlation analysis between each perceived ease of use item, and the extent of use of collaborative software.

There was no significant correlation which meant that the ease of use of collaborative software  has only a minor effect on the usage behaviour. However, it wasn’t actually possible to draw a conclusion as the survey participants were all experienced IT users, and the difficulty of the software may not have prevented it being used.

Going further, Eike investigated the impact of TAM factors on project success. Again using statistics he was able to show that there was a positive correlation between perceived usefulness and project success, and between perceived ease-of-use and project success. This confirmed that a relationship between the use of collaborative software and project success does exist.

In other words, the more useful the participants perceived the collaboration software that was used in the virtual team to be, as well as how easy they thought it was to use, had a positive impact on the success of the project in all aspects.

Summing it up

Sometimes it is easy to think “well, that’s already obvious”, but I always find it valuable to be able to scientifically prove (in one way or another) what everyone assumes.

And that is why I found Eike’s research exciting. From a handful of well thought-out survey questions, he was able to scientifically prove that

if software is considered useful by its users, it enables them to become effective and productive in their work, and if it is easy to use, it enables them to make use of it straight away, and leads quickly to desired results. 

Other useful links:

  • Virtual Teams: Key Success Factors – Part 1
  • Virtual Teams: Key Success Factors – Part 2
  • Virtual Teams: Key Success Factors – Part 3
  • The Complexity of Virtual Teams

 

 

Social Media in Business

Life is social.” …  “Business is social.  People buy from people they like and they like people who know them.  When we meet someone in their office we look at pictures on their wall so we can share something in common.  We want to build intimacy and trust.  Social media is just an electronic way to listen and engage…extending the old school way of going to someone’s office.

The above is a quote from a Forbes article (by Gene Marks) that I recently read. The article was discussing the adoption of social media in business.

While it seems that there is certainly a lot of interest in using social media in a business sense, there just hasn’t been that “compelling reason” to adopt it without question.

However there are still those that seem to see a real benefit (as seen in the quote above”, there are still a lot of people who don’t.

From what I’ve seen, business is still being run by a generation that hasn’t grown up with the web2.0 “idea”. And…there still isn’t a real business use that makes “C” level staff decide to implement it, without trying to work out first what they are going to use it for. (For some ideas on this, check out one of my earlier posts “ESS (Enterprise Social Software) – user adoption“)

Here’s the link to Gene’s post: Am I Wasting My Time On Social Media?

  • My Social Media posts
  • 3 Critical Twitter Tools for Your Social Media Strategy
  • Social Media: Making it Work for You
  • Wanted: A social media expert?!
  • Five Fundamentals of a Social Media Strategy

Comments on “The Problem with Shared Network Folders”

Adrian McGrath recently wrote a post calledThe Problems with Shared Network Folders“.

It’s a great post, and Adrian is someone that I have a lot of respect for. He’s a smart guy, and I learn a lot from him. In the post (read it here ), Adrian discusses the disadvantages and limitations of using Shared Network folders.

These include:

  • Duplication of documents and confusion as to what the latest version is
  • Complex file and folder naming conventions 
  • Lack of consistent folder structures 
  • Redundant documents 
  • Ineffective search
  • Inaccessibility of information
  • Lack of subscription and notification
  • Limited ability to synchronise documents offline
  • Inability to cross reference and relate documents
  • Lack of document governance and control
  • Compliance, Risk & Legal Admissibility 
  • Impeded collaboration
  • Storage and maintenance costs

In essence Adrian is correct. Using Shared Network drives does have limitations, but in the spirit of debate, I’d like to make a few comments on what he says.

Duplication of documents and confusion as to what the latest version is.
Complex file and folder naming conventions
Lack of consistent folder structures
Redundant documents

These are all indeed real problems. Are they inherent to Shared Folders? Not really – these can also happen with Document Management Systems.

Governance plays a large part in ensuring that these sort of things do not happen. Information Architecture is critical in ensuring that a suitable structure exists, defined by folder, and metadata, so that every document has a correct location.

However, this does require enforcement. Without enforcing such a system, even EMC systems can end up overly complex and with duplicated (and therefore redundant) documents. A lot of these systems, however have de-duplication functionality built-in (Documentum), and, if not (SharePoint), there is often a third-party tool that will do this.

Ineffective Search

Can’t argue with this. Unless some sort of indexing application is implemented, searching will be very inefficient.

There are many applications that allow Shared Network folders to be indexed. These include applications such as Google Desktop, Windows Search, X1, etc. SharePoint, also, has the ability to index information in file shares, as well as making the search results a little bit more meaningful.  

Inaccessibility of information

Adrian is definitely right here. Most (if not all) companies are quite strict with their network security. Users are not able to make ad-hoc changes.

However this can also occur in an ECM system depending on how much “freedom” a user has. I have seen some situations where, because the security policies in the ECM system were so strict, that users have resorted to exporting a document to a file share, so that it can be shared with others, or worse, e-mailed to an external party.

A good governance model helps to reduce this, as does training. If the users are aware of why something is enforced then there is, often, a better chance of compliance.

Lack of subscription and notification
Limited ability to synchronise documents offline
Inability to cross reference and relate documents

No arguments here

Lack of document governance and control
Compliance, Risk & Legal Admissibility 
Impeded collaboration

I’ve mentioned governance in my comments above. A good plan is required to ensure that documents are not haphazardly placed in seemingly random locations. And, as Adrian mentioned, Most ECM systems provide an audit trail keeping a record of the “actions” upon a document (when a document changes status, etc).

However, this is only effective for versions of the documents that are within the document management system. Once it is outside of the system (a user exports, or e-mails, a document) there is no audit trail. (Often this is done to collaborate with someone who does not have access to the ECM system.) This can create compliance issue. Again – good training, and governance, helps to reduce this risk.

Storage and maintenance costs

As Adrian mentioned, the amount of storage space required in a file share can be quite high, as users store more, and more content. And he is correct that because of the scattered nature of such content, this leads to inefficiencies.

ECM systems tend to handle the storage of content in one of two ways:

  • Content is stored in a file system on a hard drive. Usually the content will have some meaningless name, and might also be encrypted. Metadata about the content (including it’s location) is stored in a  database. Access to the content is via the CMS (native interface, or API).
  • Content, and metadata, are stored in databases. The content is usually stored as a BLOB.

If the ECM system is configured to keep create a version every time a document is checked out, and then checked back in again, the number of “duplicate” versions can increase quite quickly, thereby requiring extra space. Of course, setting a lower limit for the number of version kept can help reduce this. Configuring the system to purge all minor versions of a document (e.g. 0.1, 3.2, etc) when a major version (e.g. 1.0, 3.0) is created also ensures that disk space is kept to a minimum.

Keeping documents in the database as a BLOB also presents extra maintenance. As with a file system, the databases can grow exponentially. Often extra work is required to ensure that the database still performs efficiently.

Conclusion

I am convinced that to be able to keep content in a system that allows adding meaningful metadata, auditing, security, document life cycles, and workflows, is critical if a business needs to track, control or route content. Often these activities will exist to match the requirements of a business process, and to make it more efficient.

However there are a few situations where using a file share is still of value.

In my next a later post I will go into this more…

  • Is unauthorised use of file sharing solutions putting organisations on a slippery slope?
  • What Enterprise Content Management Technologies Do Manufacturing Companies Use?
  • Enterprise Content Management (ECM) 101
  • Using a network file share – a case study