Hand, Head, Heart as Design Operating System.

25 years of practice, spanning industries, from startups to global product teams.

A practitioner’s map of what to study, what to practise, and how to know it’s working, at your level and the one above.

Most design careers hit the same wall: craft is solid, the work ships, and something essential is still missing.

H3 is the operating system for that gap: three layers — Hand, Head, Heart — that map what a practitioner needs to develop, and in what order.

If any of these are familiar

Your portfolio is strong — but when someone asks about your design philosophy, you feel a silence.
Your manager says “elevate design’s strategic role.” You nod. You have no idea what to actually change.
The work ships. Juniors improve under your feedback. The promotion keeps not happening.
Someone you respect has suggested management — and you can’t tell if you’d lean in, or be quietly drained by it.

Then H3 is for you.

Read the book

Front matter and Chapter 1 are free · Full book unlocking soon

Sign in with Google to read the front matter and Chapter 1 free. Your highlights and progress sync across every device you sign in on.

Continue with Google →

Free account. No spam. Notes and highlights are private to you.

01 · Why Now

AI is rewriting the job faster than the field is rewriting the path.

AI compresses craft tasks faster than design training can rebuild them. Companies expect strategic, organisational work often without preparing designers for any of it. The career structure designers used to grow into no longer matches the job they’re being asked to do.

02 · The Book

H3 names the gap.
Then maps the work.

A framework with three layers, written for one practitioner.

The Hand

Instrument

The H3 Self-Assessment

Locate where you are across all three layers before you decide what to develop next.

The craft layer. What you make, and how.

The Head

Instrument

The Branch Decision Card

Six signals that read your IC-vs-management pull at the moment it matters.

The structural layer. Where the work fits, when to branch.

The Heart

Instrument

The Team H3 Audit

Read your team’s collective capacity before you write the next role.

The conduct layer. The team that ships the work.

Built in order. Hand first, Head second, Heart third — then tuned across all three for the rest of your career.

03 · Inside

Sixteen chapters. One arc.

From “What Is a Designer?” to “The Ensemble.”

