Case 01 of 14

Re-designing a traditional product from scratch

Revenue Enterprise in Games
Shape of Work plot for Re-designing a traditional product from scratch
Visual key
Design practitioner Collaborators engaged Interfaces delivered
How to read this model
Reading the plot
Abstraction abstract
Complexity complex
Scale large
Business outcome Revenue

Record

Relaunched a legacy product for a new segment; it broke the previous version's revenue record at launch.

The arc of the engagement
Risk

A company that had invested in an operational pivot to become a creative company — going from buying IPs to developing them — needed to make sure it learned to break its old assumptions.

Intervention

What began as a proof-of-concept intended to challenge executive assumptions became an organization-wide shift in product strategy, org design, and roadmap. The product was relaunched for a new target segment (casual mobile players).

Outcome

The relaunched product broke the prior version's revenue record at launch — a direct, attributable revenue outcome from a design-led strategic bet.

Playbook move — Reinvent what everyone assumed was fixed.

Read the case

The full write-up carries the risk that prompted the work, what was actually built, and how the outcome was measured.

Case 02 of 14

Allocating resources rightly

Operating cost Start-up in Data Integration and Automation
Shape of Work plot for Allocating resources rightly
Visual key
Design practitioner Collaborators engaged Interfaces delivered
How to read this model
Reading the plot
Abstraction aggregate
Complexity composite
Scale medium
Business outcome Operating cost

50 % reduction in design opex

Halved product design operating cost by rebuilding the missing information architecture instead of patching the interface.

The arc of the engagement
Risk

Design resources were misallocated toward interface-level (UI) work of low marginal value, while a structural gap — missing information architecture — went unaddressed. This produced redundant work and inflated headcount requirements without a corresponding increase in output.

Intervention

Rebuilt the missing information architecture layer instead of continuing to patch the surface layer, then centralized the team around the corrected structure.

Outcome

Reduced product design operating costs by approximately half, demonstrating the team could deliver the same output with half the headcount it carried the prior year.

Playbook move — Fix the structure, not the symptom.

Read the case

The full write-up carries the risk that prompted the work, what was actually built, and how the outcome was measured.

Case 03 of 14

Marketing consolidation and insourcing

Operating cost Scale-up in HealthTech
Shape of Work plot for Marketing consolidation and insourcing
Visual key
Design practitioner Collaborators engaged Interfaces delivered
How to read this model
Reading the plot
Abstraction concrete
Complexity composite
Scale medium
Business outcome Operating cost

200,000 CAD saved per year

Cut $200K a year of agency ad spend — 80% of the budget — with no drop in pipeline.

The arc of the engagement
Risk

Ad spend was running through two external agencies. Nobody could confirm it was ROI positive — not the company, not the agencies. The agencies themselves had been asking for tracking access and hadn't gotten it.

Intervention

I proposed a bounded, reversible test to a business unit stakeholder rather than debating the question indefinitely: pause his agency's spend for a month and watch for negative impact. He ran it, found none, and we killed the spend for his business unit entirely — still no impact. That converted an open question into evidence.

Outcome

A second stakeholder, in a different business unit, saw the result and independently followed the same move. Between the two: both external agencies were let go, ad management moved in-house to my team, and the saving came back to the business with no drop in pipeline.

Playbook move — Unsure if something adds value? Remove it and see. If nothing breaks, it wasn't.

Read the case

The full write-up carries the risk that prompted the work, what was actually built, and how the outcome was measured.

Case 04 of 14

Visuals that inform the right bets (portfolio analytics)

Team efficiency Enterprise in Games
Shape of Work plot for Visuals that inform the right bets (portfolio analytics)
Visual key
Design practitioner Collaborators engaged Interfaces delivered
How to read this model
Reading the plot
Abstraction abstract
Complexity complex
Scale large
Business outcome Team efficiency

450 games normalized

Built one visual model to compare user behaviour across a 450-game portfolio, giving leadership a shared basis for allocating design investment.

The arc of the engagement
Risk

