Guide to designing open-ended questions that generate useful information

In many organizations, feedback still works as a simple opinion-gathering exercise. Performance is measured, open comments are added, and with that, companies assume they already have a complete picture of what is happening.

 

However, when we analyze it more deeply, a very clear limitation appears. Quantitative data allows us to compare, but not always to explain. Qualitative comments provide context about the employee’s situation, but they are not always easy to analyze. If we translated this into an everyday situation, it would be like looking at the scoreboard of a match without having watched the game. A lot of questions would immediately arise, wouldn’t they?

 

At this point, we know the problem is not the lack of information, but rather how the information is designed from the very beginning. We need to start from the most basic and decisive point: learning how to design questions that generate truly useful information.

 

From here on, our goal is to build a system where questions not only collect employee responses, but also help us create an analytical structure.

Before writing a single question, it is essential to understand what the information will be used for. In practice, the opposite usually happens. Many organizations ask questions first and only later decide how to interpret the answers. It is like assembling furniture without reading the instructions. Impossible, right?

 

If the goal is to analyze performance, questions must allow behaviors to be observed. If the goal is to understand impact, they should connect with outcomes. And if the goal is decision-making, they need to be comparable across people, teams, or periods.

Once the objective has been defined, the next step is to avoid the most common mistake: asking for general opinions. Questions such as “What do you think about this person’s performance?” or “What should they improve?” usually generate broad, subjective responses shaped by personal perceptions. In most cases, they are closer to being “polite and appropriate” than to providing truly useful information for the organization.

 

The shift happens when the question forces people to ground their answer in what is actually happening within the organization. When evaluators are asked to describe a real situation in which a person demonstrated a competency, the nature of the response changes completely. The process moves from interpretation to observation. And this is where something important happens: the information stops being a simple opinion and becomes something measurable.

Describing a specific behavior is already a major step forward, but it still leaves one important question unanswered: what impact does that behavior have within the system?

 

That is why the next level involves designing questions that connect action and impact.

 

When this happens, feedback stops focusing solely on the individual and begins to reveal broader dynamics. It becomes possible to observe how teams collaborate, where bottlenecks appear, which behaviors facilitate cooperation, and which ones negatively affect the workplace climate.

 

This step is crucial because it transforms feedback into something genuinely useful. It becomes a tool for understanding relationships within the organization.

When open-ended questions are too broad, a common problem appears: there is plenty of information, but no clear way to focus or organize it.

 

Each person naturally responds in a completely different way, causing topics to become diluted and making objective analysis difficult. This is why introducing focus is essential. The goal is not to limit the response, but rather to direct attention toward a specific element.

 

Once the right focus is found, feedback stops being a collection of isolated comments and begins to reveal repeated patterns across employees. Trends emerge, shared needs become visible, and clear opportunities for improvement appear. At this stage, the value lies not in the amount of text collected, but in the ability to structure it.

The next level appears when feedback is no longer disconnected from the business itself. Evaluating competencies without linking them to organizational goals creates a partial view. It helps us understand how a person works, but not whether that way of working contributes to what truly matters.

 

However, when questions incorporate this connection, the analysis becomes genuinely transformative. It is no longer just about individual performance, but about real contribution to team and organizational objectives.

The real transformation happens when all the information collected stops being analyzed separately. Competencies, goals, open comments, climate, or eNPS start connecting with one another. Feedback stops being a sum of isolated inputs and becomes a system.

 

This is the moment when organizations can cross-reference data, detect team patterns, identify differences by role or seniority, and better understand what is happening internally. The objective is not to collect more information, but to build a more complete understanding of reality.

After going through this entire process, the conclusion is quite simple. The value of feedback does not depend on how many questions are asked or how many comments are collected. It depends on how those questions are designed from the beginning.

 

When the design is correct, feedback stops being a collection of difficult-to-interpret opinions and becomes a system that helps organizations understand, compare, and decide.

And at that point, organizations stop accumulating data and start generating useful intelligence.