← All sessionsHomeSearch
LWP Design Module 1·Chapter 2: Why we struggle so much·0:42:40

Chapter 2: Why We Struggle — Style Follows Function, and Assumptions Are the Enemy

Reno Instructor — Living With Pixels. Makes students feel the pain of unstructured design (decision fatigue, feedback spirals, ghosted projects) before prescribing the cure: the four-phase workflow previewed at the chapter's close.
▶local recording  ·  LMS lesson

Session map

THE PAINTHE PRINCIPLETHE CUREThe problem inventorywhat unstructured design actually costsStyle follows functionthe cars-and-architecture proofThe architect role-play and t…Watch out with assumptionsone dentist, three correct websitesThe cure, previewedDiscovery, Sitemap, Visual Direction, V…
The painThe principleThe cure
click a node — its card pops up (drag it anywhere, × to close)
Concept

The map reads left to right — the pain flow into the principle, then into the cure. Click any node to open that idea here; every timestamp jumps into the recording.

The short version

  1. The problem inventory, named honestly: not knowing where to start, decision fatigue, template-copying, endless feedback rounds, and clients going silent — 'projects bleed to death' — plus the four self-protective stories designers tell instead of fixing it (blame the client, race to the bottom on price, turn arrogant, blame the tools).
  2. The principle imported from two other industries: STYLE FOLLOWS FUNCTION. Car design evolved shape from aerodynamics; architecture coined 'form follows function' — and the failures are vivid when reversed: floating staircases unsafe for kids, open-air Bali bathrooms full of mosquitoes, flat roofs in Dutch rain, family sedans wearing racing wings.
  3. The empathy flip: imagine hiring an architect for YOUR dream house who doesn't ask questions and gets defensive at feedback — 'only amateurs start designing, or even worse start building, without having enough answers. It's the designer's job to ask the right questions.'
  4. Three painful truths along the way: it's not just the client's fault; clients don't care about your portfolio (keep 5-10 pieces; 'good exposure' is a manipulation flag); and not every project needs to excite you.
  5. The anti-template lesson: one dentist, three completely different correct websites (growth-hungry → conversion sections; overbooked → FAQ + treatments archive; retiring in 5 years → story-driven site for a business buyer, NO call-to-action). 'You are probably making assumptions too quickly.'
  6. The chapter lands on the cure: the 4-phase workflow — Discovery → Sitemap → Visual Direction → Visual Design. 'There's no magical process to design, but there is a wrong order.'

The concepts

01

The problem inventory: what unstructured design actually costs

'If we don't know where to start, then we're probably not gonna do anything' — the blank-canvas freeze, named as the field's first tax.

Six concrete pains: blank-canvas paralysis, inspiration drought, decision fatigue, template-copying as coping, feedback rounds that repeat '5, 10 times,' and the quiet death — clients who stop replying after the design lands. Then the harder half: the coping NARRATIVES. Blaming clients; underpricing ('a race to the bottom that you will never win'); the viral Instagram-skit arrogance he explicitly rejects ('this kind of talk, in my opinion, is very wrong'); and blaming tool complexity. The chapter's Jung callback closes the loop: 'sometimes our biggest obstacle isn't external. It is internal.'

Worked example · from the session

The sarcastic client-shaming Instagram exchange — shown as a NEGATIVE example, the arrogance coping pattern given a face.

Why it matters

The workflow chapters only motivate if these pains feel personal first — this is the before picture.

People get this wrong

Difficult clients are the main reason design projects go badly.

The narratives (blame, underpricing, arrogance, tool-blame) are symptoms; the disease is the absence of process — which is the designer's to fix.

I honestly think that this is just a race to the bottom that you will never win.
For your projects

['The four coping narratives map to agency life generally — worth keeping as a self-audit when a project sours.']

Go deeper

In one line: Unstructured design fails in six repeatable ways (start-paralysis, inspiration drought, decision fatigue, template-coping, feedback spirals, project ghosting), and designers metabolize the failure through four self-protective narratives instead of process change.

The six pains catalogued in one pass (l1427457 0:00:00)

'A race to the bottom that you will never win' — the pricing narrative (l1427457 0:02:02)

The arrogance skit rejected on the record (l1427457 0:06:04)

'Our biggest obstacle isn't external' — the internal-blame reframe (l1427457 0:08:06)

▶ Watch this taught:

Check yourself

Answer from memory first — the recall attempt is what makes it stick. Then reveal.

Which of the six pains does an agreement-round system (next chapter) directly kill?

Feedback spirals and project ghosting — capped, documented approval gates end both the endless revisions and the silent stall.

02

Style follows function: the cars-and-architecture proof

