1. Assess Your SharePoint Maturity
with
The SharePoint Maturity Model
Presented at SharePoint Saturday NYC
30 July 2011
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 1

2. Agenda
• Logistics
• What’s in it for me?
• About Me
• About My Company
• Planning for SharePoint
• About the SharePoint Maturity Model
• About Microsoft’s SP Competencies
• SMM Competency Definitions
• SMM Maturity Level Definitions
• The SharePoint Maturity Model - overview
• Self Evaluation Matrix
• The SharePoint Maturity Model – detail & case studies
• Credits & Resources
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 2

3. Logistics
• In Session
– Questions welcome!
– If you’re tweeting / live blogging, please include:
• #SPMaturity
• @sadalit
• Post-Session
– Please fill out your evaluation
– SharePint at the Hilton across the street
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 3

4. What’s In It For Me?
• The Maturity Model can help you measure what you have,
develop your strategic roadmap, and ultimately lead to:
– Greater business process efficiency
– A more trustworthy SP environment
– Happier, more empowered users
– More time for YOU
• to innovate, rather than putting out fires or answering the same
question over and over.
• You can get a quantitative sense of your progress by re-
evaluating each year.
• You are helping to build a data model that will help answer
larger questions about where organizations are in their SP
maturity by industry, number of years of use, etc.
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 4

5. About Me
• Project Manager and Business
Analyst focusing on SharePoint
• Working with SharePoint since
beta 2003 version
• 50 SharePoint
implementations
• Microsoft Certified IT Pro
Senior Software Engineer,
BlueMetal Architects
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 5

6. About My Company
• Founded by ex-Microsoft
product and technology
executives
• Helping clients architect, build,
and deploy software solutions
in 4 areas:
– Application Modernization
– Cloud Platforms
– Information Management
– User Experience
• Deep and broad expertise in
Microsoft and related
technologies.
• 20 employees with over 125
years of previous experience
working directly for Microsoft.
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 6

7. Stages of SharePoint
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 7

8. 7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 8

9. 7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 9

10. 7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 10

11. 7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 11

12. 7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 12

13. 7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 13

14. 7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 14

15. 7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 15

16. 7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 16

17. 7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 17

18. 7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 18

19. 7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 19

20. About the SharePoint Maturity Model
• Developed in Fall 2010 for the purpose of bringing a
holistic view to a SharePoint implementation, and
bringing standardization to the conversation around
functionality, best practices, and improvement.
• Starts at 100 rather than 0
• A framework rather than a formula
• Typical rather than recommended
• Does NOT currently cover:
– Public-facing websites
– Compliance and regulatory issues
– Visual design and branding
– Cloud/online versions of SP
• Version 1 published 5 November 2010.
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 20

21. About Microsoft’s SP Competencies
Ribbon UI
SharePoint Workspace
Business Connectivity Services SharePoint Mobile
InfoPath Form Services Office Client & Web App Integration
External Lists Standards Support
Workflow
SharePoint Designer
Visual Studio
API Enhancements
Tagging, Tag Cloud, Ratings
REST/ATOM/RSS
Social Bookmarking
Blogs and Wikis
My Sites
Activity Feeds
Profiles and Expertise
Org Browser
PerformancePoint Services
Excel Services
Chart Web Part
Visio Services
Web Analytics
Enterprise Content Types
SQL Server Integration
Metadata and Navigation
PowerPivot
Document Sets
Multi-stage Disposition
Social Relevance
Audio and Video Content Types
Phonetic Search
Remote Blob Storage
Navigation
List Enhancements
FAST Integration
Enhanced Pipeline
Source: Microsoft Corp.

22. About Customizations in SharePoint
• For the purposes of the Maturity Model,
Customizations are defined as anything that
touches the SharePoint server – i.e. the 12 hive,
inetpub, or GAC (thanks Mark Miller!)
• Called “Development” by some
• Represented with a red line in the matrix – above
the line, customization may be needed.
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 22

23. Competency Definitions - Core
Area Description
Presentation of content in SharePoint for consumption by a varied audience of
authenticated users. Areas of focus include navigation, presentation of content
Publication (static vs. personalized), content organization and storage, customizations to the
template, and approvals and workflow.
Multiple individuals working jointly within SharePoint. Areas of focus include
provisioning & de-provisioning, templates, organization (finding a site),
Collaboration archiving, using SP’s capabilities (i.e. versioning & doc mgmt, task mgmt,
calendar mgmt, discussion thread, surveys, workflow).
Linked business activities with a defined trigger and outcome, standardized by
SharePoint and/or custom automated workflow processes. Areas of focus
Business Process include data (unstructured/structured), workflow, user security / roles, reporting
and analytics, tracking / auditing, process modeling and simulation, and process
optimization.
The ability to query indexed content and return results that are ranked in order
Search of relevance to the search query. Areas of focus include scopes, display of
results, optimization, integration and connectors, and performance.
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 23

