As-is vs to-be

Contrast current behavior with the operating shift you want.

consulting-exhibit

Related: Comparison (2–3 options) · Numbered process

When to use

Use when the change is a behavior, not a feature list. Do not use for three options (comparison). Do not use architecture boxes unless the shift is topological — then prefer as-is/to-be still in two columns of prose, or two architecture slides.

Guidelines

Two columns, same criteria implied. Title is the shift.

Example

Harbor operating shift

Stop reconciling clipboards at close; Harbor writes the ledger at scan.

As-is

Paper dock log. Nightly spreadsheet. Disputes hit finance at month end.

To-be

Scan is the ledger. Exceptions only. Finance sees the same object Ops sees.

If it is not a behavior change, it is not a to-be

Clipboard vs scan-as-ledger. Steal behavior contrast, not a capability matrix.

Rules

  1. Two columns only: as-is and to-be.
  2. Title states the behavior change.
  3. To-be is marked recommended.
  4. No third “in progress” column on this pattern.

User recipe

Pick family: Consulting exhibit first.

Insert objects:

Assemble:

  1. As-is describes current behavior
  2. To-be describes future behavior
  3. Mark to-be column as recommended
  4. No feature lists; behavior only

Anti-patterns