d_afting_the_esults_section:how_to_ensu_e_objectivity

IGNOU project writing the Analysis: How to Ensure Objectivity

Drafting the Results Section: How to Avoid Interpretation

The data analysis is complete, the output has been generated, and now you face the seemingly simple task of writing it up. However, this phase is a delicate balancing act. The primary purpose of the findings chapter is to factually describe what you found, not to discuss what it means. Including discussion here weakens the structural integrity of your dissertation. This article provides a comprehensive set of guidelines for composing a precise and academically toned results section that faithfully reports your data while scrupulously resisting the temptation to discuss it.

1. The Fundamental Distinction: Results vs. Discussion

Understanding the essential distinction between the Results chapter and the Discussion chapter is paramount. Think of it as a strict separation of powers.

The Results Chapter: This section is the “empirical evidence.” Its sole function is to present the data in a neutral manner. It answers the question: “What did you find?” The Discussion Chapter: This is where you explain the evidence. Its job is to discuss the implications of those results, connect them to the literature, and answer the “so what?”. It answers the question: “What do these findings mean?”

Blurring this line weakens both. The reader gets confused, unsure if they are reading a observation or your speculation about that fact.

2. Using Neutral and Precise Language

The tone of your writing is your most powerful tool for maintaining objectivity. Choose your verbs and phrases to state rather than to imply.

Use Neutral Reporting Verbs:

Instead of: “The results show that the intervention was amazing.” (Subjective) Use: “The results indicated a statistically significant improvement in scores.” (Neutral) Other strong choices: “demonstrated,” “revealed,” “exhibited,” “was observed,” “was found.”

Avoid Value Judgments:

Avoid Subjective Adjectives: Interesting.

Instead of: “A surprising negative correlation was found.” Use: “A negative correlation was found.”

Avoid Speculative Verbs: Points to (Save “suggests” for the Discussion chapter).

Instead of: “This finding suggests that the theory is correct.” Use: “This finding is consistent with the proposed theory.” or “This finding aligns with the predictions of Theory X.”

3. A Standardized Approach

To ensure consistency and neutrality, follow a repetitive structure for presenting each statistical test or qualitative theme.

State the Purpose: Remind the reader what you were testing. “To address the first hypothesis, an independent-samples t-test was conducted to compare the mean scores of Group A and Group B.” Report the Key Statistics: Objectively state the relevant results. “The results indicated a significant difference between the groups (t(58) = 3.67, p = .001).” Describe the Outcome: State what the statistic means in a simple, factual statement. “The mean score for Group A (M = 85.2, SD = 4.3) was significantly higher than the mean score for Group B (M = 76.5, SD = 5.1).” Direct to the Visual: Refer them to the accompanying table or figure. “See Table 1 for a summary of the group means and standard deviations.”

This formulaic approach keeps your writing on task and prevents you from adding extra interpretation.

4. Letting the Data Speak

Well-constructed tables and figures are the backbone of an objective results section. They present the data in its rawest state, allowing the reader to view the findings for themselves.

Tables are for exact values: Use them to present multiple data points (e.g., means, standard deviations, p-values, coefficients). Figures are for trends and comparisons: Use charts (e.g., bar charts, line graphs) to showcase relationships and differences between groups. Ensure visuals are self-explanatory: A good table or figure should have a descriptive caption and be interpretable with minimal reference to the text. This minimizes the need for you to over-explain the data in your writing.

5. Reporting All Findings

An truly scientific report includes all results, not just the expected ones. A result that fails to reject the null hypothesis is still a important finding.

Do not hide them: Including non-significant results is a sign of rigorous research and prevents a skewed understanding. Report them neutrally: Use the same factual language as you would for a significant result.

Example: “The analysis revealed no statistically significant difference in satisfaction scores between the two conditions (t(42) = 1.23, p = .225).”

6. Common Pitfalls to Avoid

Be on high alert for these frequent missteps that can sneak interpretation into your results section: (Image: https://freestocks.org/fs/wp-content/uploads/2017/02/manicurist_at_work-1024x683.jpg)

Apologizing for Results: “Unfortunately, the results were not significant.” (This implies a desired outcome, which is subjective). Speculating on Causes: “The lack of significance was probably due to the small sample size.” (Save this for the Discussion chapter on limitations). Using Emotional Language: “It was exciting to find that…” (This is unprofessional and subjective). Overusing “Clearly” or “Obviously”: If it were clear and obvious, you wouldn't have needed to run the test. Let the data stand on its own.

Final Thoughts

Writing a compelling results section requires disciplinary restraint. It is an exercise in rhetorical precision, where you step back and let your hard evidence take center stage. By using objective language, employing a consistent framework, using tables and figures, and including non-significant results, you construct a chapter that is credible and trustworthy. This creates a solid foundation of uninterpreted evidence upon which you can then, in the next chapter, construct a nuanced and compelling discussion of what those facts ultimately mean. The strength of your argument depends on this clear separation.

(Image: https://freestocks.org/fs/wp-content/uploads/2019/03/metal_tape_measure_tool_5-1024x683.jpg)


Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /home/mantis/www/dokuwiki/lib/plugins/authplain/auth.php on line 370