List of figures and tables |
|
ix | |
About the authors |
|
xi | |
1 Introduction and overview |
|
1 | |
|
Why do we need scenarios for information system design? |
|
|
1 | |
|
|
3 | |
|
Scenario-less planning: what can go wrong? |
|
|
5 | |
|
The structure of the book |
|
|
6 | |
|
|
10 | |
PART 1 PRACTICAL THEORIES |
|
|
2 Framework and fundamentals |
|
|
13 | |
|
Purpose of the system and formation of the design team |
|
|
13 | |
|
|
18 | |
|
Identify user groups' environments |
|
|
20 | |
|
Methods for identifying users and their environments |
|
|
21 | |
|
Other considerations for identifying users and their environments |
|
|
26 | |
|
New human activities: training and education |
|
|
29 | |
|
|
31 | |
|
|
31 | |
|
3 Organizational cultures: ecological and cognitive approaches |
|
|
33 | |
|
|
33 | |
|
How to 'read' the client organization |
|
|
35 | |
|
|
38 | |
|
Real-world examples and analysis |
|
|
39 | |
|
Understanding organizations using ethnographic research tools |
|
|
40 | |
|
Observation as a data-gathering method |
|
|
42 | |
|
Interviews with members of the client organization |
|
|
45 | |
|
Focus groups as a way to gather data |
|
|
47 | |
|
|
49 | |
|
Sense-making as a cognitive tool to understand organizations |
|
|
50 | |
|
|
52 | |
|
|
52 | |
|
4 Communicating with stakeholders |
|
|
55 | |
|
Know who should get involved |
|
|
55 | |
|
|
57 | |
|
|
57 | |
|
|
59 | |
|
Providing a space for interaction |
|
|
65 | |
|
Keeping plans and ideas secure |
|
|
67 | |
|
|
68 | |
|
|
70 | |
|
|
71 | |
PART 2 THEORETICAL PRACTICES |
|
|
5 Managing scenario design projects and knowledge |
|
|
75 | |
|
|
75 | |
|
Who and what will be managed? |
|
|
76 | |
|
Strategic planning and goal setting |
|
|
78 | |
|
Project management principles |
|
|
82 | |
|
Knowledge management defined, again |
|
|
85 | |
|
Managing project knowledge |
|
|
87 | |
|
|
90 | |
|
|
90 | |
|
|
93 | |
|
|
93 | |
|
|
96 | |
|
Appropriate technologies for stakeholders and the design team |
|
|
102 | |
|
What strategies will work? |
|
|
110 | |
|
|
111 | |
|
|
112 | |
|
|
113 | |
|
|
113 | |
|
|
114 | |
|
|
116 | |
|
Reasons for idea management |
|
|
119 | |
|
|
124 | |
|
During-project development |
|
|
127 | |
|
|
129 | |
|
|
131 | |
|
|
131 | |
|
8 Documentation and prototyping |
|
|
133 | |
|
|
135 | |
|
Setting standards for prototyping |
|
|
136 | |
|
Documentation of stakeholder studies and system development |
|
|
138 | |
|
Approaches to prototyping in system design |
|
|
144 | |
|
|
152 | |
|
|
153 | |
|
9 Scenarios and information design: a summary |
|
|
155 | |
|
|
155 | |
|
|
158 | |
|
|
162 | |
|
|
163 | |
Appendix: Use of scenarios in information design - a checklist |
|
165 | |
Complete references |
|
171 | |
Index |
|
177 | |