This page explains how I go about closing AfD discussions that are too complicated to determine a consensus from at first glance.

Basis

What follows is how I apply the following guidance for administrators closing deletion discussions:

Step 1: Discard irrelevant opinions

I first identify opinions that are not helpful for determining whether there is consensus about the relevant issues. The relevant issues are whether and how to apply Wikipedia's policies, guidelines, past precedents or usual practices to the question of whether to delete, keep, or otherwise proceed with the article - or whether to make an exception in the interest of the project's goals). Opinions that are unhelpful for that purpose include:

Such opinions are not further taken into account.

Step 2: Count heads

Then I count how many remaining opinions there are for each proposed outcome such as delete, keep, redirect or merge. This provides me with a first approximation of the outcome of the discussion.

Step 3: Weigh arguments

Next I identify the principal lines of argument advanced for each outcome, and classify them roughly as follows:

Step 4: Assess consensus

Then I determine whether rough consensus exists for any proposed outcome, taking into account the strength of arguments. As a rough guideline, if all arguments (that I have not discarded altogether) are about equal in weight, I will normally accept a majority of more than two-thirds as establishing rough community consensus for that particular outcome. But if one line of argument is particularly strong and the opposed arguments are particularly weak, I may consider that the strong argument represents community consensus even if it is put forth by as few as one-third of the discussion's participants, or fewer. This is because the prevailing argument is considered strong because it is based on a straightforward application of Wikipedia's policies and guidelines, which themselves are founded on a much broader community consensus than can be expected to emerge from any one AfD discussion.

Step 5: Attempt to reconcile outcomes

If no rough consensus is apparent after step 4, I check whether any of the proposed solutions have something in common for which there is consensus. For example, in a discussion about notability that is split roughly half in favor of deletion and half in favor of merging, both sides agree at least that there should not be a separate article about that topic. This I can implement with a closure to "redirect" the article to the proposed merge target. In this way, the normal editing process can then determine whether any content (and how much) should be merged from the redirected article's history.

If this process results in a rough consensus to do something, then I close the discussion accordingly. If not, the article is kept by default.