24. Competency Definitions - Advanced
Area Description
The human capital of the organization as represented in SharePoint by profiles,
People &
MySites, and community spaces (the virtual spaces that support particular areas
Communities of interest that may span or fall outside the organizational structure).
Custom solutions specific to the needs of the business (traditionally served by
Composites &
paper forms, Excel spreadsheets and/or Access databases) which may be
Applications accomplished by multiple technologies working together.
Line of business data and/or content from a separate CMS integrated with the
system, allowing users to self-serve in a controlled yet flexible manner. Maturity
Integration proceeds through integration with single system, multiple systems, Data
Warehouse, and external (partner/supplier or industry) data.
The means of viewing business data in the system. Maturity proceeds through
Insight aggregation of views, drill-down and charting, actionability, and analytics and
trending.
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 24

25. Competency Definitions - Readiness
Area Description
The hardware and processes that support the system. Areas of focus include
Infrastructure &
farm planning, server configuration, storage, backup/restore, monitoring, and
Administration updates.
The human resources that support the system and the level of training with
Staffing & Training which they are provided.
Custom development and/or third-party products that extend the out-of-box
functionality of the system. Areas of focus include development environment,
Customizations management of source code, method of build and deployment, testing, and
development tier.
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 25

26. Maturity Level Definitions
SharePoint
Description
Level
500 The particular area is functioning optimally and continuous improvement
Optimizing occurs based on defined and monitored metrics.
400 The particular area is centrally supported, standardized, and in use across
Predictable the entire organization. Governance is defined and followed.
Maturation
The way the particular area is leveraged is defined and/or standardized,
300 but not in use across the entire organization. Governance is defined but
Defined may not be widely understood/followed.
200 The particular area is managed by a central group (often IT), but the focus
Managed and definition varies by functional area, or is limited to a single area.
100 The starting point of SharePoint use.
Initial
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 26

27. Maturity Level examples
SharePoint
Level Unified
Community
500
Optimizing Dynamic Experience Customized Strategic
400
Predictable
Maturation
300
Defined
200
Managed
100
Initial Static Individual Out-of-box Tactical
Needs
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 27

28. The SharePoint Maturity Model – 1 alongCore Concepts
Maturation also occurs
– this vector
Level Publication Collaboration Business Process Search
Power users can edit existing
workflows to adapt them to changing
business needs on the fly. Users
Content is personalized to the user. Users understand relationship of
Collaboration occurs outside the leverage data from BPM to optimize
Content is shared across multiple functions tagging to search results.
500 and systems without duplication. Feedback
mechanism is in place for pages and
firewall – i.e. with external
contributors. Automated processes
process, simulate on real data, clear
bottlenecks, balance work across
Process exists to create content
w/no results. Automated
exist for de-provisioning and workloads. Users have visibility into
Optimizing taxonomy. Automated tagging may be
present.
archiving sites. the process and can provide
tagging may be used. High
volumes can be handled.
feedback to process improvements.
Business processes extend to
external users.
Workflow is a component of SP-
Content is monitored, maintained, some is Collaboration tools are used across based composite applications with Content types and custom
targeted to specific groups. Usage is the entire organization. Email is connectivity to LOB systems. Users properties are leveraged in
400 analyzed. Digital assets are managed
appropriately. If more than one doc mgmt
captured & leveraged. The system
supports promotion of content from
have access to process analytics and
audit trails. Collaboration happens in
Advanced Search and/or
refiners. Results are
Predictable system is present, governance is defined.
Mobile access considered.
WIP to final. Mobile access
considered.
the context of a work item as part of
a dynamic, nonlinear business
customized to specific needs,
may be actionable.
process (the “case”).
Process is considered as a whole,
Maturation
Site Columns/ Managed Metadata Collaboration efforts extend rather than as automating functional
standardize the taxonomy. Custom content sporadically to discussion threads, tasks. Transition from procedural
Search results are analyzed.
300 Types are created. Custom page layouts &
site templates are configured. Approval
wikis, blogs, and doc libs with
versioning. Site templates are
document workflow to orchestration
of dynamic business process.
Best bets and metadata
properties are leveraged to aid
process is implemented. Incoming email developed for specific needs. SharePoint is becoming the BP
Defined activated for some lists/libs. Site Map is Incoming email activated for some platform, w/the introduction of 3rd
the search experience.
present. lists/libs. party BPM tool to support more
complex business rules.
Business processes are designed;
Custom metadata is applied to content. Mechanism is in place for new site some custom, departmental “no-
Custom scopes employed to aid
200 Templates standardized across sites. Lists
used rather than static HTML. Multiple
requests. Collaboration efforts are
collected in document libraries
code” workflows (SP Designer, Visio,
or third-party tool) may be
the search experience. More
complex iFilters may be applied.
document mgmt systems may be present (links emailed rather than implemented to handle simple
Managed w/out governance around purpose. documents). business rules (decision-based
Content may be federated.
routing). .
Business process is loosely defined.
Navigation & taxonomy not formally
Out of the box SharePoint workflows Out of box functionality for
considered. Little to no checks on content. Out of box collaboration sites set up
100 Folder structure re-created from shared
drives. Content that could be in lists is
as needed without structure or
organization. No formal process
(approval, collect feedback)
leveraged sporadically. A doclib or list
query, results, and scopes; PDF
iFilter installed; some additional
provides a central base of operations. content sources may be
Initial posted in Content Editor WP. Out of box site
templates / layouts are used.
exists for requesting a new site.
Any workflow is document- vs. indexed.
application-centric.
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 28

