Movatterモバイル変換

You are notlogged in. Your edit will be placed in a queue until it ispeer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

Rev

Required fields *

What is the XY problem?

When asking questions, how do I recognize when I'm falling into it? How do I avoid it?

Return to FAQ index

Other languages:ES,JA,PT,RU

Answer*

(separated from my other answer because this one has more opinion than explanation)

If you agree that the "XY Problem" is only another (more specialized) term for "Use of wrong working hypothesis", as [illustrated and explained here](https://meta.stackexchange.com/a/250659/205446), and similar to the "Einstellung effect" [explained here by @Jonathan Benn](https://meta.stackexchange.com/a/243965/205446)&hellip;

We can think in terms of some main situations:

 * **Rush** situation: the wrong hypothesis is only a language or over-simplification side-effect, that can be corrected by the user with a little more attention, and investing more time editing the question.

 * **Normal** situation: as in the illustrated Missing Square puzzle, you do not know that your hypothesis is wrong. This is the main situation to discuss here (!).

So let's put focus on the *normal* situation.

------

# SOLUTIONS/ATTENUATORS

## The "XY problem" is a valid problem!
The Stack Exchange question is to show a problem. If my question helps to show that the real problem is my *wrong hypothesis*, it is OK! It is a *first step*, and perhaps I will not need any other questions after obtaining the *correct hypothesis* (and trying to solve by myself). 

Example. See "https://stackoverflow.com/q/28863328/287948"; the real problem is that `@attribute::self` does not exist, so it was a wrong hypothesis on the title of the question.

## The `help/mcve` solution has limitations

[Stack Overflow's `help/mcve` rationale](https://stackoverflow.com/help/mcve): "How to create a *M*inimal, *C*omplete, and *V*erifiable *E*xample", can be used to avoid the XY problem.

But the **cost of edit** (time and attention expensive), and the perception that it is a kind of pollution in your text (a "bad marketing" for the question), are downsides.

It's correct also to simplify the problem and explain with more focus on the point. 

------

## Best practice

Train users of Stack Overflow to check if the simplification makes sense. Algorithm for a good question:

 1. Try to create an MCVE. 

 2. If an MCVE is not practical, try at least to simplify.

	2.1.  Test, check for inconsistencies, simulate the reader&hellip; and review. Does your simplification produce something strange, change the context?  Review to avoid errors.

 3. **Listen** to the comments about your question, and try to clarify, try to **work** editing the question if necessary: if there are people commenting, it is a *notice* that you can **invest more time** in your question. 

The wrong hypothesis is not self-evident, but when we simplify, we amplify the wrong effects, and it becomes more evident.

---

PS: On the other hand, when we explain and show all the details, all the context, and check the real point, the assembly of the problem (like when using `mcve`), the inconsistencies also show with more evidence.

tips on writing great answers.

Draft saved

Draft discarded

Edit Summary*

Cancel

2
It's my experience that the the MCVE creates more XY problems not less. It makes a more pure abstraction by stripping away the context of the original question. That is the X might be contained within the context of the original question but the MCVE will be constructed solely to express Y.
Philip Couling
– Philip Couling
2015-11-11 23:57:31 +00:00
CommentedNov 11, 2015 at 23:57
2
Thanks @couling (!). Yes, as methodology MCVE perhaps is not a "best practice", but is a way to enforce "... explain and show all the details...". Our brain works better after that kind of self-review... You can edit and correct the text, it is a Wiki.
Peter Krauss
– Peter Krauss
2015-11-12 07:39:10 +00:00
CommentedNov 12, 2015 at 7:39

Add a comment |

How to Edit

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

How to Format

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or**bold**
indent code by 4 spaces
backtick escapes`like _so_`
quote by placing > at start of line
to make links (use https whenever possible)
<https://example.com>
[example](https://example.com)
<a href="https://example.com">example</a>

formatting help »
answering help »

How to Tag

A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.

complete the sentence:my question is about...
use tags that describe things or concepts that areessential, not incidental to your question
favor usingexisting popular tags
read the descriptions that appear below the tag

If your question is primarily about a topic for which you can't find a tag:

combine multiple words into single-words with hyphens (e.g.stack-overflow), up to a maximum of 35 characters
creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, thenask the community to create it for you

popular tags »