Force Left Nav To at least 200 Pixels wide

 Other Sites

  Best Practices Conference
  Mindsharp
  Summit 7 Systems
Force Body To at least 500 Pixels high
SharePoint MindsharpBlogs > Bill English
SharePoint Cafe

 Last 10 Posts

Jan 25
Published: January 25, 2010 14:01 PM by  Bill English   Powered by: Mindsharp and Summit 7

Registrations for the SharePoint Best Practices Conference will open on March 1 at www.sharepointbestpractices.com. This event will be help August 24-26 with a post conference on Friday, the 27th. We'll be updating the web site and getting going on lining up speakers and topics for this conference. Be sure to include the SharePoint Best Practices conference in your line up of educational events this year. It will be held at the Reston Hyatt, outside of Washington, DC.

More details will follow as they become available.

Bill English, MVP



Jan 23
Published: January 23, 2010 13:01 PM by  Bill English   Powered by: Mindsharp and Summit 7

When you stop to think about it, what is needed in order to have a robust Enterprise Content Management System? Would we not need the following, at a minimum?

  • Ability for users to create and manage content areas
  • Ability to upload information into the system with a low transaction cost
  • Ability to directly manage that information
  • Ability to find information in the system with a low transaction cost

In other words, how information goes into the system (Putability) will directly impact how the information comes out of the system (Findability). A good Findability architecture is built on a good Putability architecture, just like a good restore system is built on a good backup system.

In SharePoint Server 2010, there are three main part of the Putability architecture:

  • Managed Metadata Service
  • Content Organizer Feature
  • Default Metadata Values

When these three features (small "f") are utilized together, they for a coherent way to describe and place information in such a manner that it can be found easily. We find information mainly through search and navigation tools, though other tools like RSS, links, shortcuts and the like can be useful in finding information. But until SharePoint Server 2010, we've not had the tools embedded within the product itself to implement a robust Putability architecture.