PPreface · Lineage & IntroductionWhere the framework came from, and the design tradition it sits inside
- P.1The Gapwhat design training teaches versus what practice demands
- P.2Three at Oncecraft, career, conduct — each demanding full presence
- P.3Three Designersa mirror before the map
- P.4How to Use This Bookacross your career, not just one reading
- L.1A Remark in 1997where the idea first landed
- L.2Pestalozzithe schoolteacher who named it
- L.3The Transmissionhow the triad moved through two centuries
- L.4The Reorderingwhy this book changes Pestalozzi's sequence
- I.1Operating Systemwhat H3 is, and what it is not
- I.2The Trianglethree layers, and what anchors each
- I.3Triadic Logicwhy removing one layer collapses the whole
- I.4Why NowH3 and the age of AI
Part IThe Model — craft & identity
01What Is a Designer?A definition in three parts and the person who holds themFree
- 1.1Tool Trapa tool is not an identity
- 1.2First Principleswhat a designer is actually accountable for
- 1.3The TriadUser, Business, Technology — held simultaneously
- 1.4The ModelHand, Head, and Heart as modes of engagement
- 1.5Not a Methodhow H3 differs from the frameworks you already know
- 1.6The Practitionerthe unit of analysis is the person, not the problem
- 1.7Levela structure, not a rank
- 1.8Craftsomething you develop, not a prerequisite
- 1.9Individual + TeamH3 applies inside a team, not instead of one
- 1.10The Outputwhat all three layers developed makes possible
02The WorkProblem Framing · Value Shaping · Experience Realisation
- 2.1Phase A · Problem FramingHead-dominant: what is the real problem?
- 2.2Phase B · Value ShapingHeart enters strongly: who is this for, what does it mean?
- 2.3Phase C · Experience RealisationHand manifests: how does it behave?
- 2.4Junior to seniorthe growing tolerance for the discomfort of not yet making
03The HandYour relationship with the work — craft as practice
- 3.1What craft meansand why "visual polish" is not enough
- 3.2The second discipline as a craft multiplier
- 3.3Prototyping as thinkingworking at code fidelity
- 3.4Design systems as craft infrastructuretokens, components, patterns
- 3.5Motion, typography, and the felt sensewhen 280ms matters
- 3.6How AI changes craftwhat it accelerates and what it cannot touch
04The HeadYour relationship with the system your work lives inside
- 4.1Strategic thinkingwhat it means at the designer's level
- 4.2Problem framingwhy the brief you receive is almost always wrong
- 4.3Design and businesslearning to speak both languages
- 4.4Systems thinkingfrom screens to service ecosystems
- 4.5DesignOpsas strategic infrastructure
05The HeartYour relationship with the people you design for
- 5.1Empathy as Disciplinenot a personality trait
- 5.2Research Methodsfrom observation to insight
- 5.3Behavioural Sciencethe minimum vocabulary every designer needs
- 5.4Journey Mappingas instrument, not deliverable
- 5.5Emotional Designwhen to evoke feeling, when to get out of the way
- 5.6Accessibilityempathy at population scale
- 5.7The RoomHeart at the table, not just in the study
06The Whole PractitionerWhere Hand, Head, and Heart converge — Purpose, Presence, Precision, Mastery
- 6.1PurposeHeart × Head — strategic empathy
- 6.2PresenceHand × Heart — emotional craft
- 6.3PrecisionHead × Hand — scalable excellence
- 6.4Masterythe centre — all three alive simultaneously
- 6.5Mode Readingwhich H to lead with, when to shift
- 6.6Self-Assessmentyour H3 profile today
- 6.7Interlude — When Craft Becomes Insufficientthe threshold between Model and Structure
Part IIThe Structure — growth & specialisation
07The π-Shaped DesignerWhy T-shaped is no longer enough
- 7.1I → T → πthe evolution of designer profiles
- 7.2The Horizontal Barbreadth as the foundation of influence
- 7.3Vertical 1 — Craftupstream or downstream depth
- 7.4Vertical 2 — Leadershippeople or thought
- 7.5Asymmetry of πwhy the two bars aren't the same shape
- 7.6The Same Briefwhere T and π diverge in practice
- 7.7T02 in Practicea practitioner mapped
08Six LevelsThe career ladder as a sequence of expanding relationships
- 8.1L1 Associate · Followbuilding the model inside yourself
- 8.2L2 Senior · Assistshipping consistently across product areas
- 8.3L3 Lead · Applythe Branch — deepening craft or owning a team
- 8.4L4 Staff · Enableprogrammes, not projects
- 8.5L5 Principal · Ensuresetting the standard others follow
- 8.6L6 Advisor · Direct & Advisethe field as your team
- 8.7Both Tracks in One Matrixreading the Branch at L3
- 8.8Same Seat, Different LevelL2 and L4 in the same critique
09The Branch DecisionThe Branch at Lead — and how to choose your path with clarity
- 9.1The Branch, Misunderstooda question of energy, not promotion
- 9.2Three IC Signalsreading the pull toward craft depth
- 9.3Three Management Signalsreading the pull toward multiplying
- 9.4H3 Map of Each BranchHand+Head vs Heart+Head
- 9.5Reversibilitythe branch is sticky, not permanent
- 9.6The Third Branchleaving design with H3 intact
- 9.7The BranchT03 in use at the moment it matters
10Two Specialisation ArchetypesThe Design Strategist and the Experience Engineer
- 10.1The Compressing Generalist Layerwhy the ends defend what the middle cannot
- 10.2The Design Strategistupstream, Head-primary
- 10.3The Experience Engineerdownstream, Hand-primary
- 10.4Portfolio & Hiring Signalswhat the evidence looks like
- 10.5π and H3 Connectionarchetypes at Vertical 1 maturity
11AI and the CareerWhat the machine changes — and what it cannot
- 11.1What AI Compressesthe L1→L2 rung and the mid-career plateau
- 11.2What AI Amplifiesframing, boldness, systems thinking
- 11.3What AI CreatesAI Direction as a new L4+ craft dimension
- 11.4Fast → Continuous Learnerhow the culture value evolves
- 11.5The Honest Companionwhat the framework does not fully answer
- 11.6Interlude — When Structure Meets Uncertaintythe threshold between Structure and Conduct
Part IIIThe Conduct — team leadership
12The Five DomainsThe full landscape of design leadership responsibility
- 12.1Vision (Head)strategic direction of the design programme
- 12.2Direction (Heart)what great design means in practice
- 12.3Function (Head + Hand)the infrastructure of design delivery
- 12.4Organisation (Heart)the people who make the work possible
- 12.5Cooperation (Head + Heart)design's relationship with the wider business
- 12.6The H3 Map of the Five Domainspattern, plateau, and the political shadow
13Focus and PriorityHow to choose what to work on — and what to let wait
- 13.1The Three-Star Modelreading the health honestly
- 13.2Focus Selection Protocolfour questions, fifteen minutes
- 13.3Quarterly Leadership Cyclethree tasks, one owner, one signal
- 13.4Domain Bundleswhat to work on per focus domain
- 13.5The Rhythm of Leadershipcadence as a design decision
14HiringBuilding a team with intentional H3 composition
- 14.1Team H3 Auditreading your ensemble before hiring
- 14.2Profiling the RoleH gap, π depth, must-haves — before the JD
- 14.3Hiring the Strategistportfolio signals and interview approach
- 14.4Hiring the Engineerportfolio signals and craft test
- 14.5Promotion CalibrationH3 as structure for the conversation
15Culture and CapabilityThe bridge between who your designers are and what they can do
- 15.1Culture as Soilwhy values fail without capability consequences
- 15.2The Bridgeten values mapped to capability dimensions
- 15.3Hire vs Growthree capabilities culture alone cannot produce
- 15.4Translation Registerusing the bridge without making it an audit
- 15.5Capable by Designmap, hire honestly, translate — simultaneously
16The EnsembleHow Model, Structure, and Conduct work together as a living system
- 16.1Model → Conductthe conductor must know the instrument
- 16.2Structure → Conductthe career as deliberate preparation
- 16.3Conduct → Modelleadership as craft's highest expression
- 16.4H3 Under AIthe three layers at organisational scale
- EpilogueA Note to the Readerwherever you are in the triangle

