Reflection: I don't know how true it is, but I remember a friend once told me that you only needed to be 10% smarter than something to operate it. Depending on the object, that seems accurate, and at times a little depressing (sad to think a door is smarter than you). However, after reading the first couple of chapters, perhaps it is the bad design of the objects and that they aren't intuitive, not that the objects are smarter than me.
I really liked the tables that were used in chapter 2. But as each one added another layer, they became more complex. I found myself having difficult not only remembering what each one was showing but the purpose of it as well. I thought this was ironic because it felt like a bad design as he kept building on the same structure
The seven stages of action was interesting to read as well. It is a good method to ensure the item, plan, etc. work as it should. I really like that he brought in modeling and simulation. I think this is something that we don't usually think about or take for granted. Even this mapping assignment is a way to model ideas. But what is important is understanding the problem, what you think should be done, and what the customer thinks should be done. A problem is rarely just one point of view, and if a model is based on one view, it might not function as it should or solve any problems.