1/18/2012
What a ridiculous thought. Or is it? A French Company is doing just that http://articles.businessinsider.com/2011-12-04/tech/30473966_1_abc-news-internal-emails-messages-employees
We all know that valuable information gets stuck and then lost in emails. And we know that email attachments cause duplication and confusion over what’s current. And now with eDiscovery, emails are a huge liability to a firm not to mention storage and back up of emails—another huge cost to any business.
So could your firm live without email. It is truly an intriguing idea.
The French firm is replacing email with a FaceBook-like tool and instant messaging. Would this be enough and would it solve the problems emails present today?
What tools could you use to replace email? I agree a FaceBook-like tool (although I would use LinkedIn as my example) would do a great job of capturing employee details – contact info, project experience, and skills. And the tool would be self-managed so the data should always be up-to-date. Instant messaging would help particularly in a dispersed setting – imagine an employee getting an answer to a question within perhaps seconds instead of searching and waiting for responses. But like email, I fear instant messaging will hoard and bury critical knowledge.
Ideally, any collaboration and communication tool needs to be mined for its valuable data. The information in instant messaging would need to be auto tagged and stored in manner so others can find and use it quickly.
In my ideal world, I can see every project having a dedicated site where all communication and collaboration could take place, be retained and mined later for reuse. And each employee assigned to the project would be linked to their profiles. The same would hold true when working with clients. One place (site) where you capture all communication and collaboration and all without email!
A world without email…quite an interesting thought! 11/2/2010Names identify, categorize, define. A single name such as Aristotle or Napoleon reminds us of stories from history books. Using the word requirement or notes in a file name leaves no second guessing the type of information stored in that file.
For years, best practice indicated organizations should adopt a file naming convention, making content identifiable and accessible to all. Often, naming conventions addressed versioning. To version a file might require including a date, a major/minor version numbering scheme, a reviewer’s initials, etc. in the file name. Many organizations implemented naming convention requirements and many of us learned to work within these guidelines.
Then, along came content management tools such as SharePoint. SharePoint stores information (metadata) about who modified the file, what date it was modified, and the version number. If versioning is enabled, we can see what changed within each version of the file and can use minor and major versioning along with workflows to enhance file tracking during the edit process. And, the most recent version of a file is always visible. The need for a file naming convention still exists, with the versioning part now handled by the technology.
But, we have trouble breaking old habits. Just as our first instinct was to create folders to be used to store files in document libraries, we also instinctively add versioning information to the file name before we upload it into the library. In doing so, we usurp SharePoint’s capability to track and store versions for us. The end result is a document library that is cluttered with multiple versions of files, requires great scrutiny to identify the most current file, might contain out-of-date files that are linked to another SharePoint site, and is no better than the file share we left behind when we moved to SharePoint.
Following are suggested best practices for managing files using SharePoint:
- Companies should standardize file naming conventions to clearly indicate the file contents.
- File names should not include dates (unless it’s tied to the content, ex: Nov2010 Sales Report), reviewer names or initials, or version numbers.
- File reviewers should never modify the file name during the edit process.
- When the document library is created, file versioning should be enabled.
- File reviewers should always check out files prior to making edits and include meaningful review comments when checking the file back in.
Does this scenario sound familiar? How are you managing files using SharePoint? 10/12/2010We recently became an authorized vendor for Microsoft’s Business Productivity Online Services (BPOS), which includes SharePoint MOSS 2007, Exchange, LiveMeeting and Office Communications. As an authorized vendor, we are able to utilize this software for our company--which allows us to try before our customers buy.
The concept is perfect for small-to-large businesses who don’t want to host their own software. You can access SharePoint and Live Meeting for collaboration, and Exchange and Office Communications to email or text message your colleagues. These applications are integrated and managed using an online Administration application, which allows you to add and manage users, create SharePoint Site Collections, and manage the volume of information stored in these applications. All good so far.
For this discussion, I will focus on the SharePoint portion of the Cloud. Within your allotted disk space, which is determined by you when you purchase the service, you can create Site Collections with multiple SubSites. You can setup User Groups to control access permissions, and can modify the look and feel by uploading or editing style sheets using Microsoft SharePoint Designer. Many of the features that we use all of the time when creating Sites are available--web parts, lists, libraries, versioning, audience targeting, and alerts--to name a few. And, the best news of all is that it is relatively inexpensive in comparison to other Cloud providers and your costs for supporting SharePoint in-house disappear.
So, where do we see limitations? We have only found three.
The first issue, and a big one for us based on our business model, is that SharePoint in the Microsoft Cloud doesn’t work well as an Extranet. We setup Customer project sites, give access to our customers, and collaborate on projects using SharePoint as if we were all co-located or at least all part of the same company. Microsoft requires all users to be part of one single domain and only supports using the Microsoft Online Services Sign In application for single sign-in access. So, ok, we can add our customers to our domain so that they can access the Site. BUT, you notice this is a big but, the sign-in requirements can make it difficult for our customers who are not permitted to download the Sign In application to their work computers. SharePoint access can still be obtained without the Sign In application, but the user might receive multiple sign-in requests and access might fail. The multiple sign-in requests are not a show-stopper, but they’re not optimal either. And failing access? That’s unacceptable.
Second, you cannot install third-party web parts. This is because you do not have server access. We use SharePoint out-of-the-box as much as possible. We consider third-party web parts to be a smart extension to the out-of-the-box functionality. No coding is required, they’re supported by the supplier, and they fulfill needs where the out-of-the-box functionality falls short. This one has no workaround and can be a show-stopper if the functionality you desire is not supported by Microsoft.
Finally, as I mentioned at the beginning of this blog, SharePoint in the Microsoft Cloud is still the MOSS 2007 version. However, they plan to upgrade their BPOS to include the 2010 versions of the software sometime this year. One announcement even indicated availability at the beginning of 2011. And, as part of the upgrade, the issue of using SharePoint as an Extranet should be resolved!
All in all, we have found using SharePoint as part of the Business Productivity Online Services to be a beneficial experience for our company. It fulfills most needs, is cost effective, and is perfect for small-to-large businesses who don’t want to support SharePoint in-house. 10/8/2010
Since the introduction of file shares, we have become creatures of habit. We create folders, sub-folders, sub-sub-folders, sub-sub-sub-folders, and store all of our project documents in these folders—meeting notes, requirements documents, test procedures, customer intel—you name it. When someone asks us for a document, we sometimes know where it is, but most times we don’t.
Search for it? Yeah, that’s done by hand. Open a folder and look—not there. Open another folder—nope, not there either. So we keep looking…and wasting time…
For many of us, file shares have been replaced by SharePoint. We are told to use SharePoint to help us manage our documents, to collaborate with our teams, to enable sharing of documents regardless of location, and the first thing we do is…you guessed it…create a folder. And so the power of SharePoint becomes limited by our habit, and we complain that SharePoint makes our jobs harder. I’m here to tell you that there is a better way!
SharePoint allows us to create “Views” of documents. Views are not a new feature, but we’re constantly surprised by the number of SharePoint users who don’t know how to use them—or don’t know that they exist.
Need to find project requirements documents? Not a problem. Want to review all meeting minutes? Got that in a second. How is this done? By creating a View that uses metadata, filtering, sorting and grouping. The filtering, sorting, and grouping is easy. We’ve done this all of our lives. The metadata? That requires planning.
In this example, I have documents of several types: requirements, notes, and procedures. I can create a column in my library called Document Type and add these types as the values for this column. When I upload a document to the library, I choose one of the types (the metadata), which categorizes the document.
Now that my documents have been categorized, I can filter, sort, and group them using Views of these documents to meet my needs. I can create an All Requirements view that filters the library so that only documents tagged as requirements are visible. I can create an All Documents view that groups the documents by category (requirements, notes, and procedures) and can choose whether to collapse or expand the group to either hide or show the documents when the View is opened.
The possibilities provided by Views are endless…as are the opportunities to find your documents without digging through multiple levels of folders and wasting valuable time. 9/22/2010
I knew it would happen, but who would have thought it would happen so quickly. Information Week just reported that in just the last year 72% of organizations are now using Wikis and Blogs for communicating with their customers, partners and suppliers. This is up from 43% just a year ago. What a jump!
This goes right in-line with i-Squared's white paper on Unstructured Information -- Quiet Killer or Profit Opportunity.
If you are doubtful about how the new Web 2/3.0 technology is going to change your business, you need to read these articles:
Information Week Article
| Edit in Browser | /_layouts/images/icxddoc.gif | /blogadmin/_layouts/formserver.aspx?XsnLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | FileType | xsn | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /blogadmin/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /blogadmin/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.2 | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /blogadmin/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.3 | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /blogadmin/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.4 | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /blogadmin/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsx | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /blogadmin/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsb | 255 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /blogadmin/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsx | 256 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /blogadmin/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsb | 256 |
|
|
|
|