Now that SharePoint Server 2010 has both robust Putability and Findability tools, I believe the market will begin to take seriously SharePoint Server 2010's ECM features. But make no mistake, a great deployment on paper coupled with sincere intentions on the part of those who are doing the implementation won't be enough to achieve success. Instead, they will need to manage (overcome?) the following ECM busters:

  • Lack of Governance (and its' enforcement) on how information will go into SharePoint
  • Lack of funding for a project that is hard to quantify the savings in real dollars
  • Lack of ongoing care and feeding of the SharePoint Server 2010 information management system
  • Resistance at the desktop to take the time to apply metadata to information
  • Lack of an overall Glossary on what the metadata column titles and value choices mean across the enterprise
  • No agreement between the stakeholders on what their overall end-result is supposed to be
  • No agreement between the stakeholders on the business requirements for improving the information management system

SharePoint Server 2010 provides solid reasons to choose it for an ECM system. I look forward to working with the community and our customers to ensure they implement ECM correctly, the first time, saving them serious dollars.

Bill English
MVP



Jan 23
Published: January 23, 2010 12:01 PM by  Bill English   Powered by: Mindsharp and Summit 7

What follows in this post is a brief sample of the type of courseware that Combined Knowledge and Mindsharp are writing for SharePoint 2010 as part of our participation in the World Education Alliance. If you're looking for SharePoint 2010 Training, we would invite you to join one of our Mindsharp or Combined Knowledge classes. Enjoy!

Why Publish Content Types?

There are four main reasons to publish content types. They are:

  • Consistency
  • Identity
  • Location
  • Lifecycle Management

Consistency

The first scenario is about consistency: Is it (the content type) the same across the enterprise? When one stops to think about it, content types and metadata are really about consistent governance and management and standardization of information in the enterprise. In other words, if I build out content type "A" in Site Collection 1, is it the same construct as when it is used in site collection 2? The MMS will answer this question in the affirmative and yet provide localized extensibility for greater usability of the content type in specific scenarios.

Identity

The second scenario is about identity: What is in the content type? When it comes to the enterprise, is this content type about the same topic with the same metadata? What metadata is in the content type? Understanding the construction of the content type helps us understand it's focus, purpose and meaning.

Location

The third scenario is about location: Where is this content type and how can I use it? The MMS will allow you to search for the content type, navigate to it, aggregate data with it and find data using it.

Lifecycle Management

The fourth and last scenario is about lifecycle: This scenario encompasses the creation, consumption and disposition of the content type in the enterprise. More specifically, the content type can be mapped to a document's lifecycle and then utilized across the enterprise in distinct ways. We'll use workflows to move the document from one lifecycle stage to the next, ensuring that compliance is enforced, tracked and audited.

Understanding Terms

The MMS has some terms that we'll use, so here are some terms and definitions:

  • Hub - A site collection designated as a "source" from
    which we share content types throughout the enterprise
  • Content Type Syndication - Publishing, sharing, pushing
    one or more content types across site collection, Web App.,
    and farm boundaries

Note that a taxonomy is not the same thing as an ontology. And ontology is the philosophical study of the nature of being, existence or reality in general, as well as of the basic categories of being and their relations. By contrast, when we refer to a taxonomy, what we're referring to is a hierarchy of objects that will likely include synonyms, equivalencies, parent/child relationships and metadata. In contrast, a folksonomy can be thought of as "free-form" without a hierarchy of terms from which to draw metadata values.

Content Type Publication

The core value of Content Type Publication is the ability to create a data element that has metadata, workflows and policies attached to that data element, and then publish it to the hub and from there, syndicate it to all web applications, site collections and sites in your farm and in child farms. For example, let's suppose your organization develops a policy that says all blog posts are to be expunged 12 months from the last date of modification. Well, you can develop a content type that includes that policy that will kick off a workflow to delete the blog post after 12 months. You'll then publish this content type to a hub and from there, syndicate it across your farm.

Publishing Content Types

Content Types are created within a normal content type gallery and then are "published" from a "normal" Site Content Type Gallery to a hub within the MMS. Each MMS gets one hub for CTS. If you need more than one hub in your farm, you'll need another MMS. It is not a requirement that an MMS syndicate content types nor is it a requirement that a service connection to an MMS consume content types from that service. Setting a site collection to be the hub enables necessary components on the hub for it to operate properly.

The elements that get published include the following:

  • Content Type with all the corresponding columns
  • Document Set Content Type
  • Policies
  • And workflow associations, but not the workflows themselves

You'll need to ensure the workflows are available downstream where the content types are going to be syndicated. Once those content types land in the destination gallery, they will be re-associated with the workflow(s). If the workflow doesn't exist in the destination site, then no assignment is made and the content type will function to the extent it can without the workflow.

For the content types that are on the hub site collection, you can perform the following actions:

  • Publish: this means that the content type is being syndicated for the first time
  • Unpublish: this means that the content type should no longer be in syndication. The effect of an unpublish action is that the content type is made read/write at the local level and is still available for use at the local level, but it's no longer available in a read-only version from the hub.
  • Republish: this action is used when changes to the content type have been made and you want to push those changes out to the consuming audience
  • Roll-up errors from consuming site collections: it is possible, in a scenario where there are thousands of content types being published from a single hub, that some content types will contain errors. In those instances, all of the consuming sites will report their errors back to the hub so that the content types can be fixed and republished.

From the consuming side of the syndication, you can:

  • Extend a published content type: consuming sites can add more columns to the content type in order to give that content type more specificity in the local environment
  • Derive from a published content type: this means that we can use that published content type as a place from which to inherit to create new, local content types
  • View import errors: this will allow the consuming site to view the errors that it is reporting back to the hub
  • Refresh all content types consumed from the Hub: this action allows the consuming site to erase all of the syndicated content types and perform a new, full download of the existing published content types from the hub. This can be especially helpful when the hub has been down or the consuming site has been down or connectivity has been lost and there is a need to capture all of the new, updated changes from the hub.

Setting up Content Type Publishing

There are several steps to setting up the MMS for content type syndication in your farm. First, you'll start at the site collection layer by associating the site collection with the MMS. The MMS is turned on from within Central Administration and the service-to-web application association is also executed within Central Administration. The site collection can be associated at the time the application service is created, as illustrated here, where we're creating a new human resource metadata hub at a new site collection called hrhub.

The MMS can use any site collection as its' hub for content type syndication as long as the owner of the MMS service has permissions to that site collection. The site collection hosting the hub does not need to reside in the local web application with which the MMS is associated. Once the hub is selected from within the MMS, the syndication service can be shared and all of the other consuming sites will need to consume from the shared services' hub. Technically speaking, the syndication is not a push technology, it is a pull technology. So the consuming sites pull the content types from the hub in a pre-configured frequency. That's why, in some ways, it's better to talk about the content types being published as opposed to be syndicated. However, be aware that the literature and informal blog posts will use both terms. In both cases, they are describing a publishing/pull architecture.

Note that the content types themselves haven't changed from SharePoint Server 2007 to SharePoint Server 2010. They are still data elements coupled with metadata, policies and workflows. The content type galleries, aside from some UI changes, also look to be pretty similar.

So, in our example in this module, we're going to create a new content type named "Candidate Evaluation Form" (not illustrated) and then publish it to other content type galleries where it can be consumed and the metadata can be extended. Since the publishing is at the content type layer (not the gallery layer), we decide to put all published content types in the hub in their content type group.

We derived the Candidate Evaluation Form from the Document content type to create a new content type. The Candidate Evaluation Form contains these unique metadata elements (not illustrated):

  • Job Number
  • Department Number
  • Hiring Contact

Once the service application is started, you'll find the publishing action in the properties of the content type itself, "Manage Publishing for The Content Type". If this link doesn't appear, then that means that the service is not started or this site content type gallery does not reside within a publishing hub. Recall that each Managed Metadata Service can have only one hub and that content type publishing is not a requirement in order for the hub to be installed and to operate.

When you click on the "Manage Publishing for this Content Type" link, you're taken to the managectpublishing.aspx. page. On this page, you're able to perform the following actions:

  • Publish
  • Unpublish
  • Republish

Because this is the first time this content type is being published, only the Publish action is available. Until the content type has been published, it cannot be unpublished or republished.

The most common scenario for using the unpublish/republish actions is when you want to update the content type by either adding metadata to the content type or deprecating metadata from it. You can also modify other properties of the content type, but those scenarios will be less common. So let's assume that you want to update a published content type with new metadata while retaining the current metadata on the content type. Here are the steps you'd take to ensure the new metadata is published:

  1. Unpublish the content type. This action will remove the content type from being pulled by consuming sites. Note that this action does not affect content types in consuming sites - their content types will continue to work as needed and as expected.
  2. Modify the content type as needed.
  3. Republish the content type: This action will put the updated content type back into the published role and the consuming sites will be able to pull the updates to the content type to their location and begin using the additional metadata

Consuming a Published Content Type

The first configuration element for the consuming site is to ensure the site is associated with the same application service. This is accomplished in Central Administration. Highlight the web application you wish to associate with the Managed Metadata Service application, then select Service Applications from the ribbon.

By default, all of the service applications appear in the Default group. But you can group the applications into different groups or you can select "Custom" and select your own mix of service applications to associate with the web application. In our illustration, we chose Custom and associated the HR metadata service and the user profile service with the Portal web application.

 

The act of consuming a content type that is published is a Site Collection Administrator act - in other words, you must have site collection admin privileges to set this up. The link you'll want to select under Site Settings is Content Type Publishing Hub. Note that in Beta2, these links in the site collection admin area are not in alphabetical order, so you'll have to hunt to find it.

That link will take you to the contenttypessyndicationhubs.aspx page. On this page, you will see the hub with which your site is associated. You can check the Republish all content types on next update check box if you wish or leave it blank. Leaving it unchecked will mean that you will not receive updates via the Republish action at the hub. Selecting the checkbox means that you'll re-copy all of the content types at the next update interval.

The update interval is run by the Content Type Subscriber timer service (one for each consuming site collection), which, by default, it set to run every hour at a randomized time between 0 and 59 minutes after the hour starts. You can customize the frequency of how often this timer service runs and, if needed, click the Run Now button (not illustrated) to force the consuming site collection to come to the hub and copy down the content types to their galleries.

Once copied down, the content type will appear under a pre-configured group called Published Content Types.

Once the content type is copied down to the consuming site, it can be extended with additional metadata and other, new content types can be derived from it. Moreover, only the Advanced properties are available on the published content type, with all of the other properties being set and controlled by the administrators managing the source content types at the hub. This means, for example, that you can't associate a different workflow with the content type than has been associated at the hub.

Notice also, that the interface will show the source of the content type to be the consuming site collection. This is because the pull action is a copy action, not just a set of pointers that point back to the source content type source. So the content type is copied and a new content type is created in the consuming site collection.

 

Bill English, MVP



Jan 18
Published: January 18, 2010 19:01 PM by  Bill English   Powered by: Mindsharp and Summit 7

Oce' has an interesting white paper on e-discovery and what I term litigation readiness. You can download the paper here (but you must register, something I don't mind doing). Key findings of the paper include the following:

  1. Attorneys agree that e-discovery preparedness is one of the most important functions of a corporate legal department (77%)
  2. Yet less than 50% have implemented any type of e-discovery preparedness via internal processes or technologies. Reasons for this varied, but the most prominent was that it took the lawyers away from case-related activities
  3. Law firms are developing e-discovery personnel to help their clients with litigation readiness
  4. Most in-house firms are nervous about working with their IT staff to help with mitigation of e-discovery risks
  5. 60% of organizations, according to their in-house counsel, lack a fully implemented records management program
  6. 35% plan to implement a records management program in the next 12 months