29. The SharePoint Maturity Model – 2 – Advanced Concepts
Maturation also occurs along this vector
People and Composites and
Level Integration Insight
Communities Applications
Users can edit certain profile Forms connect with LOB
External data
data that writes back to AD or data. New capabilities &
500 HRIS. MySites template is requirements are surfaced
(partner/supplier or Analytics and trending are
industry) is integrated with employed.
Optimizing customized. Communities & integrated into
SP.
extend to external participants. downstream capabilities.
Profile fields may integrate with Most of the systems that are
LOB data. MySites are InfoPath forms improve the desired to be integrated,
400 centralized (only one instance user experience. Mobile are integrated. A data Items are actionable.
Predictable per user). Communities flourish functionality is supported. warehouse may be
under governance. integrated with SP.
Custom profile fields reflect
company culture; photos are
Maturation
updated from central source. Most critical business forms
300 MySites rolled out to all users, are online; some involve
Multiple systems are Reports allow drill-down and
integrated with SP. charting.
Defined supported, trained. Community automated workflows.
spaces connect a particular set
of users.
MySites rolled out to pilot Increasing use of SP lists to
A single system is integrated
groups or users. Out-of-box replace Excel spreadsheets
200 profiiles implemented. and paper forms.
with SP (Line-of-business, Reports are aggregated
document management, through customization.
Managed Community spaces may be Applications are opened up
etc.).
piloted. to a larger group of users.
Some paper forms
Links to enterprise systems
converted to SP list forms.
Basic profile data imported posted on SP site. Printed or Existing reports are used;
100 from AD or other source.
Many Excel spreadsheets,
exported business data is data is brought together
Access databases, paper
Initial MySites host not created. stored in doc libs. AD manually.
forms still stored in / linked
integrated with SP profiles.
to from SharePoint.
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 29

30. The SharePoint Maturity Model – 3 – Readiness Concepts
Maturation also occurs along this vector
Infrastructure and
Level Staffing & Training Customizations
Administration
Top-down support in place; Deployment is fully automated
System health & error logs dedicated IT business analyst, via features . Source code is
500 monitored. Processes for server admin, helpdesk, training managed centrally as IP, re-
archiving & de-provisioning are staff; empowered user usable and shareable. Content
Optimizing in place. community. Multiple training owners understand the
offerings exist. importance of QA testing.
Backup/restore has been tested.
Dev and QA environments are IT has more than one resource
Deployment is fully automated
present. Administration may be knowledgeable on the system.
400 improved via third-party tools. Requests for new functionality
– solution package and scripts.
Total Cost of Ownership is
Predictable BLOB integration may be are tracked and prioritized. An
considered.
present. Performance end-user training plan is in place.
considered.
Maturation
SP evangelized around the
Number of servers is appropriate Mixed automated manual
organization by individual or small
to demands and scalable for deployment process - some
group. Content owners from
300 future growth. Dev
some functional areas are trained
artifacts deployed via scripts,
environment is present. Service others by following list of
Defined and using the system. One IT
Packs tested in QA and installed manual steps. Source control
resource knowledgeable on the
in a timely fashion. is centralized.
system.
SP evangelized to a subset of
Changes are deployed from
Multiple server installlation or depts or functional areas by an
200 single-server is backed up on a individual; work mainly done by
one environment to another
using backup/restore. Source
Managed regular basis. individual or small group.
control is simple file storage.
Training is informal, ad-hoc.
No development, or
Single-server installation, development is done in
100 sometimes rogue . No plan for
One pioneer or small group pilots
Production. No QA /
the product.
Initial availability / disaster recovery. development environments.
No source control.
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 30

