1. PNW Research Station SharePoint Survey
Baseline Assessment, January 2017
Pacific Northwest Research Station

2. Whom did we survey?
All PNW Employees (n=~350?)

3. Who responded?
Only 10 of 109 did not disclose program affiliation

4. Who responded?
Only 10 of 109 did not disclose program affiliation

5. SharePoint Use Frequency

6. What’s Frequently Accessed?

7. “Other” Frequent Needs
Four Main “Other” Categories
Awareness
Collaboration
Reference
Scheduling

8. “Other” Frequent Needs
Awareness
DC SharePoint site
File sharing in research
Program specific administrative activities and workflow
Sharing info with scientists
Station reports (not CRIS/RITS but the old PNW profiles)
WO FSweb for R&D

9. “Other” Frequent Needs
Collaboration
Allocation and budget transfers in Excel or Access.
Coordinating with other staff on hiring projects, gear inventories, etc.
Leadership in cross station working groups, such as Experimental Forest and Range Working Group
PNWRS Web Team
Project Tracking, task management and collaboration

10. “Other” Frequent Needs
Collaboration (cont’d)
RMA safety Committee Meetings
Shared projects
Sharing documents for joint editing
Station Management Team
Team info

11. “Other” Frequent Needs
Reference
Centralized study plans
Data
Drupal site wiki library / instructional manual.
Historical documents (e.g., work force planning, PNW profiles, planning docs)
Org charts
Personnel rates and days

12. “Other” Frequent Needs
Reference (cont’d)
Program charters
Space policy
Synthesis of accomplishment reports
Past briefing papers
Telework policy
Transaction registers in Excel

13. “Other” Frequent Needs
Scheduling
Shared projects and special events pages
Special events pages
Station wide calendar showing conferences, workshops PNW scientists are attending
Program specific administrative activities and workflow

14. Gauging Web App Interest
None, Not So, Unsure, Somewhat, Highly
Quickly go through “Pie” charts for each app
Organized from greatest interest to least interest
Top Five:
List App for Calendar Events
Library App for PDF and Other Documents
Library App for Instructions and How-To Guide
Library App for Photographs
Library App for Personal or Project Contacts

48. Envisioning Apps for Apps
Q4: Scoping how SharePoint might be applied at PNW
Free text responses grouped by program
Reveals different use cases by organization type
Use cases reveal user behavior
User behavior informs user experience / user interface design
Categories
Organization
Navigation
More analysis needed here

49. Identify Key Features

50. Identify Key Challenges

51. Identify Key Challenges

52. Identify Key Challenges

53. Identify Key Challenges

54. Identify Key Challenges

55. Identify Key Challenges

56. Identify Key Challenges

57. Identify Key Challenges

58. Identify Key Challenges
“Other” Responses (Free Text)
Importance of external collaboration re-iterated 9 times across 19 “other” responses.
Concern for redundancy (USDA Connect or simple as an alternative)
Data management / data loss fears

59. SharePoint Likes
Perceived Strengths

60. SharePoint Dislikes
Perceived Weaknesses

61. Next Steps Build on Strengths Address Weaknesses
S.W.O.T – Strengths, Weaknesses, Opportunities, Threats
Build on Strengths
What do people like about SharePoint?
How do we replicate / build on strengths?
Address Weaknesses
What do people dislike about SharePoint?
How do we minimize or mitigate negative aspects?
Identify Opportunities
Interest in specific SharePoint apps (Q3 follow-up)
Specific use cases (from Q4 ideas)
Anticipate Threats
Governance Document, as one example
Q7 – Challenges – No External Collaboration