How to Ask for Help

Knowing when and how to ask for help is a critical skill in school and in the workplace. This section covers how to formulate a good question, where to find the right resources, and how to make the most of the support available to you.

Learning outcomes:

Identify when you are stuck and describe strategies for determining what kind of help you need
Formulate a clear, specific question that gives someone enough context to help you effectively
List resources available for getting help such as peers, instructors, documentation, and online communities and explain when each is most appropriate

Key Takeaways:

Being stuck for 20 to 30 minutes without progress is usually a signal to ask for help, not a personal failure
A good question includes: what you are trying to do, what you already tried, and what happened when you tried it
Different resources are best for different problems: classmates for quick checks, instructors for conceptual confusion, documentation for how-to questions, forums for known technical issues
Asking clearly and specifically is respectful of the other person's time; a vague question costs them more effort than a precise one
Getting good at asking for help is a career-long skill; people who do it well get unstuck faster and build stronger working relationships

Would you like to download my PowerPoint to follow along?

Why People Avoid Asking for Help
- Many people wait too long to ask
- Worries about asking could include:
  - Don't want to look inexperienced
  - Think they should already know the answer
  - Worry about bothering others
  - Hope the problem will resolve itself
- Unfortunately, waiting too long often creates bigger problems
- Do not wait until:
  - The night before a deadline
  - A project has completely failed
  - A small issue becomes a major issue
  - You're in a panic
- Nine Ways To Encourage Employees Who Hesitate To Ask For Help
- Why High Achievers Struggle to Ask for Help
Try First
- Students
  - Re-read instructions
  - Review course materials
  - Check examples
  - Review feedback (if applicable)
  - Search notes and resources
- Workplace
  - Review documentation
  - Search internal knowledge bases
  - Check project requirements
  - Review previous communications
  - Examine similar examples (if applicable)
- The goal is to understand enough to ask a meaningful question.
- Decide how much time you will spend reviewing materials and researching on your own before asking for help.
- One technique for working through a problem before asking: Rubber Duck Debugging (Wikipedia) — explain the problem out loud, step by step, to clarify your thinking before reaching out
Identify the Specific Problem
- Specific questions receive faster and more useful responses
- Good questions also lead to shorter discussions because there is less back and forth hoping the right question gets asked or an answer is stumbled on
- Bad Example:
  - "I don't get it."
- Good Example:
  - "I understand how to create the database table, but I'm unsure how to connect it to my web application."
- A common trap is the XY Problem — asking about your attempted solution instead of the actual problem, which leads to unhelpful answers
Ask yourself some questions
- Before reaching out, write down:
  - What are you trying to do?
  - What actually happened?
  - What did you expect to happen?
  - What have you already tried?
  - What specific question do you need answered?
Find the right person to talk to
- If you are a student, your teacher/professor is a good potential first person to reach out to, they might not have the answer, but they might be able to suggest another person
- Examples of who to go to when
- Instructor:
  - Assignment expectations
  - Course concepts
  - Grading questions
- Tutor:
  - Practice and reinforcement
- Classmate:
  - Clarification and discussion
- Supervisor:
  - Priorities
  - Expectations
  - Decision-making
- Coworker:
  - Processes
  - Tools
  - Procedures
  - Internal Documentation
- Subject Matter Expert:
  - Specialized knowledge
Ask a Clear Question
- A good help request includes:
  - Context
  - What you tried/What didn't work
  - The obstacle
  - A specific clear question
- Help Request Formula:
- Context
  - What are you working on?
- Effort
  - What have you already tried?
- Problem
  - What is preventing progress?
- Question
  - What specific help do you need?
- Stack Overflow: How do I ask a good question? — a practical guide to applying this formula in technical communities
- How To Ask Questions The Smart Way — a detailed classic reference on what makes technical help requests effective or ineffective
Example of an unhelpful help request
- Poor Requests:
- "Hi. I don't understand the paper. Can you help?"
- "What do I do?"
- "This doesn't make sense"
- The instructor has no information about the problem.
Example of a helpful help request:

Hello Professor Smith,

I am working on the research paper due next week and have completed my initial source gathering.

I found six sources, including two academic journal articles, two government reports, and two news articles. After reviewing the assignment instructions, I am unsure whether the news articles meet the requirement for scholarly sources.

I reviewed the assignment sheet and the example bibliography but am still uncertain about the expectations.

Could you clarify whether news articles are acceptable supporting sources, or should I replace them with more scholarly articles?

Thank you for your time
Why this is better: Provides context, Demonstrates effort, Explains the specific concern, Asks a focused question
Example for a workplace
- Scenario:
  - An employee is working on a website update and encounters a problem connecting to a database.
- Poor Request
  - The website is broken. What should I do?
- This requires the other person to investigate everything
- How To Ask for Help in an Email (With Examples)
- How to Ask for Help at Work Correctly
Hi Betty,

I'm currently working on the customer portal update and am trying to connect the application to the new database server.

I reviewed the deployment documentation and verified that the connection string matches the project requirements. I also tested the database credentials provided in the setup guide.

