One of the best things on the old MO page was the "How to Ask" link on the top. It is true that SE took the hint and added something like that to the previous FAQ (which is now retired), but the MO one was particularly great.

Of course most people that should read it don't, but it's a shame that we don't have it anymore.

Since the migration agreement specifies that it is possible to add small JS code to the footer (or header?), is it possible to hack this link back into existence using this?

This is important because the current "how to ask" page is hidden well within the help center, and its content is sad in comparison to the previous one.

• – Manishearth Jun 25 '13 at 11:19
• We do need some MO-specific advice there.. – David Roberts Jun 25 '13 at 23:43

# How to write a good MathOverflow question

Using MathOverflow should be an extension of the way you normally do mathematics, and the same rules you use to effectively solve problems can be used to make good MO questions. Just like solving problems, crafting good questions requires you to put in some effort!

• Ask a focused question that has a specific goal
• Be precise
• Break it down
• Consider different formulations of the question
• Provide background and motivation

## Ask a focused question that has a specific goal

It should be absolutely clear what constitutes an answer to your question. Here are some examples of vague and specific questions. For each one, ask yourself, "If I saw an answer to this question, could I confidently determine whether it tells the asker what she actually wants to know?"

• What can I deduce from X?
• What is known about the X conjecture?
• What are all the ways to do X?
• Tell me about elliptic curves.

Focused

