<\/p>\n
Why ‘Too Descriptive’ Happens (and why that is fixable)<\/h2>\n
The problem usually doesn’t come from a lack of knowledge. Often it stems from one or more of these predictable places: misreading the assessment focus, playing it safe by repeating data, confusing description with interpretation, or simply writing under time pressure so the temptation is to report rather than reflect. Understanding the why helps you choose the right fixes.<\/p>\n
Common causes<\/h3>\n\n- Misplaced emphasis: assuming the assessor wants exhaustive detail rather than selective analysis.<\/li>\n
- Fear of being wrong: students sometimes avoid interpretation to sidestep being criticized for an unexpected claim.<\/li>\n
- Structure confusion: results are narrated in sequence without linking them to the research question or theory.<\/li>\n
- Weak evaluation: limitations, uncertainties, and alternative explanations are mentioned briefly \u2014 if at all.<\/li>\n<\/ul>\n
One helpful mindset shift is to treat the IA like an argument, not a diary. Description is necessary evidence; analysis is the argument that makes the evidence matter. Your task in editing is to show how each piece of description supports, complicates, or challenges your central claim or research question.<\/p>\n
How examiners distinguish ‘description’ from ‘analysis’<\/h2>\n
Examiners look for reasoning. Description answers the question ‘What happened?’ Analysis answers ‘Why does it matter?’ and ‘What does it show about the research question?’ Below is a quick comparison to help you recognize which mode your writing is currently in.<\/p>\n
\n\n\nCharacteristic<\/th>\n Descriptive Example<\/th>\n Analytical Rewrite<\/th>\n Assessment Focus<\/th>\n<\/tr>\n<\/thead>\n \n\nReporting results<\/td>\n “The temperature rose from 20\u00b0C to 30\u00b0C over five minutes.”<\/td>\n “The 10\u00b0C increase suggests a rapid heat transfer rate, which supports the hypothesis that material A has low thermal resistance under these conditions.”<\/td>\n Interpreting results in relation to the research question<\/td>\n<\/tr>\n \nExplaining methods<\/td>\n “We measured pH with a digital probe and recorded values every minute.”<\/td>\n “Using a digital probe minimized subjective reading errors and allowed detection of transient pH shifts, strengthening the reliability of the observed trend.”<\/td>\n Justifying methodological choices and reliability<\/td>\n<\/tr>\n \nContext<\/td>\n “Experiment X used solution Y as described in the lab manual.”<\/td>\n “Solution Y was chosen because its buffering capacity isolates the variable of interest; however, this choice also narrows the ecological validity of the findings.”<\/td>\n Balancing strengths and limitations<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\nQuick signals your IA is too descriptive<\/h3>\n\n- Long paragraphs of ‘what I did’ with no sentence connecting those actions to the research question.<\/li>\n
- Graphs without interpretation: numbers are listed but not related back to theory or predictions.<\/li>\n
- Conclusions that simply restate results instead of weighing implications or limitations.<\/li>\n<\/ul>\n
Concrete editing steps: sentence-level moves that create analysis<\/h2>\n
Editing a descriptive IA is like sculpting: you remove, reshape, and reattach so the form becomes clear. Below are practical edits you can make line by line. Work through them with a printed copy or in ‘suggesting’ mode so you preserve the original \u2014 that makes it easier to see progress.<\/p>\n
1. Re-anchor every paragraph to the research question<\/h3>\n
Start each paragraph with a one-sentence signpost that explicitly links the content to the research question. This tiny move converts description into argument by making purpose visible.<\/p>\n
\n- Before: “We recorded the charges at 0, 10 and 20 minutes and plotted them.”<\/li>\n
- After: “To test whether charging rate declines over time, we recorded the charge at 0, 10 and 20 minutes and plotted them to compare the observed curvature with the exponential decay predicted by the model.”<\/li>\n<\/ul>\n
That added clause (‘to test whether…’) forces you to interpret the plotted shape, not just present it.<\/p>\n
2. Ask ‘so what?’ after every key result<\/h3>\n
One sentence after a result should explain significance. Write it, then sharpen it. Don\u2019t be satisfied with obvious statements like ‘this increased’ \u2014 say what that increase implies about mechanism, validity, or broader patterns.<\/p>\n
\n- Template: ‘This suggests that… because…’ <\/li>\n
- Template: ‘An alternative explanation is…; this is less likely because…’<\/li>\n<\/ul>\n
Using these templates turns data points into contributions to your argument.<\/p>\n
3. Replace lists of observations with comparative analysis<\/h3>\n
If you have three conditions or groups, stop describing them in sequence and start comparing them directly. Comparative language\u2014’compared with’, ‘in contrast to’, ‘more likely when’\u2014forces interpretation.<\/p>\n
\n- Before: “Group A had higher values. Group B had intermediate values. Group C had lower values.”<\/li>\n
- After: “Group A\u2019s higher values, compared with Group B and C, indicate a treatment effect that is consistent with mechanism X; the absence of a similar pattern in Group C suggests Y.”<\/li>\n<\/ul>\n
4. Weigh evidence: highlight uncertainty and limitations<\/h3>\n
Good analysis includes calibrated language about confidence. Explicitly connect limitations to how they affect interpretation: not just ‘the sample is small’, but ‘the small sample reduces the power to detect differences and therefore our apparent null result may reflect Type II error rather than absence of effect.’ That signals critical thinking.<\/p>\n
5. Bring theory and prediction into the discussion<\/h3>\n
Even brief links to theoretical expectations or literature make your IA analytical. Say how your result aligns with or departs from predicted behavior, and suggest why. Using phrases like ‘consistent with’, ‘contrary to’, and ‘suggests a revision of’ helps you position your work within a broader knowledge conversation.<\/p>\n
Before-and-after mini examples (science, maths, and humanities)<\/h2>\n
Concrete examples are the fastest way to learn. Below are short before\/after rewrites you can adapt to your subject.<\/p>\n
\n- Science before: “The absorbance increased by 0.2 units at 10 minutes and 0.4 at 20 minutes.”<\/li>\n
- Science after: “The increasing absorbance over time indicates a progressive accumulation of product; the near-doubling between 10 and 20 minutes is consistent with first-order kinetics, which supports the proposed reaction mechanism.”<\/li>\n
- Maths before: “The function\u2019s graph shows a steep slope up to x=3 and then levels off.”<\/li>\n
- Maths after: “The steep initial slope followed by leveling suggests a saturation effect; fitting a logistic model could quantify the asymptote and provide a better explanatory fit than a linear model.”<\/li>\n
- Humanities before: “The character reacts angrily in scene two and quietly in scene three.”<\/li>\n
- Humanities after: “The shift from anger to quiet indicates a change in power dynamics: the silence in scene three constrains the character\u2019s agency and reframes earlier assertiveness as performative rather than stable.”<\/li>\n<\/ul>\n
Editing tools: short phrases that add analysis<\/h2>\n
Keep a handy list of analytical phrases to drop into your draft. Use them sparingly and always follow with a reason or evidence.<\/p>\n
\n- ‘This indicates that…’<\/li>\n
- ‘One plausible explanation is…’<\/li>\n
- ‘This pattern suggests a relationship between…’<\/li>\n
- ‘An alternative interpretation is…’<\/li>\n
- ‘This limits the generalizability because…’<\/li>\n<\/ul>\n
Using TOK and EE thinking to deepen evaluation<\/h2>\n
The Theory of Knowledge and Extended Essay approaches are surprisingly useful when you\u2019re trying to push beyond description. TOK encourages you to question assumptions, consider knowledge frameworks, and weigh evidence differently \u2014 for example, asking whether your methods privilege certain ways of knowing. The EE mindset emphasizes sustained argument and literature engagement; borrow EE habits like triangulating sources and explicitly situating findings within a research conversation.<\/p>\n
When you include a short TOK-style reflection \u2014 for example, ‘This result depends on how we measured X, and so our knowledge claim is shaped by that method’ \u2014 you demonstrate awareness of the limits of knowledge, which many assessors reward.<\/p>\n
<\/p>\n
Checklist: what to do in the last 24\u201372 hours<\/h2>\n
Use this checklist as a sequence. Don\u2019t try to do everything at once; work section by section.<\/p>\n
\n- Read your research question aloud. Is every paragraph answering it in some way?<\/li>\n
- Highlight pure description and convert at least half of those sentences into interpretation.<\/li>\n
- For each figure\/table, write one sentence that explains its significance for the research question.<\/li>\n
- Add a short paragraph on limitations that links each limitation to how it affects your claims.<\/li>\n
- Polish your conclusion so it weighs evidence and offers a justified answer, not just a summary.<\/li>\n<\/ul>\n
Useful quick-reference table: ‘Too descriptive’ to ‘Analytical’ fixes<\/h2>\n
One helpful mindset shift is to treat the IA like an argument, not a diary. Description is necessary evidence; analysis is the argument that makes the evidence matter. Your task in editing is to show how each piece of description supports, complicates, or challenges your central claim or research question.<\/p>\n
How examiners distinguish ‘description’ from ‘analysis’<\/h2>\n
Examiners look for reasoning. Description answers the question ‘What happened?’ Analysis answers ‘Why does it matter?’ and ‘What does it show about the research question?’ Below is a quick comparison to help you recognize which mode your writing is currently in.<\/p>\n
| Characteristic<\/th>\n | Descriptive Example<\/th>\n | Analytical Rewrite<\/th>\n | Assessment Focus<\/th>\n<\/tr>\n<\/thead>\n |
|---|---|---|---|
| Reporting results<\/td>\n | “The temperature rose from 20\u00b0C to 30\u00b0C over five minutes.”<\/td>\n | “The 10\u00b0C increase suggests a rapid heat transfer rate, which supports the hypothesis that material A has low thermal resistance under these conditions.”<\/td>\n | Interpreting results in relation to the research question<\/td>\n<\/tr>\n |
| Explaining methods<\/td>\n | “We measured pH with a digital probe and recorded values every minute.”<\/td>\n | “Using a digital probe minimized subjective reading errors and allowed detection of transient pH shifts, strengthening the reliability of the observed trend.”<\/td>\n | Justifying methodological choices and reliability<\/td>\n<\/tr>\n |
| Context<\/td>\n | “Experiment X used solution Y as described in the lab manual.”<\/td>\n | “Solution Y was chosen because its buffering capacity isolates the variable of interest; however, this choice also narrows the ecological validity of the findings.”<\/td>\n | Balancing strengths and limitations<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\nQuick signals your IA is too descriptive<\/h3>\nConcrete editing steps: sentence-level moves that create analysis<\/h2>\nEditing a descriptive IA is like sculpting: you remove, reshape, and reattach so the form becomes clear. Below are practical edits you can make line by line. Work through them with a printed copy or in ‘suggesting’ mode so you preserve the original \u2014 that makes it easier to see progress.<\/p>\n 1. Re-anchor every paragraph to the research question<\/h3>\nStart each paragraph with a one-sentence signpost that explicitly links the content to the research question. This tiny move converts description into argument by making purpose visible.<\/p>\n
|