Talk:Olin repair center: Difference between revisions
m (New page: == Tool suggestion == sounds to me like you should have an rt queue to track fixes, and to keep in contact with the people you are fixing them for. Watch your logistics closely as far as ...) |
mNo edit summary |
||
| Line 2: | Line 2: | ||
sounds to me like you should have an rt queue to track fixes, and to keep in contact with the people you are fixing them for. Watch your logistics closely as far as tracking what comes in and what goes out. (from Babbing) |
sounds to me like you should have an rt queue to track fixes, and to keep in contact with the people you are fixing them for. Watch your logistics closely as far as tracking what comes in and what goes out. (from Babbing) |
||
== Test untrained-user repairs == |
|||
I'd love to get observations on how users try to fix their own laptops - what stops them? what scares them? what breaks? How can we turn people from timid, technically-unskilled "can I just hire you to do it for me?" folks into knowledgeable, confident hackers? Get non-engineers with little computer experience into the room, hand them tools and point them towards resources, and see at what point that breaks down (and then build tools and resources to get them past that point, or get the community to help). I'd like to make it as easy as possible for people to do things on their own ''without'' the benefit of a repair center and loads of shiny equipment nearby. [[User:Mchua|Mchua]] 02:02, 11 February 2008 (EST) |
|||
Revision as of 07:02, 11 February 2008
Tool suggestion
sounds to me like you should have an rt queue to track fixes, and to keep in contact with the people you are fixing them for. Watch your logistics closely as far as tracking what comes in and what goes out. (from Babbing)
Test untrained-user repairs
I'd love to get observations on how users try to fix their own laptops - what stops them? what scares them? what breaks? How can we turn people from timid, technically-unskilled "can I just hire you to do it for me?" folks into knowledgeable, confident hackers? Get non-engineers with little computer experience into the room, hand them tools and point them towards resources, and see at what point that breaks down (and then build tools and resources to get them past that point, or get the community to help). I'd like to make it as easy as possible for people to do things on their own without the benefit of a repair center and loads of shiny equipment nearby. Mchua 02:02, 11 February 2008 (EST)