With 450+ games in the portfolio, leadership had no consistent framework to compare user behavior across products or benchmark design decisions — a blind spot for portfolio-level resource allocation.

Intervention

Led a data visualization initiative applying a vector-based model to normalize behavioral data across the full portfolio, producing a shared visual language for evaluating design performance.

Outcome

Higher precision in game design decisions and increased efficiency of design and user research investment across the portfolio.

Playbook move — See the portfolio, then place the bet.

Read the case

The full write-up carries the risk that prompted the work, what was actually built, and how the outcome was measured.

Case 05 of 14

Design systems to support the entire operation

Team efficiency Enterprise in Games
Shape of Work plot for Design systems to support the entire operation
Visual key
Design practitioner Collaborators engaged Interfaces delivered
How to read this model
Reading the plot
Abstraction aggregate
Complexity complex
Scale large
Business outcome Team efficiency

6 functions adopting

Converted six functions' one-off deliverables into reusable component and pattern libraries, raising throughput without adding headcount.

The arc of the engagement
Risk

Multiple functional teams (game design, web design, design ops, UX research, creative tech, art direction, communications) were operating without shared standards, making cross-team alignment costly and slow.

Intervention

Drove department-wide adoption of a design systems model that went beyond UI components, converting every team's output into reusable component and pattern libraries across both horizontal and global capabilities.

Outcome

Converted one-off deliverables into scalable, reusable assets — reducing duplicated effort and increasing organizational throughput without proportional headcount growth.

Playbook move — Run the org like a design system.

Read the case

The full write-up carries the risk that prompted the work, what was actually built, and how the outcome was measured.

Case 06 of 14

Visual clarity that creates efficiency

Team efficiency Start-up in Data Integration and Automation
Shape of Work plot for Visual clarity that creates efficiency
Visual key
Design practitioner Collaborators engaged Interfaces delivered
How to read this model
Reading the plot
Abstraction aggregate
Complexity singular
Scale small
Business outcome Team efficiency

25 % efficiency gain (est. 20-30)

Consolidated hundreds of use cases into one reusable visual model, freeing an estimated 20-30% of team capacity.

The arc of the engagement
Risk

Every new project required its own discovery and mapping process from scratch. This duplicated effort across projects and teams and consumed hours of billable capacity with no reusable output.

Intervention

Designed a single visual model that consolidated hundreds of use cases and multiple concurrent projects into one standardized deliverable.

Outcome

Team efficiency increased, freeing capacity for higher-value work without adding headcount.

Playbook move — Map it once, reuse it everywhere.

Read the case

The full write-up carries the risk that prompted the work, what was actually built, and how the outcome was measured.

Case 07 of 14

Lean creative capability

Team efficiency Scale-up in HealthTech
Shape of Work plot for Lean creative capability
Visual key
Design practitioner Collaborators engaged Interfaces delivered
How to read this model
Reading the plot
Abstraction concrete
Complexity composite
Scale medium
Business outcome Team efficiency

3 dedicated ICs

Covered the full creative surface of product and marketing with three cross-trained ICs.

The arc of the engagement
Risk

Covering both product and marketing creative needs typically requires either a large team or narrow specialization silos, both of which inflate headcount and slow delivery.

Intervention

Built a small, cross-trained creative team where each member operates across a wide surface of product and marketing work rather than narrow specialization.

Outcome

Covered the full creative surface area of product and marketing with a fraction of typical headcount — a small number of dedicated ICs covering core design functions including research, content, and UI.

Playbook move — Breadth beats headcount.

Read the case

The full write-up carries the risk that prompted the work, what was actually built, and how the outcome was measured.

Case 08 of 14

A better language for better UX

Team efficiency Start-up in Data Integration and Automation
Shape of Work plot for A better language for better UX
Visual key
Design practitioner Collaborators engaged Interfaces delivered
How to read this model
Reading the plot
Abstraction concrete
Complexity singular
Scale small
Business outcome Team efficiency

