How to Ask for Help When You Do Not Know What Is Wrong

When you need help but do not know what is wrong, describe the result you wanted, the result you can actually see, and where they differ. Include a relevant attempt and its outcome if you have one. Then ask someone to help choose the next thing to check. You can make that request while the cause is still unknown.

You do not need a technical name for the problem. “The file I opened contains two pages; I expected three” gives someone something to inspect. “The software is broken” adds a diagnosis you may not be able to support.

Separate the observation from your guess

Start with three short statements:

• Expected: what the finished result needs to contain or do.

• Observed: what happened in the version or output you actually checked.

• Unknown: what you cannot yet explain.

If you have a possible explanation, label it as a guess. “Could a page setting be involved?” leaves room to investigate. “The page setting caused this” says you have already established the cause.

UCLA’s Center for Cognitive Neuroscience guidance on asking for technical help recommends stating expected and actual outcomes, describing attempts and their results, and including relevant environment details. The fictional handout example below adapts those distinctions to a document task.

Turn a vague request into a next check

Imagine Rae is preparing a three-page workshop handout for review. The working document Rae opened contains pages 1, 2 and 3. The exported file Rae inspected contains only pages 1 and 2. Rae repeats the same export once and sees the same two-page result. This is a fictional example, not a test of any particular app.

Rae’s first message might be:

The export is broken. Can you fix it?

The helper cannot tell what is missing or which output Rae inspected. The message also calls the export broken before its cause is known. A more useful request is:

I need a three-page workshop handout for review. The working document I opened has all three pages, but the export I opened contains only pages 1 and 2. Repeating the export gave me the same result. Could you help me check which pages the export is set to include, or suggest the next thing to inspect? I can show the source and export versions I checked.

This request asks for help with one check, rather than asking the helper to take over the whole handout. Checking the page selection is a proposed investigation. Rae has not established that it caused the missing page.

Repeating the export is useful information because Rae can say what happened. It does not prove a software bug, and it does not explain why page 3 is missing. If Rae had made no useful attempt yet, the expected and observed results would still be a valid starting point for asking what to check first.

Include context that lets the person inspect the same problem

Keep the request tied to the material you checked. For a document problem, that may mean identifying the working document and the particular exported file, then showing where their contents differ. Someone looking at an older export would be investigating a different observation.

If the helper cannot see your setup, add the actual tool and version, relevant settings, or an exact message that appeared. Describe the short sequence that led to the result when it matters. Do not fill gaps with details you assume are true. Share only material the person is allowed to access.

If you cannot identify the right setting, say that directly: I do not know where to check which pages are included. Could you show me where to look? That is a specific request even without knowing the setting’s name.

Change the follow-up when a suggestion does not work

Suppose the helper suggests checking the selected pages. In this fictional continuation, Rae confirms that all three pages are selected, exports again, and opens the new file. It still contains only pages 1 and 2.

The next message can report the new evidence:

I checked the page selection and confirmed that all three pages were selected. I exported again and opened that new file; it still contains only pages 1 and 2. The working document still shows all three. That check did not resolve the missing page. What should I inspect next? I can show the selection and the new export.

“It still does not work” leaves out what the suggestion changed. The fuller reply tells the helper which check happened and what remained the same. It also keeps the diagnosis open: an unsuccessful suggestion has supplied another observation, not proved a different cause.

If you cannot yet say what the result should be

An expected result needs a basis. If you do not know what belongs in the handout, first ask for the requirement or an example: Which sections must the review copy contain? Could you point me to an approved example?

If you cannot open the source file, ask its owner for the access you need and name the file. Once you can inspect it, you can compare the source with the output. Describe that missing access directly instead of presenting it as an unexplained export failure.

For an unknown cause, a useful final line is simply: Given this difference, what would you check next? Send it with the observations that make “this difference” clear.