• Does X imply Y?
• Is there an example of X such that Y?
• Is the X conjecture true in situation Y?
• Is there a way to do X other than Y (which I can't use because Z)?

Note that being specific does not mean plugging in specific numbers or otherwise making your problem look like an exercise in a book. It means asking a to-the-point question that has an answer.

## Be precise

Being precise means communicating the parameters of your question so that others know where to start answering it and know when they've given you a complete answer. Of course, the includes stating the hypotheses and goal of your problem. If you suspect that you're asking an elementary question outside of your field, you may also want to explain your background a bit. This makes it easier for the person answering your question to know what she can take for granted.

It is especially important for "soft" questions and "big list" questions to be precise. Otherwise they'll be boring and useless. "What are the best number theory books" is a bad question. Best for what? Assuming what background? A better version of the question might be "What are the best textbooks for an undergraduate number theory course?" or "After an undergraduate number theory course, what should I learn if I want to study elliptic curve cryptography?" These questions aren't great, but they make it clear what the starting point is and what the goal is.

Make sure it's clear exactly what your question is. It's extremely frustrating to read a long question which explains what the general problem is but doesn't contain an actual question. I usually resort to searching the body of the post for question marks, but it often doesn't help. After defining all your terms and motivating your question, consider visually distinguishing the final version of the question (see the formatting section).

Before asking your question, try to solve it. Search Google, Wikipedia, and nLab, check any references you can think of, and try to figure the problem out yourself (maybe even sleep on it). Doing so will help you break the problem down and understand it better. Even if you don't solve the problem, putting some work into it will often help you understand exactly what it is you're having trouble with, so you'll be able to ask a better question.

## Break it down

You may have a specific problem you're trying to solve, and you may have done your research, but the problem might be a monster. Even if it's not a monster, you'll probably benefit from trying to break the problem into smaller pieces and posting one or two of the pieces on MO. To modify a quotation of Pólya, "If there is a problem you can't solve, then there is an easier problem you can't solve: find it." You may worry that the the pieces are not interesting enough or are too specific to post on MathOverflow, but you shouldn't. It's much better to post a question that is too focused than to post a question that is too vague or too broad.

It's okay to ask several questions related to a project you're working on, but try to limit yourself to one or two per day. Rather than posting all the parts of your problem at the same time, work through them one at a time. After all, the solution to one part may completely change your plan for solving the problem.

## Consider different formulations of the question

Sometimes your question is boring, but you can often make it much more interesting by recontextualizing it.

## Provide background and motivation

Use your title to convey as much information about your question as possible. Since the tags already convey the general subject area of your question, the title should communicate the question itself as faithfully as possible. If necessary, leave out hypotheses in the title, and in the body of the question, explain why the question requires those hypotheses.

Don't be afraid to make your question title long. Titles are allowed to be anywhere from 15 to 250 characters long. 140 characters (the length of a tweet) takes up about two full lines on the home page, so try to keep it less than that. But 140 characters is a lot longer than you might think. Too many people restrict themselves to 20 character titles. They're trying not to waste your time by making you read a long title, but they end up wasting more of your time because you have to actually open the question to see if it's interesting to you.

The readability of your question can often be greatly improved if you learn to use formatting commands, especially if your question ends up being quite long. Here is an example that contains a few good uses of the formatting commands:

## Background/Motivation

A *doodad* is a thingumabob together with a sheaf of doohickies (which is usually called the *doo structure* on the doodad). A doodad is said to be *regular* if the sheaf of doohickies is regular. Intuitively, regularity makes a doodad "rigid" since information about the doo structure at a point can be translated into information about the doo structure at nearby points.

A *widgit* is a whatsit which is flat (in the sense that its Plotsky curvature is zero). Showing that a space has a widgit on it is extremely useful because the flatness allows you to apply Foobar's gadget construction to prove many useful results about the space.

----

Based on the above intuition, it is natural to ask if every doodad is a widgit. However, the answer is clearly no, since a widgit is always regular, but [some example] is a non-regular doodad, so it is clear that we must impose a regularity hypothesis.

> Is every regular doodad a widgit?

## Background/Motivation

A doodad is a thingumabob together with a sheaf of doohickies (which is usually called >the doo structure on the doodad). A doodad is said to be regular if the sheaf of >doohickies is regular. Intuitively, regularity makes a doodad "rigid" since information >about the doo structure at a point can be translated into information about the doo >structure at nearby points.

A widgit is a whatsit which is flat (in the sense that its Plotsky curvature is zero). >Showing that a space has a widgit on it is extremely useful because the flatness allows >you to apply Foobar's gadget construction to prove many useful results about the space.

Based on the above intuition, it is natural to ask if every doodad is a widgit. However, >the answer is clearly no, since a widgit is always regular, but [some example] is a >non-regular doodad, so it is clear that we must impose a regularity hypothesis.

Is every regular doodad a widgit?

Notice that the background/motivation is clearly labelled with a section header and clearly delimited by the horizontal rule, making it easy for experts to know what to skip or skim. The words being defined are italicized. After the nuances about why the question introduces some hypotheses, the precise final question is visually distinguished in a blockquote, making it easy to know exactly what constitutes an answer to the question.

## A final note

Not every piece of advice on this page may apply to your problem, and it may even occasionally happen that you can make your question better by violating some rule laid out on this page. As with any writing you do, it is important to know what the basic rules are. If you violate one of them, it should be a conscious choice and you should be doing it for a very good reason.

• Eric Raymond's How To Ask Questions The Smart Way is directed at people looking to post problems to computer software/hardware forums, but much of the advice applies to asking questions on MathOverflow as well.

• copied the page here for easier access. – Kaveh Jun 25 '13 at 19:14
• I've going to move this to a FAQ question. – Scott Morrison Sep 25 '13 at 10:20
• [Do your homework] and try to figure the problem out yourself (maybe even sleep on it). Suppose I came up with a very interesting question. I tried to solve it myself and slept on it before I ask about it here. After a few weeks, I could solve it at last. Is this what this site wants? – Makoto Kato Feb 9 '15 at 0:18

There is a version of this that is shown to people asking questions for the first time, just to make sure they see it. It's not, however, editable on a per-site basis. It was in the FAQ, but we found it helpful to present this and quite a bit more 'just in time' help to folks new to the engine.

I don't know if the technical limitations that prevented each site from maintaining its own copy of this still exist, that's something I need to find out. However, stuff that we show forcibly needs to be as succinct as possible. The help you have put together over time is outstanding, but it would have to be highly condensed to fit within the same constraints as the default.

What I recommend you do for now is just create a question here on meta asking how to ask, and link to it in comments when you see that a new user doesn't quite understand how the site works. Pointing them here to boot probably isn't a bad idea as well. I know that in an ideal world, everyone would do a bit of research on how the community works before posting a question, but some folks just don't .. well .. read.

An interesting exercise is to go incognito and ask a question as a brand new user - the SE 2.0 engine has a lot of additional guidance built into it when it comes to important first steps that users take.

I realize that MO has some unique circumstances when it comes to the types of questions it will accept, and how they need to be asked. What we might be able to do as a compromise is create a new help center page for you, which would be moderator editable, if you really feel that having it (and more prominent) would help. I'll let the mods chime in in comments under me, and look into the possibility.

Not tagging this with a status yet, but wanted to chime in.

• this would be really helpful if we could have some moderator editable text that is presented to a user asking their first question. Some fraction are just going to post nonsense whatever we say to them. Nevertheless I think it would be helpful to have a succinct paragraph emphasising that this is a site for research level questions, and that they have other options (i.e. MSE) if the question is not at this level. – Scott Morrison Sep 25 '13 at 10:20
• @ScottMorrison We're close to trying it on a couple of sites beyond SO, we want to see how effective it actually is. If it tests well, then we can probably make this happen for you – Tim Post Sep 25 '13 at 17:38