Tell me something questions are straightforward prompts used to request information, examples, or perspectives. They appear in interviews, performance reviews, coaching, sales calls, and everyday conversations. Unlike quick yes/no prompts, they invite explanation, context, and detail that reveal priorities, risks, and opportunities. Used intentionally, these questions surface facts, uncover assumptions, and support more deliberate decisions. This guide explains how to design, ask, and follow up on tell me something questions so you can get actionable, reliable answers in work and personal contexts.
What Are Tell Me Something Questions
At their simplest, tell me something questions ask a person to share specific knowledge, experience, or observations. Because they are open by design, they encourage a full response rather than a single-word reply. Common structures include open prompts such as tell me something about your workflow
or scenario-based prompts such as tell me something that changed your approach to this problem
. They work well early in a conversation to set a direction and later to close gaps in understanding. Because they focus on real-world content, they help you surface facts, context, and nuance that structured forms or checklists can miss.
Purpose and Typical Uses
You use these questions to collect reliable information, test assumptions, and clarify scope. In hiring, they translate vague requirements into concrete examples of past behavior. In product discovery, they translate user needs into observable behaviors and constraints. In management, they translate strategic goals into day-to-day tradeoffs and risks. In personal contexts, they translate abstract feelings into specific events and impacts. The consistent purpose is to move from general statements to concrete, actionable detail.
How to Design Effective Tell Me Something Questions
Well-designed tell me something questions focus on one topic, use clear language, and specify the context so respondents know what to share. Avoid double-barreled phrasing and leading language that steers answers toward a preferred outcome. Instead, state the domain and invite evidence, examples, or reasoning. Good questions make it easy for a respondent to know what to include and how deeply to respond.
Key Design Principles
- Be specific about the domain, time frame, or scenario.
- Ask for factual examples, decisions, or observed patterns rather than opinions alone.
- Use neutral wording to reduce bias and defensiveness.
- Clarify the purpose of the question so the respondent can tailor their answer.
- Limit each question to one clear focus to avoid confusion.
Question Stems and Variations
You can adapt tell me something questions to different contexts by changing the stem while keeping the intent to surface concrete information. Below are reusable stems you can tailor to your domain, along with the kind of response each tends to elicit and guidance on when to use them.
Sample Question Stems
| Question Stem | What It Surfaces | Best Used When You Want To |
|---|---|---|
| Tell me something about [process, role, system]. | Overview, structure, components, stakeholders. | Map a current state or establish a baseline. |
| Tell me something that happened when [event, change, failure]. | Causes, sequence of events, unintended effects. | Investigate incidents or turning points. |
| Tell me something you did that improved [result]. | Actions, experiments, measurable outcomes. | Surface what worked and how it was achieved. |
| Tell me something you wish others understood about [topic]. | Hidden constraints, assumptions, priorities. | Reveal gaps between intent and perception. |
| Tell me something that would change your view of [decision, risk]. | Critical thresholds, dealbreakers, key variables. | Test robustness of plans and assumptions. |
Asking and Responding in Real Conversations
How and when you ask a tell me something question affects the quality of the answer. Set context, explain why the information matters, and give respondents enough time and psychological safety to share details. Avoid interrupting, and use follow-ups to clarify vague statements or request concrete examples. In group settings, call on different perspectives and invite comparisons across answers to reveal patterns and outliers.
Best Practices for Asking
- Provide brief context so respondents understand the scope.
- Ask in a neutral tone and avoid leading phrasing.
- Pause after the question to allow thoughtful responses.
- Listen for specifics: dates, decisions, data, and observed behaviors.
- Paraphrase to confirm understanding before moving on.
Techniques for Respondents
- Start with a concise framing sentence, then provide examples.
- Use concrete situations rather than generalizations.
- Share the reasoning behind decisions, not just the outcomes.
- Note constraints, tradeoffs, and assumptions you had to make.
- Highlight lessons learned and how you would act differently.
Follow-Up and Probing for Depth
One ask rarely captures the full picture. Use follow-up questions to clarify details, test implications, and connect examples to broader patterns. Well-crafted probes reduce ambiguity, separate anecdote from evidence, and help you build a reliable, structured understanding of the topic.
Effective Follow-Up Prompts
- Can you give a specific example of that?
- What happened next, and why did it matter?
- How did you decide on that approach, and what alternatives did you consider?
- What would need to change for a different outcome?
- How does this compare to similar situations you have seen?
Sequencing Follow-Ups
Start with context-seeking questions, then move to specifics, and finish with implications and general patterns. This sequence helps you build a coherent narrative from anecdote to insight. Avoid rapid cross-examination; instead, allow the conversation to unfold so the respondent can connect causes, decisions, and outcomes naturally.
Contrasting Question Types to Avoid Confusion
It can help to distinguish tell me something questions from other common types so you use each at the right time. While all are open-ended to some degree, their intent and expected output differ in focus and structure.
Comparison Table
| Type | Intent | Typical Output | When to Use |
|---|---|---|---|
| Tell me something | Surface facts, examples, lived experience. | Narratives, sequences, concrete cases, details. | Exploring an area, building shared understanding. |
| Tell me everything | Comprehensive coverage, exhaustive detail. | Extensive lists, broad mapping, possible noise. | Discovery when scope is unclear; requires heavy synthesis. |
| How does it work | Mechanisms, processes, causal links. | Step-by-step explanations, dependencies, roles. | Technical or operational explanations. |
| How would you | Approach, design, or solve a specific problem. | Methodologies, tradeoffs, proposed actions. | Solutioning, planning, and strategy discussions. |
| What do you think | Judgment, evaluation, interpretation. | Opinions, recommendations, pros and cons. | Decision input, creative ideation, subjective assessment. |
Common Use Cases and Examples
Tell me something questions adapt to many scenarios. In job interviews, they invite candidates to describe specific projects, decisions, and tradeoffs rather than reciting duties. In product discovery, they translate user complaints into usage patterns and constraints. In retrospectives, they surface decisions, surprises, and learning tied to concrete deliverables. In coaching and mentoring, they help the coachee ground insights in lived experience and clarify next steps.
Use Case Examples
- Hiring: Tell me something about a time you had to handle conflicting priorities.
- Product: Tell me something a user did that revealed a deeper need.
- Operations: Tell me something about the last release that slowed delivery.
- Leadership: Tell me something you learned from a failure that changed how you manage.
- Coaching: Tell me something you tried recently that moved a goal forward.
Synthesizing and Acting on What You Learn
Collecting answers is only the first step. Synthesize by grouping similar themes, identifying repeated patterns, and separating one-off anecdotes from systemic insights. Translate findings into concrete questions, decisions, or experiments that test assumptions or improve outcomes. Close the loop by sharing what you learned and how it changed plans or behavior; this reinforces trust and encourages richer responses over time.
A Simple Synthesis Approach
- List raw answers and quote key phrases.
- Group by theme, process, or system.
- Identify common causes, blockers, and enablers.
- Formulate testable hypotheses or actions.
- Share insights and next steps with respondents.
Used consistently, tell me something questions become a durable tool for learning and decision-making. They convert vague discussion into concrete information that can be compared over time and used to align teams, refine products, and improve personal and professional choices.