Home
About Us
Advertise
Printable version
It’s Summer… Are You Sweating?
By Eric Riz
July 19, 2011 —
(Page 1 of 2)
It’s summer, a time where business slows as employees take well-deserved vacations and out-of-office messages circulate through corporate inboxes. As we sweat in the heat of summer, now is a great time for companies to ask the following question: Are we sweating our SharePoint asset?
As a term, sweating a corporate asset is a broad way of asking if it is maximizing its value within your organization. From a SharePoint perspective, is the reason you brought SharePoint into the business the same as its current use? If you deployed SharePoint to give your customers a centralized ordering system, have you deployed it to your customers, and are they using it?
Over the years, I have worked with many companies that have lost their direction once SharePoint is deployed. In these situations, stakeholders and users have shifted from business-unit focus as other areas went online with SharePoint functionality, something that leaves an obvious poor taste in the mouths of the business decision makers and users. This is where the importance of sweating the asset is critical. The question is, what can a business do to plan on sweating their SharePoint asset?
• Drive the business case through your entire organization
– When writing the business case and selling it to your company, be sure to create tangible deliverables which intersect functionality with corporate roles and objectives for each business unit. This creates anticipation and excitement at the business unit level. As deliverables are implemented, be sure that each function is used to their maximum by each user.
• Communicate objectives and measure their success
– During your kickoff meeting, make sure to establish a clear baseline that describes the objectives and planned successes of the implementation. At the halfway and completion marks of your project, review your successes and review your expectations. If your expectations have exceeded you initial baseline, you’re sweating!
• Establish survey tools to provide feedback to the project executives
– Create a SharePoint site where users can go to complete competency and functionality surveys. Ask questions of your end users that measure their current and expected usage. Assuming that some expectations will be outside of your original scope, begin creating a sub-project for new functions and usage.
Next Page
Pages
1
2
Share this link:
https://sptechweb.com/link/35749
Related Articles
Guest View: Are Your Apps Effective? See What Users Are Doing
End user performance and management is a new way of examining how end users are adopting software and seeing what they do with what they buy. It provides a complete picture that can help a business meet the demands of users.
So You Want to Manage Your SharePoint Implementation
Eric Riz offers five steps to managing and controlling SharePoint effectively
It’s ‘Go’ Time
Now that SharePoint 2010 is out, Errin O'Connor goes over some steps to helping your organization adopt it
Add comment
Name*
Email*
Country
United States
Canada
Afghanistan
Albania
Algeria
American Samoa
Andorra
Angola
Anguilla
Antarctica
Antigua & Barbuda
Antilles, Netherlands
Arabia, Saudi
Argentina
Armenia
Aruba
Australia
Austria
Azerbaijan
Bahamas, The
Bahrain
Bangladesh
Barbados
Belarus
Belgium
Belize
Benin
Bermuda
Bhutan
Bolivia
Bosnia and Herzegovina
Botswana
Brazil
British Virgin Islands
Brunei Darussalam
Bulgaria
Burkina Faso
Burundi
Cambodia
Cameroon
Cape Verde
Cayman Islands
Central African Republic
Chad
Chile
China
Christmas Island
Cocos (Keeling) Islands
Colombia
Comoros
Congo
Cook Islands
Costa Rica
Cote D'Ivoire
Croatia
Cuba
Cyprus
Czech Republic
Denmark
Djibouti
Dominica
Dominican Republic
East Timor (Timor-Leste)
Egypt
El Salvador
Equatorial Guinea
Eritrea
Estonia
Ethiopia
Falkland Islands (Malvinas)
Faroe Islands
Fiji
Finland
France
French Guiana
French Polynesia
Gabon
Gambia, the
Georgia
Germany
Ghana
Gibraltar
Greece
Greenland
Grenada
Guadeloupe
Guam
Guatemala
Guinea
Guinea-Bissau
Guinea, Equatorial
Guyana
Haiti
Holland (see Netherlands)
Honduras
Hong Kong, (China)
Hungary
Iceland
India
Indonesia
Iran, Islamic Republic of
Iraq
Ireland
Israel
Italy
Jamaica
Japan
Jordan
Kazakhstan
Kenya
Kiribati
Korea (North)
Korea (South)
Kuwait
Kyrgyzstan
Laos
Latvia
Lebanon
Lesotho
Liberia
Libyan Arab Jamahiriya
Liechtenstein
Lithuania
Luxembourg
Macao, (China)
Macedonia, TFYR
Madagascar
Malawi
Malaysia
Maldives
Mali
Malta
Marshall Islands
Martinique
Mauritania
Mauritius
Mayotte
Mexico
Micronesia, Federated States of
Moldova, Republic of
Monaco
Mongolia
Montenegro
Montserrat
Morocco
Mozambique
Myanmar (ex-Burma)
Namibia
Nauru
Nepal
Netherlands
Netherlands Antilles
New Caledonia
New Zealand
Nicaragua
Niger
Nigeria
Niue
Norfolk Island
Northern Mariana Islands
Norway
Oman
Pakistan
Palau
Palestinian Territory
Panama
Papua New Guinea
Paraguay
Peru
Philippines
Poland
Portugal
Puerto Rico
Qatar
Reunion
Romania
Russia (Russian Federation)
Rwanda
Saint Helena
Saint Kitts and Nevis
Saint Lucia
Saint Pierre and Miquelon
Saint Vincent and the Grenadines
Samoa
San Marino
Sao Tome and Principe
Saudi Arabia
Senegal
Serbia & Montenegro
Seychelles
Sierra Leone
Singapore
Slovakia
Slovenia
Solomon Islands
Somalia
South Africa
Spain
Sri Lanka (ex-Ceilan)
Sudan
Suriname
Swaziland
Sweden
Switzerland
Syrian Arab Republic
Taiwan
Tajikistan
Tanzania, United Republic of
Thailand
Timor-Leste (East Timor)
Togo
Tokelau
Tonga
Trinidad & Tobago
Tunisia
Turkey
Turkmenistan
Turks and Caicos Islands
Tuvalu
Uganda
Ukraine
United Arab Emirates
United Kingdom
Uruguay
Uzbekistan
Vanuatu
Vatican City State (Holy See)
Venezuela
VietNam
Virgin Islands, British
Virgin Islands, U.S.
Wallis and Futuna
Western Sahara
Yemen
Zambia
Zanzibar
Zimbabwe
[Not specified]
Comment
Preview