Many will be choosing SharePoint as their Records Management system. Many will people who understand the triangle of services: technology, information architecture and business processes. Firms that can deliver these three skill sets will be in high demand.

Small and large organizations alike are in the bull's-eye when it comes to e-discovery. The fact that one in five corporations will be sued this year is no laughing matter. Forget that most of the lawsuits are frivolous. Responding to them still costs time, money, energy and employee attention. The opportunity costs can be significant. Organizing information with a view to mitigating exposure to liability for e-discovery will become a sunk cost that can't be recovered. Yet, if you're one of the 20% who will be sued this year, you'll be glad you undertook such a project.

You can learn more about e-discovery and how to organize information in SharePoint by attending my upcoming seminar on February 15 & 16. If you'd like, you can email me offline (bill@mindsharp.com) to ask questions about this seminar.

Bill English
Mindsharp



Jan 18
Published: January 18, 2010 15:01 PM by  Bill English   Powered by: Mindsharp and Summit 7

When I go out and do design and architecture engagements with our customers, I'm routinely asked about staffing levels for their deployment.  Often, I'm asked about what other companies and organizations are doing to staff their SharePoint deployment and support needs.  So, after asking several customers if they would be interested in participating in a staffing survey and getting their consent, I thought I would post this and ask if others would be willing to participate in the same survey. 

