Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Culture: Answering without Context #164

Open
actionjack opened this issue Oct 14, 2019 · 4 comments
Open

Culture: Answering without Context #164

actionjack opened this issue Oct 14, 2019 · 4 comments

Comments

@actionjack
Copy link
Owner

Examples are:

Why is failing?

Ah that would because of the XYZ issue

When XYZ is some issue specific to their environment.

Ok Assume that I'm new here and I have yet to come across the XYZ issue. So what is the XYZ and how do I get around it?

@actionjack
Copy link
Owner Author

familiarity breeds contempt

@actionjack actionjack changed the title Answering without Context Culture: Answering without Context Oct 15, 2019
@actionjack
Copy link
Owner Author

actionjack commented Oct 15, 2019

There's no such thing as a stupid question but there is definitely such as thing as an Inadequate Answer

@actionjack
Copy link
Owner Author

@actionjack
Copy link
Owner Author

There's No Such Thing as a Stupid Question, But There Is Such a Thing as an Inadequate Answer

We've all heard the saying, "There's no such thing as a stupid question." It's a valuable reminder that curiosity and inquiry are crucial for learning and growth. However, what we often overlook is that while no question is inherently stupid, there is such a thing as an inadequate answer. The quality of answers we provide can significantly impact understanding and problem-solving within our teams and organizations.

The Problem with Inadequate Answers

Inadequate answers can stem from various sources—lack of knowledge, assumptions, or even the reluctance to dig deeper into the root causes of an issue. These insufficient responses can lead to misunderstandings, perpetuate problems, and create a culture where questions are discouraged rather than welcomed.

The Significance of Using the Five Whys

One powerful method to combat inadequate answers and foster a culture of thorough understanding is the "Five Whys" technique. Originating from Toyota's lean manufacturing methodology, the Five Whys is a simple yet effective problem-solving tool that asks "why" five times (or as many times as needed) to drill down into the root cause of an issue.

How to Apply the Five Whys

  1. Identify the Problem: Clearly state your problem.
  2. Ask Why: Ask why the problem is occurring.
  3. Analyze the Answer: Take the answer from the first "why" and ask "why" again.
  4. Repeat: Continue this process until you reach the root cause of the problem.
  5. Address the Root Cause: Once the root cause is identified, take corrective actions to address it.

Example in Practice

Let's illustrate this with a practical example:

Problem: The project deadline still needs to be met.

  1. Why was the project deadline missed?

    • Because the final deliverable still needs to be completed on time.
  2. Why was the final deliverable not completed on time?

    • Because the team encountered unexpected technical issues.
  3. Why did the team encounter unexpected technical issues?

    • Because there was insufficient testing during the development phase.
  4. Why was there insufficient testing during the development phase?

    • Because the project timeline needed to allocate more time for comprehensive testing.
  5. Why did the project timeline need more time for comprehensive testing?

    • Because the project was underestimated during the planning phase.

By applying the Five Whys, we uncover that the root cause of the missed deadline was an underestimation during the planning phase. Addressing this root cause might involve improving the estimation process and ensuring adequate testing time is allocated in future projects.

Benefits of Using the Five Whys

  1. Promotes Deeper Understanding: Encourages teams to look beyond surface-level symptoms and understand the underlying causes of problems.
  2. Encourages Continuous Improvement: By addressing root causes, organizations can implement changes that prevent recurring issues.
  3. Enhances Problem-Solving Skills: Fosters a culture of critical thinking and thorough analysis.
  4. Builds a Culture of Inquiry: Reinforces that asking questions is valuable and necessary for continuous improvement.

Conclusion

While there may not be such a thing as a stupid question, inadequate answers can certainly hinder progress and understanding. By leveraging techniques like the Five Whys, we can ensure that we provide meaningful, thorough answers that drive real solutions and foster a culture of continuous improvement. Encouraging deep inquiry and critical thinking will solve problems more effectively and empower teams to innovate and excel.

What methods do you use to solve problems in your organization? Share your experiences and insights in the comments!

#ProblemSolving #ContinuousImprovement #FiveWhys #Leadership #TeamCollaboration #CriticalThinking #LeanManufacturing #RootCauseAnalysis

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant