Genial Brand Book

start

HSL SR & ScR Content

Website Mock Up

Why the Change?

Attention Span

We have a short window of opportunity to grab a readers attention and sustain it. A lengthly body of text, even if it is well written is likely to overwhelm readers.

Level of Expertise

Our community base is large, and the range of expertise is wide. The content visible on the HSL website should be valuable across this spectrum. (Student --> Faculty) (unexpereinced ---> Expereinced)

Build Structure

We have so much information on the website, it is hard for a user to discern what is and what is not useful for them.

Solving a Probelm

The problem we are seeing often: 1. Wrong methodology choice 2. Lack of preliminary topic investigation 3. Lack of project planning

Next

+ The Fix

+The Fix

+ The Fix

+ The Fix

How to display?

What content?

The Decisions...

Goal is to simplify and de-silo the content by:

• Providing landing pages to simplify navigation and provide order to the key resources.
• Layer in and link out to more complex information, without causing initial information overload.

Preliminary Topic Investigation

Systematic Review Process

Scoping Review Process

KNOWLEDGE BASE - The Key KBAs

+ Visual B

+ Visual A

• Does not reduce informaiton overload (lots of text)
• Doesnt allow for interactive elements to break up content

CONs

• Comfortable for everyone to create
• Easy to edit/update
• Can layer in short videos

+ Visual

PROs

• Requires Aaron's assistance
• Not as easy to edit.

CONs

Content Display Options

• Allows for more engaging interactive elements
• Breaks content up into digestable pieces

PROs

Articulate Embed

HSL KBA basic

User Expertise

Our user commuinty has a large range of expertise with systematic and scoping reviews. Majority of inquires are coming from first-timers. We want the resources we create to be helpful to all levels of expertise, and/or be very easy to navigate, so that more advanced users can find what they're looking for.

Our Expertise

Per Anna's request, let's connect people with the experts on the topic. Like Cochrane for Systematic reviews and JBI for Scoping reviews. "We don't want to re-state what is already said" What we can do is help our community navigate through the complexity of these resources, currating the key resources for them, giving clarity as to why it is important to read, and providing a pathway forward. Take our expertise of knowing our communities need + our expertise on how to engage with information = use as a strategy of developing content.

These problems should influence the landing pages that we create. More details to come.

Create content with these problems in mind

Nest one button in a KBA which will open a pop up window with an interactive lessons from articulate rise.

Present content in a timeline strucutre to: 1. Provide details on roughly how long each step will take. 2. Establish order, emphasizing to do preliminary topic investigation first! 3. Give an overview of the key methodological steps. See to the right an example from articulate rise.

Timeline Structure

Goal is to simplify and de-silo the content by:

• Discuss the tasks of a PTI broadly
• Link out to more specific KBAs/insights. Such as term havesting and question development frameworks.
• Break up content and provide variety. (Use details drop down menus, add short videos, use articulate rise embedd)
• Explain nuances between specific methodology

Example Structure of the KBA:

• Overview of PTI's Purpose
• Explaination of what you can learn from the KBA
• Sections split up based on the purpose of the PTI and the tasks associated with fulfilling that purpose.
• Explain how the process differs for Systematic and scoping reviews
• Provide Checklists, linked to Basic Page.

Instead of indavidual KBAs on Preliminary Topic Investigation for Systematic, Scoping Reviews, general research, and each corresponding insight with a checklist, there can be one landing page!

Instead of many, many very specific KBAs and insights, creating landing pages, will give structure for users. Keeping information in one place, providing an order for users who need it, and flexibility for users who like to bounce around. More detailed information can be layerd in, by linking out to expert resources, or linking to other KBAs, insights and tutorials. See the scoping review methodology infographic, as an example. This provides an order of operations, compiles key resources and information, and links out to the experts and more specific HSL content.

Create Structure

Timeline Structure

Present content in a timeline strucutre to:

• Provide details on roughly how long each step will take.
• Establish order, emphasizing to do preliminary topic investigation first!
• Give an overview of the key methodological steps.

Example of how to organize content using headers and the details drop down menu.

Nest multiple buttons in a KBA which will open a pop up window with bite-size interactive lessons from articulate rise.

Break up Content

• Offer conent in multiple mediums (video, activity, text, audio). See example image below.
• Split up content into bite-size pieces.
• Empasize importance of lesson, provide context as to why it is important to them, and then link them out to learn more!