Be a Problem-Solver, Not an Order-Taker

Posted by Phil Weber on December 10, 2013

This post is talking about software, but the principle applies to any consulting situation, including instructional design:

Just because people ask for something doesn’t mean we should build it… It’s our skill and responsibility as creators and experts to understand and synthesize user feedback into great products, and not slavishly do what our users say, producing one more pointless product after another.

Remember that the next time a client requests “training” focused on delivering information, rather than building skill or changing behavior. As Cathy Moore so eloquently puts it, “Be a problem-solver, not an order-taker!”


Leave a comment