45% recuction in internal unproductive product debates

Turned unused internal documentation into a shared visual vocabulary deployed across every user touchpoint, lowering the barrier for non-expert users.

The arc of the engagement
Risk

Low product adoption among non-expert users represented a direct commercial risk: a technically capable product that only expert users could operate limits addressable market and increases customer support and onboarding cost.

Intervention

Converted underused internal documentation into a visual taxonomy and shared vocabulary, deployed across every user touchpoint and reused internally to align product, engineering, and design.

Outcome

Lowered the comprehension barrier to adoption, reducing onboarding friction and support dependency.

Playbook move — Name it, and it becomes usable.

Read the case

The full write-up carries the risk that prompted the work, what was actually built, and how the outcome was measured.

Case 09 of 14

Design thinking as an algorithm

Team efficiency Enterprise in Games
Shape of Work plot for Design thinking as an algorithm
Visual key
Design practitioner Collaborators engaged Interfaces delivered
How to read this model
Reading the plot
Abstraction abstract
Complexity complex
Scale large
Business outcome Team efficiency

5 Increase in employee engagement in functions other than design

Installed a five-step design process across every operating cadence; portfolio gains surpassed 20%.

The arc of the engagement
Risk

Absence of a repeatable, well-defined process created friction and inconsistent outcomes across product development, design delivery, and cross-functional working sessions.

Intervention

Implemented a simple 5-step design-thinking process applied consistently across every operating cadence — daily, weekly, phase, and project level.

Outcome

A more innovative product organization with improved revenue performance and more efficient operations. The company went from buying IP to developing it themselves.

Playbook move — Codify what works so it repeats without you.

Read the case

The full write-up carries the risk that prompted the work, what was actually built, and how the outcome was measured.

Case 10 of 14

Collaborating in a complex and competitive environment

Org authority Enterprise in Games
Shape of Work plot for Collaborating in a complex and competitive environment
Visual key
Design practitioner Collaborators engaged Interfaces delivered
How to read this model
Reading the plot
Abstraction abstract
Complexity complex
Scale large
Business outcome Org authority

12 months to reorg

Ran design-thinking workshops across the organisation; within a year the company reorganised product around design-led practice.

The arc of the engagement
Risk

Limited understanding of design's function and value among adjacent teams constrained the design organization's ability to grow its scope and influence.

Intervention

Applied a management-cybernetics approach, systematically running a design-thinking workshop across as much of the organization as possible.

Outcome

Created the conditions for a company-wide product reorganization in favor of design-led practices, and grew the design function's influence, scope of responsibility, and headcount.

Playbook move — Teach your function; the org reorganizes around it.

Read the case

The full write-up carries the risk that prompted the work, what was actually built, and how the outcome was measured.

Case 11 of 14

Cross-functional center of gravity

Org authority Scale-up in HealthTech
Shape of Work plot for Cross-functional center of gravity
Visual key
Design practitioner Collaborators engaged Interfaces delivered
How to read this model
Reading the plot
Abstraction aggregate
Complexity composite
Scale medium
Business outcome Org authority

35 % Increase in stakeholders satisfaction

Became the rallying point for cross-functional initiatives without any change in formal authority.

The arc of the engagement
Risk

Without a function or person actively driving alignment, cross-functional initiatives fragment, stall, or compete for priority — a common failure mode in scaling organizations.

Intervention

Built cross-functional relationships deliberately and positioned the creative function as the rallying point for core initiatives, without any change in formal authority or mandate.

Outcome

Became the organizational center of gravity for core initiatives — the same authority-without-mandate pattern demonstrated in Co-Evolution, now repeated at a second company.

Playbook move — Authority follows clarity, not title.

Read the case

The full write-up carries the risk that prompted the work, what was actually built, and how the outcome was measured.

Case 12 of 14

Operationalizing AI across the function

Delivery speed Scale-up in HealthTech
Shape of Work plot for Operationalizing AI across the function
Visual key
Design practitioner Collaborators engaged Interfaces delivered
How to read this model
Reading the plot
Abstraction concrete
Complexity composite
Scale medium
Business outcome Delivery speed