A floating staircase is gorgeous — until a toddler lives in the house.

The principle arrives from outside web design so it can't be argued with. CARS: early boxes → streamlined racers → the modern Porsche silhouette, every curve a function (aerodynamics, rear engine) that became a style. ARCHITECTURE: 'form follows function' — and three vivid reversals: the open floating staircase (unsafe for small children), the open-air Bali bathroom (mosquitoes, splash, heat — he's in Bali as he records), flat roofs in Dutch/English rain (fine in Spain and California). The kicker image: family sedans wearing sport-car wings — 'awkward designs' born of choosing the look before the job. 'A pretty design is not always practical... functional design always comes first.'

Worked example · from the session

The climate test: the SAME flat roof is good design in Spain and bad design in the Netherlands — function is contextual, so style can never lead.

Why it matters

This is the chapter's load-bearing principle: every workflow phase in Chapter 3 exists to establish function (goal, structure) before style is allowed in.

People get this wrong

Good taste protects you from bad design.

Taste chose the floating staircase. Only function analysis catches the toddler. Aesthetics can't detect functional failure — process can.

Style follows function Function the job, user, context Form the shape it takes Style what people admire Reversed: floating staircase + toddler · open-air bathroom + mosquitoes · flat roof + Dutch rain the failures only show up in CONTEXT Cars and architecture prove it before web design applies it - 'a pretty design is not always practical'
Function first, style second - the failures happen when the order flips
Style follows function... in architecture they have a quote called form follows function. It's the same.
A pretty design is not always practical.
For your projects

["This is the design-side twin of your architecture reviews: stack choices are 'style' too, and the failures also show up only in context."]

Go deeper

In one line: Function (the job, the user, the context) determines form; style is the visible residue of functional decisions. Reversing the order produces designs that look right and work wrong — and the failure is often invisible until context (kids, rain, mosquitoes) reveals it.

'Style follows function... in architecture they call it form follows function. It's the same.' (l1427458 0:04:04)

Three architecture reversals: staircase, outdoor bathroom, flat roof (l1427458 0:04:04)

'A pretty design is not always practical' (l1427458 0:06:04)

'Don't start with the end result... functional design always comes first' (l1427458 0:08:05)

Try it now

Pick any site you admire and name the function behind three of its stylistic choices — if you can't, you're admiring the wing, not the car.

▶ Watch this taught:

Check yourself

Answer from memory first — the recall attempt is what makes it stick. Then reveal.

A client wants their site to look like a famous brand's. What's the function-first response?

Ask what job THAT design does for THAT brand's users, then ask whether your client's users share the job. The style is only portable if the function is.

03

The architect role-play and the three painful truths

You finally have the money for your dream house — and the architect doesn't ask what you want in it.

The empathy flip: students play CLIENT for ten minutes. The architect who under-asks, delivers the wrong design, and defends it against feedback is unbearable — and is also, uncomfortably, most freelance designers. 'Only amateurs start designing, or even worse start building, without having enough answers. It's the designer's job to ask the right questions.'

Then the three truths. (1) It's not just the client's fault — though sometimes the client IS wrong; responsibility for extraction sits with the professional. (2) 'Clients don't really care about your portfolio' — and 'this will be good exposure' is a manipulation flag; keep a working portfolio of 5-10 pieces and stop optimizing for it. (3) Not every project needs to be exciting or on-brand for you — boring, well-run projects are the business. The closer is the discipline argument: Figma's free experimentation (unlike a car maker's million-dollar prototypes) is exactly why designers need self-imposed process — the tool won't impose it for you.

Worked example · from the session

The manipulation flag in the wild: 'exposure' offered as payment correlates with clients who will also skip the discovery questions.

Why it matters

It converts the function principle into professional posture: asking is the job; the deliverable is downstream of the questions.

People get this wrong

A bigger portfolio wins more clients.

Clients buy outcomes for THEIR business; 5-10 relevant pieces close as well as fifty — portfolio-building is designer ego spend, and 'exposure' offers monetize it.

Only amateurs start designing or even worse start building without having enough answers.
You're not being paid to add a cool item to your portfolio.
For your projects

['Truth #2 doubles as agency advice: your case-study page needs depth on 5, not breadth on 50.']

Go deeper

In one line: Professionalism = question-asking discipline plus three accepted truths: extraction responsibility is yours, the portfolio serves you not clients (5-10 pieces suffice), and unexciting projects are legitimate business. Free tooling raises, not lowers, the need for self-imposed process.

'Only amateurs start designing... without having enough answers' (l1427459 0:04:02)

'Clients don't really care about your portfolio... they're probably manipulating you' (l1427459 0:08:06)

Portfolio sizing: 5-10 items, 'that is enough' (l1427459 0:08:06)

Car-prototype contrast: free experimentation still deserves discipline (l1427459 0:10:07)

'We need a good process for good design... become true professionals' (l1427459 0:12:11)

▶ Watch this taught:

Check yourself

Answer from memory first — the recall attempt is what makes it stick. Then reveal.

Why does the free cost of a Figma artboard argue FOR more discipline, not less?

Because nothing external stops you iterating forever — car makers have budget gates; designers must build their own gates (the agreement rounds of Chapter 3) or drown in free options.

04

Watch out with assumptions: one dentist, three correct websites

'Does every dentist need this?... If your answer was yes, of course — then I have to say no.'

The lesson that keeps the new process-mindset from calcifying into templates. One dentist practice, three real briefs: GROWTH — hero, services, benefits, testimonials, CTA (the 'standard' local-business kit). OVERBOOKED — the standard kit is wrong; this practice needs an FAQ and a treatments archive to DEFLECT inquiries, not attract them. RETIRING IN FIVE YEARS — story-driven site (video, testimonials) aimed at a potential BUYER of the practice, with no call-to-action at all. 'This is the same business. It's all a dentist, but they have 3 completely different websites.' The named enemy: YouTube-tutorial section lists ('a local business should always have these sections... it's like, yes, probably, but it depends').

