Why Most Papers Have Structural Problems

When I review manuscripts for surgical journals, I can usually tell within the first two pages if the paper is going to be rejected. It is rarely because the science is fundamentally flawed. More often, the underlying problem is structural. The authors have confused the chronological order of their research with the logical order of a scientific argument.

As researchers, we spend months or years living in the timeline of our study. We conceive an idea, apply for ethics approval, collect data, run analyses, and finally interpret the results. When it comes time to write the manuscript, our instinct is to tell that story exactly as it happened. We write a diary of our research journey.

But a scientific paper is not a diary. The reviewer does not care about your journey. They care about your argument. They are evaluating a specific set of claims, and they need the information presented in an order that allows them to test the validity of those claims. If you force them to reconstruct your logic from a chronological narrative, you are going to lose them.

The Chronology Trap

The chronology trap is the most common structural mistake in academic writing. It happens when you organize your manuscript based on when things occurred rather than why they matter to the reader's understanding.

You see this frequently in the Introduction. Authors will start by explaining how their research group became interested in a topic, followed by a historical recap of previous studies in the order they were published. This might reflect how the authors learned about the field, but it forces the reader to wade through irrelevant history before finding the actual research gap.

You see it in the Methods section when authors describe their data collection process exactly as it unfolded. They might explain that they initially planned to collect variables A and B, but halfway through the study decided to add variable C. While true to life, this chronological detour dilutes the clarity of the study design.

The most damaging place the chronology trap appears is in the Results. Authors often present their findings in the exact order the statistical software spit them out, or the order in which the experiments were completed. This results in a disjointed narrative where a crucial primary outcome is buried between two minor secondary findings simply because it was analyzed second.

IMRaD is an Argumentative Framework, Not a Timeline

The IMRaD structure (Introduction, Methods, Results, and Discussion) is universally adopted for a reason. It is not an arbitrary set of headings; it is an argumentative framework designed to guide a skeptical reader through a logical progression of thought.

The Introduction: Establishing the Premise

The Introduction should not be a chronological literature review. Its sole purpose is to establish the logical necessity of your study. You are building a funnel: starting with what is known, identifying a specific unknown (the gap), and stating how your study fills that gap. The flow must be entirely logical. If a historical fact does not directly set up the research gap, it does not belong in the Introduction, no matter how much time you spent reading about it.

The Methods: Proving Validity

The Methods section is where you defend the validity of your approach. It should be organized conceptually, not chronologically. Group your methods by logical domains: study design and population, data collection, variables and definitions, and statistical analysis. It does not matter if you secured ethics approval before you finalized the definition of your primary outcome. In the paper, you must present the study population and setting first, because the reader needs to understand who is being studied before they can understand how they are being measured.

The Results: Building the Case

Results must be structured hierarchically based on importance to the core argument, not based on when the data was processed. You start with the baseline characteristics to prove that your sample is representative and your groups are comparable. Then, you immediately answer your primary research question. Only after the primary claim is established do you move on to secondary outcomes, subgroup analyses, or exploratory findings. If you discovered a fascinating secondary finding late in the analysis phase, it still belongs at the end of the Results section, not at the top.

The Discussion: Defending the Claim

The Discussion is where many authors fall back into summarizing their journey. They repeat the results in paragraph after paragraph. Instead, the Discussion must be a conceptual defense. You state your main finding, compare it logically (not chronologically) to existing literature, explain the mechanisms behind it, and critically evaluate the limitations of your approach.

How to Shift from Chronological to Logical Flow

Breaking the habit of chronological writing requires a deliberate shift in your workflow. Before you open a blank document, you need to map the logic of your argument.

Step 1: Define the Core Claims

Before writing, identify the three or four specific claims your paper is making. What exactly do you want the reader to believe when they finish reading? Write these claims down as single, declarative sentences. Everything in the manuscript must serve to introduce, prove, or defend these specific claims.

Step 2: Reverse Engineer the Results

Once you have your core claims, organize your tables and figures to support them directly. Table 1 is almost always baseline characteristics. Figure 1 or Table 2 must address Claim 1 (your primary outcome). If you have a piece of data that does not support any of your core claims, cut it. It might be interesting, and it might have taken you weeks to analyze, but if it does not serve the logical argument, it is just noise.

Step 3: Map Methods to Results

For every result you intend to present, there must be a corresponding method described. Conversely, if you describe a complex method but do not report a result for it, you are wasting the reader's time. Go through your draft and draw a line between every result and its specific method. If the logical link is broken, fix the structure.

A Clinical Example: When Timelines Confuse the Reader

Consider a pediatric surgery paper comparing two techniques for managing complex appendicitis. In a chronological draft, the authors might first describe the outcomes of patients treated in 2021 (Technique A), followed by the outcomes of patients treated in 2023 (Technique B), and then discuss the complications that occurred during the transition period.

The reader is forced to do mental gymnastics to compare the two techniques. The logical structure requires presenting the data conceptually. First, demonstrate that the patient populations in both periods were clinically comparable. Second, present the primary outcome (e.g., abscess rate) directly comparing Technique A to Technique B. Third, present the secondary outcomes (operative time, length of stay). The timeline of the study is irrelevant to the clinical comparison. The reader needs to evaluate the techniques side-by-side, not year-by-year.

The Takeaway

Reviewers and readers are inherently skeptical. They are reading your paper to find holes in your argument. If they have to constantly stop and re-orient themselves because your narrative is jumping around a timeline rather than following a logical progression, they will become frustrated. Frustrated reviewers look for reasons to reject.

Stop writing the story of your research journey. Start writing the defense of your research findings. When you align your manuscript with the logical needs of the reader rather than the chronological timeline of your work, your writing will immediately become clearer, more persuasive, and much closer to acceptance.

If you are struggling with the logical structure of your manuscript, my Prompt Pack: Paper Structuring can help you systematically outline your draft.