The survey will focus on your current SharePoint staff relative to the size and type of your deployment.  In many organizations, SharePoint is "part-timed" within the same staff of those who support other applications. In some, it is full-timed. All you'll be asked to do is to estimate the FTE (Full-time equivalency) of the various SharePoint roles, then report on the number of SharePoint servers, number of site collections and size of content databases as well as if you have MOSS or a WSS-only implementation.  We'll also ask about the number of SharePoint users in your environment and the number of overall desktops too. That will help all of us understand SharePoint penetration in most organizations. We will not ask about salary information.

The survey won't take long if you have the information needed for the survey.  We'll releases the results back to those who complete the survey, but that means they will need to identify themselves in the survey to ensure that they have completed it.  If you want to participate, please respond indicating as much to me (bill@mindsharp.com) and we'll send you the link to take the survey. If you are on our mailing list, an email went out today about this. If you've not received the email, please check your Junk Mail folder and ensure that email from Mindsharp is white listed on your email server.

I trust you've had a great holiday season and that you're on a good track for 2010.  While it has been a difficult time for many businesses, it's also a great time to be thankful for what we have and to work harder to create a better future.  Take care and I hope to hear from you soon.  Please let me know if you have any questions.

Bill English
Mindsharp

 



Jan 17
Published: January 17, 2010 18:01 PM by  Bill English   Powered by: Mindsharp and Summit 7

I was working with the crew at DePaul University this past week and we talked for a while about the danger signs that would indicate the unhealthy use of a site collection. So I thought I'd share some of our conversation with you all. Many thanks to the talented team at DePaul University for their input in thinking through this with me.

Constant Need to Move Information Out of the Site Collection to Keep it Within Prescribed Database Ranges

This is actually a constant battle for several of our clients who must keep information for X number of years, but still need to have that information available for collaboration within the site collection. Recommendation: programmatically move the oldest information to a file server or other location so that the newest information can be developed and utilized within the site collection. Use Scopes in search to group the two locations together for fast retrieval of information.

URLs longer than 256 characters

We've know about this for some time, but it seems to me that URLs that are longer than 256 characters represent either a lack of good user education or an information structure that is too deep (or both). Wide, but more shallow site collections will help prevent this problem.

Lack of good end-user education

Despite what you might have heard, SharePoint is not entirely intuitive. Users need education, not only on how to use it, but also on how to use it within your environment (think Governance training here).

Installation of untested home-grown code

Note that I'm not against home-grown code being installed and utilized in your farm. What I'm against is untested code. Site collections with untested code = high potential for disaster. This was brought home (not by DePaul), but by our theoretical (and tangential) discussion of how much code should be tested in a lab before being deployed in production.

Wrongly Secured Information