10 x faster delivery

Embedded AI into research, management and design as daily practice, taking marketing and product delivery at least 10x faster.

The arc of the engagement
Risk

Research, management, and design each ran on manual, high-friction workflows. Output was capped by individual bandwidth, and tool adoption was scattered project-by-project rather than embedded in how the org worked.

Intervention

Deployed simple and pragmatic bits of AI capability across three distinct functions — research, management, and design — rather than as a point solution in one. Built the practice into daily operating cadence instead of treating it as a side experiment.

Outcome

Increased capacity and output across research, management, and design without adding headcount, with a substantial reduction in marketing and product delivery time.

Playbook move — Make it a habit, not an experiment.

Read the case

The full write-up carries the risk that prompted the work, what was actually built, and how the outcome was measured.

Case 13 of 14

Closing the design-to-code gap

Delivery speed Scale-up in HealthTech
Shape of Work plot for Closing the design-to-code gap
Visual key
Design practitioner Collaborators engaged Interfaces delivered
How to read this model
Reading the plot
Abstraction concrete
Complexity singular
Scale medium
Business outcome Delivery speed

10 x faster spec-to-deploy

Built front-end fluency into the design function, cutting design-to-engineering rework to near zero and spec-to-deploy time by 10x.

The arc of the engagement
Risk

Design handoff to engineering created recurring back-and-forth — specs misread, technical constraints discovered late, iteration bottlenecked by translation loss between design and code.

Intervention

Built front-end coding fluency directly into the design function (vibecoding), closing the Skeleton-to-Surface gap the Elements of UX framework identifies as a common source of rework. Design output is now technically pre-validated before it reaches engineering.

Outcome

Cut design-to-engineering back-and-forth to near zero, removing a cost center from the delivery chain and shortening time-to-ship without adding engineering headcount.

Playbook move — Know your material.

Read the case

The full write-up carries the risk that prompted the work, what was actually built, and how the outcome was measured.

Case 14 of 14

A one-person team that runs like a system

Delivery speed AlejandroMarin.design
Shape of Work plot for A one-person team that runs like a system
Visual key
Design practitioner Collaborators engaged Interfaces delivered
How to read this model
Reading the plot
Abstraction abstract
Complexity composite
Scale small
Business outcome Delivery speed

26 client case-study pages generated from one spreadsheet

Generated all 13 client case studies in English and French from one spreadsheet — 26 pages, none edited by hand.

The arc of the engagement
Risk

An independent practice must do three things at once: be found, show proof, and stay correct in two languages. There is no team. AI makes building fast, but it also makes mistakes fast. Eight weeks in, a review found eleven places where the project's notes no longer matched the code.

Intervention

I treated the practice as a system to design, not a website to build. First, I learned the market's words: I researched how buyers and recruiters search, and split their words into two lists that never mix in one asset. Second, I put my whole career in one spreadsheet — 18 engagements, 30 claims, 13 cases — and generated every case-study page from it, so a number exists in one place only. Third, I decided who does what: an allocation matrix, adapted from NASA Human Systems Integration, assigns each task to me, to the AI or to a script. If a script can check a fact, the script checks it. Fourth, every AI session reads the same rulebook first, and diagrams settle what words leave open. Last, I log every decision (43 so far) and audit drift every month.

Outcome

In January 2026 the site was a Wix build designed in Figma. In February it moved to code. Today, 13 client case studies ship in English and French, generated and never hand-edited, and every release passes six automated gates. Where a script enforces a rule, nothing drifted; where only prose described a rule, the review found eleven gaps. A privacy check now keeps client names out of the code, where three had slipped in before it existed. The analytics loop is instrumented; it starts when distribution starts.

Playbook move — AI scales the structure you give it. Neglect to structure and AI will scale a mess.

Read the case

The full write-up carries the risk that prompted the work, what was actually built, and how the outcome was measured.