When facing yet another field issue with a high price tag, my Chief Technical Officer asked me, “How do we get more predictive so we can identify and prevent these failures from occurring in the future?” Similarly, I had a friend who was trying to optimize a key customer feature of a future product. He ran robustness experimentation considering over 40 noise and control factors that the team had brainstormed. And yet, when field trials started, the device had several failures of unknown cause. Of the more than 40 factors that they had considered during brainstorming, they missed the noise factor that was triggering these failures. I’ll turn to you and ask the same question: How do we get better at predicting future failures and preventing them from occurring? If we had infinite knowledge, we could see these failures before they occurred.
[Read more…]on Leadership & Career
A listing in reverse chronological order of articles by:
- Katie Switzer — Advanced Engineering Culture series
- John Martz & Jim Liddy — ASQR&R series
- Ash Norton — Engineering Leadership series
- Tim Rodgers — Managing in the 2000s series
- Rob Allen — Product Development and Process Improvement series
Module Level Weibulls
We can learn more from our failures than we can from our successes. This isn’t just a good rule for us to live by personally but is applicable to the products that we design and manufacture. In my experience, the all-important step that is short-changed in “learning from our failures” is “learning”—not just getting to the root cause in order to solve the problem but to understanding the gaps that exist in our current design and manufacturing requirements and practices that allowed the failure to spill into the field. Identifying these gaps is the key to future failure prevention. In this installment, I’m going to highlight how Weibull Analysis (a reliability tool when used in the time domain) of module field failures can be used to identify the holes in our design or manufacturing requirements or processes.
[Read more…]Robustness, Reliability and Quality
Robustness: That Often Overlooked Yet Powerful Discipline and Toolset. Most companies have a Quality organization, and some have a Reliability organization. But rarely will you find a company with a Robustness organization or even a single Robustness Engineer. And yet, of these three disciplines, Robustness can have the largest impact on your customer satisfaction because Robustness as a discipline and toolset addresses:
- a wider range of field issues than reliability and quality
- those issues that occur during the “design life”
Mitigating Employee Fears
Fear is that hidden factor present in every organization, preventing leadership from achieving the growth they desire. In the 2 previous articles, I brought up the types of employee fears and how that fear can negatively impact a given organization. Additionally, I brought up the importance of assessing these fears and understanding how they’re specifically affecting your organization. In this third and final article in this series, I’ll explore what leadership can do to mitigate these fears towards cultivating a culture of trust and empowerment.
[Read more…]Measuring Employees’ Fears and Effects
In the previous article, I shared how employee fears can negatively influence the work culture of your organization, stifling innovation, hampering collaboration, limiting growth and preventing continuous improvement. In this, the second article of a 3-part series, I’ll share the elements of an effective tool to evaluate your organization for employee fears and the impact of those fears.
[Read more…]Effects of Workplace Fear
In any organization, effective leadership is crucial to driving success and achieving goals. However, one often overlooked aspect of leadership is the role fear plays in an organization. Fear and its negative effects are present in every organization but rarely identified or measured. And when employees are afraid, they are less likely to take risks, share ideas, or give clear, honest assessments of risk. In this first article of a 3-part series, I’ll share the general effects that fear can have on your organization. And in the follow-up articles, I’ll share what can be done to identify, measure and mitigate these fears. In the end, employee fears stifles innovation, hampers collaboration, limits growth and prevents continuous improvement as detailed below.
[Read more…]Saving Time and Money through Efficient Planning and Optimization
The first article in The Power of Design of Experiments Article Series
In the world of research and development, time and money are precious commodities. DOE is the one statistical tool to save both time and money through its efficiency and efficacy. By carefully planning and executing experiments, DOE not only saves time and money but also leads to optimized designs and improved outcomes.
[Read more…]Who called this meeting, anyway?
Often, when the completion of a task or deliverable is needed, a meeting is a good way to establish mutual understanding of the way forward. With many resources working remote these days, effective meetings are taking on even greater importance.
Demystifying Business Requirements
In a previous article, we compared and contrasted the definition of a requirement, with a ‘story’, which is used in agile/scrum. In that article, we stated: “requirements and stories establish a clear understanding of customer needs in the context of desired functionality”.
What if we want to establish a clear understanding of a customer’s needs in the context of desired business functionality? The customer can be an internal or external customer, business functionality can be a business process (IT-enabled or otherwise).
Tiered Meetings Structure Enables Production Oversight & Support
A complex production process requires a mixture of leadership, governance and management. In this article, we’ll discuss a tiered meetings structure that can effectively enable this. Empowerment, escalation paths, accountability and responsibility are included as some key ingredients. We’ll start with the following diagram:
Fundamentals of Applying a Structured Approach
In reviewing several previous articles in this article series, it’s apparent there is much in common with product development, project management and process improvement.
Let’s look at a brief list that considers a structured approach vs. unstructured
While this list is pretty “high-level” it reveals the importance of project leadership, governance and management. A structured approach (for example a phase-gate structure, DMAIC or agile/scrum) enables management and planning, which enables governance and governance enables leadership.
Some structured approaches may be more suitable than others depending on the type of project. However, any structure (with leadership, governance and management in mind) is probably better than none.
Minimizing Waste In Task Management
Our previous article identified several forms of waste, specific to completing tasks, as detailed by the following table:
Keep in mind, by focusing on tasks, this table assumes several things:
- a project selection process that ensures the project is valuable
- robust project requirements & planning
- project sponsorship and resources (team members) are made available
Achieving Lean by Identifying Forms of Waste
Our previous article compared agile/scrum with lean/kaizen and revealed several similar fundamentals that helped make each methodology easier to understand.
Since the objective of lean and agile is waste reduction, we also want to identify and eliminate various forms of waste.
In order to do this, first let’s consider our objective to manufacture hardware product, develop a hardware or digital product and/or execute a project:
Benefits of Comparing Lean/Kaizen with Agile/Scrum
Our previous article covered the benefits of comparing the DMAIC problem solving thought process with project management. The key takeaway was DMAIC can be more effectively executed using “measure & plan” phase.
Now let’s compare and contrast agile/scrum with lean/kaizen. While agile is primarily used in software development, there are many valid comparisons. By making this comparison, those familiar with kaizen will improve their understanding of agile and vice-versa. Also we’ll cover key success factors that are applicable to both.
Benefits of Comparing DMAIC with Project Management
Our previous article covered the benefits of comparing waterfall with agile, emphasizing the benefit of planning the agile process and product backlog content. In this article we’ll compare the Define, Measure, Analyze, Improve and Control (DMAIC) thought process, with a project management thought process.
DMAIC is a problem-solving thought process applies critical thinking to ensure robust problem solving. (See our previous article on the subject here.) DMAIC is not necessarily a process by which projects are managed, however. Recall the high-level project management process as follows:
- 1
- 2
- 3
- …
- 7
- Next Page »