6/26/2010
MicroWorks has been deploying SharePoint solutions for our clients since 2001. Our SharePoint and IM practice continues to grow, and we are looking for an experienced SharePoint Specialist to join our team.
1/19/2010
The association for enterprise content management (AIIM) has produced a white paper on the 10 excuses given by managers for not introducing document management. Basically it says that managers need to be convinced to do document management because they:
1. Aren’t concerned about how long staff are spending looking for information.
2. Aren’t worried about being sued and having to produce critical records.
3. Aren’t concerned about how much it’s costing staff to create, file, search for and reproduce lost documents.
4. Aren’t concerned about the cost or environmental impact of photocopying documents (the average for a document is 19 times).
5. Aren’t concerned that staff are spending 1½ hours per day on average managing email.
6. Are happy to fly everyone in for meetings at which everyone has a different draft of the document being discussed.
7. Don’t worry about losing information in a disaster.
8. Aren’t that concerned about information security.
9. Don’t think process automation is cost effective.
10. Don’t think that managing documents is as important as managing financial information and HR systems.
After reading the paper, I felt more than a little insulted on behalf of managers everywhere.
I’ve been working in the IM field for a long time and have talked to many managers about their corporate information. The managers I talk to are more likely to be lying awake at night worrying about these very things.
The most common concerns that I hear from managers are:
1. I know we have problems and I don’t know how to fix them.
2. We’ve tried different systems and people don’t use them.
3. Everyone’s too busy right now to take this on.
My responses to these concerns are:
1. Many organizations are facing the same problems, and they can be fixed. There are best practices out there and there are professionals who know what to do.
2. You need a good system that is integrated with the tools people use every day, that isn’t overly complex, and is introduced in phases. 100% adoption has to be the goal from day 1. You need to involve users in defining the solution. They need a sense of ownership over the solution that is introduced.
3. Treat it as a project, and find the best time to do it. Management has to make it a priority. The project doesn’t have to over-tax your people, but they know the business and have to be involved in defining a solution that will work for them. You can bring in the experience you need to put fresh eyes on the problems and help select and implement the best solution.
When it comes to managing information, often small changes can have a big impact. Bite off manageable pieces to tackle, and tackle the high impact ones first. The rest will follow. 10/28/2009
By Jill Austin, Director, IM Practice
Microsoft has at last unveiled features of SharePoint 2010 and there are lots of exciting improvements. Some of the highlights (from an information management wish list perspective):
· The Ribbon is integrated throughout SharePoint.
· Compliant, accessible (WCAG 2.0) XHTML for browsers including IE, Firefox, Safari and mobile browsers.
· Social networking includes managed taxonomies and folksonomies, expertise finding, content rating, commenting. Improved wikis and blogs.
· Much improved search with FAST integrated. Previews of Office docs in search results.
· Records management integrated into document libraries. Documents can be locked for changes and have multistage lifecycle. (Yeah!)
· Document sets can create collections of documents with shared metadata (Yeah!)
· Million-plus item lists, and ten-million item libraries.
· Taxonomy management and ability to drive metadata into documents automatically (e.g., based on folder); automatically route documents into the right library (Yeah!)
· Service Applications manages content types and taxonomy across sites, collections, web apps, and server farms.
· Multiuser editing with shared visibility of real time changes in Office documents.
· KPIs, available in all sites, can be used track project status. (Yeah!)
· Performance Point Services integrated into SharePoint. Interactions with PivotTables, sparklines and slicers in Excel.
· SharePoint Online for Internet Sites will host public Web sites
· Mission critical Access applications and Visio diagrams can be hosted by SharePoint.
· Sites are now made up of pages in a library, and each can be edited inline. Much improved themes and branding tools for sites.
All pretty exciting for those of us living in SharePoint day and night! Still hoping for better integration between Outlook and SharePoint – will find out more over the next few months. The public beta will be available in November and we will want to try it out for ourselves and provide more info at that time.
by Jill Austin, Director, IM Practice
We’ve been talking and hearing about knowledge management for years. It was an idea that was ahead of its time, in many ways. Companies tried to implement mega-KM projects that were really destined to fail because they were trying to boil the ocean. Most solutions didn’t have a good answer to the ‘What’s in it for me?’ question – something busy people will always ask.
Several things have re-energized the quest for corporate knowledge management. One is the emergence of social media, providing better tools for building collective intelligence. Another is the influx of a new generation of workers who expect (demand?) knowledge sharing and a collaborative work environment. Related to that is the tidal wave of Boomers retiring – and taking their 30 or 40 years of experience with them. It’s a truly scary prospect having all the knowledge walking out your door.
Over the past few months, I have been reaching out to organizations in Ottawa to find out what KM initiatives they have underway. Everyone likes to talk about what they’re doing and everyone is hoping someone else has a better idea.
One suggestion I’ve heard is to form a KM community of practice (CoP) in Ottawa. I think we need one that is open to everyone and is not sector-specific (not just public service or NGO’s, for example).
This is the place to go to ask who’s doing corporate wikis and how are they working out? What are you doing to capture lessons learned and best practices? What policies have you instituted for staff about use of social media tools?
MicroWorks is willing to host a CoP site to help get things started. Face-to-face meetings would be great, too – maybe find a nice pub for get-togethers!
If there is someone in your organization who is interested in knowledge management, please send them this blog.
If you’re interested in sharing experiences about managing knowledge in your organization, send us an email: admin@microworks.ca. Give us any ideas you have about what you’d like to do and how you’d like to do it.
Looking forward to hearing from you! 7/16/2009
by Jill Austin, Director, Information Management Practice
During the conference, I’ve been trying to glean what I can about Office 2010. What I’m hearing is pretty exciting and music to my ears as an IM specialist. Here are some of the notes I’ve made:
· Exchange 2010 will have voicemail and email archiving, voice to text conversion in local languages, and email will have retention policies and ability to enforce legal holds (established by a designated compliance officer).
· PowerPoint Broadcast is the name for PowerPoint 2010 and it has all kinds of cool features added to enliven presentations.
· Word 2010 features simultaneous edit by multiple authors. You check out sections of a document and then synchronize changes (“collaboration with control”).
· Excel 2010 is phenomenal. They demonstrated on a laptop, a spreadsheet with 100 million rows in it (yes, that’s 100,000,000 rows!) and the ability to create pivot tables and extract data in seconds. The audience was totally wow'd.
· SharePoint 2010 clearly demonstrates that this is the platform for Microsoft moving forward. The message here is - if you’re not on it now, you'd better get on it soon. It’s the storage backend for all these other apps and the integration between them is pretty seamless.
· Because of the success of Excel Services in SharePoint 2007, Visio, Word and Access Services are being added to SharePoint 2010.
This morning’s keynote included a presentation by a senior researcher from Microsoft. This guy looks like a cross between the crazy scientist in Back to the Future and crazy scientist in Independence Day. His presentation was fascinating.
He talked about the future of computing and demonstrated with technology that is prevalent throughout the conference centre: Microsoft Surface. This is the flat panel where you use your hands to extract, move, and combine documents, images, etc. If you saw the last James Bond movie or the movie Minority Report, then you’ve seen this. We’re all using it at the show to share business cards (no more physical cards) and get updates on conference events, local weather, bus schedules, and so forth.
If you have a few minutes and want to see something pretty cool have a look at this video. Everything in it is technology that Microsoft in working on now (expect to see this within 10 years). http://www.officelabs.com/projects/productivityfuturevision/Pages/default.aspx (click on Watch the Video and select the Watch as WMV for the best picture). 6/26/2009
By Kendall Lougheed, President, MicroWorks
I just attended a SharePoint users group meeting the other day and I walked away with the feeling that I had stepped through a time warp from 25 years ago. The room was filled with all kinds of people but the presentation was for developers about how to get this done or that done. And then I thought about all the SharePoint projects that get over-engineered, then stumble or even fail. So how is it that one company (ours, I say immodestly) can bat 1000 for successfully adopted collaboration and document management systems in a relatively short time while others seem to take forever and even end up being abandoned. I have an opinion that I would like to share.
Fundamental Mistake Number 1 – “Build it and they will come.” Let’s do an intranet, put up some information and people will get drawn to it over time. Sigh. Busy people do not have time to poke around a web site and see if anything useful will show up eventually. That intranet better be purposeful right away or you lose your chance just like that. Do not let your developers or your IT staff guess at what your organization needs. No matter how smart they are (and they are usually very smart), they are not the voice of your business needs. Nope, this approach is dead in the water.
Fundamental Mistake Number 2 - “Let’s make a list of our requirements.” In its best form, this involves business analysts, consultations, senior level involvement. Sounds great but all too many companies end up with a list of requirements, compare them to SharePoint’s capabilities then abandon or build. Both can be a big mistake. The requirements list ends up like a shopping list written when you’re hungry – lots of everything whether you need it or not. I believe in business analysis but not the shopping list kind.
Fundamental Mistake Number 3 – “Let’s get an IM expert to figure it out.” Yes, maybe. But do you really want to go to an extensive document management system with full workflow controls everywhere, and with compelling all your users to type in metadata until they are blue in the face? Look how many excellent RDMS solutions there are out there and users hate them. Notice how they have tended to move their documents from the corporate RDMS and back to the email system or their C Drive?
Keys to Success If you want a successful, relevant document and collaboration solution be sure to do the following. Begin with a good visioning exercise that involves all levels of the organization. We have huge (100%) success with our process because it builds vision, momentum and consensus very quickly. Next do your business analysis but ensure it has an effective facilitation component so that minor needs do not falsely become major needs. Include a priority setting exercise to identify the most impactful solutions for quick wins and initial deployment. Focus on adoption – users are not willing to take very long to apply metadata or to fight with a taxonomy they do not understand or care about. Most important, focus on simplicity. I will go on record to say that over 90% of what users want when it comes to identifying, collecting, managing, and reusing content is captured right out of the box in SharePoint. 5/28/2009
by Jill Austin, Director IM Practice
One of the things that we have learned from our years of implementing SharePoint solutions is the importance of having a governance plan. Often people just want to get started with SharePoint, usually to solve a pressing problem. One of SharePoint’s strengths is the ease with which you can ‘just get started’, particularly when implementing Windows SharePoint Services (WSS). If you’ve done sufficient planning, requirements definition and design, then you’re ahead of the game. But, you will still run into problems very quickly unless you have a plan for governing the new system.
Your new SharePoint is a living thing. It has to grow and change with your business over time. You have to plan for this to happen and do the planning before you release SharePoint to your organization.
What are the elements of a governance plan?
· A SharePoint roadmap to plan for new features in future releases, such as integration with other business applications or an extranet for collaboration with stakeholders or customers.
· Custodians defined for all the evolving elements: portal pages, metadata, navigation and taxonomy, collaboration sites, document libraries and lists, records centre.
· A SharePoint Administrator defined and trained to manage the server, user access, monitoring reports, and system upgrades.
· Standards established for any development on the SharePoint platform.
· A training plan to ensure that all users (current and new hires) know how to use the system and understand their responsibilities with respect to the content in the system.
· Ongoing monitoring to ensure that the system is being governed according to the plan, and that the plan is renewed periodically.
Establishing governance is straightforward. The sooner you do it, the better – and definitely do it before your system goes into production.
When it comes to SharePoint, give us a call. We can help. 4/14/2009
by Kendall Lougheed, President
The word “SharePoint” can be heard every time you go near IT people these days. Just in case you don’t know what it is, Microsoft SharePoint is a web-enabled portal that acts as a repository for your corporate information. Just as Windows is the interface to the applications and files on your computer, SharePoint is the window to your corporate applications and data.
But SharePoint has become a kind of Holy Grail. Microsoft touts it as being the most successful software for many years with many millions of licenses sold. Everybody who doesn’t have SharePoint feels lacking and wants it. Executives want to say they have SharePoint just like they wanted email and web sites on their business cards when the web was first popularised.
And SharePoint can do so many things. Open up the box and you will immediately see a nice web site with a folder system for storing documents, a list of upcoming events, a list of contacts, a search box, news items, social networking, and dozens of other “web parts”. Rather like a large hardware store with so many tools.
Great, we’re all excited and we’re all on board but what does it do? And there’s the rub. SharePoint does everything and nothing. At the Montreal Summit that ended yesterday (April 8, 2009), we heard presenters, architects, developers, and corporate users talk about what I shall call “re-purposing SharePoint.” And it sounds just like the early days of the World Wide Web when the excitement of a single static page captivated our imaginations. But just for a while. Now everybody is clamouring to build the next version, this time with a clear purpose.
As a corporate intranet, many users threw together a site with a little corporate information, HR policies, and maybe a travel claims form or two. All static, nothing comprehensive, and nothing central to the information worker’s day-to-day life . “Build it and they will come” said many – a common mistake. Well, maybe people came, but they didn’t come back. It was like the old days of silent movies with Fatty Arbuckle and his crew playing baseball all day until somebody got an idea for the next scene.
Communities of practice, communities of interest, workgroups, collaboration groups, idea building. All great notions and I am loyal still to these concepts from my early days studying Communications at University. Many collaboration initiatives are not that active. Adoption is a big problem, and people are concerned. Often collaboration initiatives are like a membership to a health club. You know it’s good for you and you pony up your membership, but in the end you never seem to get the time.
The good news at the conference is the re-awakening of everybody who has been involved for at least one full iteration. The Summit revealed new thinking on this that is deeply concerned with adoption, introducing best practice document management, analysing and implementing workflows, and aggregating data from the financial and CRM systems. And there are many tools being developed to help overcome the limitations of SharePoint and to help integrate more information from more applications.
And the best news is we are starting to see best practices emerge. These best practices are looking well outside the developer world and into the worlds of business analysis, IT strategy, visioning, communications, library science, and document management. The studies have always shown great potential for considerably improved productivity. Just like the movies, we are in the age of talkies and colour. We know we can do great technical production, but most importantly we know that we need a good script.
Kendall.Lougheed@MicroWorks.ca 1/6/2009
This is the first in a series of blogs about how to ensure successful SharePoint deployment. At MicroWorks, we’ve been building SharePoint solutions and working in SharePoint since version 1 in 2001. We’ve distilled this experience into a number of best practices.
SharePoint is transformative for your business. You are introducing a knowledge management system, not just a place to store documents. It is an opportunity to achieve integration of information across the enterprise. If you under-scale or over-scale the implementation, your SharePoint deployment may fail.
Under-scaling is doing a deployment that is too small in scope, or provides a solution that has low impact and low priority for many users. You end up with a big yawn for users who barely notice the new system – and management wondering what all the fuss is about. Over-scaling is doing a deployment that tries to boil the ocean and affects many business units at once. This is a high-risk proposition in terms of project management, user engagement, and achieving a high impact business solution in a reasonable time period.
We recommend identifying a series of projects to implement SharePoint across the organization in phases. First look at the big picture, then break it into a series of manageable projects with business partners for each project, e.g., HR, Admin, Sales and Marketing, Board and Senior Management, Communications, Policy. Each project should have a willing business partner, a well-defined scope, and an anticipated high-impact business result. This lets you manage project scope, implement in a reasonable time period, engage users in the project without over-taxing them, and focus on what is most useful and most important to that business partner. With completion of each successful project, management gains confidence, a ‘buzz’ builds about SharePoint to encourage more business partners to engage in the process, and you are getting incremental improvements in productivity within the company.
Future blogs will look at defining requirements, implementing using prototypes, change management and user adoption, and SharePoint governance.
Jill Austin, Director Information Management 11/9/2008
I’ve been working my way through the Microsoft Office SharePoint Server 2007 Best Practices book, published in June this year. Great book, but at 900 pages, takes some time to digest. It provides some rather startling statistics about document management:
- Over 30 billion original documents are used each year in the U.S.
- 85% of documents are never retrieved.
- 50% of documents are duplicates.
- 60% of documents are obsolete.
- For every $1 that a company spends to create a final document, $10 are spent to manage the document creation process.
- The cost of documents to corporations is estimated to be as much as 15% of annual revenue.
With numbers like these, it's clear that we need to invest in managing our information. The cost of creating documents is significant. Recreating documents that already exist or will never be used at all is an incredible waste of corporate resources. Spending time culling through huge numbers of obsolete documents to find current information, and the potential damage from inadvertently using obsolete information, has to be factored into the cost.
Consider introducing best practices for managing your documents, such as document naming standards, better document organization, version control, document properties to improve search, and enforcing retention and archiving. Give us a call if you’d like to talk about improving document management in your organization.
Jill Austin, Director, Information Management
| Edit in Browser | /_layouts/images/icxddoc.gif | /blog/_layouts/formserver.aspx?XsnLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | FileType | xsn | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /blog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /blog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.2 | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /blog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.3 | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /blog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.4 | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /blog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsx | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /blog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsb | 255 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /blog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsx | 256 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /blog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsb | 256 |
|
|
|
|
|