Sketch¶
Artifact — instantiates Rapid Prototype Learning Loop
A rough visual or spatial representation used to make a concept discussable and testable.
A sketch is the fastest possible externalization: a few rough marks that turn a vague intention into something concrete enough for a group to point at and argue about. Its defining move is that it works upstream of any test. A sketch does not measure how a design behaves; its job is to surface which assumption is even worth testing and to state that assumption as a claim the next, higher-fidelity artifact can probe. A sketch is a proposition, not a proof — deliberately ambiguous, disposable, and cheap enough that no one is attached to it. That is exactly what makes it good at separating the question "what are we really unsure about?" from the later question "does it work?"
Example¶
A landscape architect is proposing a redesign of a tired downtown transit plaza. Rather than commission a rendering, she stands at a whiteboard during the stakeholder meeting and draws three thumbnails in under two minutes: one keeps the fountain central, one cuts a diagonal desire-line path corner-to-corner, one wraps the edge in a market colonnade. The drawings are crude — boxes and arrows — but they make the real disagreement visible. The parks department worries the colonnade kills sightlines the police rely on; the retailers want foot traffic dragged past their storefronts; a transit planner points at the diagonal and asks whether anyone will actually use a paved path when they can just cut across the lawn.
That last question is the payoff. Nobody argues about the quality of the drawing; they argue about the idea. By the end of the meeting the group has named the riskiest assumption — that pedestrians will follow the diagonal instead of trampling a shortcut — and turned it into a stated hypothesis for the next prototype to test. The sketch settled nothing about the plaza. It decided what to find out.
How it works¶
The distinctive method is generation-and-framing, not testing:
- Externalize fast, in parallel. Produce several rival thumbnails cheaply so alternatives sit side by side and can be compared rather than defended one at a time.
- Use the mark as a shared object. The rough drawing pulls the disagreement out of people's heads and onto a surface everyone can annotate, which locates where the disagreement actually is — goal, sequence, layout, or a buried assumption.
- Extract, then hand off. The sketch's output is a prioritized risky assumption plus a testable hypothesis, which it passes to whatever artifact will run the real test. It closes no loop by itself.
Tuning parameters¶
- Number of alternatives — one sketch to refine a direction, or a spread of six to open the space; more options widen exploration but dilute depth on any one.
- Roughness level — rough enough to invite revision, but not so cryptic it gets misread; the sweet spot signals "unfinished, argue with me."
- Annotation vs. pure image — labels and arrows sharpen a claim but can smuggle in false precision; bare images stay open but risk divergent readings.
- Divergent vs. convergent — generating rival concepts vs. narrowing to one; the same tool serves both, but not in the same pass.
- Audience — a private thinking-sketch for the designer's own reasoning vs. a talking-sketch built to provoke a room.
When it helps, and when it misleads¶
Its strength is being the cheapest way to make a thought inspectable — and the only mechanism here whose entire value is choosing the question before anyone spends on answering it. Because the artifact is obviously disposable, criticism lands on the drawing rather than on the person, which makes disagreement safer and faster.
Its failure mode is that a sketch is not evidence, and a compelling sketch is dangerous precisely because it can be mistaken for a validated design — a nice drawing gets nodded through and quietly becomes the plan. The complementary error is over-reading an ambiguous mark as if it specified something it never claimed. The guarding discipline is to insist the sketch's only legitimate output is a question — a prioritized assumption and a hypothesis — never a verdict, and to force it to hand that question to a test artifact. This tracks Bill Buxton's distinction between sketching and prototyping: a sketch is meant to suggest and explore possibilities, not to confirm a chosen one.[1]
How it implements the components¶
A sketch fills only the loop's framing components — the ones that must be settled before any artifact can earn its fidelity:
risky_assumption— laying rival concepts side by side surfaces and prioritizes the uncertainty most worth spending a test on.design_hypothesis— it converts a fuzzy intention into a stated, testable claim that the next artifact will probe.
It does not implement prototype_fidelity or participant_or_stakeholder_sample — resolving a design's look at presentation fidelity and taking it to stakeholders is the Mockup's job, and a sketch deliberately stops below that fidelity. Nor does it capture a feedback_signal or reach a revision_decision from a user operating it — those belong to the Paper Prototype.
Related¶
- Instantiates: Rapid Prototype Learning Loop — the sketch supplies the framed assumption and hypothesis the rest of the loop tests.
- Sibling mechanisms: Mockup · Paper Prototype · Rough Physical Model · Clickable Prototype · Service Walkthrough · Small-Scale Pilot · Wizard-of-Oz Test
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: Sketch operates as a static representation, map, specification, schema, or prospective plan that externalizes information because it a rough visual or spatial representation used to make a concept discussable and testable.
Independent corroboration: The frozen evidence defines Sketch as 'A rough visual or spatial representation used to make a concept discussable and testable', so its operative form is Representation, Specification & Plan.
Nearest alternative: Communication, Facilitation & Learning — Sketch includes features of a designed message, facilitated interaction, ritual, or learning activity that changes shared understanding, but its defining operation is a static representation, map, specification, schema, or prospective plan that externalizes information.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Art & Aesthetics
Origin pattern: Convergent development
Present-day reach: Universal
Rationale: A rough visual representation used to externalize and explore an idea is foundational drawing and design practice.
Related originating lineages:
- Architecture & Urban Planning — Spatial sketches test massing and relation.
- Engineering & Design — Engineering sketches make mechanisms discussable before formal specification.
- Human-Computer Interaction — Interface sketches enable rapid critique of flows and layout.
Review resolution: The blind reviewers agree that art_aesthetics is the primary origin and differ only on alternate origin disagreement. I preserve every independently explained alternate from both records rather than imposing a numeric cap. I retain convergent because the combined evidence shows independent disciplinary development. The broader reach of universal records portability separately from historical provenance; encyclopedia_synthesis=false preserves the affirmative synthesis judgment where either reviewer identified one.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
The sketch is the only sibling that closes no loop on its own. It decides what to test and then hands off; if a sketch is ever treated as the answer rather than the question, the loop has been skipped, not run.
References¶
[1] In Sketching User Experiences (2007), interaction-design researcher Bill Buxton draws a working distinction between sketches and prototypes: a sketch is tentative, suggestive, and non-committal — made to propose and explore possibilities — whereas a prototype is made to test and refine a direction already chosen. registry ↩