How to Get the Best Recommendation: Questions We’ll Ask You

Why We Ask Questions

Discovery questions are not there to slow you down. They are there to make sure the recommendation actually fits the situation you are in. The same request can lead to very different answers depending on the goal, the deadline, the budget, the setting, or the amount of flexibility you have.

That is why I prefer a real conversation over a rushed assumption. One clear answer can save several rounds of back-and-forth later. It also gives us a chance to notice the things that are easy to overlook at first, like a constraint that changes the option list or a preference that changes the tone of the recommendation.

A good question does not interrogate you. It narrows the field so the next answer is more useful. When that works well, the process feels less like explaining yourself and more like being understood.

If you are the kind of person who wants to see the method behind the method, the article on open-ended questions is a useful reminder that the quality of the answer often depends on the quality of the prompt.

• Questions help us understand your actual use case, not just the headline version of it.
• Questions make it easier to compare options without turning the process into guesswork.
• Questions reduce the chance that we recommend something too broad, too narrow, or too expensive for the job.

A Short Glossary

People sometimes know what they need, but not the vocabulary to describe it. That is normal. I keep this glossary simple on purpose so the process feels less intimidating.

Once those terms are clear, the rest of the conversation becomes easier. I do not need you to use the exact language above. I just need the real-world version of it.

Common Questions We Ask

The exact questions change with the request, but most discovery conversations return to the same core themes: what you need, what stands in the way, and what outcome would feel like a success. If you know those three things, you are already off to a strong start.

1. What are you trying to do?

This is usually the first question because it gives the request shape. A person may come in asking for one thing, but the underlying goal may be something else entirely. Maybe they want a recommendation that feels more personal. Maybe they need something fast. Maybe they are trying to solve a problem they have already run into twice.

A good answer does not need to be long. It just needs to be honest and specific enough to set the direction. “I need help choosing an option for a private dinner” is much more useful than “I need advice.” One tells us the context. The other leaves us guessing.

2. What constraints do we need to respect?

Constraints are often the most important part of the conversation. A recommendation that ignores timing, budget, size, accessibility, or available resources is not really a recommendation at all. It is a wish list.

That is why I ask about the boundaries early. If something cannot change, say so. If something is flexible, say that too. Even a short answer like “the date is fixed, but the format is flexible” helps us focus on the right possibilities.

3. What matters most to you?

Some people care most about convenience. Others care most about presentation, speed, longevity, simplicity, or cost. When you tell us your top priority, we can rank the options in a way that matches your real goals instead of assuming one priority fits everyone.

This question matters because tradeoffs are part of almost every recommendation. If you want the most polished option, we will talk differently than if you want the easiest option to manage. Neither answer is wrong. They just lead to different paths.

4. What have you already tried?

This is the question that saves everyone time. If you have tested an idea before, used a similar service, or received a recommendation that did not work, that history helps us avoid repeating the same mistake. Sometimes the most useful detail is not what you want now, but what already failed.

Even a brief note can help: “We tried a broader option and it was more than we needed,” or “The first version looked good, but it was too hard to maintain.” Those small lessons are worth more than they sound like they should be.

5. What would a good result look like?

This question turns a vague request into a practical target. A good result might mean fewer steps, a cleaner look, better coordination, a smoother process, or simply feeling confident that the choice makes sense. You do not need a perfect definition. You just need a direction.

I often think of this as the “after” picture. When the request is complete, what should be different? What should feel easier? What should you no longer have to worry about?

6. Is there anything we should avoid?

This is a small question with a big payoff. Sometimes a single “do not” matters more than five preferences. You might want to avoid a certain style, a certain format, a certain color, a certain level of formality, or a process that felt confusing last time.

When you share those boundaries, the recommendation gets safer and more comfortable. It is often easier to say what you do not want first, and that is perfectly fine.

How to Answer Clearly

Clear answers are not about sounding formal. They are about making your situation easy to understand. I recommend thinking in three layers: the goal, the context, and the limits. If you can give those three pieces, the rest can be refined later.

Here is the simplest way to answer well:

1. Start with the goal. Tell us what you are trying to achieve in one or two plain sentences.
2. Add the context. Explain where, when, or how the request will be used.
3. Name the limits. Share the deadline, budget, size, timing, or other constraint that cannot be ignored.
4. Give one or two examples. A previous experience, a photo, or a reference helps us understand your taste faster than a paragraph of abstract description.
5. Say what is still uncertain. If you are not sure about part of the request, say that directly.

The best answers are usually short, but complete enough to remove the biggest guesswork. If you need a model, try this pattern:

Example: “I am looking for a recommendation for a small group gathering in early fall. The date is fixed, the budget is moderate, and I want something simple to coordinate. I can share a few reference photos if that helps.”

