Build Goals 2011

Build Program Goals for 2011

Accessibility

• LCD monitors at different heights on the walls/adjustable LCDs to accommodate different heights and people's varying vision levels.
• Work with Access and Ability working group on Build job duties, trainings, policies, etc in re: to accessibility of the Build program
• Better communication with the front desk re: volunteers with specific needs and shift scheduling
• Making shelves and other supplies easily reachable for people in wheelchairs and people who aren't tall.

Documentation

• Improve checklist readability
• Account for different learning styles w/ our documentation and teaching materials.
• Update wiki pages (Build tips, etc) and having print-outs of them
• Create educational "Learn More" packets
• Have a documentation intern to lead these projects

Production

• We need more high end systems (maybe collaborating with the city of

Beaverton)

• Hardware Grants is doing better than ever, we might need to create a

waiting list for desktops or have shelves that are off-limits for grants. -Leah will look in the database to try to detect trends in outputs and disbursements

• Jason will be sending a report every month that details how many

systems sold in the store are high ends

• Have enough computers for volunteers, grants, the store. Perhaps even

setting a numeric goal?

• In terms of quality of production: better attention to detail, fewer

systems going to Tech Support. (Having Reuse Program Coordinators in Tech Support should encourage this feedback loop but we also want an ctual automatic feedback channel). -Chris will reach out to Paul on this.

• Reexamining sign-off procedure of printmes. Will the new electronic

sign-off method allow us to discern any patterns in returned boxes? ?Including a checklist of things that have been done to the system?

• Training checklist for Build instructors is helpful and needs to

continue to be followed, especially the one month check-in

• Have Build instructor training quarterly, rather than only twice a year
• LCDs out of Build, optical drive testing in

Program

• integrating Spanish Build into regular Build shifts
• integrating Laptops in such a way that it doesn't impede on Desktop

Build's output needs

• integrating Macs once all Macs are Intels
• better balance production and education (right now we don't have many

completed systems but there has been a big push to make Build more educational)