31. Self Evaluation Matrix
Publication Collaboration Business Search People & Composites & Integration Insight Infrastructure Staffing & Customizations
Process Communities Applications & Admin. Training
599
500
Optimizing
500
499
400
Predictable
400
399
300
Defined
300
299
200
200
Managed
199
100
Initial
100
Date of Assessment
Years the organization has used SharePoint
Current SP Version (year + standard or enterprise if known)
# of users organization-wide
# of IT staff supporting SharePoint (combine part-timers &
include vendors if they are a regular part of your team)
Organization’s Industry
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 31

32. Self Evaluation Matrix – Filled-in Example
Publication Collaboration Business Search People & Composites & Integration Insight Infrastructure Staffing & Customizations
Process Communities Applications & Admin. Training
599
500
Optimizing
500
499
400
Predictable
400
399
300
Defined
300
299
200
200
Managed
199
100
Initial
100
Date of Assessment 1/29/11
Years the organization has used SharePoint 7
Current SP Version (year + standard or enterprise if known) SP 2010 Enterprise
# of users organization-wide 50
# of IT staff supporting SharePoint (combine part-timers & 2.5
include vendors if they are a regular part of your team)
Organization’s Industry Professional Services
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 32

33. Data Model Examples
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 33

34. Publication
Presentation of content in SharePoint for consumption by a varied audience of
authenticated users. Areas of focus include navigation, presentation of content (static
vs. personalized), content organization and storage, customizations to the template,
and approvals and workflow.
Level Maturity Level Definition Competency
The particular area is functioning optimally Content is personalized to the user. Content is shared across
500 and continuous improvement occurs based on
multiple functions and systems without duplication.
Feedback mechanism is in place for pages and taxonomy.
Optimizing defined and monitored metrics. Automated tagging may be present.
The particular area is centrally supported, Content is monitored, maintained, some is targeted to
400 standardized, and in use across the entire specific groups. Usage is analyzed. Digital assets are
organization. Governance is defined and managed appropriately. If more than one doc mgmt system
Predictable is present, governance is defined. Mobile access considered.
followed.
Site Columns/ Managed Metadata standardize the
The way the particular area is leveraged is taxonomy. Custom content Types are created. Custom page
300 defined and/or standardized, but not in use layouts & site templates are configured. Approval process is
Defined across the entire organization. implemented. Incoming email activated for some lists/libs.
Site Map is present.
The particular area is managed by a central Custom metadata is applied to content. Templates
200 group (often IT), but the focus and definition
standardized across sites. Lists used rather than static HTML.
Multiple document mgmt systems may be present w/out
Managed varies by functional area. governance around purpose.
Navigation & taxonomy not formally considered. Little to no
100 The starting point of SharePoint use.
checks on content. Folder structure re-created from shared
drives. Content that could be in lists is posted in Content
Initial Editor WP. Out of box site templates / layouts are used.
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 35

35. Publication – End User Perspective
Level End User Perspective
I see the content that is relevant to me.
500 I can report a problem or make a suggestion about anything on
Optimizing
the site.
400 I see the content that is relevant to my department or location.
Predictable I know that the content is fresh and regularly maintained.
When I navigate around the different sites, I know what to
300 expect at each site.
Defined
But I have no idea if the content is fresh or not.
200 I know how to use metadata columns.
Managed Could you just post this for me?
100 I know how to publish a document in SharePoint.
Initial I still get to use my network drive, right? And folders?
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 37

36. Maturity per Years of Use
Publication
550
500
450
Maturity Level
400
350
350
300
300
250 272 266
278
236 243
200
150
100
1 2 3 4 6 7 9
Years of SharePoint Use
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 38

37. Publication – 100-level example
Source: S. Van Buren
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 39

38. Publication – 500-level example
Source: Microsoft
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 41