Front matter & Chapter 1 free · Full book launching 2026

04 · The Long Read

It will be three different books.

Once a Map. Once a Mirror. Once an Instrument.

As a Map

When the path is still ahead of you.

As a Mirror

When you’re deep in the work.

As an Instrument

When you’re leading the people walking it.

05 · What Changes

What’s different after reading.

After reading, you will be able to:

For the IC

Walk into your next review with words for the shape of your work.
Hear “be more strategic” and know what’s actually being asked.

For the Lead at the branch

Read your IC-vs-management decision and know which one your energy is already answering.
See the next two career levels named in a way you can act on this quarter.

For the Manager

Run your team’s H3 audit in one 30-minute session and identify the gap that’s keeping the work from compounding.
Open your next role with a profile of the H gap you’re actually hiring for, before you write the JD.

Solo or in transition? Read Part III as preparation.

06 · Author

Why I wrote this.

Fares Farhan

I’m a digital product designer with 25 years of practice across startups, agencies, and Fortune 500s, including Xamarin, Dropbox, Google, Spotify, Saatchi & Saatchi, and DBS Bank Singapore, where I led the redesign of the consumer mobile banking app.

The same gap kept showing up in conversations with mid-senior designers across decades, including in me. I wrote H3 because I kept needing it: when forming a team, when leading one, when mentoring inside it.

H3 is the distillation of that career: a practitioner’s operating system built from the inside out, not handed down from above.

I’m also a drummer, once a Warner Music recording artist, and a novice guitarist.

07 · FAQ

Common questions.

Is this for me if I'm a junior designer?

Yes, and probably the highest-leverage moment to read it. Part I (Model) is your primary work for the next two to three years. Part II (Structure) names the levels and decisions ahead of you so they don't show up as surprises. Part III (Conduct) waits. Read it once now, return at each transition.

Is this for me if I'm a freelancer or solo practitioner?

Parts I and II are directly for you. Part III assumes a team being led, but the chapter on the Five Domains translates: Vision becomes practice direction, Function becomes workflow operations, Cooperation becomes client relationships. Read Part III as preparation. The moment you hire a collaborator, take on an apprentice, or found a studio, it becomes operational.

What's the format and how do I read it?

A web-native reading experience. No PDF, no app. Open it in any browser, read in any order, return to specific tools (Self-Assessment, Branch Decision Card, Team Audit) without reflowing or losing your place.

Is this AI-skeptic or AI-positive?

Neither. Chapter 11 names what AI compresses, what it amplifies, and what new craft dimension it creates. The position is that a practitioner who develops all three layers is more useful in an AI-shaped industry, not less. The framework was built before this AI cycle and survives it.

Will Chapter 1 be enough to know if the rest is for me?

Yes. Chapter 1 establishes the first-principles definition of a designer and the four structural distinctions that separate H3 from process frameworks. If twenty minutes with that chapter doesn't earn your trust, the rest won't.

08 · Read Today

Start with Chapter 1.

What Is a Designer? is the foundation the rest of the book builds on. It stands on its own. Below is how it opens.

From Chapter 1 · What Is a Designer?

The first question in the screening call is always the same: what tools do you work in? The designer names three. The actual work — the problems solved, the misdiagnoses caught, the briefs reframed — never comes up.

Until a designer can say what they do without naming a tool, a deliverable, or a position, they don’t have an identity — they have a description of current working conditions.

— Continues for ~20 minutes

If that landed

The full chapter is one click away. Free, with sign-in.

Continue with Google →

Hand, Head, Heart as Design Operating System.

AI is rewriting the job faster than the field is rewriting the path.

H3 names the gap. Then maps the work.

Sixteen chapters. One arc.

It will be three different books.

What’s different after reading.

Why I wrote this.

Common questions.

Start with Chapter 1.

H3 names the gap.
Then maps the work.