Worked example · from the session

The overbooked case is the sharpest: the conversion-optimized 'best practice' homepage would make their actual problem WORSE.

Why it matters

It's the bridge to Discovery: the correct sections are unknowable without the goal, which is exactly what phase 1 of the workflow extracts.

People get this wrong

Best-practice section lists are a safe default.

They're the GROWTH dentist's list — one of at least three possible correct answers, and actively harmful for the other two.

This is the same business. It's all a dentist, but they have 3 completely different websites.
For your projects

['The three-dentist device is your best OI-089 spec input: a starter-site generator MUST ask the goal question before choosing sections — otherwise it automates the assumption.']

Go deeper

In one line: Business category does not determine site structure; the client's actual goal does. Any advice of the form '[business type] sites should have [sections]' is an assumption wearing a best-practice costume — the guardrail is goal-first discovery.

Three briefs, one dentist: growth / deflection / exit-sale (l1427460 0:02:00)

The retiring dentist's site has NO call-to-action — correctly (l1427460 0:02:00)

'You are probably making assumptions too quickly' (l1427460 0:02:00)

YouTube section-list advice named as the assumption factory (l1427460 0:04:01)

Try it now

Take any business category and write three divergent goals for it — then note how few sections survive all three lists.

▶ Watch this taught:

Check yourself

Answer from memory first — the recall attempt is what makes it stick. Then reveal.

What single discovery question separates the three dentists?

'What should this website achieve for the business in the next few years?' — growth, relief, or sale. Everything structural follows from that answer.

05

The cure, previewed: Discovery, Sitemap, Visual Direction, Visual Design

'There's no magical process to design, guys — but there is a wrong order.'

Four phases, fixed order, each mapped against the chapter's pains: DISCOVERY finds the real goal (kills generic sites and wrong assumptions); SITEMAP fixes structure before pixels (kills late 'we forgot this section' revisions); VISUAL DIRECTION locks styling globally before detail design (kills redo-every-page rework); VISUAL DESIGN assembles sections with inspiration and testing (kills the blank canvas). 'Good design agencies all use this workflow in order to avoid losing time and money.' The next chapter teaches each phase in depth; this lesson exists so the pains and the phases are seen as one picture.

Worked example · from the session

The pains-to-phases mapping read back against lesson 10's list — each pain gets exactly one phase as its antidote.

Why it matters

It's the course's table of contents disguised as a lesson — and the KB's cleanest statement of what the whole method is.

People get this wrong

Process kills creativity.

The order constrains WHEN choices happen, not WHAT you may choose — and Chapter 3 explicitly preserves 'some chaos' inside each phase.

There's no magical process to design guys, but there is a wrong order.
For your projects

['For OI-089: these four phases are the natural pipeline stages of a Cowork starter-site generator — Discovery as intake form, Sitemap as generated structure, Direction as Stylekit palette, Design as the build.']

Go deeper

In one line: The LWP client workflow: Discovery (goal) → Sitemap (structure) → Visual Direction (global style) → Visual Design (sections), in fixed order, each phase ending in client agreement — order itself being the professional differentiator.

Four phases named, order fixed (l1427461 0:00:00)

'There is a wrong order' — the anti-magic framing (l1427461 0:02:00)

Agency practice invoked as social proof (l1427461 0:02:00)

