jamiemill

Techniques for defining the product's objects, relationships, states, and vocabulary independently of any interface — the most load-bearing layer

Framework orientation for Layers of Product Design — load this first; provides the context all other skills depend on

Techniques for mapping interaction structure and flow — places, affordances, edge cases, and failure paths — without committing to visual form

Techniques for connecting user opportunities to business outcomes and solution bets, and testing the riskiest assumptions cheaply

Techniques for auditing and deciding the surface against the layers below — vocabulary, object consistency, completeness, feedback, hierarchy, accessibility

Diagnostic audit across all seven layers — identifies the bottleneck layer and recommends where to focus

Techniques for mapping a domain's concepts, terminology conflicts, and bounded contexts — the raw material the conceptual model is built from

Techniques for eliciting and prioritising user needs, pains, and desires — the opportunities that feed product strategy

Techniques for planning user research and synthesising it into grounded, confidence-rated findings about what users actually do