It is very easy to confuse good interview questions with good Evidence-Based Management questions. They are related, but they are not the same thing. An interview question is something you ask one person about their own experience:
- Do you feel that your supervisor listens to your suggestions?
- What usually happens when a machine breaks down during your shift?
- Why do you think people leave this department?
- Do you find the new scheduling system useful?
These can all be excellent questions. They may generate rich information, examples and stories. But they are still questions designed to collect data from individual respondents.
A management question operates at a different level. It asks what we want to understand once we combine evidence from several people, teams, sites, documents or studies.
For example:
To what extent do employees perceive that their improvement suggestions are taken into account, and what organizational factors influence that perception?
Or, in an operations context:
What factors are associated with recurring production disruptions, and how do operators and supervisors perceive the effectiveness of the current response process?
The difference may look subtle, but it matters.
A simple test: Could a single interviewee give me the answer? If the answer is yes, you probably have an interview question. If answering the question requires gathering evidence from several people, comparing experiences, identifying patterns, or combining interview evidence with other sources, then you are much closer to a management question. This distinction is particularly useful for junior professionals because, in practice, they are often given broad assignments such as:
- Find out why productivity has fallen.
- Understand why people are leaving.
- See whether employees are really involved in continuous improvement.
- Investigate why the new process is not working.
The temptation is to immediately prepare a long list of interview questions. But before doing that, it is worth deciding what you actually want to know.
Start from the interview questions, but do not stop there
You do not need to discard the questions you have already written. Instead, group the questions that appear to explore the same underlying phenomenon. Imagine, for example, that you are analysing employee participation in an operations team. You may have drafted questions such as:
- What happens when an operator identifies an improvement opportunity?
- How can employees submit improvement ideas?
- Who decides whether an idea is implemented?
- Can you remember an occasion when an employee’s suggestion resulted in a real change?
- Do people receive feedback about the ideas they submit?
These are useful interview items. But together they point towards a broader question:
How do employee participation channels operate in practice, and to what extent do employees perceive that their suggestions lead to meaningful action?
That is the question that gives coherence to the interviews.
The same logic applies in people management. Suppose you are trying to understand voluntary turnover in a department. Your interview guide may contain questions about workload, supervision, promotion opportunities, scheduling, recognition, and team relationships. The management question might instead be:
What factors do employees and line managers associate with voluntary turnover in this department, and which of these factors appear consistently across different roles or teams?
Now the project has a clearer analytical purpose. You are not simply collecting twenty individual stories. You are looking for patterns, differences, and plausible explanations.
A good management question defines the scope of the problem
In the CEBMa approach, a useful Evidence-Based Management question normally makes several things reasonably explicit.
- First, who or what are we talking about?
- Employees? Front-line supervisors? Maintenance teams? Production plants? Knowledge workers? Newly hired employees?
- Second, what phenomenon are we interested in?
- Absenteeism, employee voice, turnover, implementation of standard work, quality problems, safety behavior, workload, coordination between departments, and adoption of a new technology?
- Third, what do we want to know about it?
- How frequently does it occur?
- How does the process operate?
- How do people experience it?
- What factors appear to influence it?
- What consequences does it have?
- What interventions seem to improve it?
- And if a comparison is important, include that comparison explicitly.
For example:
How does perceived workload differ between production and support teams, and what organizational factors are associated with those differences?
Or:
How do highly standardized production units differ from less standardized units in the way operators report and resolve process deviations?
Once the comparison appears in the question, it becomes much harder to forget that you need to collect the corresponding information.
Why this matters in real organizational projects? The quality of the management question affects almost everything that follows. A vague question often produces a vague evidence-gathering exercise. You interview many people, collect dozens of interesting comments, and eventually discover that the material is difficult to synthesize because different interviews were actually exploring different issues. A clearer question helps you decide:
- Whom you need to interview;
- What information do you need to collect;
- Which comparisons are relevant;
- What additional organizational data may be useful;
- What external research evidence you should look for.
Consider an operations problem such as recurring delays.
If the question is simply:
- Why are there delays?
the investigation can quickly become unmanageable. But suppose you formulate it as:
- What are the main sources of recurrent scheduling delays in the assembly process, and how consistently are these causes identified across operators, supervisors and production data?
That question immediately suggests several sources of evidence. You may need interviews with operators and supervisors, but you may also need downtime records, production schedules, quality data or process observations.
That is an important feature of Evidence-Based Management: interviews are one source of evidence, not necessarily the whole evidence base.
Do not confuse a long interview guide with a sophisticated research design. Junior professionals sometimes worry that having only one or two management questions makes a project look too simple. Usually the opposite is true. A well-defined management question can require many interview items, several evidence sources and substantial analysis. For example, one question about employee involvement in continuous improvement may require you to explore:
- Access to participation channels
- Managerial response
- Psychological safety
- Feedback mechanisms
- Implementation rates
- Perceived fairness
- Differences between departments
- Examples of successful and unsuccessful suggestions
Those are not eight separate management questions. They may simply be different aspects of one phenomenon that need to be examined carefully. This is why one or two strong questions are often enough. If you end up with ten “research questions,” there is a good chance that some of them are actually interview questions in disguise.
The practical shift
For someone starting a career in Operations Management or People Management, I think the most useful change in mindset is this:
Do not begin by asking, “What questions should I ask people?”
Begin by asking “What do we need to understand in order to make a better management decision?”
Then decide what evidence would help answer that question. Some of that evidence may come from interviews. Some may come from organizational data. Some may come from scientific research. Some may come from professional expertise or stakeholder concerns.
The interview guide comes later.
Moving from questions to ask individuals to questions the organization needs evidence to answer is one of the most important steps in turning an informal investigation into an Evidence-Based Management process.
Visitas: 4
