The principle applies to any medium in which information must be consumed at multiple resolutions. A well-designed dashboard permits both the glance that summarizes the state of the system and the drill-down that investigates specific anomalies. A well-written report provides both the executive summary and the underlying analysis. A well-designed API offers both the high-level interface and the detailed parameter documentation. In each case, the medium must allow the viewer to shift between readings without the cognitive cost of changing displays, losing context, or reassembling her understanding from scratch.
The iterative loop of AI-augmented building supports macro and micro reading through the accumulation of conversational context. Early iterations operate at the macro level — the builder evaluates overall structure and fundamental architecture. Later iterations operate at the micro level — specific interactions, individual animations, particular error messages. The transition is natural because the AI maintains the macro decisions as background constraints while the builder focuses attention on micro refinement. She does not need to re-specify the overall architecture when adjusting a single interaction, because the conversation holds the architecture stable.
The principle extends to the evaluation of AI output itself. A builder examining generated code can read it at the macro level — what is the overall architecture, what libraries does it use, what are the major data flows — and at the micro level — what does this specific function do, what are its edge cases, what happens if this input is malformed. A well-designed AI system supports both readings: it explains its macro choices when asked and makes its micro implementations inspectable when needed. An AI system that presents only final output, without either macro explanation or micro traceability, has denied the builder both readings and forced her to evaluate the product as an uninspectable whole.
The application to output interrogation is direct. The discipline of evaluating AI output includes asking macro questions (is the overall approach sound, does it match my intent) and micro questions (does this specific decision hold up under inspection). A builder who asks only macro questions will miss micro failures that propagate silently. A builder who asks only micro questions will miss macro failures in approach that no amount of local correctness can compensate for. The fluency of polished AI output tempts the builder toward macro reading only — the prose looks right, move on — and the discipline required is the return to micro inspection when stakes warrant it.
Tufte developed the macro-micro framework most extensively in Envisioning Information (1990), where it underlies his analysis of layered displays, dense information graphics, and the principle that rich displays serve viewers better than simplified summaries. The distinction reappears throughout his subsequent work and has become standard vocabulary in information-design curricula.
Two complementary readings. Macro for the overall pattern, micro for the specific detail. Neither is sufficient alone; the best displays support both.
Dense displays serve viewers. Contrary to the instinct to simplify, Tufte argues that information-dense displays serve viewers better than sparse ones because they permit both readings.
The iterative loop supports both. AI-augmented workflows naturally progress from macro to micro as conversational context accumulates and the builder shifts attention from architecture to detail.
Layered transparency for AI. A well-designed AI system exposes macro reasoning when asked and micro implementations when inspected, serving the builder's analytical task at the resolution she needs.
Output interrogation requires both. Evaluating AI output at macro and micro levels is the discipline that catches both approach failures and local failures, neither of which alone is sufficient to compensate for the other.