jidoka

What Is Jidoka? Jidoka In A Nutshell

Jidoka was first used in 1896 by Sakichi Toyoda, who invented a textile loom that would stop automatically when it encountered a defective thread. Jidoka is a Japanese term used in lean manufacturing. The term describes a scenario where machines cease operating without human intervention when a problem or defect is discovered.

AspectExplanation
Concept OverviewJidoka is a Japanese term often translated as “automation with a human touch” or “autonomation.” It is a key concept in lean manufacturing and the Toyota Production System (TPS). Jidoka involves building quality into the manufacturing process by incorporating automatic mechanisms for detecting defects and stopping production when an abnormality is identified. This proactive approach to quality control aims to prevent the production of defective products, reduce waste, and ensure consistent product quality. Jidoka exemplifies the TPS principle of “stopping the production line to fix problems.”
Key PrinciplesJidoka is guided by several key principles:
1. Built-In Quality: Jidoka emphasizes the importance of producing quality products from the outset rather than relying on inspection at the end of the process.
2. Autonomy: Machines and processes are designed to have a degree of autonomy, allowing them to detect and respond to abnormalities independently.
3. Immediate Response: When an abnormality is detected, production is stopped immediately to prevent the creation of defective products.
4. Andon System: The use of an Andon system, which is a visual display, to signal abnormalities and facilitate quick response and resolution.
5. Human Intervention: Jidoka encourages human intervention to address and resolve issues, ensuring that the root cause is identified and corrected.
ComponentsJidoka incorporates several components and practices:
1. Poka-Yoke (Error-Proofing): The design and use of devices or mechanisms that prevent or detect errors in real-time.
2. Andon System: Visual displays or signals that indicate abnormalities or stoppages in the production process.
3. Jidoka Equipment: Machines and equipment are equipped with sensors and mechanisms to detect defects and stop production when necessary.
4. Empowered Workers: Workers are trained and empowered to identify and address abnormalities and quality issues.
ApplicationsJidoka is widely applied in manufacturing, particularly in industries such as automotive, electronics, and aerospace. It can also be adapted to non-manufacturing processes to enhance quality and efficiency.
Benefits and ImpactJidoka offers several benefits and impacts:
1. Quality Improvement: By preventing defects and errors at the source, Jidoka leads to higher product quality and reduced rework or scrap.
2. Cost Reduction: It reduces the costs associated with defects, warranty claims, and customer complaints.
3. Increased Efficiency: Although it may temporarily stop production when abnormalities are detected, Jidoka ultimately leads to smoother, more efficient processes.
4. Empowered Workforce: It empowers employees to actively participate in quality control and problem-solving.
5. Customer Satisfaction: Consistent quality and reliability enhance customer satisfaction and loyalty.
Challenges and RisksChallenges in implementing Jidoka may include the initial investment in automation and training, as well as the need for a cultural shift toward proactive problem-solving. Risks may involve the overreliance on automation without addressing root causes or neglecting the human element in quality control.

Understanding Jidoka

Jidoka then became one of the three pillars of the Toyota Production System (TPS) after Toyoda’s son Kiichiro transformed the textile company into an automobile manufacturer.

toyota-production-system
The Toyota Production System (TPS) is an early form of lean manufacturing created by auto-manufacturer Toyota. Created by the Toyota Motor Corporation in the 1940s and 50s, the Toyota Production System seeks to manufacture vehicles ordered by customers most quickly and efficiently possible.

The concept facilitates autonomation, defined as automation with a human touch.

Having a human watch over a machine constantly is both physically demanding and prone to error.

For example, a worker required to inspect every part of a machine for one defect will quickly experience tired eyes or repetitive strain injuries.

Defect rates in most processes are well below 1%, which means a worker employed to look for them would become bored very easily.

Since Jidoka automates error detection, the business can reassign employees to more productive roles.

Like most aspects of lean manufacturing, Jidoka exists to minimize waste and improve efficiency.

Before modern businesses adopted the concept, manufacturing defects were not detected until long after they had occurred.

In some cases, the product had already been sold to a consumer before a problem was identified.

The four principles of Jidoka

Four simple principles of Jidoka exist, with each playing a role in preventing defects from reaching the customer.

Each principle takes the form of a step:

Discover an abnormality (automated)

In an ideal world, abnormalities are prevented by building quality into a process from the start and not by inspecting for quality at the end.

Tools such as Kanban and 5S can also help discover problems before they occur.

