|
|
Friday, 7 January 2005
|
|
Putting Context Into Context.
This is a nice article that tries to analyze context, or elements of context that can influence design outcomes.
- Goals: What is the user trying to accomplish? How do the user's actions fit into the objectives of the organization?
- Process: What are the steps the user will follow? How does information flow from one step to the next? What are the various roles (such as creator, contributor, editor, or approver) that are involved?
- Inputs & Outputs: What materials and information will the user need to successfully use the interface? What will they need from the interface to continue with their overarching goals?
- Experience: What similar things has the user done in their past? How has the organization survived without this design in the past?
- Constraints: What physical, temporal, or financial constraints are likely to impose themselves on the user's work?
- Physical Environment: How much room does the user have to work? What materials on their desk? What access do they have to necessary information (such as user manuals)? What is taped to their monitor?
- Tools In use: What hardware and software does the user currently use?
- Relationships: What are the interconnections between the primary user and other people who are affected by the tool?
[Source: elearningpost]
10:32:22 PM
|
|
|
© Copyright 2005 Bill.
Last update: 16/1/05; 10:39:29 PM.
|
|
January 2005 |
Sun |
Mon |
Tue |
Wed |
Thu |
Fri |
Sat |
|
|
|
|
|
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 |
16 |
17 |
18 |
19 |
20 |
21 |
22 |
23 |
24 |
25 |
26 |
27 |
28 |
29 |
30 |
31 |
|
|
|
|
|
Dec Feb |
|
|