Framework, Maturity Model

    Design Org Maturity Roadmap: how I scale design orgs from reactive to strategic

    A four-phase maturity roadmap I use, and teach design leaders to use, when growing a team from a request queue into a product function. Each phase has its signals, its moves, and the work it unlocks.

    Author

    Ashwarya Subhluxmi

    Audience

    Design leaders and execs

    Format

    4-phase maturity model

    Stress-tested on

    Credit Karma, 7 years

    Why This Exists

    Most design orgs stall not because of talent, but because of phase confusion.

    I have inherited teams stuck in Phase 1 trying to operate like Phase 3, and I have watched Phase 3 teams lose ground because they skipped the rituals that earn the seat in the first place. The pattern repeats. The fix is different every time.

    This roadmap is what I use to diagnose where a design org actually sits, what the next phase asks of leadership, and which moves compound. It is four phases, in order, with the signals, the work, and the lived experience behind each one.


    The Roadmap

    Four phases, in order

    Walk them top to bottom. Diagnose honestly. The fastest way to stall a design org is to perform the rituals of a later phase without building the foundation of the current one.

    01

    Reactive Support

    Start Here

    Where most design teams start.

    Designers are attached to squads with no shared rituals, inconsistent quality bars, and no org-level visibility. Work is measured by output (screens shipped), not outcome.

    → Signals you are here

    • Design is brought in after PRDs are written
    • No shared design system or component library
    • Designers report to PMs or engineering leads
    • No design critique or review cadence

    Lived experience, Credit Karma, Personal Loans

    When I joined the Personal Loans team at Credit Karma, design was a request queue. PMs wrote PRDs, then handed off frames to ship. There was no critique, no shared system, and no way to defend a recommendation with evidence.

    02

    Consistent Craft

    Establishing the foundation.

    Introduce shared rituals (weekly critique, design reviews), a component library, and basic quality standards. Designers still work inside squads but now have a dotted line to a design lead.

    → Signals you are here

    • Weekly design critique with structured feedback
    • Shared Figma libraries and naming conventions
    • Design QA process before launch
    • Hiring bar document for consistent recruiting

    Lived experience, Credit Karma, Marketplaces

    On the marketplaces team, the first move was rituals, weekly critique, a shared component library, and a written hiring bar. Quality stopped depending on which designer happened to own the surface.

    03

    Strategic Influence

    Design earns a seat at the table.

    Design leaders participate in roadmap planning, not just execution. The team begins owning metrics (activation, retention, NPS) and running discovery independently.

    → Key moves

    • Design-led discovery sprints
    • Outcome-based performance reviews
    • Cross-functional design system governance
    • Regular executive storytelling that shows impact, not just output
    • Design representation in quarterly planning

    Lived experience, Credit Karma, Personal Loans Redesign

    Design-led discovery on Personal Loans produced the redesign that delivered an 80% revenue uplift at launch and compounded into 300% growth over three years. The team moved from polishing PM ideas to setting the roadmap.

    04

    Product Partnership

    Design as a strategic function.

    Design has its own budget, hiring pipeline, and OKRs. The design leader reports to the CPO or CEO. The team drives product vision alongside PM and engineering.

    → Key moves

    • Design-originated features in the roadmap
    • Dedicated research and content design roles
    • Design metrics tied to business outcomes
    • External brand as a design-forward org
    • Design leader in executive leadership team

    Lived experience, Credit Karma, Shopping Futures

    Leading Shopping Futures, design originated the first debt agent and pitched a three-year AI-first vision to execs. Design was not staffed against PM roadmaps, it set the portfolio direction across a $3B+ marketplace.


    Operating Principles

    What I want design leaders to internalize

    The phases are the surface. Underneath are five principles I hold leaders to when growing a design org. They are the difference between a team that scales and a team that stalls.

    01

    Maturity is not headcount

    It is how design decisions are made and who is in the room when they happen. A five-person team can operate at Phase 3 if the rituals are right.

    02

    Each phase needs a different leader

    Phase 1 needs craft champions. Phase 4 needs business strategists. If you keep promoting the leaders who fit the phase you just finished, the team stalls in the next one.

    03

    Do not skip phases

    Rituals and trust are compounding assets. Teams that skip Consistent Craft to chase Strategic Influence lose both within a quarter.

    04

    Executive alignment is a practice

    Not a one-time pitch. Design earns the seat by telling the story of impact every quarter, in the language the business already speaks.

    05

    Outcome over output

    Screens shipped is a vanity metric. When the question is whether design is a cost center or a growth function, activation, retention, and revenue are the only numbers that move it.


    Closing

    The job is to build the next phase, not perform it

    The design leaders who scale orgs are not the ones with the loudest case for Phase 4. They are the ones honest enough to diagnose Phase 1, patient enough to install the rituals of Phase 2, and disciplined enough to earn Phase 3 before pitching Phase 4.

    A design org does not mature by ambition. It matures by the rituals it can sustain on its worst week, not its best one.

    Related: once you know your phase, restructuring the team for the AI era covers the org shape, how to hire a Head of Design covers when to bring in a design leader, and the design KPIs that survive a board meeting covers how to report it.