Nmap:Management/Workshop Design::3D Printer X 18.10

Tension Processed

Marcin claims the workshop is a transformative experience because people build something in 1 day w/ no prior knowledge. At best, this claim is unsubstantiated except for what Marcin says. There's no surveys, no testimonials, no recorded interviews. However, based on what I've heard from other non-Marcin sources, I've heard from 4 diff folks that it's: disorganized, badly time budgeted, folks expectations upset, final product outcome not 100% successful, safety procedures woefully in need, rumor mills misleading participants leading to re-work, incomplete knowledge of entire building process on an individual basis, and inadequate support for total beginners. This should not be so.

Process for Improving

I recommend some variation of applying "The Basics of Process Mapping" found here.

Here's what gets done in this process:

1. Use 3 diagrams to visualize processes: swimlane diagram, flowchart, and relationship maps.
2. Identify metrics from the outside-in: for a specific item, who is the customer? What do they value? (metrics) And what does demand look like?
3. Figure out how to track: "% Complete and Accurate" and "First Pass Yield" % defect-free items and "throughput" # items completed / unit time
4. Figure out how to automate any metrics
5. Use the 6 countermeasures to improve workflow: workflow design, information systems, motivation & measurement, human resources, policies & rules, facilities

Initial Plan

• Organize build into "Build Phases," with the flow: Teach-Build-Approve-Feedback
• Identify how to measure the things that workshoppers value: learning theory, learning technical skills, feeling supported while learning
• Insist that all questions be asked only to fellows. We will document all questions and provide accessible answers, on-the-fly.
• During build, attendees follow this workflow: attempt-struggle-reference-ask... in doing this, improve documentation.
• As QC folks get trained, follow this workflow: invite-ask-prompt-standby

Instructor Flow

1. Theme - at the beginning of each module, speak to the theme.
2. Teach - for each build phase, cover conceptual work, then technical work. Refer to theme as relevant.
3. Build - let people build. stay in 1 spot, and let people come to you. Potentially have a queue system. "Instructor, queue me up -- Revlon--Alex" Give printers names. (specify? with conceptual q, technical q, approval)
4. Document - cover any questions. ask folks to check reference first. document answers.
5. Approve - show people a printed-out quality control checklist. Guide them and doing it themselves. Watch them guide the next person in doing it themselves. Give the 1st approved person a special necklace or colored index card, as well as they checklist. Now when ppl queue up, they can be handle it.
6. Feedback - When people are approved, have them fill out a short survey about their xp in that build phase.