kanban
Kanban is a lean manufacturing framework first developed by Toyota in the late 1940s. The Kanban framework is a means of visualizing work as it moves through identifying potential bottlenecks. It does that through a process called just-in-time (JIT) manufacturing to optimize engineering processes, speed up manufacturing products, and improve the go-to-market strategy.
5s-system
The 5S System is a lean manufacturing tool that improves efficiency and eliminates waste. First used in the Toyota Production System (TPS). The 5S System seeks to mitigate the factors contributing to process inefficiencies with six areas of concern: sort, set in order, shine, standardize, sustain, and safety.

Stop (automated)

Stopping the line is as important as developing a culture where doing so is accepted and not feared.

Many Western businesses fear a loss of productivity when the line is constantly stopped for problems.

However, Jidoka favors addressing minor issues before they have a chance to become major issues.

Fix the immediate problem (human)

At companies such as Toyota, line interruptions are a way of life.

When operators detect a problem, supervisors are immediately notified to help solve the problem.

If the solution is easy, the problem is rectified and the line restarted.

If not, the appropriate expertise is called in for support.

Investigate and correct the root cause by installing a countermeasure (human)

Despite being notified of problems by superior technology, some businesses still find it difficult to correct the problem and identify the root cause.

To ensure problems are solved once and for all, personnel should be trained in root cause identification techniques.

Then, any change to relevant operating procedures must be documented and communicated to the staff. 

Jidoka and Andon

Within Jidoka there are various quality control methods, among which Andon.

Andon is a quality control method described as “intelligent automation” or “automation with a human touch”.

andon-system
The andon system alerts managerial, maintenance, or other staff of a production process problem. The alert itself can be activated manually with a button or pull cord, but it can also be activated automatically by production equipment. Most Andon boards utilize three colored lights similar to a traffic signal: green (no errors), yellow or amber (problem identified, or quality check needed), and red (production stopped due to unidentified issue).

It simply consists of a “traffic light” mechanism for lean production, where quality issues are identified and solved.

If they can’t be identified and solved, production stops until the defect is found.

This is an example of the various quality methods within Jidoka, which were part of the broader Toyota Production System.

When to Use Jidoka:

Jidoka is suitable in various business scenarios:

  1. Manufacturing Processes: In manufacturing, especially in industries where quality control is critical, such as automotive and electronics.
  2. Batch and Continuous Production: Jidoka can be applied in both batch production and continuous production settings.
  3. Complex Assembly: When products involve intricate assembly processes, Jidoka helps ensure quality at every step.
  4. Quality Improvement Initiatives: Jidoka supports quality improvement efforts by preventing defects and identifying root causes.
  5. Cost Reduction: By reducing defects and waste, Jidoka contributes to cost reduction and increased profitability.

How to Implement Jidoka Effectively:

To effectively implement Jidoka, consider the following steps:

  1. Training and Education: Provide training to employees on the principles of Jidoka, including autonomation and the use of the Andon system.
  2. Andon System Setup: Implement the Andon system, which includes visual and auditory alerts for detecting abnormalities.
  3. Poka-Yoke Design: Design processes with built-in Poka-Yoke mechanisms to prevent defects.
  4. Error Analysis: Analyze errors and defects to identify root causes and implement corrective actions.
  5. Continuous Improvement: Continuously seek ways to improve processes, address recurring issues, and enhance the effectiveness of Jidoka.

Drawbacks and Limitations of Jidoka:

While Jidoka is a powerful quality control concept, it also has drawbacks and limitations:

  1. Resource Intensive: Implementing Jidoka, including setting up Andon systems and error analysis, can require significant resources.
  2. Cultural Change: Transforming the organizational culture to embrace Jidoka principles may face resistance and take time.
  3. Complexity: In highly complex production processes, the implementation of Jidoka can be challenging.
  4. Initial Investment: There may be a need for initial investments in technology and training.

What to Expect When Using Jidoka:

When using Jidoka, expect the following outcomes and considerations:

  1. Improved Quality: Jidoka leads to higher product quality and a reduction in defects.
  2. Reduced Waste: By preventing defects and stopping production when issues occur, Jidoka reduces waste and associated costs.
  3. Employee Empowerment: Employees become more engaged and empowered to take ownership of quality.
  4. Continuous Improvement: Jidoka fosters a culture of continuous improvement, with a focus on root cause analysis and problem-solving.

