SharePointMaturity.com

Business process is loosely defined. Out of the box SharePoint workflows (approval, collect feedback) leveraged sporadically. A doclib or list provides a central base of operations.  Any workflow is document- vs. application-centric.

End User Perspective:
There are workflows in SharePoint?  What is a workflow?  /
I know how to route a document for approval within SharePoint.

Business processes are designed; some custom, departmental “no-code” workflows (SP Designer, Visio, or third-party tool) may be implemented to handle simple business rules (decision-based routing).

End User Perspective:
We use simple workflows for tasks like approvals within our department.  I initiate tasks or report their completion in SharePoint.

Process is considered as a whole, rather than as automating functional tasks. Transition from procedural document workflow to orchestration of dynamic business process.  SharePoint is becoming the BP platform, w/the introduction of 3rd party BPM tool to support more complex business rules.

End User Perspective:
We understand the need to automate processes to improve how work gets done.  The workflow can recognize me or my role, and fill in information about me (“my manager”).  Process work is assigned to roles, not people.

Workflow is a component of SP-based composite applications with connectivity to LOB systems.  Users have access to process analytics and audit trails. Collaboration happens in the context of a work item as part of a dynamic, nonlinear business process (the “case”).

End User Perspective:
We monitor business activities to understand what’s happening and identify potential hot spots.  I went from using 7 different applications to a single one in order to get my work done. I can access my work from any browser-based environment, including those on mobile devices.

Power users can edit existing workflows to adapt them to changing business needs on the fly.  Users leverage data from BPM to optimize process, simulate on real data, clear bottlenecks, balance work across workloads.  Users have visibility into the process and can provide feedback to process improvements.  Business processes extend to external users.

End User Perspective:
Managers have a business process dashboard that allows them to see all work in progress as well as trends in demand.  Processes are goal-driven with associated service level agreements.  Operational data about the process is examined regularly by business analysts for potential improvements.

Out of box collaboration sites set up as needed without structure or organization.  No formal process exists for requesting a new site.

End User Perspective:
We have a team site for the work we’re doing.

Mechanism is in place for new site requests. Collaboration efforts are collected in document libraries (links emailed rather than documents)

End User Perspective:
There is a standard way for me to request a new site.  I email links rather than attachments.

Collaboration efforts extend sporadically to discussion threads, wikis, blogs, and doc libs with versioning.  Site templates are developed for specific needs.

End User Perspective:
I can use different collaboration tools or site templates based on what I need.

Collaboration tools are used across the entire organization.  Email is captured & leveraged. Work is promoted from WIP to Final which is leverageable. Mobile access considered.

End User Perspective:
I can collaborate using my mobile device.

Collaboration occurs outside the firewall – i.e. with external contributors. Automated processes exist for de-provisioning and archiving sites.

End User Perspective:
I can collaborate with external contributors.

Some paper forms converted to SP list forms.  Many Excel spreadsheets, Access databases, paper forms still stored in / linked to from SharePoint.

Increasing use of SP lists to replace Excel spreadsheets and paper forms.  Applications are opened up to a larger group of users.

Most critical business forms are online; some involve automated workflows.  "No-Code" InfoPath forms improve the user experience.

InfoPath forms may involve custom code. Mobile functionality is supported.  Access Services and Visio Services may be used.

Forms connect with LOB data. New capabilities & requirements are surfaced & integrated into downstream capabilities.

No development, or development is done in Production.  No QA / development environments.  No source control.

Changes are deployed from one environment to another using backup/restore. Source control is simple file storage. Buy vs. Build is evaluated.

Mixed automated \ manual deployment process - some artifacts deployed via scripts, others by following list of manual steps.  Source control is centralized.   Staging mirrors Production.

Deployment is fully automated – solution package and scripts.  Total Cost of Ownership is considered.  Requirements fully vetted; SMEs fully test the customizations.

Deployment is fully automated via features .  Source code is  managed centrally as IP, re-usable and shareable.

Single-server installation, sometimes rogue.  No plan for availability / disaster recovery.

Multiple server installlation or single-server is backed up on a regular basis.

Number of servers is appropriate to demands and scalable for future growth.   Dev environment is present. Service Packs  tested in QA and installed in a timely fashion.

Backup/restore has been tested.  Dev and QA environments are present.   Administration may be improved via third-party tools. BLOB integration may be present. Performance considered.

System health & error logs monitored.  Processes for archiving & de-provisioning are in place.  Disaster Recovery plan is in place.

Existing reports are used; data is brought together manually. OOB SP reports (analytics and queries) may be viewed periodically.

Reports are aggregated through customization. Excel Services may be used.

End User Perspective:
I can see what happened.

Reports allow drill-down and charting.


