ERAU MGMT 535 Reflection Blog (Pratt)

MGMT 535 (Module 9) Reflection Blog: Course Reflection When I started this course I didn't really know what to expect.  Based on the title of the textbook, I assumed it would be a lot of info that I was already familiar with, but presented in a different way.  While there were a lot of concepts and information I was familiar with, there was lots of other information in the textbook that I was not aware of or had not considered.  I will also say that in previous classes, it was difficult for me to choose a classmate to respond to as part of the discussion post requirements.  I have to feel inspired by something they said in order to give genuine feedback.  I can honestly say that throughout this course, I had a difficult time only choosing two or three classmates to respond to because their posts and responses were filled with so much experience, information, and inspiration. Like many of the others in this course, I feel like I really gained a lot from the "...

MGMT 535 (Module 8) Reflection Blog: Innovation When I read this week's chapter on innovation I couldn't help but reflect on the only innovation program I am familiar with and that is the program that the Air Force adopted years ago.  I suppose the AFSO21 program could also be considered an avenue for innovation as well.  AFSO21 stood for "Air Force Smart Operations for the 21st Century".  It was basically the Air Force's combination of LEAN, Six Sigma, 5S, and Continuous Process Improvement.  Taking lots of notes from Toyota's process improvement program.  But the program I am referring to is the Airman Powered by Innovation (API) program.  It was formerly known as the IDEA program and evolved into the API program just a few years before I retired.  It may even be something else now. In a nutshell, the API program promotes innovation from every level in the Air Force.  There is a central place and format to submit your ideas, ther...

MGMT 535 (Module 7) Reflection Blog: Communicating in Your Organization Ironically I chose this exact article for my discussion post before I looked at this week's reading assignments.  I specifically chose it because of the statement about how teamwork across organizational boundaries is unnatural.  In my response to Rob (a classmate), I touched on it a little, but I will go into it with more depth in this blog post. When I was in the Air Force I was the squadron superintendent for an operations support squadron.  This type of squadron is unique in that it has anywhere from 7 to 10 flights on average.  That's 7 to 10 unique jobs each with their own chain of command (under the squadron commander) and a job-specific subculture.  As a result, it was always a challenge to find ways to get the squadron to come together as a unit versus 9 separate flights.  We tried cookouts, sporting events, physical training days,  team building events, etc.  Eve...