We have seen the word “layoff” used during a reduction in force. A reduction in force is a mass firing, often engendered by management ineptitude but sometimes driven by market forces. A layoff occurs when we temporarily dismiss an employee, but we provide preferential treatment for them when the market bounces back. Even with the […]
Teams must grow; teams cannot be simply appointed and anointed. We may have a designated group that evolves into a team, but this emergent phenomenon takes time. It takes time to discover the strengths and weakness if each member of the group, understanding that ultimately transforms into trust, the backbone value/concept for any successful team. […]
Occasionally, we are put in the position of removing an employee; that is, we must fire them. In many cases, we will not have enough documentation to validate the ineptitude of such an employee. Furthermore, we may not have a standard algorithm (procedure) to follow when removing this individual. Many companies add the impediment of […]
We have never seen a meaningful employee evaluation system. The abominations are generally designed as a tool to assess the performance of the employee with respect to corporate goals. When they present the illusion of quantification, the values are really qualitative and they will inflate over time as people are ‘soft’ about providing ‘real’ assessment. […]
Ideally, the human resources function or department represents the employee to management and management to the employee. Sadly, in our experience, most human resources people are inclined to support the individuals who sign their paycheck and the employees are left swinging in the breeze. It is no wonder that employees will gravitate towards collective bargaining […]
Creating a separate software test group has pluses and minuses. At a minimum, we may have more to manage. Some of the minuses are a product of human nature. When we know our work will be inspected, we will often assume the inspector will catch issues and we pay less attention to the issue ourselves. […]
The Pareto chart (not to be directly confused with the Pareto probability distribution function) is a simple approach to revealing significance in data. Before we plot our chart, we need to complete some initial work: Gather the data in a natural format (count, floating point [decimal], dollars, etc.) Sort the data from high to low […]
We have been on a bit a tear (or rant) about FMEAs. We suggest the FMEA documentation is part of the core of a design process. The ultimate approach we have seen is that of Michael Anleitner (The Power of Deduction: Failure Modes and Effects Analysis for Design, Quality Press, 2010), which uses functional analysis […]
There is only one way to describe this scenario and that is via a story. Consider the organization that is coming to the end of the project. The product is a complicated subassembly that goes into a larger system and has numerous interactions and incarnations of the design. They are late in the delivery of […]
We submit that a Failure Mode and Effects Analysis (FMEA) review is a form of design review. After all, one of the purposes of a design review is to try and remove defects before they appear in the product and that is the entire rationale for the FMEA in the first place. Yet, most of […]