Reflection on Reading 2

Here are my takeaways from this week's reading:
* There is a lot of good, useful information in the early writings by the pioneers of this dicipline that is still valuable for today's issues. I was pleasantly surprised to see that the readings were not really stale or dated.
*In particular, the readings (Kaufman and Romiszowski) underscored the importance of a clear "future state" in the front-end analysis review. I am a firm believer that a major issue in front-end analysis is that the future state of the organization (context) or the job is seldom articulated in writing, especially if one is relying on strategic plans and job descriptions respectively for data. They are usually either outdated or, at best, written for the current state, thus being useless in defining the "need" or "gap."
*Bucketing the Issues: I thought that 111-5, Joe Harless' An Ounce of Analysis, was both simple and practical in its approach to bucketing the problems. I've never differentiated the issue at hand by skill/knowledge, environment or motivation before. I've used other, different buckets or labels (i.e., management, leadership, process) but these broad buckets seem better. I had an aha moment here. On that same note, I also like Romy's Performance Problem Analysis Schema. He has more and different buckets, but I would definately try both approaches on real life situations to evaluate them more. It was stimulating to be challenged to a paradigm shift in thinking about approach.