The application starts successfully, but I receive a connection timeout whenever it attempts to retrieve customer data.

Before I continue troubleshooting, can you confirm whether there are any firewall or network configuration steps required for development environments?

Thank you
Common Mistakes
- Avoid:
  - "It doesn't work."
    - Explain what happened instead.
  - Asking Multiple Unrelated Questions
    - Focus on the most important issue first.
  - Waiting Too Long
    - Small problems become larger problems.
  - Hiding What You Tried
    - Sharing your attempts helps others avoid repeating steps.
  - Asking for the Entire Solution
    - Ask for guidance, not for someone else to complete the work.
Following Up After Receiving Help
- Acknowledge the Help
  - Thank the person for their time.
- Apply the Advice
  - Attempt the suggested solution.
- Report Results or follow up if needed
  - If appropriate, explain whether the suggestion worked.
- Example:
  - Thank you for the recommendation. Updating the connection settings resolved the issue and the application is now communicating with the database correctly.

Suggested Activities and Discussion Topics:

Activity: Listen to This Podcast That was created using AI from these materials. Transcript for the Podcast What are your thoughts? Did the AI do a good job representing the materials? Did you find any mistakes? This should take about 20–25 minutes.
Activity: Go through This AI generated study guide, what do you think? Did it capture the week materials well? How did you do on the self quiz? Do you know all the vocab used?
Activity: Go through this AI-generated key terms list for this module. How many of the terms did you already know? Were there any definitions you would update or expand based on the lecture notes? Did the AI miss any important terms? This should take about 10–15 minutes.
Activity: Two different AI tools were used to generate two different study guides for this topic: Study Guide A and Study Guide B. Both were produced entirely by AI from the same source materials. Read through both and write a compare and contrast response addressing the following questions: What did each AI choose to emphasize, and what did each one leave out or treat lightly? Are there any facts, definitions, or explanations in either guide that seem inaccurate or misleading compared to the original materials? Which guide would be more useful for studying? Is it more complete, better organized, or clearer? What does the difference between the two guides tell you about the reliability of AI-generated study materials in general? Would you trust either of these guides to prepare for an exam without cross-checking against the original materials? This should take about 30–45 minutes.
Activity: Take a problem you are currently stuck on (in any class, at work, or in a personal project). Write two versions of a request for help: one vague and one specific. The vague version should be what you might dash off in a panic. The specific version should include what you are trying to do, what you have already tried, what result you expected, and what actually happened instead. Then reflect: How much easier would it be to help the second version of you? What did writing the detailed version help you realize on your own? This should take about 20–30 minutes.
Activity: Research what makes a good question on a technical help forum such as Stack Overflow or a class discussion board. Read at least one resource on how to ask a good question, then find a real example of a poorly asked question and rewrite it following the guidelines you found. Be prepared to explain what was wrong with the original and what you changed and why. This should take about 30–45 minutes.
Discussion: Have you ever been afraid to ask for help? What made it feel risky: fear of judgment, not knowing how to phrase the question, or something else? What helped or what do you think would help reduce that barrier, both for yourself and for others around you?
Discussion: In a professional setting there is an expectation of some independence, but asking for help at the right time is also a sign of good judgment. Where do you think the line is? How long should you try to figure something out on your own before asking? Does the answer change depending on the stakes, the urgency, or who you would be asking?
Activity: Read these three example emails asking for help (Poor, OK, and Good) and evaluate each one using the following questions: What information is present and what is missing? Could you answer this question on the first try, or would you need to ask follow-up questions before you could help? What specifically would you change to make the weaker examples more effective? Then think about the last time you asked someone for help: which of these three examples is closest to how you asked, and what would you do differently now? This should take about 20–30 minutes.
Activity: Choose an AI tool of your choice such as ChatGPT, Gemini, or Claude. Copy and paste the text of the poor help email example into the AI and ask it to rewrite it as a clear, effective request for help. Then compare the AI's version to the good example from this module. Answer the following: What did the AI add that was missing from the original? Did it make up any details it couldn't have known? Does the AI version include all the key elements a good help request needs, including what you're trying to do, what you tried, what happened, and your environment? What would you still need to change before sending it? This should take about 5–10 minutes.
Activity: Find a real question posted on a technical forum such as Stack Overflow that received helpful, upvoted answers. Using the framework from this module, evaluate the original question: Does it include context, effort, the specific problem, and a focused question? What did the person do well? What could they have improved? Then find a question on the same site that was closed, downvoted, or marked as unclear. What specifically is missing compared to the well-received one? This should take about 20–30 minutes.
Activity: Practice asking for help from a real source. Identify something you are genuinely stuck on (in any class, a personal project, or something technical). Using the help request formula (Context, Effort, Problem, Question), write a help request and actually send it to an instructor, a classmate, a forum, or an online community. After you receive a response, reflect: Did using the formula make the question easier for someone to answer? Did they ask any follow-up questions you could have anticipated? What would you do differently next time? This should take about 15–20 minutes to write; response time will vary.

Related modules you might find useful:

Would you like to see some more How tos? See more How tos