Related Business Frameworks

  • Total Quality Management (TQM): TQM is a holistic approach to improving quality across all organizational levels, aligning well with Jidoka’s goal of defect reduction and continuous improvement.
  • Lean Manufacturing: Lean principles and tools, such as Value Stream Mapping and 5S, complement Jidoka by eliminating waste and optimizing processes.
  • Six Sigma: Six Sigma’s data-driven methodology helps identify and eliminate process defects, synergizing with Jidoka’s focus on quality and efficiency.
  • Kaizen: Kaizen, emphasizing continuous improvement through incremental changes, pairs seamlessly with Jidoka’s philosophy of defect prevention and process enhancement.
  • Poka-Yoke (Mistake-Proofing): Poka-Yoke techniques, closely related to Jidoka, aid in designing error-resistant processes to further enhance quality control.
  • ISO 9001 Quality Management System: Integrating ISO 9001 principles with Jidoka helps establish robust quality control systems and consistent processes.
  • Statistical Process Control (SPC): SPC uses statistical methods for real-time monitoring and control, reinforcing Jidoka’s ability to detect and address process variations.
  • Design of Experiments (DOE): DOE optimizes processes and identifies key factors affecting quality, aligning with Jidoka for defect reduction.
  • Root Cause Analysis (RCA): RCA methodologies, like the 5 Whys or Ishikawa diagrams, help organizations investigate and resolve underlying causes of defects, complementing Jidoka’s detection capabilities.
  • Failure Mode and Effects Analysis (FMEA): FMEA is a structured approach for assessing and mitigating quality risks, enhancing Jidoka’s proactive defect prevention.

Case Studies

Agile and Backlog Refinement:

  • User Story Review: During backlog refinement, a software development team reviews user stories to ensure clarity and alignment with customer needs. For instance, they might clarify the acceptance criteria for a “user registration” feature.
  • Backlog Grooming: An Agile team prioritizes and organizes backlog items, such as “bug fixes,” “new features,” and “user interface improvements,” to ensure a clear roadmap for development.
  • Estimation: The team estimates the effort required for backlog items. For example, they might estimate that implementing a search functionality will take two sprints.
  • Collaboration: The Product Owner, Development Team, and Scrum Master collaborate to refine the backlog. They discuss the scope of work, priorities, and potential challenges.

Lean Manufacturing and Jidoka:

  • Defect Detection: In a manufacturing facility, a machine automatically stops when a faulty part is detected, preventing the production of defective products.
  • Andon System: A production line uses an Andon system with color-coded lights. When a quality issue is identified, a worker presses a button, activating the Andon light to signal the need for assistance.
  • Continuous Improvement: A manufacturing team uses Jidoka principles to stop the production line temporarily to address a minor issue, preventing it from escalating into a larger problem.
  • Autonomation: An assembly robot senses resistance while tightening screws and stops before damaging the product, prompting an operator to intervene.

Capacity Planning and Resource Allocation:

  • Demand Forecasting: A retail store uses historical sales data and market trends to predict future demand for specific products, ensuring adequate stock levels.
  • Resource Availability: A software development team assesses the availability of skilled developers and assigns tasks based on their expertise.
  • Priority Setting: A project manager prioritizes tasks based on their impact on project milestones and overall project goals.
  • Scenario Analysis: A manufacturing company evaluates different production scenarios to identify potential bottlenecks and make informed decisions.

Jidoka and Quality Control:

  • Automated Defect Detection: In an automobile assembly line, a camera system detects paint defects on car bodies and automatically halts the production process for inspection.
  • Immediate Problem Resolution: A machine in a production facility identifies a malfunction and alerts a technician for quick troubleshooting and repair.
  • Root Cause Analysis: After a defect is identified, a cross-functional team conducts a root cause analysis to determine why the issue occurred and implements corrective actions.
  • Reducing Waste: An electronics manufacturer uses Jidoka principles to identify defects early, reducing the need for rework and minimizing waste in the production process.

Jidoka-Inspired Applications Beyond Manufacturing:

  1. Healthcare – Automated Medication Dispensing:
    • Scenario: A hospital adopts Jidoka principles to automate medication dispensing. Smart dispensers monitor the dispensing process, ensuring the correct dosage is administered to patients.
    • Implications: Medication errors are significantly reduced, enhancing patient safety and reducing healthcare costs associated with adverse drug events.
  2. Retail – Autonomous Inventory Management:
    • Scenario: A retail chain utilizes Jidoka-inspired technology to automate inventory management. RFID tags and sensors track merchandise movement in real-time, triggering automatic restocking when inventory levels are low.
    • Implications: The retailer minimizes out-of-stock situations, improves inventory turnover, and optimizes supply chain efficiency.
  3. Software Development – Automated Testing:
    • Scenario: A software development company implements Jidoka principles in its quality assurance process. Automated test scripts are designed to identify bugs and inconsistencies during software development.
    • Implications: Defects are detected early in the development cycle, reducing debugging time and ensuring the delivery of high-quality software products.

