Data Insights Playbook: Five Formats, One Discipline

The section nobody prepped for in 2015

Data Insights is the newest face of the GMAT and a full third of your total score — 20 questions, 45 minutes, five distinct formats, and the only section with an on-screen calculator. It tests the most "day job" skill on the exam: making sound calls from messy, multi-format information — tables, charts, emails, claims that don't quite agree.

Five formats, one section. Learn each one's decision shape and the section stops feeling chaotic:

📊 Format	The task in one line	The skill being probed
Data Sufficiency (DS)	Decide if the data could answer the question — without answering it	Knowing when you know enough
Multi-Source Reasoning (MSR)	Reconcile several tabs (text, tables, charts) feeding 3+ questions	Synthesis & spotting disagreement
Table Analysis (TA)	Judge yes/no conditions against a sortable table	Precise condition-checking
Graphics Interpretation (GI)	Complete statements from a chart's actual content	Reading axes, units, trends honestly
Two-Part Analysis (TPA)	One scenario, two linked answers	Handling coupled constraints

Data Sufficiency: the format that punishes solving

DS gives a question plus two numbered statements; the five options are always the same ladder (statement 1 alone / 2 alone / together / either / neither). Three habits decide your DS accuracy:

1. Know what "sufficient" means for this stem. A value question needs exactly one possible value; a yes/no question needs a guaranteed yes or a guaranteed no — "always no" is sufficient. Most DS misses are really stem-misreads.
2. Quarantine the statements. Evaluate (1) with (2) erased from your mind, then (2) alone, only then together. Letting information leak between statements is the classic contamination error.
3. Hunt the hidden constraint. "x is positive", "n is an integer", "the figure is not to scale" — sufficiency usually turns on these. Test edge cases: zero, negatives, fractions, equal values.

And the meta-rule: stop at sufficiency. Computing the actual answer is paying for goods you already own — DS rewards the judgment, not the arithmetic.

Multi-Source Reasoning: read like an auditor

MSR hands you two or three labelled sources and asks several questions against them.

• 🗂️ First pass = map, don't memorize. Thirty seconds: what does each source contain (claims? definitions? numbers?) and in what units?
• Expect engineered friction: a figure in one tab and a percentage in another that almost match; a definition in the text that changes how a table column must be read. Questions live in those seams.
• For every question, identify which source(s) it needs before reasoning. Answering from the wrong tab — or from your own knowledge of the topic — is the designed failure mode. If the sources don't say it, it isn't true.

Table Analysis: condition-checking at speed

You get a spreadsheet-style table and statements to judge against a stated condition (true/false, yes/no, met/not met).

• Sort with intent — sorting by the column in the condition usually turns scanning into a glance.
• Quantifiers are the trap: every, any, at least, median, only. One counter-example settles an "every"; one example settles an "any". Check exactly what the condition requires — no more.

Graphics Interpretation: the axes are the question

A chart plus statements to complete from a dropdown (in our practice bank: as multiple choice).

• 📏 Read the furniture first: axis labels, units, scale (linear? does it start at zero?), legend. Most GI errors are committed before any "thinking" happens.
• Cross-check units in the text vs units in the graphic — a mismatch is rarely accidental.
• Read all dropdown options before choosing; they reveal what precision the question wants (a trend? a ratio? a specific value?). Pick what the data supports, not what it suggests.

Two-Part Analysis: one scenario, two blanks

TPA presents a scenario and asks for two answers that may be independent (two separate mini-questions) or coupled (a pair that must satisfy a relationship — budgets that sum, rates that meet, trade-offs that balance).

• Diagnose the coupling first; coupled parts usually mean solving one constraint system, not two questions.
• Remember the same value can fill both blanks — candidates often un-pick a correct pair because it "looks wrong".

Section-wide tactics

• 🧮 The calculator is a precision tool, not a strategy. It exists here (and only here) — use it for ugly division, never for arithmetic a glance could estimate. Calculator-dependence is the quiet pacing killer of this section.
• ⏱️ 2:15 per question, but think in sets: an MSR block is one reading investment amortized over several questions — protect that investment by mapping sources properly the first time.
• The universal DI error is importing outside knowledge. The sources are the entire universe. Answer from them alone.

Drill each format separately in the question bank until its decision shape is automatic — then mix them under time in mocks, because format-switching is itself the skill the section tests.