Notice what that example does not do. It does not try to sound perfect. It just gives enough information for a useful response.

If you want more guidance on how to frame an open-ended answer, the NNGroup article on open-ended questions is a helpful companion piece.

Another thing that helps is using concrete language instead of abstract language. “I need something that works for three people and a short timeline” is easier to use than “I need a nice option.” The first answer lets us do something with it.

What Good Answers Let Us Do

When you give clear context, we can move faster without cutting corners. That matters because a recommendation is only helpful if it respects the realities of the request.

• We can narrow the options. Instead of offering everything, we can focus on what actually fits.
• We can spot conflicts early. A deadline, budget, or format mismatch is easier to solve before the recommendation is finalized.
• We can explain the tradeoffs. If there are two or three sensible paths, we can show the difference plainly.
• We can save your time. Clear answers mean fewer follow-up questions and fewer surprise revisions.

That is the part of the process people usually feel right away. The conversation gets shorter, but the result gets better. I like that tradeoff. It is one of the rare ones that improves both speed and quality at the same time.

Optional Information That Helps

You never have to provide every possible detail. Still, a few extra pieces of context can make the recommendation much stronger. When you have them ready, they can save a round of clarification later.

• Photos or visual references: These help us understand style, scale, and finish without relying on guesswork.
• Examples of past experiences: If something worked or failed before, that history is worth sharing.
• Relevant documents or links: A short reference file, a product page, or a note from another conversation can be surprisingly useful.
• Decision timing: If you need to choose quickly, say so. Timing often changes the recommendation.
• Who needs to approve it: If more than one person is involved, tell us who else is part of the decision.

For requests that touch workflow, coordination, or automation, it can also help to think through how the recommendation will be used after the initial decision. In some cases, a neutral resource like AI consulting services can be a useful example of how broad ideas become a practical plan before anything is built or adopted.

That kind of extra context is not about making the request complicated. It is about making sure the recommendation fits the real world, where people, deadlines, and budgets all have opinions of their own.

What If You Are Unsure?

This part matters more than people think. You do not need to have every answer before you reach out. In fact, some of the best conversations start with a rough idea and a few honest unknowns.

If you are not sure how to answer one of the questions, say that directly. A simple “I am still deciding” or “I am not sure what the best option is yet” is enough to keep the conversation moving. We can help narrow it down together.

If you want, you can also send what you do know and leave the rest blank. The goal is not perfection. The goal is momentum.

Here is a safe way to phrase an uncertain request:

“I know the general goal, but I am still sorting out the details. The timing is flexible, and I am open to guidance on the best fit. If there is anything else you need from me, I am happy to fill it in.”

If you are stuck, you can always move the conversation forward through our contact page. If you would rather read a little more first, browse the blog index for related guidance on communication, preparation, and next steps.

Request Checklist

Before you reach out, it helps to gather a few basics. You do not need a long document. You just need enough to make the first reply useful.

• Your goal in one sentence
• Any fixed dates or timing needs
• Budget, size, or scope limits if they matter
• Preferences that should shape the recommendation
• Examples, photos, or reference links if you have them
• Anything you want to avoid
• Who will make the final decision
• Any questions you still want answered

If you only have half of that list, send it anyway. Partial context is still useful, and it gives us something concrete to work with. The next step is usually easier than the first draft of the request.

Frequently Asked Questions

Do I need to answer every question?

No. Share what you know, and leave the rest for later if needed. The goal is to get enough context for a sensible recommendation, not to force a perfect form.

What if I only know the general idea?

That is fine. A general idea is still a good starting point. If you can describe the purpose, the timing, and any clear limits, we can help you fill in the missing pieces.

Can I send examples instead of long explanations?

Yes. Examples are often better than long explanations because they show style, scope, and expectation all at once. A photo, a link, or a short note can say more than a paragraph of vague description.

What if my answer changes later?

That happens. If something changes, just tell us before the recommendation is finalized. A small update early is much easier to handle than a bigger revision later.

What if I am choosing with someone else?

Say who is involved and what matters to each person if you know it. Multi-person decisions are common, and they are easier to manage when we understand who needs to feel comfortable with the result.

Final Thoughts

The discovery process should feel reassuring, not stressful. When the questions are clear, the answers become easier to give. When the answers are easier to give, the recommendation becomes more accurate. That is the whole point.

I like to think of this as a small courtesy with a big effect: a few well-placed questions save time, reduce confusion, and make the result feel more intentional. You do not need to solve the whole problem before you contact us. You just need to bring the best version of what you know right now.

If you are ready, use the checklist above, send your details through /contact/, and we will take it from there. If you want to keep reading first, /blog/ has more practical articles that explain how we help people prepare, decide, and move forward.