Organizational Orientation to Change: Kaizen and Agile
This paper examines an organization's orientation to change through the lens of Kaizen continuous improvement and Agile product development methodologies. It applies Dr. Ashby's organizational change typology to characterize the company as a "Quantum Peeper" — one that follows established leads rather than driving radical change — largely due to a conservative customer base in aerospace and defense. The paper also reflects on how individuals within an organization can personally prepare for and respond to change, emphasizing incremental growth, continuous learning, and ethical behavior as core strategies for remaining relevant in a rapidly evolving enterprise software market.
- Introduction: A Kaizen and Agile Approach to Change: Organization uses Kaizen and Agile for incremental improvement
- Classifying the Organization: The Quantum Peeper Model: Firm labeled Quantum Peeper due to conservative customer base
- The Role of Organizational Culture in Shaping Change: Aerospace clients demand slow, secure, documented change processes
- Personal Response to Change Within the Organization: Balancing cultural norms with forward-looking innovation push
- Preparing for Change: Strategies for Continuous Growth: Four personal strategies for embracing and leading change
✍️ How to write this paper — guide, tools & examples ▾
What makes this paper effective
- The paper grounds abstract change management frameworks in a real organizational context, making theoretical concepts like Kaizen and the Quantum Peeper model immediately concrete and relatable.
- It moves logically from the organizational level down to the individual level, creating a coherent progression from macro to micro analysis.
- The use of peer-reviewed citations to support practical observations lends academic credibility to what might otherwise read as purely anecdotal reflection.
Key academic technique demonstrated
The paper demonstrates applied theoretical analysis — taking established academic frameworks (Kaizen, Agile, Ashby's change typology) and systematically applying each one to a specific organizational case. This technique shows the writer's ability to bridge theory and practice, a core skill in business and management writing at the undergraduate level.
Structure breakdown
The paper is organized around a question-and-answer format, with each prompt driving a new analytical section. It opens by describing the organization's change philosophy, then applies Dr. Ashby's typology, then turns inward to assess the author's personal role, and closes with actionable personal strategies. This scaffold moves from external description to internal reflection, ending with a forward-looking conclusion.
Introduction: A Kaizen and Agile Approach to Change
My organization is one that is focused on gradual improvements over time. The software created for customers is quite complex and would be nearly impossible to produce through seismic, large-scale organizational change. Using the approaches of Kaizen and a project management methodology called Agile Product Development (Vlaanderen, Jansen, Brinkkemper, & Jaspers, 2011), our software teams continually work to align software features to what customers are looking for in terms of functionality, navigation, and performance. This is a Kaizen-based approach because the iterative nature of fine-tuning software to customer needs requires continual refining and re-orienting to their requirements.
Over time, this approach to creating software has proven highly effective, reducing the number of errors and, most importantly, keeping the organization in step with customer expectations. This is consistent with findings from longitudinal studies of Kaizen-based organizational change and effectiveness (Farris, Van Aken, Doolen, & Worley, 2009). The adoption of Agile as a development platform has also significantly reduced the anxiety and pressure associated with producing large volumes of software all at once. The current approach is to incrementally create modules and release them over time — consistent with the Kaizen principle of defining continuous improvement through smaller, incremental steps (Bessant, Caffyn, & Gallagher, 2001). These approaches have helped the organization respond more effectively to competitors and create greater long-term value for customers.
Classifying the Organization: The Quantum Peeper Model
The organization I work for falls solidly into the category of a Quantum Peeper — one that successfully follows the leads of others rather than driving radical change. This is partly because the customer base is quite conservative and does not welcome rapid changes to their software applications. The majority of customers pay a maintenance fee of between 20% and 22% of their contract amount for yearly updates, and they expect a steady flow of updates relevant to their needs. Moving too far from their original goals for purchasing the application risks alienating them and potentially causing them to cancel their contracts and move to another vendor.
The Quantum Peeper classification also reflects the organization's approach to adopting new development technologies. Because many customers operate in the aerospace and defense industry, their security requirements are exceptionally high. They expect robust safeguards governing how data is captured, analyzed, and presented to the end user.
References
Bessant, J., Caffyn, S., & Gallagher, M. (2001). An evolutionary model of continuous improvement behaviour. Technovation, 21(2), 67–77.
Farris, J., Van Aken, E., Doolen, T., & Worley, J. (2009). Longitudinal analysis of Kaizen event effectiveness. IIE Annual Conference Proceedings, 1–7.
Valencia, J. C. N., Valle, R. S., & Jimenez, D. (2010). Organizational culture as determinant of product innovation. European Journal of Innovation Management, 13(4), 466–480.
Vlaanderen, K., Jansen, S., Brinkkemper, S., & Jaspers, E. (2011). The agile requirements refinery: Applying SCRUM principles to software product management. Information and Software Technology, 53(1), 58.
Always verify citation format against your institution’s current style guide requirements.