<\/p>\nEvery student who has wrestled with an IA knows the moment: you finish plotting your results, write a careful methods paragraph, and then\u2014somewhere in the discussion\u2014your writing becomes a catalog of observations. The graph looks like this. The peak is here. The sample increased. It\u2019s accurate and tidy, but it sits on the fence between trustworthy reporting and the kind of analysis that convinces an examiner you truly understand what you did, why it matters, and how it connects to the research question.<\/p>\n
This blog is a friendly, practical handbook for turning those tidy descriptions into sharp analysis. It\u2019s aimed at IB DP students across subjects who want to move from \u201cthis happened\u201d to \u201cthis matters because…\u201d, and to make sure their IA gives examiners the reasoning they\u2019re looking for. Expect concrete rewrites, checklists you can use at midnight before submission, and subject-specific notes that keep your work rigorous without becoming overcomplicated.<\/p>\n
<\/p>\n
Descriptive IA writing explains observations. Analytical IA writing interprets them. The difference is like the difference between taking a photograph and writing a critique of what that photograph shows about a larger subject. Description answers \u201cwhat\u201d; analysis answers \u201cso what?\u201d and \u201cwhy?\u201d.<\/p>\n
Examiners are not asking you to delete careful description\u2014clear reporting is essential. They are asking you to connect that reporting to reasoned interpretation, to show insight into methodology, uncertainty and significance.<\/p>\n
When you write or revise, read each paragraph and answer these three quick questions aloud (or in the margin). If the paragraph fails any question, rewrite it.<\/p>\n
Those three questions convert description into argument. They also align your wording. Instead of layering on extra sentences, aim to merge observation and interpretation: evidence followed immediately by its consequence.<\/p>\n
A structure that foregrounds analysis helps you avoid slip-back into description. Below is a compact order you can use and adapt to any subject.<\/p>\n
When you place interpretation right after data, you show examiners that you can read data actively. A list of numbers followed by an entire page of discussion often reads like a missed opportunity: it suggests your analysis was an afterthought. Short, focused \u201cresult + interpretation\u201d blocks keep the argument tight.<\/p>\n
Here are quick before\/after examples that show how small wording and structural changes create analysis rather than description.<\/p>\n
| Subject<\/th>\n | Descriptive phrasing<\/th>\n | Analytical phrasing<\/th>\n<\/tr>\n<\/thead>\n | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Biology<\/td>\n | “Species A increased in number after the treatment.”<\/td>\n | “Species A increased after treatment, which suggests the treatment reduced interspecific competition or altered habitat suitability; this supports the hypothesis that factor X drives local abundance.”<\/td>\n<\/tr>\n | ||||||||||||
| Chemistry<\/td>\n | “The colour changed from blue to green as reagent B was added.”<\/td>\n | “The colour shift from blue to green corresponds with complexation between ion Y and B, indicating ligand exchange; the observed shift supports a 1:2 stoichiometry under the experimental conditions.”<\/td>\n<\/tr>\n | ||||||||||||
| Economics<\/td>\n | “Prices rose after the policy was introduced.”<\/td>\n | “Prices rose following the policy, suggesting a short-run supply constraint and a probable demand shock; regression results indicate the effect is significant when controlled for seasonality.”<\/td>\n<\/tr>\n | ||||||||||||
| History\/Geography<\/td>\n | “Trade routes developed more quickly in Region X.”<\/td>\n | “Trade routes in Region X developed more rapidly, implying geographic advantages and institutional factors that reduced transaction costs; this accelerates urbanisation relative to neighbouring regions.”<\/td>\n<\/tr>\n | ||||||||||||
| Mathematics\/Computer Science<\/td>\n | “The algorithm runs faster on dataset B.”<\/td>\n | “Algorithmic runtime improves on dataset B, likely because data sparsity reduces average-case complexity; this suggests the chosen heuristic scales well for sparse inputs but may degrade with dense matrices.”<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\nHow to rewrite in practice<\/h3>\nPick any descriptive sentence in your draft and ask \u201cwhat does this prove?\u201d Then add one short sentence that connects it to your research question or theoretical framework. If you can\u2019t make a defensible connection, either remove the sentence or provide more evidence\/analysis.<\/p>\n Turn Methods and Limitations into Analytical Opportunities<\/h2>\nMany students treat methods and limitations as dry housekeeping. Instead, use them to show critical thinking. Examiners reward the student who recognises where the method constrains interpretation and who proposes how that creates uncertainty in the claims made.<\/p>\n
|
<\/p>\n