“What is” and “just like that” are concise ways to name something as it stands and to signal that a result or state arrived without a drawn-out explanation. In performance and design, they frame a baseline condition and an immediate, observable outcome. This evergreen explainer clarifies how these phrases function, when they help communication, and when more detail is needed to keep work precise, testable, and maintainable.
What ‘what is’ establishes
“What is” points to a current definition, state, or artifact. It anchors a statement in an observable or verifiable baseline, which is useful when alignment is needed across teams. It works well to surface assumptions, clarify scope, or frame constraints before diving into changes.
- Use it to name an existing interface, schema, or contract.
- Use it to surface implicit expectations about behavior or quality.
- Avoid using it as a shortcut that hides context needed for decisions.
Concrete uses of what is
- A product requirement: “What is delivered is a read-only view of orders for the analytics dashboard.”
- A performance baseline: “What is measured is median latency at the 95th percentile under normal load.”
- A design system token: “What is defined is the color scale used across components.”
Just like that in practice
“Just like that” describes an immediate, seemingly effortless transition or outcome. In systems and design, it can highlight speed and simplicity, but it can also mask complexity or undocumented dependencies. Use it when the how is intentionally opaque and trust is high; avoid it when reproducibility, debugging, or onboarding require clarity.
When just like that adds value
- Celebrating lightweight solutions that solve a narrow problem quickly.
- Describing user-perceived flow that feels seamless and frictionless.
When to be explicit instead
- When steps must be repeated reliably by others.
- When audit, compliance, or incident response needs traceability.
Comparing framing approaches
| Phrase | Best used for | When to prefer detail | |
|---|---|---|---|
| what is | Baseline definitions, current state, scope | Aligning stakeholders, documenting contracts, establishing metrics | |
| just like that | Describing fast, seamless outcomes | User experience storytelling, lightweight prototypes, trust contexts | Audits, debugging, onboarding, compliance |
Using the phrases in requirements and tests
Treat “what is” as a clear given and “just like that” as a prompt to ask whether the underlying steps are sufficiently understood. Explicit acceptance criteria and automated tests reduce ambiguity when speed is celebrated but reproducibility is required.
- Pair a “what is” statement with measurable conditions.
- Convert a “just like that” outcome into observable events when reliability matters.
When simplicity miscommunicates
If a “just like that” description hides important dependencies or trade-offs, replace it with a lightweight diagram, a checklist, or a short narrative of steps. Clarity at the boundary between teams often outweighs brevity.
Takeaways
- “What is” is a useful anchor for current definitions and measurable baselines.
- “Just like that” can capture delightful, seamless experiences but should prompt a check for hidden complexity.
- Use explicit artifacts when reproducibility, testing, or cross-team coordination are required.
By pairing succinct framing with the right supporting detail, teams can communicate efficiently while preserving the information needed to maintain and improve their systems over time.