Design Methodology
How we think about design — and why that thinking shapes everything we build.
Design addresses wicked problems
Not all problems are created equal. Some have clean inputs, measurable constraints, and verifiable solutions. Design problems are different. They're underspecified, ill-constrained, and resist neat resolution. Solutions are good or bad, not true or false. Most importantly, a wicked problem can be explained in numerous ways — and the choice of explanation determines the nature of the resolution.
Data governance is a textbook wicked problem. Every organization's data flows are unique. A governance posture is evaluated qualitatively. And before you can solve it, you have to see it — the flows are encrypted, distributed, and largely invisible.
Qpoint's core value proposition is an act of design: giving a shapeless problem tangible form. Invisible flows become visible. A macro problem becomes addressable micro problems. Forming the problem is the problem.
Design is assemblage
There is a persistent myth that design is creation from nothing — the designer as magician. But designed things are composed of existing pieces. Every artifact is the combinatory or transformative result of existing forms and ideas. The designer is a builder of structures, not a mystical creator.
12 notes. 1,200 chords. Infinite compositions.
The brilliance isn't in which notes exist — it's in how they're composed. A limited number of elements produces infinite expressive range when the composer deeply understands the nature of the pieces.
The same holds for a design system. Components, tokens, and patterns are the vocabulary. The compositions — product interfaces, marketing pages, documentation — arise from how those pieces are arranged. The richer the vocabulary, the more expressive the work. But the expression comes from composition, not from invention of new primitives.
Decomposition and modularity
Large wicked problems can only be addressed through decomposition into smaller, modular sub-problems. Each module has two requirements: a functional purpose, and protocols for interfacing with the whole. Internal workings are independent — what matters is what the module does and how it connects.
Components as modules
Each has a functional purpose and interface points — props, slots, events. Internal implementation is encapsulated.
Composition over configuration
A button has an icon slot. It doesn't need to know what icon or where. The consuming project composes the behavior.
Innovation stays local
A component can be rebuilt internally without breaking consumers — as long as the interface holds.
A city planner doesn't need to understand the engine to plan a bus route. A page author doesn't need to understand focus trapping to use a modal. Simple, specific interfaces let multiple people — and agents — contribute to a coherent whole without holding the entire system in their heads.
The edge of chaos
The productive space is the boundary where a more than usual level of imagination meets a more than usual degree of order.
Without freedom, work stagnates. Without structure, independent efforts diverge. The right balance depends on the stage of the process and the scale of the problem.
Order and freedom aren't opposites — they're the two hands of effective design. The design system provides the connective tissue that lets both coexist.
Modes of innovation
Innovation doesn't arrive through a single repeatable process. It manifests through a repertoire of approaches, each suited to different moments.
Evolution
Small stepsGradual iterative improvement. Stable forms adapted to shifting requirements. Survival of the fittest mutations.
Cycle-based development — each cycle makes a focused improvement, tested in production.
Archaeology
Uncovering what's already thereStudying the evidence to find unique qualities already embedded in the problem space.
Pattern discovery — scanning projects to surface compositions that emerged organically from real use.
Formula
Codified rulesDesign principles encoded as repeatable structures. Means to an end, not ends in themselves.
Design tokens, type scale, grid system — rules that enable consistency until intentional departure.
Rebellion
Purposeful rejectionBreaking convention deliberately. Revolutionary work doesn't just revolt — it offers something in return.
Swiss-modern confidence where competitors lean on dark dashboards and threat imagery.
Alchemy
Stubborn experimentationCuriosity in unknown territory. The advantage of not being an expert is the freedom to try things specialists wouldn't.
Using AI agents to build an AI-aware design system — working at the boundary of what's understood.
Assemblage
Finding hidden connectionsComposing disparate ideas already present in the problem space into structures that illuminate new meaning.
The design system itself — combining tokens, components, and patterns into coherent experiences.
Forming the problem is the problem
The deepest principle: problem and solution are equivalent expressions. Every specification of the problem is a specification of the direction in which a treatment is considered. The act of giving a vague statement of need precise form is itself the creative work.
Product
Qpoint gives data governance its first tangible form. Before visibility, the problem is a vague feeling of exposure. After visibility, it's specific flows, classifications, and patterns that can be acted on. The product doesn't just solve the problem — it forms it.
Brand
Qpoint is defining a category that doesn't cleanly exist yet. The brand's job isn't just to describe what Qpoint does — it's to form the problem of data governance in the audience's mind. The way we explain the problem determines the shape of the solution they see.
Why this matters
These aren't abstract ideas. They're the operating principles behind concrete decisions.
Why composition over configuration?
Modularity is how complex systems stay manageable. Deep prop trees require the city planner to understand engine mechanics.
Why cycles instead of continuous development?
Structured phases with clear objectives create the right balance of freedom and order. Each cycle is a bounded space for innovation.
Why a constrained token palette?
Limitations sharpen composition. More expression comes from deeper understanding of fewer elements, not from an unlimited palette.
Why visibility before control?
Forming the problem is the problem. You can't address what you can't see, and seeing transforms a wicked problem into a workable one.
Why replicate first?
Understanding what exists is the first step. Premature optimization is premature problem formulation — it locks in assumptions before the problem is fully understood.