A low-fidelity visual layout of a screen
A wireframe is a deliberately plain layout of a screen: boxes, labels, and hierarchy with the colour, type, and polish stripped out. The point of the plainness is to force conversation about structure and content priority before anyone argues about a shade of blue. Its recurring failure is the opposite, a wireframe so detailed it gets mistaken for the finished design and signed off as one.
The word is borrowed from computer-aided design and 3D modelling, where a "wireframe" shows an object as line art, its edges visible as if built from wires, with no surfaces or shading. The visual idea of a structural skeleton without finish carried directly into screen design.
The term migrated to interface work in the early-to-mid 1990s as the web arrived. The precise coinage is disputed; one frequently cited account is Matthew Van Horn's recollection of separating page structure from look and feel at Snickelways Interactive around 1993-94, explicitly by analogy to the 3D wireframe model that shows shape without shading or texture. The honest reading is that the practice emerged across several studios at once as designers needed a cheap artefact to debate layout.
Thinking since has organised around fidelity. A low-fidelity wireframe is grey boxes and placeholder text, fast to draw and cheap to throw away. High-fidelity wireframes carry real content and accurate spacing, edging toward a mockup. The discipline's working principle is to keep fidelity low while the questions are about structure, and to raise it only once those questions are settled, because high fidelity invites feedback on aesthetics that the artefact was never meant to invite.
A team is designing a checkout. Before opening the visual design tool in earnest, a designer sketches six low-fidelity wireframes for the payment step in an afternoon: one with a single long form, one split across steps, one with an express path on top. In a thirty-minute review the team kills four. The two survivors raise a real question, whether to show the order summary inline or in a collapsible panel, which becomes a Design QuestionExperience DesignAn open design problem to exploreView reference → to resolve with a quick test. No pixels were polished, no engineer estimated anything, and the expensive disagreement surfaced while it was still cheap to change.design_question
prototypePrototypeExperience DesignAn interactive mockup for testingView reference → simulates screens, while a wireframe specifies one.In the Unified Product Graph, WireframeExperience DesignA low-fidelity structural layout is a leaf in the Experience Design domain of the Experience, Design & Brand region, sitting late in the creation sequence after journeys, screens, and flows are roughed in. Its key edge is wireframeWireframespecifiesScreencross-domain: a wireframe is a proposal pointed at a durable screen. It also carries wireframe_specifies_screenWireframespecifiesFeaturecross-domain, which crosses sideways into Product Delivery and lets a featureFeatureProduct SpecificationA product capability or featureView reference → trace to the sketch that first explored it. Inbound, a wireframe_specifies_featureDesign ConceptExperience DesignA possible design direction or approachView reference → reaches it through design_conceptDesign Conceptsketched inWireframehierarchy. That placement keeps the wireframe honest as a draft, connected to the screen it proposes and the concept it serves, never floating as decoration.design_concept_sketched_in_wireframe
Type-specific fields on BaseNode
fidelitystringDetail level
screen_namestringRepresented screen name
versionstringVersion or iteration (e.g. "v2", "2026-04-B")
toolstringAuthoring tool. @example "Figma", "Balsamiq", "pen and paper"
review_statusstringReview gate status
linked_prototype_urlstringURL of the corresponding interactive prototype
idstringrequiredUnique identifier (UUID)
typeNodeTyperequiredDiscriminator for the entity type
titlestringrequiredDisplay name
descriptionstringOptional detailed description
statusstringLifecycle status
tagsstring[]Freeform tags for filtering
4 phases — initial: draft · template: PUBLISHING
5 edge types connected to this entity.
product_sketched_in_wireframedesign_concept_sketched_in_wireframescreen_wireframed_as_wireframe1 framework use this entity type.