Key takeaways

  • Jidoka is a Japanese term used in lean manufacturing which promotes autonomation, or automation with a human touch. It was developed by Sakichi Toyoda, whose son would eventually found the Toyota Motor Company.
  • Jidoka exists to minimize waste and improve efficiency. This is achieved by detecting errors before they occur through automation, which frees up employees to be assigned to more productive roles.
  • Jidoka is based on four simple principles, with each representing a step in the error detection process. Discovering the abnormality and stopping the line should be automated, while fixing the immediate problem, and correcting the root cause by installing a countermeasure is performed by workers.

Key Highlights

  • Jidoka in Lean Manufacturing:
    • Jidoka is a concept originating in lean manufacturing, first used in 1896 by Sakichi Toyoda, who invented a textile loom that could stop automatically upon detecting a defective thread.
    • Jidoka involves automation with a human touch, aiming to prevent defects and improve efficiency in the production process.
  • Jidoka’s Role in Toyota Production System (TPS):
    • Jidoka became one of the three pillars of the Toyota Production System (TPS) after Kiichiro Toyoda, Sakichi Toyoda’s son, transformed the textile company into an automobile manufacturer.
  • Toyota Production System (TPS):
    • TPS, created by Toyota in the 1940s and 50s, seeks to manufacture vehicles quickly and efficiently in response to customer orders.
    • Jidoka is integral to TPS, enabling autonomation to identify and address defects.
  • Jidoka’s Contribution to Efficiency:
    • Jidoka automates error detection, preventing defects from reaching customers and reducing waste.
    • It allows employees to be reassigned to more productive tasks.
  • Four Principles of Jidoka:
    • Discover an Abnormality (Automated): Build quality into the process from the start and use tools like Kanban and 5S to identify potential issues.
    • Stop (Automated): Stopping the line for minor issues prevents them from becoming major problems.
    • Fix the Immediate Problem (Human): Operators notify supervisors of issues and address simple problems immediately.
    • Investigate and Correct Root Cause (Human): Train personnel in root cause identification and document changes to procedures.
  • Jidoka and Andon:
    • Andon is a quality control method within Jidoka, signaling production process problems to management or maintenance.
    • Andon uses a three-colored light system to indicate production status: green (no errors), yellow (issues identified), and red (production stopped).
  • Key Takeaways:
    • Jidoka emphasizes automation with human involvement to prevent defects and improve efficiency.
    • It was developed by Sakichi Toyoda and plays a significant role in the Toyota Production System (TPS).
    • Four principles guide Jidoka’s implementation, and it incorporates methods like Andon for quality control.