End User Perspective:
I can see what happened.

Items are actionable.

End User Perspective:
I can see what happened and what's happening.

Analytics and trending are employed.

End-User Perspective:
I can see what's going to happen.

Links to enterprise systems posted on SP site. Printed or exported business data is stored in doc libs.

A single system is integrated with SharePoint (in addition to Active Directory and search content sources).

Multiple systems are integrated with SharePoint.

Most of the systems that are desired to be integrated,  are integrated. A data warehouse  may be integrated with SP.

External data (partner/supplier or industry) is integrated with SP.

Basic profile data imported from AD or other source. MySites host not created.  Manually-created org chart is published in SP.

End User Perspective:
I can see information about other users like email address and telephone number.

MySites rolled out to pilot groups or users.  Out-of-box profiiles implemented.   Community spaces may be piloted.

End User Perspective:
I hear we’re getting this thing called MySites.

Custom profile fields reflect company culture; photos are updated from central source.  MySites rolled out to all users, supported, trained. Community spaces connect a particular set of users.

End User Perspective:
We have a company FaceBook, and community sites where employees come together based on affinity.

Profile fields may integrate with LOB data.  MySites are centralized (only one instance). Communities flourish under governance. Notion of subscription – to groups, topics, people.  Org chart is dynamic.  Admins have visibility into use.

End User Perspective:
I can subscribe to the things I’m interested in and the content will find me.  My profile is automatically updated with business data (e.g. projects I’ve worked on).

Users can edit certain profile data that writes back to AD or HRIS. MySites template is customized.   Communities / conversations extend to external participants.

End User Perspective:
When I want to find an expert resource, I can search the profiles.  External users can participate in affinity groups.

Navigation & taxonomy not formally considered.  Little to no checks on content.  Folder structure re-created from shared drives.  Content that could be in lists is posted in Content Editor WP. Out of box site templates / layouts are used.

End User Perspective:
I know how to publish a document in SharePoint.

Custom metadata is applied to content.  Templates standardized across sites.  Lists used rather than static HTML. Multiple document mgmt systems may be present w/out governance around purpose.

End User Perspective:
I know how to use metadata columns.  Could you just post this for me?

Site Columns/ Managed Metadata standardize the taxonomy.  Custom content Types are created.  Custom page layouts & site templates are configured.  Approval process is implemented.  Incoming email activated for some lists/libs.  Site Map is present.  Some content targeted to groups.

End User Perspective:
When I navigate around the different sites, I know what to expect at each site.  But I have no idea if the content is fresh or not.

Content is monitored, maintained, targeted to specific groups. Usage is analyzed.  Digital assets are managed appropriately.  If more than one doc mgmt system is present, governance is defined.  Mobile access considered.

End User Perspective:
I see the content that is relevant to my department or location.  I know that the content is fresh and regularly maintained.

Content is personalized to the user.  
Content is shared across multiple functions and systems without duplication. 
Feedback mechanism is in place for pages and taxonomy.
Automated tagging may be present.

End User Perspective:
I see the content that is relevant to me.  I can report a problem or make a suggestion about anything on the site.

Out of box functionality for query, results, and scopes; some additional content sources may be indexed.

End User Perspective:
I can’t find anything.  There’s Search in SharePoint?

Custom scopes and iFilters employed to aid the search experience. Content may be federated.  Search Center created.

End User Perspective:
I can use SharePoint to search the intranet and our shared drives at the same time.

Search results are analyzed.  Best bets and metadata properties are leveraged to aid the search experience.

End User Perspective:
The definitive item in my search results is marked with a little star.  We see where there are gaps in the content & have process for creating content to fill gaps.

Content types and custom properties are leveraged in Advanced Search and/or refiners.  Results customized to specific needs, may be actionable.  3rd-party product may be used.

End User Perspective:
Advanced Search helps me filter content before I search for it.  I can refine before and after searching.

Users understand relationship of tagging to search results.  Automated tagging may be used.  High volumes can be handled.

End User Perspective:
Information finds me, based on the preferences I set.  The more I tag, the better I (and others) will be able to find.

One pioneer or small group pilots the product.

SP evangelized to a subset of depts or functional areas by an individual; work mainly done by individual or small group.  Training is informal, ad-hoc.

SP evangelized around the organization by individual or small group.  Content owners from some functional areas are trained and using the system.  One IT resource  knowledgeable on the system.  Rollout strategy defined.

IT has more than one resource knowledgeable on the system.  Requests for new functionality are tracked and prioritized.  An end-user training plan is in place.  Rollout strategy implemented.

Top-down support in place; dedicated IT business analyst, server admin, helpdesk, training staff; empowered user community.  Multiple training offerings exist.