About the author |
|
xi | |
Preface |
|
xiii | |
|
|
1 | (16) |
|
|
1 | (2) |
|
Dashboard and reports---the data storefront |
|
|
3 | (1) |
|
Build it and they will come (spoiler: they won't) |
|
|
3 | (1) |
|
Supporting decision-making |
|
|
4 | (2) |
|
|
6 | (2) |
|
|
8 | (2) |
|
|
10 | (2) |
|
The elements of a process |
|
|
12 | (3) |
|
Shifting the data culture |
|
|
15 | (1) |
|
|
15 | (2) |
|
|
17 | (16) |
|
|
18 | (1) |
|
|
18 | (1) |
|
|
19 | (1) |
|
|
20 | (1) |
|
|
21 | (6) |
|
|
27 | (3) |
|
|
30 | (1) |
|
Who and what will be impacted? |
|
|
31 | (1) |
|
|
32 | (1) |
|
|
33 | (14) |
|
The seven principles of user experience |
|
|
34 | (4) |
|
The user experience formula |
|
|
38 | (1) |
|
Who owns user experience? |
|
|
39 | (1) |
|
Answering the why, what, and how |
|
|
40 | (1) |
|
|
40 | (1) |
|
|
41 | (2) |
|
Breaking down the persona |
|
|
43 | (2) |
|
|
45 | (2) |
|
04 Requirements gathering |
|
|
47 | (20) |
|
|
49 | (1) |
|
The two types of interviews |
|
|
50 | (1) |
|
|
51 | (2) |
|
|
53 | (1) |
|
|
54 | (3) |
|
|
57 | (5) |
|
|
62 | (3) |
|
Alternatives to interviews |
|
|
65 | (2) |
|
|
67 | (16) |
|
|
69 | (2) |
|
Scoring business value questions |
|
|
71 | (1) |
|
|
72 | (1) |
|
|
73 | (4) |
|
The bigger picture of scoring |
|
|
77 | (2) |
|
|
79 | (2) |
|
|
81 | (2) |
|
|
83 | (20) |
|
|
84 | (1) |
|
|
85 | (3) |
|
Rolling the agile principles together |
|
|
88 | (1) |
|
|
89 | (1) |
|
The stages of a successful process |
|
|
90 | (6) |
|
|
96 | (2) |
|
|
98 | (1) |
|
|
99 | (1) |
|
|
100 | (1) |
|
|
100 | (1) |
|
|
101 | (2) |
|
|
103 | (22) |
|
The story arc applied to insight |
|
|
106 | (1) |
|
|
107 | (1) |
|
The challenge of enterprise storytelling |
|
|
108 | (1) |
|
Translating acts to dashboards |
|
|
109 | (1) |
|
|
110 | (2) |
|
|
112 | (1) |
|
What does the end user need to see? |
|
|
113 | (1) |
|
Key performance indicators |
|
|
114 | (3) |
|
How should it be filtered? |
|
|
117 | (1) |
|
Scenarios for taking action |
|
|
118 | (1) |
|
|
119 | (2) |
|
The scenario mapping flow |
|
|
121 | (2) |
|
Getting to the "So what?" |
|
|
123 | (2) |
|
|
125 | (24) |
|
User interface design principles |
|
|
127 | (3) |
|
|
130 | (2) |
|
|
132 | (1) |
|
|
132 | (2) |
|
Tabs and grouping of BVQs |
|
|
134 | (2) |
|
One dashboard layout to rule them all |
|
|
136 | (1) |
|
|
137 | (2) |
|
|
139 | (2) |
|
|
141 | (5) |
|
|
146 | (1) |
|
|
147 | (2) |
|
|
149 | (16) |
|
|
152 | (3) |
|
|
155 | (3) |
|
|
158 | (2) |
|
|
160 | (1) |
|
Tying back to the process |
|
|
161 | (2) |
|
|
163 | (1) |
|
|
164 | (1) |
|
10 Adoption and ownership |
|
|
165 | (16) |
|
Compensation based on adoption |
|
|
168 | (2) |
|
|
170 | (1) |
|
Technology approaches to adoption |
|
|
171 | (2) |
|
|
173 | (1) |
|
Assigning ownership and accountability |
|
|
174 | (1) |
|
|
175 | (2) |
|
|
177 | (1) |
|
What gets measured, gets managed |
|
|
178 | (3) |
|
11 Training and documentation |
|
|
181 | (16) |
|
|
182 | (1) |
|
|
183 | (1) |
|
The modern approach to user enablement |
|
|
184 | (1) |
|
Degree of user competence |
|
|
185 | (1) |
|
Where should training happen? |
|
|
186 | (2) |
|
|
188 | (1) |
|
Types of training content |
|
|
189 | (5) |
|
|
194 | (2) |
|
The importance of enablement |
|
|
196 | (1) |
|
|
197 | (10) |
|
|
199 | (4) |
|
|
203 | (1) |
|
|
203 | (2) |
|
|
205 | (1) |
|
|
205 | (2) |
Index |
|
207 | |