FrameworkDescriptionWhen to Apply
Total Quality Management (TQM)– TQM is a management approach that focuses on continuous improvement, customer satisfaction, and employee involvement in all aspects of an organization’s operations. – It emphasizes quality management principles such as customer focus, process improvement, and data-driven decision-making to achieve organizational excellence. – Key concepts include Kaizen, quality circles, and benchmarking.– When organizations aim to improve product quality, customer satisfaction, and operational efficiency through systematic and continuous improvement initiatives.
Lean Manufacturing– Lean Manufacturing, derived from the Toyota Production System (TPS), aims to minimize waste and maximize value by optimizing processes and eliminating non-value-added activities. – It focuses on principles such as value stream mapping, just-in-time production, and Jidoka (autonomation) to achieve flow and quality. – Key concepts include kanban systems, 5S methodology, and standardized work.– When organizations seek to streamline production processes, reduce lead times, and improve overall efficiency in manufacturing operations.
Six Sigma– Six Sigma is a data-driven methodology for process improvement and variation reduction to achieve near-perfect quality. – It uses a DMAIC (Define, Measure, Analyze, Improve, Control) framework to identify and eliminate defects in processes. – Six Sigma aims to achieve no more than 3.4 defects per million opportunities. – Key concepts include statistical analysis, root cause analysis, and process capability.– When organizations aim to reduce defects, improve process efficiency, and enhance overall quality by applying statistical methods and problem-solving techniques.
Poka-Yoke (Mistake-Proofing)– Poka-Yoke is a technique for error prevention that aims to design processes and systems in a way that makes errors impossible or immediately detectable. – It involves incorporating fail-safe mechanisms and visual cues to prevent mistakes before they occur. – Poka-Yoke is based on the principle of Jidoka, where machines and processes stop automatically when defects are detected.– When organizations want to minimize human errors, defects, and rework by implementing fail-safe mechanisms and mistake-proofing techniques in their processes.
5 Whys Analysis– The 5 Whys Analysis is a problem-solving technique used to identify the root cause of an issue by asking why repeatedly. – It helps uncover deeper layers of causes beyond the obvious symptoms, enabling organizations to address underlying problems effectively. – The goal is to reach the fundamental cause of the problem and implement corrective actions to prevent recurrence.– When organizations encounter recurring issues or quality problems and want to investigate the underlying causes to implement effective solutions.
Andon System– The Andon System is a visual management tool used in Lean manufacturing to alert operators, supervisors, or maintenance personnel of production issues or defects in real-time. – It enables quick problem identification and response, facilitating Jidoka principles. – Andon signals can include lights, alarms, or digital displays that indicate the status of production processes.– When organizations aim to create a culture of transparency, accountability, and continuous improvement by providing real-time visibility into production status and empowering employees to address issues promptly.
Kaizen Blitz (Rapid Improvement Event)– Kaizen Blitz, also known as a Rapid Improvement Event, is a focused team-based approach to implementing Kaizen or continuous improvement initiatives within a short timeframe. – It involves cross-functional teams working intensively on specific processes or areas to identify and implement immediate improvements. – Kaizen Blitz aims to achieve quick wins and build momentum for broader improvement efforts.– When organizations need to address specific process challenges or improvement opportunities quickly and efficiently by leveraging the expertise and collaboration of cross-functional teams.
Gemba Walk– Gemba Walk is a Lean management practice that involves going to the source or where the work is done to observe, understand, and engage with frontline employees and processes. – It enables leaders to identify opportunities for improvement, listen to employee feedback, and gain insights into daily operations. – Gemba– When organizations aim to understand their operations better, foster employee engagement, and identify improvement opportunities by observing processes firsthand.
Kanban System– Kanban is a visual scheduling system used to manage workflow and optimize processes in manufacturing, software development, and other industries. – It visualizes work items and workflow stages on a Kanban board, enabling teams to prioritize tasks, limit work in progress (WIP), and identify bottlenecks. – Kanban promotes flow and continuous improvement by signaling when to start, stop, or expedite work.– When organizations seek to improve workflow visibility, optimize resource utilization, and implement a pull-based system for managing tasks and projects.
Theory of Constraints (TOC)– TOC is a management philosophy that focuses on identifying and elevating constraints (bottlenecks) in a system to improve overall throughput and performance. – It emphasizes continuous improvement and systematic problem-solving to overcome constraints and maximize organizational effectiveness. – TOC principles include identifying constraints, exploiting constraints, and subordinating everything else to the constraints.– When organizations encounter bottlenecks or constraints that limit their productivity or performance and want to adopt a systematic approach to address them and improve overall efficiency.
5S Methodology– 5S is a workplace organization methodology focused on creating a clean, organized, and efficient work environment. – It consists of five steps: Sort, Set in Order, Shine, Standardize, and Sustain. – 5S aims to eliminate waste, improve safety, and enhance productivity by ensuring tools, materials, and processes are well-organized and easily accessible.– When organizations aim to improve workplace organization, safety, and efficiency by implementing standardized practices for workspace cleanliness, organization, and maintenance.

Connected Agile & Lean Frameworks

AIOps

aiops
AIOps is the application of artificial intelligence to IT operations. It has become particularly useful for modern IT management in hybridized, distributed, and dynamic environments. AIOps has become a key operational component of modern digital-based organizations, built around software and algorithms.

AgileSHIFT

AgileSHIFT
AgileSHIFT is a framework that prepares individuals for transformational change by creating a culture of agility.

Agile Methodology

agile-methodology
Agile started as a lightweight development method compared to heavyweight software development, which is the core paradigm of the previous decades of software development. By 2001 the Manifesto for Agile Software Development was born as a set of principles that defined the new paradigm for software development as a continuous iteration. This would also influence the way of doing business.

Agile Program Management

agile-program-management
Agile Program Management is a means of managing, planning, and coordinating interrelated work in such a way that value delivery is emphasized for all key stakeholders. Agile Program Management (AgilePgM) is a disciplined yet flexible agile approach to managing transformational change within an organization.

Agile Project Management

agile-project-management
Agile project management (APM) is a strategy that breaks large projects into smaller, more manageable tasks. In the APM methodology, each project is completed in small sections – often referred to as iterations. Each iteration is completed according to its project life cycle, beginning with the initial design and progressing to testing and then quality assurance.

Agile Modeling

agile-modeling
Agile Modeling (AM) is a methodology for modeling and documenting software-based systems. Agile Modeling is critical to the rapid and continuous delivery of software. It is a collection of values, principles, and practices that guide effective, lightweight software modeling.

Agile Business Analysis