He pre-empts 'but global styles make redoing cheap' — conceded, and direction still comes first (brief, ch2 close)

▶ Watch this taught:

Check yourself

Answer from memory first — the recall attempt is what makes it stick. Then reveal.

Why does Visual Direction precede Visual Design even when global styles make changes cheap?

Cheap changes are still changes: without an agreed direction, every section design is a bet that may be re-litigated. The phase buys agreement, not just efficiency.

Every concept, three clicks deep

The same concepts as a quick reference: the closed row is the glance, open is the study card, and every timestamp jumps into the recording.

01The problem inventory: what unstructured design actually costsUnstructured design fails in six repeatable ways (start-paralysis, inspiration drought, decision fatigue, t…›

Unstructured design fails in six repeatable ways (start-paralysis, inspiration drought, decision fatigue, template-coping, feedback spirals, project ghosting), and designers metabolize the failure through four self-protective narratives instead of process change.

The six pains catalogued in one pass (l1427457 0:00:00)

'A race to the bottom that you will never win' — the pricing narrative (l1427457 0:02:02)

The arrogance skit rejected on the record (l1427457 0:06:04)

'Our biggest obstacle isn't external' — the internal-blame reframe (l1427457 0:08:06)

02Style follows function: the cars-and-architecture proofFunction (the job, the user, the context) determines form;›

Function (the job, the user, the context) determines form; style is the visible residue of functional decisions. Reversing the order produces designs that look right and work wrong — and the failure is often invisible until context (kids, rain, mosquitoes) reveals it.

'Style follows function... in architecture they call it form follows function. It's the same.' (l1427458 0:04:04)

Three architecture reversals: staircase, outdoor bathroom, flat roof (l1427458 0:04:04)

'A pretty design is not always practical' (l1427458 0:06:04)

'Don't start with the end result... functional design always comes first' (l1427458 0:08:05)

03The architect role-play and the three painful truthsProfessionalism = question-asking discipline plus three accepted truths: extraction responsibility is yours…›

Professionalism = question-asking discipline plus three accepted truths: extraction responsibility is yours, the portfolio serves you not clients (5-10 pieces suffice), and unexciting projects are legitimate business. Free tooling raises, not lowers, the need for self-imposed process.

'Only amateurs start designing... without having enough answers' (l1427459 0:04:02)

'Clients don't really care about your portfolio... they're probably manipulating you' (l1427459 0:08:06)

Portfolio sizing: 5-10 items, 'that is enough' (l1427459 0:08:06)

Car-prototype contrast: free experimentation still deserves discipline (l1427459 0:10:07)

'We need a good process for good design... become true professionals' (l1427459 0:12:11)

04Watch out with assumptions: one dentist, three correct websitesBusiness category does not determine site structure;›

Business category does not determine site structure; the client's actual goal does. Any advice of the form '[business type] sites should have [sections]' is an assumption wearing a best-practice costume — the guardrail is goal-first discovery.

Three briefs, one dentist: growth / deflection / exit-sale (l1427460 0:02:00)

The retiring dentist's site has NO call-to-action — correctly (l1427460 0:02:00)

'You are probably making assumptions too quickly' (l1427460 0:02:00)

YouTube section-list advice named as the assumption factory (l1427460 0:04:01)

05The cure, previewed: Discovery, Sitemap, Visual Direction, Visual DesignThe LWP client workflow: Discovery (goal) → Sitemap (structure) → Visual Direction (global style) → Visual…›

The LWP client workflow: Discovery (goal) → Sitemap (structure) → Visual Direction (global style) → Visual Design (sections), in fixed order, each phase ending in client agreement — order itself being the professional differentiator.

Four phases named, order fixed (l1427461 0:00:00)

'There is a wrong order' — the anti-magic framing (l1427461 0:02:00)

Agency practice invoked as social proof (l1427461 0:02:00)

He pre-empts 'but global styles make redoing cheap' — conceded, and direction still comes first (brief, ch2 close)

Tools referenced

ToolCoverageMomentContext
FigmamentionedNamed with Adobe XD and Photoshop as tools where an extra page costs nothing - the free-experimentation discipline argument

Action items

Resources mentioned

Resources
  • docThe three-dentist case study
  • docThe 4-phase workflow preview

Extraction notes

This page was built from an auto-generated transcript, which garbles product and people's names. Those were corrected silently in everything above and logged here for transparency. The warnings flag claims that were true on the recording day but change fast.

Transcript corrections applied

The transcript saysThe trainer actually means
in a country like work where I live. The Netherlandsa country like where I live - the Netherlands (disfluency)
5, 10 times (feedback)illustrative revision counts, not a measured statistic

True on recording day — verify before relying