To start your results section without the paralysis, stop thinking of it as "writing" and start thinking of it as translating. You aren't trying to compose a literary masterpiece or prove a grand theory right now; you are simply describing the patterns in your data so that someone else can see what you see. The results section is the most literal part of your paper. Its only job is to report the facts of your findings without interpreting what they mean or why they happened. If you can describe a photo to a friend over the phone, you can write a results section.
The Translation Model: Moving from Spreadsheet to Sentence
Marcus broke through when he stopped trying to write a paper and started writing a list of observations. He realized that every single chart or table in his Excel file was essentially a sentence waiting to happen. For example, he had a table showing that 40% of freshmen skipped at least one meal a week. Instead of trying to frame this within a sociological theory of class, he simply wrote: "Forty percent of freshman respondents reported skipping at least one meal per week." By treating the process as a translation—taking a data point and turning it into a plain English sentence—the blank screen disappeared. He wasn't "writing" anymore; he was just documenting.
This translation model works because it removes the pressure of performance. When you feel frozen, it's usually because you're worried about whether your findings are "significant" or if you're sounding "smart" enough for your professor. But the results section is the one place where you don't have to be a theorist. You just have to be a reporter. If your data shows that 10% of people answered "maybe," you report that 10% answered "maybe," even if that result feels boring or unexpected. The "smart" part happens later in the Discussion section, where you explain the implications of that 10%.
To apply this, you should look at your Excel sheet and identify the anchor points. An anchor point is any number, percentage, or quote that directly relates to your original research question. If your question was about how social media affects study habits, an anchor point is the average number of hours spent on TikTok per day. Once you have these points, you write one sentence for each. Don't worry about transitions or flow yet. Just get the facts onto the page. You can turn those disjointed sentences into a cohesive narrative later, but you can't polish a blank page.
Structuring the Narrative Flow
Once you have your translated sentences, you'll likely have a messy list of facts. The secret to organizing these into a professional sociology paper is to follow the hierarchy of importance. You don't report every single cell in your spreadsheet; you report the data that answers your research question, starting with the most general findings and moving toward the most specific ones. This prevents the reader from getting lost in a sea of numbers.
Imagine Sarah, a junior studying urban sociology who interviewed ten residents about gentrification. She had pages of transcripts and a spreadsheet of themes. She initially tried to write her results chronologically, reporting what each person said in the order she interviewed them. This resulted in a repetitive, rambling section that felt more like a diary than a research paper. Her professor pointed out that the reader doesn't care about the order of the interviews; the reader cares about the themes.
Sarah shifted her approach. She grouped her data by theme. First, she reported the general consensus on neighborhood change (the "big picture"). Then, she moved into specific disagreements among residents (the "nuance"). Finally, she included the most striking individual quotes to illustrate those points (the "evidence"). By organizing by theme rather than by source, Sarah transformed her raw data into a structured argument. She used the data to tell a story, but she kept the storytelling strictly factual.
For quantitative data, this means starting with descriptive statistics. Tell the reader who your sample was—the demographics—before you dive into the core findings. For example, if you're studying student stress, start by stating the average age, year in school, and major of your participants. This sets the stage. Then, move to your primary findings. If you found a correlation between sleep and GPA, report the correlation coefficient and the p-value clearly. Avoid using adjectives like "shocking" or "disappointing." Instead of saying "A shocking 60% of students failed the test," say "Sixty percent of students did not achieve a passing grade." The data should provide the impact; your adjectives shouldn't.
If you're struggling to decide what stays and what goes, use this decision framework to filter your data:
| Data Type | Keep it if... | Cut it if... |
|---|---|---|
| Demographics | It provides necessary context for the sample. | It's irrelevant to the research question (e.g., eye color). |
| Primary Findings | It directly answers your main hypothesis. | It's a "side quest" that distracts from the main point. |
| Unexpected Results | It contradicts your hypothesis in a meaningful way. | It's a statistical fluke with no clear pattern. |
| Quotes/Anecdotes | It perfectly illustrates a trend seen in the numbers. | It's redundant or doesn't represent a broader theme. |
The Final Polish and Common Pitfalls
The biggest mistake students make in their first results section is "leakage." Leakage happens when your analysis or opinion leaks into your reporting. You might be tempted to write, "The data shows that students are struggling, which suggests that the university's mental health resources are inadequate." That second half of the sentence is leakage. You haven't proven the resources are inadequate yet; you've only proven that students are struggling. In the results section, you stop at "students are struggling." Save the "why" and the "what this means" for the Discussion section.
Another common hurdle is the fear of "boring" results. Many students panic when their data doesn't support their hypothesis. They feel that a "null result"—finding no relationship between two variables—is a failure. In sociology, a null result is still a result. Reporting that "there was no statistically significant difference between the two groups" is a valid and important finding. It tells future researchers that this specific path might not be the key to the puzzle. Be honest with your data. If you try to massage the numbers to fit a narrative, an experienced professor will spot it immediately.
To ensure your section is clean, do a final pass specifically looking for "interpretation words." Search your document for words like suggests, indicates, proves, unfortunately, surprisingly, or interestingly. These words are markers of analysis. While a few might be okay to guide the reader, too many of them signal that you're analyzing rather than reporting. Strip them away. Let the numbers speak for themselves. If the number is 90%, the reader will find it "surprising" on their own; you don't need to tell them it is.
Finally, check your alignment between your tables and your text. A common error is mentioning a finding in a paragraph that isn't reflected in the accompanying table, or having a table that contains data you never mention in the text. Your text should act as a guided tour of your tables. You don't need to repeat every single number from a table in your paragraph—that's tedious. Instead, highlight the key takeaways from the table. Use phrases like "As shown in Table 1, the majority of respondents..." This creates a bridge between your raw data and your narrative.
If you're still feeling stuck, take this immediate action: open a new document and create three headings: Who participated, What happened, and What stood out. Under "Who participated," write three sentences about your demographics. Under "What happened," list five bullet points of your main findings. Under "What stood out," write three sentences about the most unexpected data points. You now have the skeleton of your results section. All you have to do is turn those bullets into full sentences and remove the headings. You've already started.