agile-business-analysis
Agile Business Analysis (AgileBA) is certification in the form of guidance and training for business analysts seeking to work in agile environments. To support this shift, AgileBA also helps the business analyst relate Agile projects to a wider organizational mission or strategy. To ensure that analysts have the necessary skills and expertise, AgileBA certification was developed.

Agile Leadership

agile-leadership
Agile leadership is the embodiment of agile manifesto principles by a manager or management team. Agile leadership impacts two important levels of a business. The structural level defines the roles, responsibilities, and key performance indicators. The behavioral level describes the actions leaders exhibit to others based on agile principles. 

Andon System

andon-system
The andon system alerts managerial, maintenance, or other staff of a production process problem. The alert itself can be activated manually with a button or pull cord, but it can also be activated automatically by production equipment. Most Andon boards utilize three colored lights similar to a traffic signal: green (no errors), yellow or amber (problem identified, or quality check needed), and red (production stopped due to unidentified issue).

Bimodal Portfolio Management

bimodal-portfolio-management
Bimodal Portfolio Management (BimodalPfM) helps an organization manage both agile and traditional portfolios concurrently. Bimodal Portfolio Management – sometimes referred to as bimodal development – was coined by research and advisory company Gartner. The firm argued that many agile organizations still needed to run some aspects of their operations using traditional delivery models.

Business Innovation Matrix

business-innovation
Business innovation is about creating new opportunities for an organization to reinvent its core offerings, revenue streams, and enhance the value proposition for existing or new customers, thus renewing its whole business model. Business innovation springs by understanding the structure of the market, thus adapting or anticipating those changes.

Business Model Innovation

business-model-innovation
Business model innovation is about increasing the success of an organization with existing products and technologies by crafting a compelling value proposition able to propel a new business model to scale up customers and create a lasting competitive advantage. And it all starts by mastering the key customers.

Constructive Disruption

constructive-disruption
A consumer brand company like Procter & Gamble (P&G) defines “Constructive Disruption” as: a willingness to change, adapt, and create new trends and technologies that will shape our industry for the future. According to P&G, it moves around four pillars: lean innovation, brand building, supply chain, and digitalization & data analytics.

Continuous Innovation

continuous-innovation
That is a process that requires a continuous feedback loop to develop a valuable product and build a viable business model. Continuous innovation is a mindset where products and services are designed and delivered to tune them around the customers’ problem and not the technical solution of its founders.

Design Sprint

design-sprint
A design sprint is a proven five-day process where critical business questions are answered through speedy design and prototyping, focusing on the end-user. A design sprint starts with a weekly challenge that should finish with a prototype, test at the end, and therefore a lesson learned to be iterated.

Design Thinking

design-thinking
Tim Brown, Executive Chair of IDEO, defined design thinking as “a human-centered approach to innovation that draws from the designer’s toolkit to integrate the needs of people, the possibilities of technology, and the requirements for business success.” Therefore, desirability, feasibility, and viability are balanced to solve critical problems.

DevOps

devops-engineering
DevOps refers to a series of practices performed to perform automated software development processes. It is a conjugation of the term “development” and “operations” to emphasize how functions integrate across IT teams. DevOps strategies promote seamless building, testing, and deployment of products. It aims to bridge a gap between development and operations teams to streamline the development altogether.

Dual Track Agile

dual-track-agile
Product discovery is a critical part of agile methodologies, as its aim is to ensure that products customers love are built. Product discovery involves learning through a raft of methods, including design thinking, lean start-up, and A/B testing to name a few. Dual Track Agile is an agile methodology containing two separate tracks: the “discovery” track and the “delivery” track.

eXtreme Programming

extreme-programming
eXtreme Programming was developed in the late 1990s by Ken Beck, Ron Jeffries, and Ward Cunningham. During this time, the trio was working on the Chrysler Comprehensive Compensation System (C3) to help manage the company payroll system. eXtreme Programming (XP) is a software development methodology. It is designed to improve software quality and the ability of software to adapt to changing customer needs.

Feature-Driven Development

feature-driven-development
Feature-Driven Development is a pragmatic software process that is client and architecture-centric. Feature-Driven Development (FDD) is an agile software development model that organizes workflow according to which features need to be developed next.

Gemba Walk

gemba-walk
A Gemba Walk is a fundamental component of lean management. It describes the personal observation of work to learn more about it. Gemba is a Japanese word that loosely translates as “the real place”, or in business, “the place where value is created”. The Gemba Walk as a concept was created by Taiichi Ohno, the father of the Toyota Production System of lean manufacturing. Ohno wanted to encourage management executives to leave their offices and see where the real work happened. This, he hoped, would build relationships between employees with vastly different skillsets and build trust.