39. Publication – Resources Needed
Level Resources
500 • System/Business Analyst
Optimizing
• SharePoint Evangelist
400 • System/Business Analyst
Predictable
• SharePoint Configurator / Power User
• SharePoint Evangelist
300 • System/Business Analyst
Defined
• SharePoint Configurator / Power User
200 • SharePoint Evangelist
Managed • SharePoint Configurator / Power User
100 • SharePoint Configurator / Power User
Initial
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 42

40. Collaboration
Multiple individuals working jointly within SharePoint. Areas of focus include
provisioning & de-provisioning, templates, organization (finding a site), archiving,
using SP’s capabilities (i.e. versioning & doc mgmt, task mgmt, calendar mgmt,
discussion thread, surveys, workflow).
Level Maturity Level Definition Competency
The particular area is functioning
Collaboration occurs outside the firewall – i.e. with external
500 optimally and continuous improvement
contributors. Automated processes exist for de-provisioning
Optimizing occurs based on defined and monitored and archiving sites.
metrics.
The particular area is centrally supported,
Collaboration tools are used across the entire organization.
400 standardized, and in use across the entire
Email is captured & leveraged. Work is promoted from WIP to
Predictable organization. Governance is defined and Final which is leverageable. Mobile access considered.
followed.
The way the particular area is leveraged Collaboration efforts extend sporadically to discussion threads,
300 is defined and/or standardized, but not in wikis, blogs, and doc libs with versioning. Site templates are
Defined use across the entire organization. developed for specific needs.
The particular area is managed by a Mechanism is in place for new site requests. Collaboration
200 central group (often IT), but the focus and efforts are collected in document libraries (links emailed rather
Managed definition varies by functional area. than documents)
Out of box collaboration sites set up as needed without
100 The starting point of SharePoint use. structure or organization. No formal process exists for
Initial requesting a new site.
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 43

41. Collaboration – End User Perspective
Level End User Perspective
500 I can collaborate with external contributors.
Optimizing
400 I can collaborate using my mobile device.
Predictable
300 I can use different collaboration tools or site templates based on what I need.
Defined
200 I email links rather than attachments.
Managed
100 We have a team site for the work we’re doing.
Initial
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 44

42. Maturity per Years of Use
Collaboration
550
500
450
Maturity Level
400
350
300
250
200
150
100
1 2 3 4 6 7 9
Years of SharePoint Use
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 45

43. Collaboration – 100-level example
Source: S. Van Buren:
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 46

44. Collaboration– 400-level example
Source: Nielsen Norman Intranet Design Annual 2010
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 47

45. Business Process
Linked business activities with a defined trigger and outcome, standardized by SharePoint
and/or custom automated workflow processes. Areas of focus include data
(unstructured/structured), workflow, user security / roles, reporting and analytics, tracking /
auditing, process modeling and simulation, and process optimization.
Level Maturity Level Definition Competency
Power users can edit existing workflows to adapt them to
changing business needs on the fly. Users leverage data
The particular area is functioning optimally from BPM to optimize process, simulate on real data, clear
500 and continuous improvement occurs based bottlenecks, balance work across workloads. Users have
Optimizing on defined and monitored metrics. visibility into the process and can provide feedback to
process improvements. Business processes extend to
external users.
The particular area is centrally supported, Workflow is a component of SP-based composite applications
with connectivity to LOB systems. Users have access to
400 standardized, and in use across the entire
process analytics and audit trails. Collaboration happens in
Predictable organization. Governance is defined and the context of a work item as part of a dynamic, nonlinear
followed. business process (the “case”).
Process is considered as a whole, rather than as automating
The way the particular area is leveraged is functional tasks. Transition from procedural document
300 defined and/or standardized, but not in use workflow to orchestration of dynamic business process.
SharePoint is becoming the BP platform, w/the introduction
Defined across the entire organization. of 3rd party BPM tool to support more complex business
rules.
The particular area is managed by a central Business processes are designed; some custom,
200 group (often IT), but the focus and definition departmental “no-code” workflows (SP Designer, Visio, or
third-party tool) may be implemented to handle simple
Managed varies by functional area. business rules (decision-based routing). .
Business process is loosely defined. Out of the box
SharePoint workflows (approval, collect feedback) leveraged
100 The starting point of SharePoint use. sporadically. A doclib or list provides a central base of
Initial operations. Any workflow is document- vs. application- 48
centric.
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren

46. Business Process – End User Perspective
Level End User Perspective
Managers have a business process dashboard that allows them to see all work
in progress as well as trends in business demand. Processes are goal-driven
500 with associated service level agreements and productivity expectations
Optimizing
Operational data about the process execution is examined regularly by
business analysts for potential improvements.
We have modeled our end-to-end business process. We monitor business
activities to understand what’s happening and identify potential hot spots; we
recognize the need to re-engineer and improve existing processes to maintain
400 competitiveness
Predictable
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.
We understand the need to automate processes to improve how work gets
300 done. The workflow can recognize me or my role, and fill in information about
Defined
me (“my manager”). Process work is assigned to roles, not people
200 We use simple workflows for tasks like approvals within our department. I
Managed initiate tasks or report their completion in SharePoint.
100 There are workflows in SharePoint? What is a workflow?
Initial I know how to route a document for approval within SharePoint
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 49

47. Maturity per Years of Use
Business Process
550
500
450
Maturity Level
400
350
300
250
200
150
100
1 2 3 4 6 7 9
Years of SharePoint Use
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 50

48. Business Process – 100-level example
Source: S. Van Buren
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 51

49. Business Process – 500-level example
Source: Global360
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 53

50. Search
The ability to query indexed content and return results that are ranked in order of
relevance to the search query. Areas of focus include scopes, display of results,
optimization, integration and connectors, and performance.
Level Maturity Level Definition Competency
The particular area is functioning optimally Users understand relationship of tagging to search
500 and continuous improvement occurs based results. Automated tagging may be used. High
Optimizing on defined and monitored metrics. volumes can be handled.
The particular area is centrally supported,
Content types and custom properties are leveraged
400 standardized, and in use across the entire
in Advanced Search and/or refiners. Results
Predictable organization. Governance is defined and
customized to specific needs, may be actionable.
followed.
The way the particular area is leveraged is Search results are analyzed. Best bets and
300 defined and/or standardized, but not in use metadata properties are leveraged to aid the
Defined across the entire organization. search experience.
The particular area is managed by a central
200 group (often IT), but the focus and
Custom scopes and iFilters employed to aid the
Managed search experience. Content may be federated.
definition varies by functional area.
Out of box functionality for query, results, and
100 The starting point of SharePoint use. scopes; some additional content sources may be
Initial indexed.
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 54

51. Search – End User Perspective
Level End User Perspective
500 Information finds me, based on the preferences I set.
Optimizing
400 Advanced Search helps me filter content before I search for it.
Predictable
300 The definitive item in my search results is marked with a little star.
Defined
200 I can use SharePoint to search the intranet and our shared drives at the same
Managed time.
100 I can’t find anything.
Initial There’s Search in SharePoint?
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 55

52. Maturity per Years of Use
Search
550
500
450
Maturity Level
400
350
300
250
200
150
100
1 2 3 4 6 7 9
Years of SharePoint Use
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 56

53. Search – 100-level example
Source: S. Van Buren
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 57

54. Search – 400-level example (query)
Source: Nielsen Norman Intranet Design Annual 2010
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 58

55. Search – 400-level example (results)
Source: S. Van Buren
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 59

56. 7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 82

57. Future Plans and Improvements
• Centralized system for receiving data
• Mapping to vendors – services and products
• Complete mapping to resourcing (in conjunction
with Veronique Palmer)
• Mapping to SP versions
– Standard/Enterprise
– Cloud
• Operational steps to maturity in the competencies
– (Torben Ellert has already done this for Search –
http://www.surfray.com/resources/tech-blog/459-boosting-your-
sharepoint-search-maturity-level.html)
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 83

58. Upcoming Events
• August 11-13 – SharePoint Saturday the
Conference – Washington, DC
– http://www.spstc.org/Pages/default.aspx
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 84

59. Call to Action
• Fill out the SMM self-assessment!
• Send me your data to help build a data model
for everyone (your name & company name will remain
anonymous.)
• Contact me (contact info on next slide)
– With Questions
– With Feedback
– If you’d like help assessing your SP
implementation and learning more about how to
get to greater SharePoint Maturity.
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 85

60. Contact Information
Sadie Van Buren
• Twitter: @sadalit
• LinkedIn: http://www.linkedin.com/in/sadalit
SharePoint Maturity
• Twitter: @SPMaturity
• http://www.sharepointmaturity.com
– Tools, templates, and resources
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 87

61. Thank you!
7/30/2011 - #spmaturity @sadalit ©2011 Sadalit Van Buren 88