I suspect that most people don't stop to think about the site collection owners having access to every document and list item within the site collection. If information is placed in a site collection to which the site collection owners should not have access, then you have wrongly secured that information. It should be moved to a site collection whose SC owners can and should be able to see the information.

There were more items we came up with, but this is all I can remember. Perhaps I'll get the rest of the list and post it here at some point. Thanks.

Bill English
MVP, Mindsharp



Dec 13
Published: December 13, 2009 16:12 PM by  Bill English   Powered by: Mindsharp and Summit 7

Mindsharp has developed UserVersity™, an end-to-end solution to help companies ensure that their end-user fully adopt SharePoint and that they become skillful in the use of SharePoint Products and Technologies. Kim Lund will be presenting this webinar. Here are the details:

Title of Webinar: "Maximizing SharePoint User Adoption - Equipping end users to confidently and skillfully leverage the new technology"

Overview: (30 Minutes) Are your users skeptical of the value SharePoint can bring to your organization? Do they continue to create work-arounds versus using the new technology? Do they lack the understanding of what SharePoint is all about? If this describes your situation, please let us share with you how to overcome slow or stalled out SharePoint user adoption. Mindsharp – a leader in SharePoint education –  has been helping hundreds of companies increase their use of SharePoint and provide real solutions that provide a high ROI. This webinar covers:

  • 10 Reasons SharePoint User Adoption is Slow
  • How to Overcome Slow User Adoption
  • Announcing UserVersity
  • Program Components
  • Call to Action

December 17, 11:30 – 12noon, CST

December 17, 1:30 – 2:00 pm, CST

If you need to roll out SharePoint to thousands of users, then this webinar is for you. Please plan to attend.

Bill English, MVP



Nov 12
Published: November 12, 2009 17:11 PM by  Bill English   Powered by: Mindsharp and Summit 7

I'm pleased to announce that the SharePoint Best Practices Conference for 2010 will be held at the Reston Hyatt outside of Washington, DC, August 24-26 with a post conference on August 27. Please mark these dates on your calendar. We'll be publishing a formal call for speakers in the near future and should have the web site ready for registrations within a few weeks. However, if you want to ensure that you have a registration at the conference or want to know that you'll be notified about the call for speakers, then please email me directly at bill@ebacompanies.com.

I look forward to see you there at the conference. It should be great time of learning and growing in our use of SharePoint 2010.

Bill English, MVP
EBA Companies



Oct 20
Published: October 20, 2009 16:10 PM by  Bill English   Powered by: Mindsharp and Summit 7

UserVersity is a turn-key, end user solution designed to propel end-user adoption and proficiency with SharePoint. UserVersity is Mindsharp's latest update in our end-user products. You can learn all about it on the Mindsharp web site.

Bill English, MVP
EBA Companies



Oct 18

I often read books and articles that are not technology related. Recently, my sister called me to recommend a book that she had started reading for her job in fundraising for non-profits. So, I took a look at "When Generations Collide" and found some interesting concepts on how the different generations view life and work and then began to think about how that would impact a SharePoint deployment. Not that everything I read is filtered through the SharePoint deployment experience, but after I had read several chapters, I knew that there were direct applications that we could use. What follows in this post are some raw thoughts that I'll likely refine over time.

What are Generational Differences?

General differences are cultural in nature and they reflect how different generations are raised, what their shared experiences are and what their shared values are. This book - and by extension our SharePoint deployments - will need to accommodate four different generations: Traditionalists, Boomers, GenX and Millennium (Gen Y?).

My main thesis is this: the differences in technology adoption between the generations directly impacts how SharePoint is adopted in the workplace and presents unique challenges for teams who work cross-generationally.

