Repository Access Management and Taxonomy
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

View only
 
 
ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
Created by Please make a copy of this sheet and add it to your drive before modifying the content. You can also download it on your computer.
2
www.getenjoyhq.com
3
Purpose Examples
4
ProjectsA project is a workspace where you can add all the raw data related to your research question and analyze and write down your findings and insights.Personas
New features/products
Hypothesis
Usability testing
5
Project LabelsLabels are use to organize your projects so they are easy to filter and find by colleagues. You can use multiple labels for projects, some teams combine labels that describe the type of study, the product or product area it relates to. You can use as many labels as you need.Label 1: Usability
Label 2: Onboarding
Label 3: IOs App
6
DocumentsWe use the term "Documents" to describe data in EnjoyHQ. It could be a note, a video or interview transcript. They are all documents in the context of EnjoyHQ. Normally is your raw data.Interview transcript
Survey responses
Support tickets
Research Notes
Video files
7
HighlightsHighlights are snippets of text that contain evidence that is relevant to your research question. Normally they are customers quotes describing their behavior or problems.Customers quotes
Short Statements
8
TagsTags are mostly use for analysis. We recommend using tags for high level classification. Feature request
UX Issue
Pre-Sales
Signup
Usability Problem
Onboarding
Bug
Upgrade
Integrations
Trial End / Non-Upgrade
General Feedback
Retention
Cancellation
9
PropertiesYou can think of properties as super tags. You can use properties to add more context to your highlights. They are very flexible in that you can create one property and associate multiple values to it. That way you can create patterns for classification. Property: Objection
Values:
No budget
No buy-in
Customer missed value
Internal Barrier
Needed more support
Stuck in status quo
Critical feature is missing
Failed security review

Property: Product Area
Values:
Account settings
Uploads
Exports
API
Check-out
Billing
10
StoriesYou can think of Stories as mini-blog posts that help you capture your learnings and share insights with your team and entire organization. You can think about Stories as more digestible research reports. For Atomic research fans, at Stories is your unit of insight. It is the finding and any data point that can help back it up.Users that successfully add seven friends to the platform stay active and have more sessions than users that do not invite friends.

User experience high levels of anxiety when booking a nanny outside their neighbourhood.

Color blind users where unable to find the export feature on the dashboard.
11
Stories LabelsLabels are use to organize your Stories so they are easy to filter and find by colleagues. You can use multiple labels for Stories, some teams combine labels that describe the type of insight, the product or product area it relates to. You can use as many labels as you need.
In the same way you use labels to organize your projects, you want to use labels to organize your insights. It is ok if they overlap, the idea is to make it as easy as possible for the rest of the organization to find information.
Label 1: Onboarding Experiment
Label 2: User Motivation
Label 3: Product Area
12
Research SummariesResearch summaries are the equivalent of your research reports. You can write a summary within a research project or you can also group a series of Stories and share them as the final outcome of your research.
Both the project summary and the stories have the same purpose, to help you share insights easily. The benefit of creating Stories is that you make your findings more digestible and you can link them to each other as you generate more insights. However, there will be time when writing a long summary document will be the best approach and that when Project Summaries can help. You can always attached Stories to summaries anyway so they don't have to work separately. All read-only users have access to both Summaries and Stories.
Summary: Revised Personas for the Enterprise Segment.
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
Loading...