Web Strategy: An Initial Review
Stakeholder Feedback and Next Steps
Robert Williams
November 14, 2017
Our Digital Front Door
2
2
Presentation Overview
�
3
3
Web Content Strategy Objective and Goals
4
4
2013 Target Audiences
Users | Goals |
Potential employees | Browse opportunities, submit resumes |
Researchers | Find, access publications |
Policymakers | Obtain objective evidence to inform or support policies |
Clients and prospective funders | Learn about Mathematica’s capabilities, make contact about contracting |
General public | Browse research and publications on topics of interest |
5
2013 Content Framework by Content Types
What users want to do: | FIND & ACCESS INFORMATION � | CONNECT
| |
What MPR wants to do: | PROMOTE | EXPLAIN | INFLUENCE | ENGAGE | BUILD RELATIONSHIPS |
Sample Content types or functions supporting user/business goals |
|
|
|
6
6
Content Framework - Overarching
What is mathematica-mpr.com?
7
7
Mathematica-mpr.com Site Traffic
Source: Google Analytics, July 2014 - October 2017
Year | Pages/Visit | Bounce Rate |
2014 | 3.16 | 42% |
2015 | 3.20 | 46% |
2016 | 3.56 | 50% |
2017 | 3.11 | 57% |
8
8
Pageview Breakout by Site Section 2014 - 2017�
Source: Google Analytics, July 2014 - October 2017
9
9
Internal Stakeholder Feedback
How well is the current content framework serving our strategic goals and the experiences of our priority users?
10
10
Internal Stakeholder Feedback
Key discussion topics:
11
11
Internal Stakeholder Feedback
Hard to find information…I didn’t even know we had a podcast – that is great, but what is the next step we want them to take? …Some content and document types in the search menu don’t having meaning to me, and I work here…Designs and layout have a print orientation, creates some visual inconsistency over time. Photos have a generic look; we have resources and have created original imagery, should be using original imagery more frequently when possible …Site content can feel a bit “over-engineered”...Search results don’t display chronologically.. Boolean searches don’t work to refine search results… I refer people to Google search instead of our search…we need to tell our story on the homepage… not sure what more storytelling content gets us. Will just be more words on the site and we already have too many words… [Federal Agency] prospects are probably going to the site only as part of a passive vetting...checking bios, looking to get a sense of firm’s polish, legitimacy.; not that integral to the RFP process..State and foundation prospects don’t know us. They have no place to go on the website…Centers content becomes moribund; need to have a rescue mission plan…Our URL is hard to remember, looks awkward … After doing a blog post, there is no mechanism for getting feedback.. To much review in the blogging process; makes it difficult to sustain blog content …Need more publicity on the work… ”Publications” needs an academic look and feel… Sitecore is a constraint, often get told ‘we can’t do that in Sitecore’… Recommendation engine has gotten better, but doesn’t seem to be working as well as it could… too complex, wordy… We’re trying to get into new markets, website doesn’t help because the conversation is not “how can we help you?” Capabilities list is complex… States want to see state examples; where can we send them?… Competitors are rebranding to cleaner designs [specifically: Booz, ICF, NORC, Urban, Westat] …blog doesn’t look like a blog; can’t search by authors… We should have aesthetic alignment with academic-oriented research organizations…academic users are used to robust digital search tools and indexing approaches.. we want to showcase the depth of work being done including working papers in which there is an academic constituency for…Topics areas on homepage feel disparate. They don’t feed into an overarching story.. Site “feels” non-academic, especially for work section. We want to distinguish MPR from consulting firms, be more aligned with academic-focused researchers…data analytics is hard to find; is it a focus area or capability?... Going from PA to PI, support model may need to change; we may need dedicated SME content owners and increase the focus on business development…
12
12
Broad Feedback Themes
BRANDING
FINDABILITY
ENGAGEMENT
Tell our story better
Refine design
Make content easier to find
Create more opportunities for engagement
Funnel users to content that supports communications or engagement
13
13
Key Theme: “Tell Our Story Better”
We have “lots of words”, but where and how to engage users with the broad Mathematica story and discuss…
14
14
Key Theme: Competitor Design Trends
Expanded widths ( >960px)
Simpler Gallery UIs
Bold Usage of Photography & Type
“Storytelling”
Long Scrolling
Brand Promises
Offerings/Capabilities on homepage
Prominent Search
Markets \Served
Expert Highlights
News
Publications
People
Contact Calls to Action
15
15
Key Theme: “Design Consistency”
16
16
Key Theme: Findability: “Content Hard to Find”
Search feedback:�
17
17
Key Theme: Findability: “Content Hard to Find”
Layouts and content design:
18
18
Key Theme: “Engagement”
Connecting:�
19
19
Going Forward
20
20
Going Forward: Digital Strategy Functions
Managing Inputs:
Conducting Analysis:
Delivering Outputs:
21
21
UX-focused Research, Planning, and Execution�
Objective:
Align a digital product vision with:
22
22
UX-focused Research, Planning, and Execution�
Goals:
23
23
Tactics: 4 Project Tracks
24
24
Timing: Q1 2018 - Q1 2019
2018
Q1
Q2
Q3
Q4
Q1
Q2
Q3
Q4
Survey Implementation
1. Planned Projects
2. UX Projects
3. New Iterative Improvement Projects
4. Establish Digital Product Vision & Determine Execution Approach
2019
UX Engagement
Decision on Redesign
UX Recommendations
25
25
Track 1: 2017-2018 Planned Projects
�
26
26
Track 2: User Research - Site Survey
27
27
Track 2: User Research - UX Engagement
28
28
Track 2: User Research - UX Engagement
When to Use Which User-Experience Research Methods
by Christian Rohrer on October 12, 2014
Tactical considerations for UX research:
29
29
Track 3: Iterative Improvements
Iterative Enhancement Projects: Design, development or content projects pulled from backlog based on the UX Research project.
30
30
Track 3: Iterative Improvements
Example Project: Revise Site Navigation Approaches and Taxonomy
31
31
Track 3: Iterative Improvements
Example Project: Build new template for capabilities:
32
32
Track 3: Iterative Improvements
Example Project: Revamping information design of “related” components:
33
33
Track 4: Establish Digital Product Vision �
Long-term Digital Product Vision
34
34
Digital Product Vision�
From… | To? |
|
|
|
|
|
|
|
|
|
|
35
35
Next Steps
36
36
Questions?
37
37
Key Theme: “Design Consistency”
How consistent are the design and UI treatments for:
38
38
Key Theme: “Design Consistency”
Buttons, CTA links, page functions and fields:
39
39
Key Theme: “Design Consistency”
Secondary in-page navigation:
PDF downloads:
40
40
Key Theme: “Design Consistency”
Video presentation:
41
41
Key Theme: “Design Consistency”
People:
42
42
Key Theme: “Design Consistency”
Reference to work/projects:
43
43
Key Theme: “Design Consistency”
Block quotes, callouts:
44
44
Key Theme: “Design Consistency”
“Related” content:
45
45
Key Theme: Competitor Design & Content Trends
46
46
Key Theme: Findability: “Content Hard to Find”
Navigation:
47
47
Key Theme: “Engagement”
Deeper Engagement:��
48
48