GIST Planning

gist-planning
GIST Planning is a relatively easy and lightweight agile approach to product planning that favors autonomous working. GIST Planning is a lean and agile methodology that was created by former Google product manager Itamar Gilad. GIST Planning seeks to address this situation by creating lightweight plans that are responsive and adaptable to change. GIST Planning also improves team velocity, autonomy, and alignment by reducing the pervasive influence of management. It consists of four blocks: goals, ideas, step-projects, and tasks.

ICE Scoring

ice-scoring-model
The ICE Scoring Model is an agile methodology that prioritizes features using data according to three components: impact, confidence, and ease of implementation. The ICE Scoring Model was initially created by author and growth expert Sean Ellis to help companies expand. Today, the model is broadly used to prioritize projects, features, initiatives, and rollouts. It is ideally suited for early-stage product development where there is a continuous flow of ideas and momentum must be maintained.

Innovation Funnel

innovation-funnel
An innovation funnel is a tool or process ensuring only the best ideas are executed. In a metaphorical sense, the funnel screens innovative ideas for viability so that only the best products, processes, or business models are launched to the market. An innovation funnel provides a framework for the screening and testing of innovative ideas for viability.

Innovation Matrix

types-of-innovation
According to how well defined is the problem and how well defined the domain, we have four main types of innovations: basic research (problem and domain or not well defined); breakthrough innovation (domain is not well defined, the problem is well defined); sustaining innovation (both problem and domain are well defined); and disruptive innovation (domain is well defined, the problem is not well defined).

Innovation Theory

innovation-theory
The innovation loop is a methodology/framework derived from the Bell Labs, which produced innovation at scale throughout the 20th century. They learned how to leverage a hybrid innovation management model based on science, invention, engineering, and manufacturing at scale. By leveraging individual genius, creativity, and small/large groups.

Lean vs. Agile

lean-methodology-vs-agile
The Agile methodology has been primarily thought of for software development (and other business disciplines have also adopted it). Lean thinking is a process improvement technique where teams prioritize the value streams to improve it continuously. Both methodologies look at the customer as the key driver to improvement and waste reduction. Both methodologies look at improvement as something continuous.

Lean Startup

startup-company
A startup company is a high-tech business that tries to build a scalable business model in tech-driven industries. A startup company usually follows a lean methodology, where continuous innovation, driven by built-in viral loops is the rule. Thus, driving growth and building network effects as a consequence of this strategy.

Minimum Viable Product

minimum-viable-product
As pointed out by Eric Ries, a minimum viable product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort through a cycle of build, measure, learn; that is the foundation of the lean startup methodology.

Leaner MVP

leaner-mvp
A leaner MVP is the evolution of the MPV approach. Where the market risk is validated before anything else

Kanban

kanban
Kanban is a lean manufacturing framework first developed by Toyota in the late 1940s. The Kanban framework is a means of visualizing work as it moves through identifying potential bottlenecks. It does that through a process called just-in-time (JIT) manufacturing to optimize engineering processes, speed up manufacturing products, and improve the go-to-market strategy.

Jidoka

jidoka
Jidoka was first used in 1896 by Sakichi Toyoda, who invented a textile loom that would stop automatically when it encountered a defective thread. Jidoka is a Japanese term used in lean manufacturing. The term describes a scenario where machines cease operating without human intervention when a problem or defect is discovered.

PDCA Cycle

pdca-cycle
The PDCA (Plan-Do-Check-Act) cycle was first proposed by American physicist and engineer Walter A. Shewhart in the 1920s. The PDCA cycle is a continuous process and product improvement method and an essential component of the lean manufacturing philosophy.

Rational Unified Process

rational-unified-process
Rational unified process (RUP) is an agile software development methodology that breaks the project life cycle down into four distinct phases.

Rapid Application Development

rapid-application-development
RAD was first introduced by author and consultant James Martin in 1991. Martin recognized and then took advantage of the endless malleability of software in designing development models. Rapid Application Development (RAD) is a methodology focusing on delivering rapidly through continuous feedback and frequent iterations.

Retrospective Analysis

retrospective-analysis
Retrospective analyses are held after a project to determine what worked well and what did not. They are also conducted at the end of an iteration in Agile project management. Agile practitioners call these meetings retrospectives or retros. They are an effective way to check the pulse of a project team, reflect on the work performed to date, and reach a consensus on how to tackle the next sprint cycle. These are the five stages of a retrospective analysis for effective Agile project management: set the stage, gather the data, generate insights, decide on the next steps, and close the retrospective.

Scaled Agile

