Skip to content
Writing Style Library

Comparison-Contrast

Places two or more options, ideas, or states side by side to illuminate the differences that matter.

Comparison-Contrast

Section titled “Comparison-Contrast”

Comparison-contrast is the style of the decision document and the analytical essay. Its power comes from the precision that side-by-side placement creates: similarities and differences emerge that would be invisible in a sequential treatment of each option. The reader comes away not just knowing both options but knowing the delta - which is usually what they needed.

Two structural approaches exist. Block structure presents everything about A, then everything about B - better for complex subjects where the reader needs to understand each option fully before comparing. Alternating structure moves back and forth between A and B on each dimension - better for focused comparisons where the points of contrast are the main event.

The risk of comparison-contrast is false balance: treating two things as equally deserving of parallel treatment when one is clearly better for the reader’s situation. The style is most honest when it selects dimensions of comparison that actually matter for the decision at hand, not every dimension on which the options differ.

Structural conventions

Section titled “Structural conventions”
  • Establishes the comparison frame early: “We are comparing X and Y on dimensions D1, D2, D3”
  • Either block structure (all of A, then all of B) or alternating structure (A vs B on D1, then D2, etc.)
  • A summary comparison (usually a table or verdict) resolves the structure
  • Dimensions of comparison selected for relevance, not exhaustiveness

When to use

Section titled “When to use”

Technology selection docs, ADRs, research reports, product comparisons, any decision involving multiple options.

When not to use

Section titled “When not to use”

Single-subject explanations, narrative writing, persuasive essays with a settled conclusion.

Pairs well with

Section titled “Pairs well with”

pragmatic-architect, matter-of-fact, candid, adr

Often confused with

Section titled “Often confused with”

classical-argument: Classical argument examines one position and defends it against objections. Comparison-contrast requires at least two subjects and measures relative differences without necessarily advocating for one.

problem-solution: Problem-solution names a pain and proposes a fix. Comparison-contrast evaluates options for a reader who is making a choice - the “problem” may already be understood.

Instruction

Section titled “Instruction”
Write using comparison-contrast structure. Establish the comparison frame early: name what you
are comparing and on which dimensions. Choose between block structure (all of A, then all of B)
or alternating structure (A vs B per dimension) based on complexity. Select dimensions that
matter for the decision at hand - do not compare on every axis, only the relevant ones. End with
a summary that resolves the structure: a table, a verdict, or a clear statement of the key
differentiator. Avoid false balance - if one option is clearly better for the stated situation,
say so.
Section titled “Related”

Pairs well with

Section titled “Pairs well with”

Pragmatic Architect, Matter of Fact, Candid, Architecture Decision Record

Avoid with

Section titled “Avoid with”

Devotional Reflection, Reverent, Pastoral

Often confused with

Section titled “Often confused with”

Classical Argument, Problem-Solution

Examples

Section titled “Examples”

We are comparing synchronous daily standups against async standup updates across four dimensions: participation equity, information persistence, blocker resolution speed, and team cohesion.

Participation equity

Synchronous: A fixed meeting time requires all participants to be available at the same moment. For distributed teams, this means someone is always accommodating an inconvenient hour. The cost is not shared equally - it accumulates on the people furthest from the meeting’s timezone anchor.

Async: Each participant posts on their own schedule within a defined window (typically “by 10am local time”). No one bears a timezone penalty. Part-time team members and contractors with flexible hours participate without negotiating a slot.

Information persistence

Synchronous: Information shared verbally in a meeting exists in the memory of whoever was present. A critical piece - “the auth service is throwing a 401 on the /validate endpoint” - survives only as long as the listener’s memory or their notes. It is not searchable. It does not reach engineers who were absent.

Async: Every update is a written record in a searchable channel. An engineer who joins the team three weeks later can read back through updates to understand what the team has been working on. Blockers and solutions are findable.

Blocker resolution speed

Synchronous: A blocker reaches the person who can resolve it only if that person attended the meeting and noted the item. Routing to the right person depends on the right person being present.

Async: A blocker can include a direct @mention of the person who can resolve it. The notification reaches them regardless of whether they would have attended a meeting.

Team cohesion

Synchronous: Shared presence at a defined moment creates a daily ritual of togetherness. The meeting’s social function - brief acknowledgment, casual connection - builds team fabric that is hard to replicate asynchronously.

Async: Updates are text on a screen. The social bonding that synchronous presence creates does not transfer. Teams that switch fully to async without a synchronous substitute often feel more fragmented over time.

Verdict: Async standups outperform synchronous on participation equity, information persistence, and blocker routing. They underperform on social cohesion. The practical answer for most distributed teams is async standup plus a weekly synchronous working session - not an either/or.