Design Strategy

What we do

Concept Architects is the core of the team’s output. Concept architects work on named bets: distinct, researched, and designed expressions of where GitLab’s product experience should go. These are not wireframes for a backlog. They are fully reasoned design positions, grounded in market context and customer need, built to inform executive decisions about where to invest.

DesignOps runs the infrastructure that makes Upstream Studios effective. This includes how the organization measures design quality, how design work moves through the company, and how the team’s operational rhythms support the pace and quality of the work.

Craft Quotient (CQ) is Design Strategy’s investment in raising the quality ceiling across GitLab’s design practice. This includes tools, standards, and capability development that benefit the broader organization, not just Design Strategy.

How we work

Design Strategy is a Central Organization, not a capacity resource for Product Studios or stage groups. The team does not backfill headcount gaps, take on scoped feature work, or serve as an overflow design function. What the team produces is upstream of product planning: it informs what gets built, not how a committed scope gets staffed.

Concept work is internally developed until it reaches a point where executive input or cross-functional investment decisions are needed. At that point, Design Strategy brings work forward through Upstream Studios leadership.

Principles

These principles are the operating foundation for Design Strategy. They apply across all three practices and, where noted, within each one specifically. Each principle names what it closes off and offers a question for the moment when it matters.

Shared

We run today in the direction of tomorrow.

• What it closes off: “Service work and strategy work are separate tracks.” They aren’t. How we handle today’s request is itself a move toward the future state, or a vote against it.
• What to ask: Is this response also a step toward where we’re going?

We ship leverage, not artifacts.

• What it closes off: “We delivered the thing.” A deck, a doc, a template that gets used once isn’t the job. The job is what works the tenth time, not the first.
• What to ask: Does this create value when I’m not in the room?

We work in the open.

• What it closes off: “I’ll write it up later.” Thinking that stays invisible until it’s finished, and work that lives with one person and no one else. Open means anyone can find it and pick it up. It does not mean we are introducing it before it’s ready, and it does not override a specific agreement to keep collaborative work contained.
• What to ask: Is my thinking visible while it’s still shapeable, not just after it’s done?

We ground every concept in a real problem.

• What it closes off: Starting from “this would be interesting” instead of a real problem. If you can’t name what’s not working, or what’s missing, the work won’t survive scrutiny, and it shouldn’t.
• What to ask: Can I name the problem, the user, and the business case before I open the design tool?

We leave the platform better than we found it.

• What it closes off: Treating the work as separate from the platform it touches. Whatever we build, whatever process we run, whatever we fix, it’s evidence. It can expose, and sometimes resolve, the structural problems that would otherwise block what comes next.
• What to ask: What did this reveal about the platform, and did I leave it more ready for what’s next?

DesignOps

How design works is our work. What design ships is theirs.

• What it closes off: “Help where they need it.” We work on the practice itself, how designers operate, decide, ship, and build on each other’s work across the design org.
• What to ask: Am I shaping the practice, or running it?

Small changes compound.

• What it closes off: “This needs a big initiative.” Most practice change happens through small, repeated moves that accumulate. Big rollouts fail or get diluted.
• What to ask: Is this the smallest move that creates the right shift?

Decisions have owners. Discussion has limits.

• What it closes off: “Let’s get everyone aligned.” Consensus is slow and often dishonest. Someone owns the call, makes it with the input they have, and the team moves. Disagreement is welcome before the decision, commitment is required after.
• What to ask: Who owns this decision, and what’s stopping them from making it?

Concept Architects

We make ideas hard to ignore.

• What it closes off: “We pitched it.” A single moment of attention isn’t momentum. Compounding signals, engineering pickup, exec pull, external resonance, is what carries an idea from concept to commitment.
• What to ask: Am I creating one moment of attention, or stacking signals?

We make the future tangible.

• What it closes off: “Here’s the strategy doc.” Decks don’t move people. Prototypes, videos, and working things do. The thing leadership can see and react to is the work.
• What to ask: Can someone feel this, or only read about it?

We follow good ideas wherever they start.

• What it closes off: Treating Concept as the only place future-facing thinking can happen. Good ideas don’t check which team they came from.
• What to ask: Is this idea good enough to follow, no matter who had it first?

We swing, and we miss sometimes.

• What it closes off: “It has to land.” A team that only proposes safe ideas isn’t doing the job. The misses are how we earn the ones that land.
• What to ask: Would I still propose this if I knew it might miss?

We read the window.

• What it closes off: “We’re working on the future.” Some windows are open now and won’t be for long. Others won’t open for years. Treating them the same kills both.
• What to ask: What’s the right window for this idea, and am I working to it?

Craft Quotient

We fix to learn.

• What it closes off: “Just ship the fix.” Fixing without learning is firefighting. Each defect is data about where the bar lives and where it doesn’t hold.
• What to ask: What does this fix teach us?

Patterns over instances.

• What it closes off: “Fix this one, move on.” A list of fixes isn’t a standard. The pattern is what carries to the next case, and the case after that.
• What to ask: What pattern does this point to?

Not every defect is ours.

• What it closes off: “If we don’t fix it, no one will.” Quality belongs to the org. We pick the work that teaches the standard. The rest goes back to its owner.
• What to ask: Does picking this up move the standard?

Scale comes through partnership and mentorship.

• What it closes off: Treating craft improvement as something CQ delivers by fiat, fixes shipped, standards published, without the relationship work that makes them stick. A standard nobody was mentored into doesn’t scale, it sits.
• What to ask: Am I doing this work for someone, or with them?

Team

Design Strategy is supported by two researchers from Experience Research who are embedded with the team. Jessica Kane and Will Leidheiser report into Experience Research but work closely with Design Strategy on concept development and directional research.

Working with Design Strategy

Find us in #design_strategy on Slack.

View page source - Edit this page - please contribute.