Re-designing a traditional product from scratch
Record
Relaunched a legacy product for a new segment; it broke the previous version's revenue record at launch.
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.
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).
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.
The full write-up carries the risk that prompted the work, what was actually built, and how the outcome was measured.
50 % reduction in design opex
Halved product design operating cost by rebuilding the missing information architecture instead of patching the interface.
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.
Rebuilt the missing information architecture layer instead of continuing to patch the surface layer, then centralized the team around the corrected structure.
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.
The full write-up carries the risk that prompted the work, what was actually built, and how the outcome was measured.
200,000 CAD saved per year
Cut $200K a year of agency ad spend — 80% of the budget — with no drop in pipeline.
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.
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.
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.
The full write-up carries the risk that prompted the work, what was actually built, and how the outcome was measured.
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.
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.
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.
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.
The full write-up carries the risk that prompted the work, what was actually built, and how the outcome was measured.
6 functions adopting
Converted six functions' one-off deliverables into reusable component and pattern libraries, raising throughput without adding headcount.
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.
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.
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.
The full write-up carries the risk that prompted the work, what was actually built, and how the outcome was measured.
25 % efficiency gain (est. 20-30)
Consolidated hundreds of use cases into one reusable visual model, freeing an estimated 20-30% of team capacity.
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.
Designed a single visual model that consolidated hundreds of use cases and multiple concurrent projects into one standardized deliverable.
Team efficiency increased, freeing capacity for higher-value work without adding headcount.
Playbook move — Map it once, reuse it everywhere.
The full write-up carries the risk that prompted the work, what was actually built, and how the outcome was measured.
3 dedicated ICs
Covered the full creative surface of product and marketing with three cross-trained ICs.
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.
Built a small, cross-trained creative team where each member operates across a wide surface of product and marketing work rather than narrow specialization.
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.
The full write-up carries the risk that prompted the work, what was actually built, and how the outcome was measured.
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.
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.
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.
Lowered the comprehension barrier to adoption, reducing onboarding friction and support dependency.
Playbook move — Name it, and it becomes usable.
The full write-up carries the risk that prompted the work, what was actually built, and how the outcome was measured.
5 Increase in employee engagement in functions other than design
Installed a five-step design process across every operating cadence; portfolio gains surpassed 20%.
Absence of a repeatable, well-defined process created friction and inconsistent outcomes across product development, design delivery, and cross-functional working sessions.
Implemented a simple 5-step design-thinking process applied consistently across every operating cadence — daily, weekly, phase, and project level.
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.
The full write-up carries the risk that prompted the work, what was actually built, and how the outcome was measured.
12 months to reorg
Ran design-thinking workshops across the organisation; within a year the company reorganised product around design-led practice.
Limited understanding of design's function and value among adjacent teams constrained the design organization's ability to grow its scope and influence.
Applied a management-cybernetics approach, systematically running a design-thinking workshop across as much of the organization as possible.
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.
The full write-up carries the risk that prompted the work, what was actually built, and how the outcome was measured.
35 % Increase in stakeholders satisfaction
Became the rallying point for cross-functional initiatives without any change in formal authority.
Without a function or person actively driving alignment, cross-functional initiatives fragment, stall, or compete for priority — a common failure mode in scaling organizations.
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.
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.
The full write-up carries the risk that prompted the work, what was actually built, and how the outcome was measured.
10 x faster delivery
Embedded AI into research, management and design as daily practice, taking marketing and product delivery at least 10x faster.
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.
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.
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.
The full write-up carries the risk that prompted the work, what was actually built, and how the outcome was measured.
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.
Design handoff to engineering created recurring back-and-forth — specs misread, technical constraints discovered late, iteration bottlenecked by translation loss between design and code.
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.
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.
The full write-up carries the risk that prompted the work, what was actually built, and how the outcome was measured.
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.
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.
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.
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.
The full write-up carries the risk that prompted the work, what was actually built, and how the outcome was measured.