My main illustration: I was talking with a product team member about SharePoint adoption and brought up this idea of generational differences in a SharePoint adoption. Not surprisingly, she had not thought of this aspect of adoption. Then I asked her this: Are most of the people on the SharePoint product team (I'm referring both to server and services) under the age of 35? Her answer: "probably". Hmmm…. and are most of the people who are the decision makers about SharePoint above the age of 50? Again, her answer: "probably". Hmmmm….. It's no wonder that most decision makers for the purchase of SharePoint intuitively know that they need SharePoint (or something like it), but they have a hard time describing and verbalizing that need. Couple that with (usually) a lack of solid business requirements for a SharePoint implementation and we have the recipe for a less-than optimal implementation.

Let's first describe the three main generations in our workforce, then let's apply what we've learned.

The Traditionalists (1900-1945, workforce age 64-109)

  • There are 75 million traditionalists
  • Their Influencers were people like Joe Dimaggio, Joe Lewis, Rat Pack, Dr. Spock, FDR, Duke Ellington, Charles Lindberg, Edward R. Murrow, John Wayne, Bob Hope, Elizabeth Taylor, Betty Crocker & others
  • Places that became important to them included Pearl Harbor, Normandy, Hiroshima, Korea, Bay of Pigs, Midway, Iwo Jima
  • Events that shaped this generation: WWI, Roaring 20's, Crash of 1929, Great Depression, WWII, New Deal, Korean War, GI Bill

Things were scarce for this generation. They endured the depression of the 1930's (which was much worse than our current economic woes) and they fought two world wars. As a generation, they sacrificed for their country. For example, did you know that between 1941 - 1945 only 124 new cars were manufactured in the entire United States? Why? Because the auto companies pitched into the war effort by having their manufacturing plants churn out airplanes and other vehicles that the fighting men needed.

Their base value: Waste Not, Want Not.

A good single-word description for this generation is Loyal. They learned that by pulling together and denying individual needs and wants, they could accomplish amazing things. As a generation, they partnered with large institutions to win two wars, build the A-Bomb and send a man to the moon. This generation has high levels of faith in institutions, such as church, corporations, the government, the military and the lists go on. Patriotism is a given with Traditionalists. Over 50% of Traditionalist men are veterans and they lived in a world without social safety nets. Their neighbors were their safety nets and they learned to look after each other. They also learned that a top-down approach was the best way to get things done, so they know how to take orders and "get the job done".

In terms of management and work ethic, this generation is built on the notion that managers manage and everyone else follows. The top-down approach works with this generation. For them, most management models are build on a military model: the guy in charge gives the orders and the troops follow.

When SharePoint is introduced to Traditionalists, they will often have a reaction of not understanding why they need to collaborate with others on the team. Their understanding is that if the manager would make appropriate assignments and if everyone would just do their job, then the project will succeed. If you tell a Traditionalist that they need to use SharePoint to collaborate, they'll likely try their best at doing it, but don't count on them to live and breathe SharePoint. They would rather hold face-to-face meetings and hash things out verbally than to work asynchronously with others whom, sometimes, they may never meet.

The Boomers (1945-1964, workforce age 45-64)

  • There are 80 million Boomers
  • Their influencers were people like JFK, Nixon, LBJ, MLK, Rosa Parks, Deep Throat, Jimmy Conners, Beaver Cleaver, Manson Family, Osmond Family, Barbara Streisand, Janis Joplin, Captain Kangaroo, Beetles, Laugh-in, Bob Newhart and the Rolling Stones
  • Places that become important to them included Watergate Hotel, Hanoi Hilton, sit-ins, love-ins, Woodstock
  • Then came the suburbs: the boardroom, the bedroom, the delivery room and in time, Divorce Court.

This generation experienced an explosion of things: Bell bottoms, mood rings, TVs, microwaves, Brooks Brothers, Rolex, junk food, junk bonds, LSD, MJ, etc… Their reference points were vastly different and unknown to their parents: TV shows, movie characters, plots, advertisers and products. Because of Vietnam, Watergate, women's rights, OPEC, stagflation, inflation, recession and gas lines, their faith in large institutions waned and this led to significant inter-generational conflict, both at home and at work. Consider the lyrics to this song from Five Man Electrical Band that illustrates the Boomers lack of faith in institutions and traditions:

And the sign said long haired freaky people need not apply
So I tucked my hair up under my hat and I went in to ask him why
He said you look like a fine upstanding young man, I think you'll do
So I took off my hat I said imagine that, huh, me working for you

Sign Sign everywhere a sign
Blocking out the scenery breaking my mind
Do this, don't do that, can't you read the sign

And the sign said anybody caught trespassing would be shot on sight
So I jumped on the fence and yelled at the house, Hey! what gives you the right
To put up a fence to keep me out or to keep mother nature in
If God was here, he'd tell you to your face, man you're some kinda sinner

Now, hey you Mister! can't you read, you got to have a shirt and tie to get a seat
You can't even watch, no you can't eat, you ain't suppose to be here
Sign said you got to have a membership card to get inside Uh!

And the sign said everybody welcome, come in, kneel down and pray
But when they passed around the plate at the end of it all,
I didn't have a penny to pay, so I got me a pen and a paper and I made up my own little sign
I said thank you Lord for thinking about me, I'm alive and doing fine

Sign Sign everywhere a sign
Blocking out the scenery breaking my mind
Do this, don't do that, can't you read the sign

This attitude was not uncommon in the 60's for the Boomer generation. But they also found that because there were so many of them, that they had to compete and fight for everything they got. They earned their way through life, it was not handed to them. Even though they questioned the status quo and pushed for political and social change, they were usually an optimistic bunch: they had the promise of a better education, they have turned out to be much more affluent than their parents, and they remain intent on fixing America and forming it to their ideals.

In comparison to the Traditionalists, who can be described as "loyal", the Boomers can be described as "self-absorbed". No other generation has learned as much about themselves and yet has been as confused and restless as this generation. If the Traditionalists were described as the "chain of command" generation, the Boomers can be described as the "Change in Command" generation. They would rather change who is in charge with themselves than follow.

When it comes to SharePoint, this group will learn it and use it, but often to the extent that it helps them achieve and compete. They will see SharePoint as a tool, not as an addition to their lives. For this generation, who grew up learning their times tables, doing long math by hand, and having to compete and work hard for everything they earned, they will find technology to be a (sometimes) evil necessary to an end goal, but they could just as easily live without cell phones, computers, texting and the internet. Don't expect this generation to embrace SharePoint as quickly or as pervasively as the younger generations. Don't expect them to like it just because it's "cool". Nope. If SharePoint, like any technology, gets in their way, they'll just go around it and not think twice about jettising collaborative technology. However, assuming that SharePoint works for them and enhances their success on their job, they'll use it and might even become advocates for it.

Note that most of the decision-makers for the purchasing of technology are in the Boomer generation. I continue to remain surprised at home much costs corporate America is willing to put up with when it comes to technology. When selling to this crowd, emphasizing how cool the technology is or how easily it can be used 24x7 will likely turn them off. They'll see 24x7 use as an imposition into their lives - an appendage to be carved out of their lives so they can enjoy what they want to do. While the younger generations will "eat up" the latest and coolest technologies, the Boomers (most anyways) will not.

Gen X (1965 - 1980, workforce age 29-45)

  • There are only 46 million X'ers.
  • People who are important to this generation: Bill Clinton, Bill Gates, Monica Lewinsky, Ted Bundy, Al Bundy, Beavis and Butt-Head, Clarence Thomas, O.J. Simpson, Newt Gingrich, Dilbert, Ronald Reagan
  • The emergence of a 24-hour media meant that they could see and virtually visit places anywhere in the world. Through television, they traveled to the Soviet Union, Somalia, Cannes, Chernobyl, Lockerbie, Starbucks and the international space station

This generation experienced and explosion of technology. From cable TV, digital TV, satellite TV, VCR, video games, fax machines, pagers, cell phones, palm pilots, and the personal computer, they learned swiftly to live with change in the tools they used to communicate with and interact with their environment. But what they found is that while these inventions were meant to simplify their lives, the exact opposite happened. Their lives become much more complex. Increased violence, AIDS, crack, child molesters, drunk drivers - the world was no longer safe. The number of single-parent households skyrocketed as the divorce rates for their parents tripled in their growing-up years. As a result, they became independent and resourceful.

If there is one word to describe this generation, it would be skeptical. Nearly every American institution was called into question for them: the Presidency, military, organized religion and corporate America. If you name the institution, a GenX'er can name the crime. hence, they distrust the permanence of institutional and personal relationships and they trust themselves more than institutions. This often spills over into not trusting their boss a very much.

So, if the Traditionalists were "Chain of Command" and Boomers were "Change in Command" a GenX'er would be "Self-Command". Boomer managers resent having to overly-praise them in order to motivate them. Often, Boomer managers will complain that GenX'ers are more interested in a paycheck and in receiving praise than in earning praise. Because X'ers haven't had to compete for much of what they've received in life and because they were often overly praised for performing mundane tasks ("great job in taking out the garbage!"), GenX'ers often exhibit a sense of entitlement and self-centric view of the world. It really is all about them, at least in their minds.

Technology is baked into their world. They have no concept of a world without portable communications, the internet, instant knowledge, instant gratification and ever-increasing capabilities of their technology. Because they like the latest and coolest toys, employers who offer higher-than-normal technology components are often viewed as "cool". This generation communicates and lives in a world that Boomers and Traditionalists don't understand. And the GenX'ers know that they are not understood. X'ers relate through technology. They are just as comfortable with texting as with talking. In fact, for many, they live their lives through technology. To the older generations, this seems absurd. But this is the way it is.

This generation is most loyal to their peers and not very loyal to institutions. They are more concerned about career security than job security, though perhaps the last 12 months has taught them differently. They will put up with hypocrisy more readily than Boomers or Traditionalists and are more accepting of a wide range of values than their predecessors.

When it comes to SharePoint, they might actually find it to be lacking and a tool that needs improvement. While they will readily adopt and use collaborative technologies, they will want SharePoint to be mobile and sometimes, baked into their world. But they'll also want control over it. The asynchronous nature of SharePoint will sometimes frustrate their need for instant gratification to know what the outcome is. This generation grew on watching 30 minute and 60 minute shows, so they have difficulty with real-world situations that don't resolve themselves quickly. SharePoint will be adopted and used swiftly by this generation - they'll be one's pushing the envelope on how to use the technology to meet their own needs.

Millennialists (1980 - ??, workforce age 18-29)

  • There are nearly 80 million Millennalists
  • This generation is still entering the workforce
  • They voted heavily for Jesse Ventura (pro-wrestler turned Governor of Minnesota), Obama and other progressive candidates.

We're still learning about this generation, but due to the large number of them, it's clear that they will be a competitive generation. In fact, it's possible that they will over-take the GenX'ers in Corporate America as they mature, simple because the X'ers won't be able to fill the large number of positions that will be vacated by the Boomers.

Technology for this generation is a given. Most of their toys had computer chips in them. Video games and social networking are highly important to this group. They don't watch network TV or go to moves. They download everything. Viral is a way of life for them. Because they have had immense control over their environment for most of their lives, they want the world to revolve on their terms. And being a younger generation, they tend to have the most disposable income available to them, so they spend and spend.

SharePoint will be readily and easily adopted by this group, but they will likely question Governance policies since they like to use technology on their terms.

 

Discussion

So, what to make of all this? Well, here are some ideas and tips on deploying SharePoint to all four generations in your company.

The Traditionalists will have two main reactions:

  • Resist: "I've learned it the hard way, you can too!"
  • Willingness: "I'd like to learn, but am scared"

Instructor-led training is best for this generation. Give them the opportunity to ask questions. Give them the base/efficient ways to do things – "no frills" - click here, do this, done. Don't show them everything that SharePoint can do, just show them what they need to know to improve their work performance. You'll need to bridge the technology with improved job performance and show them why it will help them in the long run.

The Boomers will likely take the notion that if you "train 'em too much, they'll leave". This is based on their own experience of viewing life through the lens of competition. Instructor-led and some CBT training will fit this generation. Use their competitiveness to help with adoption:

  • Certification programs
  • Tie status to learning achievements
  • Prestige in earning an accomplishment

But, don't ask them work 24x7 in SharePoint. Extranets sometimes will not be welcome by them. Support their views of a strong work/life balance and help them balance SharePoint adoption with their life goals.

GenX'ers will the opposite view of the Boomers: "the more I learn, the more I stay". Focus on career security for the Xer, not job security. Use CBTs and other viral learning methods to help them learn and adopt SharePoint. Help them bake in SharePoint into their current technologies, such as publishing your farm via ISA server for mobile consumption. And help them understand the older generations may not find technology to be an over-riding assumption about life. Also count on them getting board swiftly with SharePoint and bypassing it's use if they find it too cumbersome. You'll need to spot check their work to ensure that they are following the rules.

Governance and the Generations

For two years now, we've heard the Governance drum-beat from nearly every corner of the SharePoint community. It was all the rage. It has calmed down some. Governance is deciding how SharePoint will be used in your environment and, more importantly, deciding who gets to decide what the rules are. The dark side of Governance is enforcement. Without enforcement, you won't have Governance. You can count on the Boomers and the Traditionalists to pretty much stick to the rules for using SharePoint. You can also count on the GenX folks working with the rules if they agree with them. If they don't, then you'll find that they'll either comply in a half-hearted way: enough to meet the minimum standard, but not enough to fully comply or they'll just stop using SharePoint or find a way around the rules. The GenX generation, because they are accustomed to being on their own and being resourceful, will work around the rules when it suits their fancy. Be prepared to enforce and help them understand that SharePoint works best when everyone works cooperatively with it.

Conclusion

While not everyone's resistance to adoption of SharePoint will fall neatly into these categories, I trust that this post will help us all consider the generational aspects of a SharePoint adoption.

Bill English
EBA Companies



 ‭(Hidden)‬ Admin Links