scaled-agile-lean-development
Scaled Agile Lean Development (ScALeD) helps businesses discover a balanced approach to agile transition and scaling questions. The ScALed approach helps businesses successfully respond to change. Inspired by a combination of lean and agile values, ScALed is practitioner-based and can be completed through various agile frameworks and practices.

SMED

smed
The SMED (single minute exchange of die) method is a lean production framework to reduce waste and increase production efficiency. The SMED method is a framework for reducing the time associated with completing an equipment changeover.

Spotify Model

spotify-model
The Spotify Model is an autonomous approach to scaling agile, focusing on culture communication, accountability, and quality. The Spotify model was first recognized in 2012 after Henrik Kniberg, and Anders Ivarsson released a white paper detailing how streaming company Spotify approached agility. Therefore, the Spotify model represents an evolution of agile.

Test-Driven Development

test-driven-development
As the name suggests, TDD is a test-driven technique for delivering high-quality software rapidly and sustainably. It is an iterative approach based on the idea that a failing test should be written before any code for a feature or function is written. Test-Driven Development (TDD) is an approach to software development that relies on very short development cycles.

Timeboxing

timeboxing
Timeboxing is a simple yet powerful time-management technique for improving productivity. Timeboxing describes the process of proactively scheduling a block of time to spend on a task in the future. It was first described by author James Martin in a book about agile software development.

Scrum

what-is-scrum
Scrum is a methodology co-created by Ken Schwaber and Jeff Sutherland for effective team collaboration on complex products. Scrum was primarily thought for software development projects to deliver new software capability every 2-4 weeks. It is a sub-group of agile also used in project management to improve startups’ productivity.

Scrumban

scrumban
Scrumban is a project management framework that is a hybrid of two popular agile methodologies: Scrum and Kanban. Scrumban is a popular approach to helping businesses focus on the right strategic tasks while simultaneously strengthening their processes.

Scrum Anti-Patterns

scrum-anti-patterns
Scrum anti-patterns describe any attractive, easy-to-implement solution that ultimately makes a problem worse. Therefore, these are the practice not to follow to prevent issues from emerging. Some classic examples of scrum anti-patterns comprise absent product owners, pre-assigned tickets (making individuals work in isolation), and discounting retrospectives (where review meetings are not useful to really make improvements).

Scrum At Scale

scrum-at-scale
Scrum at Scale (Scrum@Scale) is a framework that Scrum teams use to address complex problems and deliver high-value products. Scrum at Scale was created through a joint venture between the Scrum Alliance and Scrum Inc. The joint venture was overseen by Jeff Sutherland, a co-creator of Scrum and one of the principal authors of the Agile Manifesto.

Six Sigma

six-sigma
Six Sigma is a data-driven approach and methodology for eliminating errors or defects in a product, service, or process. Six Sigma was developed by Motorola as a management approach based on quality fundamentals in the early 1980s. A decade later, it was popularized by General Electric who estimated that the methodology saved them $12 billion in the first five years of operation.

Stretch Objectives

stretch-objectives
Stretch objectives describe any task an agile team plans to complete without expressly committing to do so. Teams incorporate stretch objectives during a Sprint or Program Increment (PI) as part of Scaled Agile. They are used when the agile team is unsure of its capacity to attain an objective. Therefore, stretch objectives are instead outcomes that, while extremely desirable, are not the difference between the success or failure of each sprint.

Toyota Production System

toyota-production-system
The Toyota Production System (TPS) is an early form of lean manufacturing created by auto-manufacturer Toyota. Created by the Toyota Motor Corporation in the 1940s and 50s, the Toyota Production System seeks to manufacture vehicles ordered by customers most quickly and efficiently possible.

Total Quality Management

total-quality-management
The Total Quality Management (TQM) framework is a technique based on the premise that employees continuously work on their ability to provide value to customers. Importantly, the word “total” means that all employees are involved in the process – regardless of whether they work in development, production, or fulfillment.

Waterfall

waterfall-model
The waterfall model was first described by Herbert D. Benington in 1956 during a presentation about the software used in radar imaging during the Cold War. Since there were no knowledge-based, creative software development strategies at the time, the waterfall method became standard practice. The waterfall model is a linear and sequential project management framework. 

Read Also: Continuous InnovationAgile MethodologyLean StartupBusiness Model InnovationProject Management.

Read Next: Agile Methodology, Lean Methodology, Agile Project Management, Scrum, Kanban, Six Sigma.

Main Guides:

Main Case Studies:

Discover more from FourWeekMBA

Subscribe now to keep reading and get access to the full archive.

Continue reading

Scroll to Top
FourWeekMBA