What Is JDI Problem Solving?
JDI Problem Solving stands for “Just Do It” – fixing problems right away without delays. JDI Problem Solving is a simple but powerful quality tool. It focuses on taking quick action. It works best for small, clear issues that need fast solutions.
Download: JDI Problem Solving Guide
JDI Problem Solving: Quick Guide
This guide helps you understand and apply the JDI Problem Solving so you can spot small problems earlier and fix them faster.
See also downloadable real-world examples below.
JDI Problem Solving vs. 8D Report, A3 and Kaizen PDCA
JDI Problem Solving is best applied in daily operations when immediate action can prevent quality issues from escalating. Use it during production, when serving customers, or while performing routine tasks. Apply JDI at the moment you notice a problem, not later when it might be forgotten. The right time is now – especially when small issues are fresh and visible to everyone involved.
When picking a problem-solving tool like JDI, it is important to think about the issue’s complexity, urgency, and type:
JDI ("Just Do It")
Basic, everyday problems that one person or a small group can quickly fix without formal methods are good for just-do-it (JDI) solutions.
The JDI (Just Do It) method is ideal for straightforward issues that individuals can resolve through immediate action and common sense, without requiring formal procedures or extensive documentation.
PDCA
The PDCA/A3 Method helps teams to plan, implement, and check solutions in a structured way, for internal problems that need order but are not pressing.
The PDCA (Plan-Do-Check-Act) cycle is a continuous improvement method that guides teams through a systematic process of planning actions, implementing changes, checking results, and acting on lessons learned for ongoing improvements.
A3
The PDCA/A3 Method helps teams to plan, implement, and check solutions in a structured way, for internal problems that need order but are not pressing.
The A3 Method, named after the paper size traditionally used for the report, is a structured problem-solving approach that tells the complete story of a problem on a single page, forcing concise documentation while walking through background information, current conditions, root cause analysis, proposed countermeasures, and follow-up actions.
8D Report
The 8D (Eight Disciplines) process is specifically designed for complex quality issues and customer complaints, requiring a thorough, documented approach that includes containment actions, root cause analysis, and verification of corrective measures.
6σ Six Sigma
Six Sigma (6σ) represents the most rigorous and resource-intensive methodology, typically reserved for chronic, high-impact problems that require statistical analysis and long-term process improvement to achieve near-perfect quality levels.
When to Use JDI Problem Solving
Use JDI Problem Solving when you need to fix small, clear problems immediately without delays. JDI answers the critical question: “Can I solve this now, quickly and safely, without waiting for approval or extensive analysis?”
Typical triggers are:
Daily Production Issues
When small problems occur during routine operations, JDI enables immediate fixes. “The label printer keeps jamming – why wait for maintenance when I can clear it now?” Quick action prevents accumulation of minor issues into major production delays. Every minute of downtime costs money.
Frontline Quality Defects
When an operator spots a visible defect with an obvious cause, JDI empowers immediate correction. “These parts are scratched because the bin edge is sharp – let me add padding now.” Frontline workers see problems first; give them authority to fix them. Quality starts at the workstation.
Workplace Organization (5S)
When you notice disorganization, missing labels, or unclear workstations, JDI enables instant improvement. “Tools aren’t returning to the right spot – let me add shadow board markings now.” A tidy workplace prevents errors and saves search time. 5S lives through daily small improvements.
Safety Near-Misses
When a minor safety hazard appears with an obvious fix, JDI prevents accidents. “That cable across the walkway could trip someone – let me secure it now.” Safety cannot wait for committee meetings. Immediate action prevents injuries.
Customer-Facing Issues
When serving customers and something goes wrong with a simple fix, JDI saves the experience. “The menu board shows the wrong price – I can correct it immediately.” Customers don’t wait; neither should your fixes. Customer satisfaction depends on response speed.
Equipment Quick Fixes
When simple equipment adjustments can restore performance, JDI keeps production moving. “The conveyor belt is slightly misaligned – I can adjust the tensioner now.” Minor adjustments don’t need work orders. Trained operators maintain equipment proactively.
Process Bottlenecks
When simple equipment adjustments can restore performance, JDI keeps production moving. “The conveyor belt is slightly misaligned – I can adjust the tensioner now.” Minor adjustments don’t need work orders. Trained operators maintain equipment proactively.
Communication Gaps
When information isn’t reaching the right people, JDI closes the gap immediately. “The shift handover board is outdated – let me update it now.” Clear communication prevents errors and rework. Information flow is quality flow.
Standard Work Deviations
When information isn’t reaching the right people, JDI closes the gap immediately. “The shift handover board is outdated – let me update it now.” Clear communication prevents errors and rework. Information flow is quality flow.
Material Handling Problems
When packaging, storage, or transport creates product damage, JDI protects quality. “Parts are getting scratched in this container – let me add protective dividers now.” Damage prevention is cheaper than rework. Simple solutions often work best.
Kaizen Events / Continuous Improvement
When small obstacles create unnecessary waiting or movement, JDI streamlines flow. “The staging area is too far from the workstation – let me relocate it today.” Small flow improvements compound into significant productivity gains. Waste hiding in plain sight.
Kaizen Events / Continuous Improvement
During improvement workshops, JDI captures quick wins while larger projects are planned. “While we analyze the big issues, let’s JDI these obvious fixes today.” Quick wins build momentum for larger improvements. Don’t wait to improve what’s obvious.
Why Use JDI Problem Solving?
Organizations implement JDI because small issues often accumulate and create bigger problems when left unresolved. It empowers frontline workers to take ownership of quality rather than waiting for management approval. JDI builds a proactive culture that values immediate improvements over perfect but delayed solutions. It keeps the focus on customer satisfaction by fixing issues before they impact the end user. Simply put, JDI works because it removes the barriers between identifying a problem and solving it.
Principles of JDI Problem Solving
JDI is guided by the laws of:
Act Now, Not Later
Analysis paralysis is the enemy of continuous improvement. This principle encourages immediate action on clear issues rather than excessive planning. When a problem has an obvious solution, taking action now creates immediate value and prevents the issue from growing. This doesn't mean rushing without thinking, but rather recognizing when enough information exists to move forward confidently.
Trust Frontline Workers
The people closest to the work understand it best. Frontline workers see problems firsthand and often know the simplest solutions. By trusting their judgment and giving them authority to make changes, organizations tap into valuable expertise. This principle builds employee engagement while solving problems faster than escalation to management would allow.
Focus on Small Wins
Transformational change often comes from many small improvements rather than a few big ones. Each small fix builds momentum and confidence. Like compound interest, these small gains accumulate over time into significant improvements. This approach makes large goals less intimidating by breaking them into achievable steps.
Learn by Doing
Practical experience teaches lessons that theory cannot. By taking action, we discover unforeseen challenges and opportunities. This hands-on learning generates valuable knowledge that can be applied to future improvements. The JDI approach values this experiential learning over hypothetical planning.
Fix Root Causes, Not Symptoms
While JDI emphasizes quick action, it doesn't advocate for band-aid solutions. Even small fixes should address underlying causes when possible. This prevents the same problems from recurring. A good JDI solution eliminates the need to solve the same problem repeatedly.
Keep Solutions Simple
Complexity is the enemy of execution. The best solutions are often the simplest ones. Complex fixes introduce new failure points and maintenance challenges. This principle encourages straightforward approaches that anyone can understand and maintain, ensuring that improvements last.
How to Apply JDI Problem Solving: 7 Steps
Step 1: Spot the Problem
Be alert for small issues during your daily work. Look for defects, inconsistencies, inefficiencies, or customer pain points that have simple solutions. Train yourself to notice when something “doesn’t look right” or creates waste. The best JDI opportunities are often found in recurring annoyances that everyone has learned to work around rather than fix.
Step 2: Check Your Authority
Before making changes, verify that the solution falls within your authority level. Know your organization’s boundaries for independent action. Some fixes might need approval, especially if they affect multiple departments, have safety implications, or require spending beyond certain limits. When in doubt, a quick check with your supervisor can prevent overstepping.
Step 3: Assess Safety and Risk
Evaluate potential risks and unintended consequences before acting. Consider how your solution might affect other processes, people, or quality parameters. Use a quick mental check: “Will this fix create new issues elsewhere?” Focus on solutions that truly solve problems rather than shifting them to different areas or people.
Step 4: Take Immediate Action
Once you’ve identified a safe solution within your authority, implement it immediately. Don’t wait for the “perfect time” that may never come. The essence of JDI is in its name – just do it now. Quick action prevents the problem from continuing and demonstrates a commitment to quality. Use the tools and resources immediately available to you.
Step 5: Track the Results
After implementing the fix, observe its effects. Did it solve the problem completely? Partially? Has it remained stable? Collect simple data when possible, such as counting defects before and after, measuring time saved, or noting customer feedback. This verification step ensures your solution actually works and provides evidence of improvement.
Step 6: Document in the JDI Log
Create a brief record of the problem, action taken, and results. Include before/after data when available. A simple JDI log helps track small improvements that collectively make a big difference. Documentation ensures the solution becomes standard practice rather than a one-time fix. Include photos or diagrams when they help explain the improvement better than words alone.
Step 7: Share What You Learned
Communicate your fix and its results with teammates, especially those affected by the same issue. This can be as simple as a note at a team huddle or a quick email summarizing what you did. Sharing prevents others from duplicating efforts and spreads effective practices. It also gives visibility to small improvements that might otherwise go unnoticed.
JDI Problem Solving Documentation Guidelines
Keep a Simple JDI Log
Maintain a straightforward record that anyone can easily update and understand. This log becomes your quality improvement history, showing patterns and progress over time. A good JDI log doesn’t need complex forms or databases – even a simple spreadsheet works well. The key is consistency in recording each improvement, no matter how small, to build a complete picture of ongoing quality efforts.
Take Before/After Photos
Visual evidence is powerful for demonstrating improvements. A quick smartphone photo before and after a JDI fix creates compelling documentation that words alone cannot capture. These images help others understand exactly what changed and why it matters. Visual documentation is particularly effective for physical changes to workspaces, equipment adjustments, or organization improvements.
Create One-Point Lessons (OPL)
When you solve a problem that might happen again, develop a simple one-page lesson. These concise documents combine visuals and minimal text to teach others how to implement the same fix. One-point lessons turn individual knowledge into organizational knowledge, ensuring consistent handling of common issues. They should be visual, focused on a single point, and simple enough to understand in minutes.
Update Standard Work Documents
Ensure your improvement becomes the new normal by updating official procedures. When a JDI fix proves effective, incorporate it into standard work instructions, checklists, or training materials. This step transforms a one-time fix into a permanent improvement. Updated documentation prevents backsliding to old methods and ensures new team members learn the improved approach from the start.
Use Visual Management
Make improvements obvious through visual indicators. This might include color-coding, before/after displays, or simple status boards tracking JDI progress. Visual management helps everyone see at a glance what has improved and where. This visibility celebrates success while highlighting opportunities for additional improvements in similar areas.
Document Time Saved and Impact
Quantify the impact of your JDI actions whenever possible. Measure improvements in concrete terms – minutes saved, defects prevented, customer complaints reduced, or materials conserved. These metrics help justify the time spent on small improvements and build support for the JDI approach. Even rough estimates provide valuable data for demonstrating cumulative benefits over time.
How to Combine JDI Problem Solving with Other Quality Tools
JDI is a QUICK ACTION tool – it bridges the gap between problem identification and immediate resolution. Here’s how it integrates:
8D Report
Ishikawa generates causes; FMEA organizes them by failure mode and assesses risk. “All causes for this failure (Ishikawa) → Risk rating for each (FMEA).” Cause brainstorming → Risk quantification.
PDCA Cycle
JDI captures quick wins; A3 documents complex problem-solving journeys. When JDI reveals deeper issues, escalate to A3. “This JDI fix keeps recurring – time for an A3 investigation.”
Quick fix → Comprehensive analysis.
A3 Method
Ishikawa is the engine of 8D Step D4 (Root Cause Analysis). “Problem defined (D2) → Causes explored (D4 with Ishikawa) → Root cause verified (D4).” Systematic investigation framework.
Quality Alert
JDI actions feed into Lessons Learned databases. “This JDI could help other sites – let’s document it in Lessons Learned.” Local improvement → Global benefit.
Check Sheets (Tally Sheets)
Quality Alerts raise the flag; JDI provides immediate response. When an alert triggers, JDI containment actions protect customers. “Quality Alert issued – JDI containment started within 15 minutes.” Alert notification → Immediate action.
Pareto Chart
When a simple JDI reveals deeper questions, 5-Why digs further. “JDI fixed the loose screw – but why did it loosen? 5-Why time.” JDI stops the bleeding; 5-Why prevents future wounds.
Symptom treatment → Cause elimination.
Ishikawa Diagram
Is-Is-Not identifies WHERE in the process problems occur. “IS: After Step 5. IS NOT: Before Step 5.” Process mapping validates location hypotheses.
5-Why Analysis
When JDI fixes don’t stick, Ishikawa investigates why. JDI addresses obvious causes; Ishikawa uncovers hidden ones. “JDI fixed this three times – Ishikawa shows we’re missing something.” Surface fix → Root cause discovery.
5W2H Method
Before JDI action, 5W2H ensures you understand the problem completely. “What, Where, When, Who, Why, How, How Much – now JDI it.” Problem clarity → Effective action.
Is-Is-Not Analysis
When unsure if JDI is appropriate, Is-Is-Not clarifies the scope. “Is it happening here but not there? Simple pattern – JDI applies.” Problem boundaries → Right approach selection.
One-Point Lesson (OPL)
FMEA is a core APQP deliverable. Design FMEA in Phase 2, Process FMEA in Phase 3, both feeding Control Plans in Phase 4. APQP provides the framework; FMEA provides the risk analysis within it.
Lessons Learned
JDI actions should be tracked in the action management system. “JDI completed – log it in action management for tracking.” Individual action → System visibility.
Standard Work / Work Instructions
Every good JDI deserves a One-Point Lesson for knowledge sharing. “JDI fixed it – OPL ensures everyone learns how.” Individual learning → Organizational knowledge.
Control Plan
Histograms visualize differences between IS and IS NOT populations. “Affected parts have different distribution than unaffected parts.” Overlay histograms for visual contrast. Statistical visualization supports Is-Is-Not conclusions.
Visual Management
Successful JDI fixes should update standard work. “This JDI improved the process – update the work instruction now.” One-time fix → Permanent improvement.
Poka Yoke
SIPOC shows process context; Is-Is-Not pinpoints problem location within it. “Supplier X, Process Y, Output Z – Is-Is-Not says problem is in Process Y.” Process context → Problem isolation.
Action Management
Gemba walks identify JDI opportunities; JDI demonstrates immediate response. “Saw it on Gemba, fixed it with JDI, documented with OPL.” Observation → Action → Documentation.
Gemba Walk
JDI solutions often become visual management tools. “This JDI color-coding prevents the error – make it a standard visual.” Quick fix → Permanent visual control.
Six Sigma DMAIC
JDI is rapid “Do” without extensive “Plan”; PDCA provides the full improvement cycle. Small JDI fixes feed into larger PDCA projects. “JDI fixed the symptom – now let’s PDCA the system.” Immediate relief → Systematic improvement.
JDI Problem Solving– Real-World Examples
1. Pizza Production
Daily Pizzeria Operations
Complete JDI industry example for food service. Shows 10 practical problem solutions from a pizzeria: shifted toppings fixed with cardboard triangles, forgotten sides eliminated with sticker system, FIFO improved with visual arrows. Total savings: over €600/week.
💡 Want to create your own? Contact me for the free template.
2. Automotive / Manufacturing
Assembly Plant Operations
Complete JDI industry example for automotive manufacturing. Shows 10 practical problem solutions from an assembly plant: missed Kanban cards eliminated with orange signs, tool searching reduced with shadow boards, Andon signal enhanced with flashing lights. ROI: approx. 12 hours/week productivity gain.
💡 Want to create your own? Contact me for the free template.
3. Pharmaceutical Industry
GMP-compliant Solutions
Complete JDI industry example for pharmaceutical industry. Shows 10 GMP-compliant problem solutions: incomplete signatures eliminated with checklist cards, calibration status visualized with flip cards, date formats standardized with stamps. Zero findings at last FDA inspection.
💡 Want to create your own? Contact me for the free template.
4. Service Industry
Restaurant Solution
Complete JDI industry example for hospitality/service industry. Shows 10 practical problem solutions from a café: allergen questions reduced with color dot system, WiFi requests eliminated with QR codes, customer flow improved with floor markings. Total savings: approx. 1.5 hours/day.
💡 Want to create your own? Contact me for the free template.
5. IT/Software Industry
IT Department
Complete JDI industry example for IT departments. Shows 10 practical problem solutions: Teams delays eliminated with OPL, WiFi requests reduced with QR codes, VPN tickets reduced by 60% with self-help guide. Total savings: approx. 4 hours/week for strategic IT projects.
💡 Want to create your own? Contact me for the free template.
Benefits of JDI Problem Solving
Speeds Up Continuous Improvement
JDI dramatically accelerates the pace of positive change in an organization. Traditional improvement methods often get bogged down in approval processes, committee meetings, and extensive documentation requirements. By removing these barriers for small, low-risk improvements, JDI allows organizations to implement dozens or even hundreds of small fixes in the time it would take to execute a single large project. This rapid execution creates momentum and delivers immediate benefits rather than delayed gratification.
Builds Team Confidence
Every successful JDI action develops problem-solving skills and builds confidence. When employees see that they can identify and fix issues on their own, they gain self-assurance in their abilities. This confidence grows with each successful fix, encouraging more initiative in the future. As team members see their ideas implemented and working, they develop a sense of ownership and pride in their work. This psychological benefit often outweighs the technical value of the fix itself.
Creates a Culture of Action
Consistent use of JDI shifts organizational culture from passive acceptance of problems to active problem-solving. When everyone from frontline workers to executives embraces the JDI mindset, the entire organization becomes more responsive and agile. This culture of action values doing over endless discussing, testing over theorizing, and progress over perfection. In such environments, problems are seen as opportunities to improve rather than failures to hide, dramatically increasing the pace of positive change.
Reduces Backlog of Small Issues
Many organizations suffer from a growing list of minor problems that never receive attention because they’re not critical enough to prioritize. JDI provides a mechanism to clear this backlog without diverting resources from major initiatives. By addressing small issues as they’re discovered, the organization prevents them from accumulating into overwhelming technical debt. This continuous clearing of small problems ensures that resources can be focused on strategic improvements rather than constantly fighting accumulated small issues.
Respects Frontline Expertise
JDI fundamentally acknowledges that those closest to the work understand it best. By empowering frontline workers to make improvements without extensive approval chains, organizations demonstrate trust in their employees’ expertise and judgment. This respect increases engagement and job satisfaction while capturing valuable insights that might otherwise never reach management. Workers who feel respected and valued contribute more readily to improvement efforts at all levels.
Keeps Focus on Customer Needs
At its core, JDI prioritizes fixing problems that affect customer satisfaction. Since many JDI actions address visible quality issues, waste, or inefficiencies that directly impact customers, the approach naturally maintains focus on customer needs. Quick fixes to customer pain points have immediate positive effects on satisfaction levels. The methodology’s emphasis on rapid response aligns perfectly with customers’ expectations for quick resolution of issues, making it particularly valuable in service-oriented environments.
Limitations of JDI Problem Solving
Not Suitable for Complex Problems
JDI works best for simple, well-understood issues with clear solutions. Complex problems with multiple variables, interdependencies, or unclear cause-effect relationships require more structured problem-solving approaches. Attempting to apply JDI to complex challenges often results in superficial fixes that fail to address underlying system issues. For complex problems, methodologies like Six Sigma, DMAIC, or Design Thinking provide the analytical depth and cross-functional collaboration needed for sustainable solutions. Know when to transition from JDI to more comprehensive methods.
May Miss Deeper Root Causes
The quick-action nature of JDI can sometimes address symptoms while leaving root causes untouched. When multiple related small problems appear, they might indicate a deeper systemic issue that JDI alone cannot resolve. Without occasional step-back analysis, organizations might continuously fix the same types of problems without addressing fundamental flaws in processes, equipment, or systems. Effective quality systems pair JDI with periodic root cause analysis to ensure that patterns of similar issues receive deeper investigation.
Can Lead to Uncoordinated Efforts
When many individuals implement JDI fixes independently, improvements may lack strategic alignment. Without some coordination, JDI efforts might optimize local processes at the expense of overall system performance. Resources might be spent on low-impact improvements while significant opportunities remain unaddressed. Organizations need to balance empowerment for quick action with sufficient coordination to ensure efforts align with strategic priorities. Regular reviews of JDI logs can help identify areas needing more coordinated improvement approaches.
May Create Inconsistent Solutions
Different teams solving similar problems independently through JDI can develop different solutions, creating inconsistency across the organization. This variation makes standardization difficult and can complicate training, maintenance, and quality assurance. When multiple locations or shifts encounter similar issues, some mechanism for sharing and standardizing solutions becomes necessary. Without this cross-pollination of ideas and standardization of best practices, JDI can inadvertently increase process variation rather than reducing it.
Not Ideal for High-Risk Situations
The rapid implementation characteristic of JDI makes it inappropriate for situations where failures could have serious consequences for safety, compliance, or business continuity. High-risk changes require thorough risk assessment, testing, validation, and often external approval before implementation. JDI’s streamlined approach deliberately bypasses these safeguards to enable quick action. Organizations must clearly define boundaries for JDI application, explicitly excluding high-risk areas where more controlled change management processes must prevail.
JDI Problem Solving Best Practices
Set Clear Boundaries for JDI
Establish specific guidelines that define when team members should use JDI versus when they should escalate or use more formal improvement methods. These boundaries might include cost limits (e.g., "JDI for fixes under $100"), time thresholds (e.g., "Use JDI for solutions requiring less than 2 hours to implement"), or risk parameters (e.g., "JDI is not appropriate for changes affecting critical safety systems"). Clear boundaries provide confidence to act independently while preventing overreach. Review and adjust these boundaries periodically based on team maturity and organizational needs. Consider creating a simple decision flowchart to help team members determine when JDI is the right approach.
Celebrate Quick Wins
Recognize and publicize successful JDI fixes to reinforce the value of small improvements. Share before-and-after success stories in team meetings, company newsletters, or on improvement boards. Consider creating a "JDI improvement of the month" recognition or other ways to highlight particularly creative or impactful quick fixes. These celebrations build positive reinforcement for improvement activities and help spread effective practices across the organization. When team members see their efforts recognized, they become more motivated to identify and implement additional improvements. Even small acknowledgments can significantly boost participation in continuous improvement.
Use the 15-Minute Rule
if it takes less than 15 minutes, just do it: Adopt this simple heuristic to overcome hesitation and procrastination. When you spot a problem with a solution that takes less than 15 minutes to implement, do it immediately rather than adding it to a to-do list. This rule prevents small issues from accumulating and helps build the habit of immediate action. The time threshold—whether 15 minutes, 30 minutes, or another short interval—should match your organization's context and risk tolerance. This rule is particularly effective because it acknowledges that the mental overhead of tracking a small task often exceeds the effort required to simply complete it.
Pair JDI with Other Methods
Create a seamless transition between quick fixes and more structured improvement methods. When JDI identifies issues beyond its scope, have clear pathways to escalate these to appropriate problem-solving methods like A3, PDCA cycles, or project teams. Teach team members to recognize when a problem requires deeper analysis even after a JDI fix has addressed immediate symptoms. JDI often serves as an excellent "first response" that mitigates immediate issues while more comprehensive solutions are developed. This paired approach ensures both quick wins and sustainable, system-level improvements.
Create JDI Cards for Common Issues
Create standardized cards or forms that pre-authorize specific types of frequent fixes. These cards outline the problem, standard solution, and implementation steps for common issues that repeatedly occur. When team members encounter these familiar problems, the card gives them immediate authority to implement the standard fix without seeking additional approval. This approach speeds resolution for known issues while ensuring consistent solutions. The cards also serve as training tools for new team members. Review and update these standard solutions periodically to incorporate new learning or changed conditions.
JDI Problem Solving Example: Pizza Delivery
JDI improving Pizza Delievery at Zero-Defect Pizzeria
At Zero-Defect Pizza, a chain priding itself on quality and consistency, delivery driver Marco noticed a recurring issue. Almost daily, at least two or three pizzas arrived at customers’ homes with toppings that had shifted to one side during delivery. This was causing customer complaints and occasionally required remaking pizzas at company expense.
Instead of simply reporting the problem to management or accepting it as unavoidable, Marco applied JDI principles:
Step 1: Spotting the Problem
Marco identified that pizzas were sliding inside their boxes during sharp turns and quick stops.
Step 2: Checking Authority
As this involved a minor change to packing procedures with no safety concerns, Marco knew he had the authority to test a solution.
Step 3: Ensuring Safety
Marco confirmed his idea wouldn’t compromise food safety or quality, as it only affected how the pizza was secured during transport.
4. Taking immediate action
During his next shift, Marco folded small cardboard triangles from unused box flaps and placed them against the pizzas to prevent sliding. This simple fix took less than 30 seconds per order.
Step 5: Tracking Results
Over the next week, Marco kept count of complaints related to shifted toppings. The number dropped from an average of 15 per week to zero.
Step 6: Documenting the Fix
Marco created a simple one-point lesson with photos showing how to make and place the cardboard supports. He added this to the delivery station with a tracking sheet to monitor effectiveness.
Step 7: Sharing the Solution
At the next staff meeting, Marco demonstrated his solution. Drivers from other locations quickly adopted the practice.
Results: $500/Week Saved
The JDI approach saved Zero-Defect Pizza approximately $500 weekly in remade pizzas and prevented countless minor customer disappointments. Management was so impressed they installed a small cutting station at each location to produce the cardboard triangles consistently. They also recognized Marco with their monthly “Quality Hero” award.
This example demonstrates how a frontline worker using JDI principles can solve a persistent quality problem without complex planning or approval processes. The solution was simple, cost-effective, and implemented immediately—exactly what JDI is designed to achieve:
FAQ JDI Problem Solving
What is JDI Problem Solving?
“JDI” in JDI Problem Solving means “Just Do It” – a quality tool focused on fixing problems immediately without delays. It’s a simple but powerful approach that emphasizes taking quick action rather than prolonged planning.
When should I use JDI Problem Solving?
JDI Problem Solving is best applied in daily operations when immediate action can prevent quality issues from escalating. Use it during production, when serving customers, or while performing routine tasks. The right time is now – especially when small issues are fresh and visible.
Why do organizations implement JDI Problem Solving?
Organizations implement JDI Problem Solving because:
- Small issues often accumulate into bigger problems when left unresolved
- It empowers frontline workers to take ownership of quality
- It builds a proactive culture valuing immediate improvements
- It keeps focus on customer satisfaction by fixing issues before they impact the end user
- It removes barriers between identifying a problem and solving it
What are the guiding principles of JDI Problem Solving?
JDI Problem Solving is guided by six core principles:
- Act now rather than plan endlessly
- Trust workers to make good decisions
- Focus on small wins that add up
- Learn by doing, not just thinking
- Fix root causes, not just symptoms
- Keep solutions simple and direct
How does JDI Problem Solving differ from other quality improvement methods?
JDI Problem Solving is focused on immediate action for simple, clear problems that don’t require extensive analysis. Unlike more structured methods (Six Sigma, DMAIC), JDI empowers frontline workers to implement fixes without lengthy approval processes or documentation requirements.
What's the step-by-step process for implementing JDI Problem Solving?
The steps for JDI Problem Solving are:
- Spot a problem you can fix now
- Check your authority to act
- Make sure the fix is safe and won’t cause new problems
- Take action right away
- Track the results
- Document the fix in a JDI log
- Share what you learned
How do I know if a problem is suitable for JDI Problem Solving?
A problem is suitable for JDI Problem Solving if it:
- Has a clear, obvious solution
- Can be fixed quickly (typically in under 15 minutes)
- Is within your authority to address
- Doesn’t pose safety risks or create new problems
- Doesn’t require significant resources or cross-functional coordination
What documentation should I maintain for JDI Problem Solving activities?
Documentation for JDI Problem Solving should be simple but consistent:
- Keep a basic JDI log with date, issue, action taken, and result
- Take before/after photos when appropriate
- Create one-point lessons (OPL) for recurring issues
- Update standard work documents to include the fix
- Document time saved or quality improved
What is the "15-minute rule" in JDI Problem Solving?
The 15-minute rule of JDI Problem Solving states that if a fix takes less than 15 minutes to implement, do it immediately rather than adding it to a to-do list. This prevents small issues from accumulating and builds the habit of immediate action.
What are the key benefits of implementing JDI Problem Solving?
The key benefits of JDI Problem Solving are:
- Speeds up improvement
- Builds confidence in team members
- Creates a culture of action
- Reduces backlog of small issues
- Shows respect for workers’ knowledge
- Keeps focus on customer needs
What are the limitations of JDI Problem Solving?
- Not suitable for complex problems
- May miss root causes of bigger issues
- Can lead to scattered efforts without coordination
- Might create inconsistent solutions across teams
- Not ideal for high-risk situations
What are some best practices for successful JDI Problem Solving implementation?
The limitations of JDI Problem Solving are:
- Set clear boundaries for when JDI is appropriate
- Celebrate quick wins to build momentum
- Use the 15-minute rule
- Pair JDI with other tools for bigger problems
- Create “Just Do It” cards for common issues
How can I set appropriate boundaries for JDI Problem Solving?
Establish specific guidelines defining when team members should use JDI Problem Solving versus when they should escalate issues. These boundaries might include:
- Cost limits (e.g., “JDI for fixes under $100”)
- Time thresholds (e.g., “Use JDI for solutions requiring less than 2 hours”)
- Risk parameters (e.g., “JDI is not appropriate for changes affecting critical safety systems”)
How can JDI Problem Solving be integrated with other improvement methodologies?
Create a seamless transition between quick fixes and more structured methods. When JDI Problem Solving identifies issues beyond its scope, have clear pathways to escalate these to appropriate problem-solving methods like A3, PDCA cycles, or project teams. JDI often serves as an excellent “first response” while more comprehensive solutions are developed.
What are JDI Problem Solving "Just Do It" cards?
JDI Problem Solving cards are standardized cards or forms that pre-authorize specific types of frequent fixes. They outline the problem, standard solution, and implementation steps for common issues, giving team members immediate authority to implement fixes without seeking additional approval.
