Adam's topic was "Problem Solving: How I Do It." The questions that he asks prior to embarking on a problem are:
- What is the problem I'm solving? (Am I solving the right problem?)
- What is the big picture? (Where is the problem that I am currently solving fit into a larger context?)
- How much time do I have?
- How precise to I have to be?
- What is my rhythm and how does it fit with this project?
- What are my resources?
- Does the place in which I'm solving this problem help or hinder the process?
- How many people do I have? (Is the team big enough? Is it too big?)
- Do I have all the skills necessary?
- Do I have a realistic understanding of what my skill level is for the problem that I'm about to solve?
- If I'm not good enough at something, is there enough time for me to get good, or do I have to contract it out?
- How important is this particular step?
- How important is it that I get this step right?
- Is my machine deteriorating?
- Is this a step I might be able to improve later?
- Am I missing something stupid? (Am I being too clever? Is there a simpler way?)
- Am I sure that how what I'm doing fits into the larger picture?
- What does the whole picture look like now that I've solved this part?
...my crew knows intimately that I hate to look for things, so before I start a project, I go everywhere in the shop and I get every tool that I need and put it on the table. And I get every material that I need, and I put it on the table. And I get everything lined up so that I don't have to move once I'm in the sluice; once I'm rolling, I wanna keep on rolling......which is essentially mise en place for engineers. I'm glad to know that there's an overlap.
Adam spoke for about 25 minutes, and then took questions for another 25 minutes; the latter part is where he really shone. I loved that he took a ton of questions from the kids in the audience.