Team Building
From Library Success: A Best Practices Wiki
(Difference between revisions)
| (One intermediate revision by one user not shown) | |||
| Line 1: | Line 1: | ||
| + | == Technology Review Team Tips == | ||
| + | |||
| + | * divide technology projects into two stages -- a review stage and a design stage. | ||
| + | * Keep your knowledgable technophiles and graphic designers out of the review stage, except as a resource or to answer questions. That way, you can have people identify user needs without thinking about how to solve them. | ||
| + | * During the design stage, you bring in your technophiles and aesthetes and present them with a particular problem to solve. Ie. "Our users want to do x, y, & z at the library -- how can we let them?" This method keeps teams thinking about using technology and design as solutions to particular service problems, rather than having technology for technology's sake. | ||
| + | |||
| + | |||
[[Category:Management and Leadership]] | [[Category:Management and Leadership]] | ||
Latest revision as of 14:16, 13 July 2005
[edit] Technology Review Team Tips
- divide technology projects into two stages -- a review stage and a design stage.
- Keep your knowledgable technophiles and graphic designers out of the review stage, except as a resource or to answer questions. That way, you can have people identify user needs without thinking about how to solve them.
- During the design stage, you bring in your technophiles and aesthetes and present them with a particular problem to solve. Ie. "Our users want to do x, y, & z at the library -- how can we let them?" This method keeps teams thinking about using technology and design as solutions to particular service problems, rather than having technology for technology's sake.
