Structuring the discussion section of my MBA manuscript to avoid just repeating the results, is there a logical flow?
My strategy consultant professor keeps marking me down for 'reiterating data' instead of synthesizing insights in my final journal draft. I’ve tried grouping my findings by hypothesis, but the argument feels disjointed and lacks that high-level executive narrative. I’m struggling to bridge the gap between the raw analysis and the broader strategic implications the rubric demands.
1 Answer
The most effective way to break the cycle of repeating your results is to shift your focus from what the data says to what the data means for a decision-maker. Instead of organizing your discussion by hypothesis, try structuring it around the strategic questions your research answers. Think of your results as the evidence you’ve gathered, but your discussion as the executive briefing that explains why that evidence matters for a firm’s competitive advantage or operational efficiency. You should start each paragraph with a thematic claim—a high-level insight—and then use the data only as a brief, secondary reference to support that claim. If you find yourself listing numbers or describing trends without connecting them to a broader business context, you’re likely still stuck in the reporting phase rather than the synthesis phase. A common trap is assuming that the reader needs a refresher on the findings before you can interpret them, but in a professional manuscript, your audience already trusts your analysis. They are looking for the "so what?" factor. For instance, imagine you’re analyzing a supply chain disruption; don’t just write that "delivery times increased by fifteen percent," which is a restatement of your results. Instead, frame it as a strategic vulnerability: "The fifteen percent increase in delivery latency reveals a critical dependency on single-source logistics that undermines the firm’s agility in volatile markets." By leading with the strategic implication, you force yourself to analyze the trade-offs, such as the cost of diversifying suppliers versus the risk of future delays. This approach transforms your writing from a dry summary into a persuasive narrative that speaks directly to the strategic challenges a consultant would face in the field. The nuance here lies in balancing your original hypotheses with the unexpected realities you uncovered. It’s perfectly fine if your discussion doesn't mirror the exact order of your results section; in fact, it’s often better if it doesn't. Group your insights by their impact on strategy, such as organizational culture, market positioning, or financial sustainability. If a specific finding doesn't directly contribute to a strategic recommendation or a broader theoretical understanding, consider whether it belongs in the discussion at all. You’re building a case, not just summarizing a spreadsheet, so feel free to weave together multiple findings if they point toward the same overarching conclusion. This creates a cohesive "executive narrative" that feels purposeful rather than disjointed. Ultimately, your goal is to move the reader from the "what" to the "what now." If you can clearly articulate how your findings challenge existing business models or provide a roadmap for future strategic shifts, you’ll naturally stop repeating the data and start delivering the high-level synthesis your professor is looking for. Keep your focus on the implications for stakeholders and you will find that the argument flows much more logically.
Have a similar question?
Ask the community →