Table A1

Survey items on each of the six KE phases

Sub scaleItems
Problem definition phasePD1I ask questions in order to understand what the real problem is
PD2I ask questions to understand why a certain disparity is a problem for the organization
PD3I ask questions to estimate what the factual consequences of a disparity could be
PD4I ask questions to determine why a disparity is a problem at this point in time
Root-cause analysis phaseRA1I keep asking questions to find the root cause of a problem
RA6I think it is important to analyse possible root causes thoroughly
RA7I believe that you cannot make a decision about what should be solved, without a thorough root cause analysis
RA8*It annoys me when team members start discussing the implementation when we have not finished the root cause analysis
Generate idea phaseGI9I have ideas about how to solve the root cause of a problem
GI10I share my problem solving ideas without being influenced by possible restrictions
GI11I can suggest out-of-the-box solutions
GI12I enjoy coming up with creative solutions with everyone
GI13*I can assess whether an idea will really solve a root cause
GI14*It annoys me when team members say they cannot think of more solutions, after just 1 or 2 ideas
Plan implementation phasePI15I ask questions about the current situation to gain a proper understanding of how the work-floor employees will react to a proposed change
PI16I think about what work-floor employees need before they can start working with a solution
PI17*I think it is important that an implementation plan is achievable
PI18*I ask questions about the preconditions that need to be fulfilled before a solution can be implemented
PI19I ask questions about who needs to be involved in the decision making, in order to implement a solution successfully
PI20I think it is important to discuss and decide on the end result of a change
Implement phaseI21*I like implementing a solution
I22I talk to work-floor employees to get their opinions about a change
I23I talk to work-floor employees to see if a solution can be implemented
I24When I receive any signals that an implementation is not going well, I discuss it and, if necessary, take action
I25*I keep an eye on the progress of a plan and make adjustments where necessary
I26I make sure that no friction arises during the implementation of a solution
Check and sustain phaseCS27I make sure that we stick to the scope of what we want to implement
CS28*I ask questions to find out whether we have ensured that a new method will last
CS29I check whether all the elements of an aspired end result have been achieved
CS30I make sure that we report the end result of an implementation
CS31I make sure that we close a project properly
CS32*After implementing the solution, I ask if the problem is solved good enough

Note(s): The lead question of this survey was: “In general, when you are a member of a group that has to solve a problem, which statement is applicable to you?” All items were scored on a 7-point Likert scale with 1: totally disagree to 7: totally agree

*Items excluded based on exploratory factor analysis (communality to sub-scale <0.4)

Source(s): Created by authors

or Create an Account

Close Modal
Close Modal