Concept Release Discipline
Release phases
- Dark. All concept work begins here. Work in this phase is visible to anyone in the company through the backlog and active issues. GitLab’s commitment to transparency means working in the open is a baseline expectation, not an exception. Dark does not mean hidden. It means Design Strategy is not actively amplifying the work. No previews, no posts, no informal shares. Work stays in this phase until the Concept Architect lead coordinates a move forward.
- Internal debut. A concept enters this phase when it is ready to be introduced to a specific audience inside GitLab. The debut moment is planned in advance: a leadership review, an offsite, a Loop post, or a dedicated meeting. The channel, timing, and audience are confirmed before anything is shared.
- External. A concept moves to external release after its internal debut has happened and Developer Advocacy has been brought in to coordinate timing. External release is how Design Strategy establishes GitLab’s point of view in the market before the conversation happens without us.
How work moves between phases
The Concept Architect lead is accountable for coordinating the timing of phase transitions. That timing is not determined in a Slack thread, through informal preview, or by individual judgment in the moment.
A concept is ready for internal debut when it is coherent enough to be understood without the designer present to explain it, a debut moment has been identified and scheduled, and the lead has confirmed the timing.
A concept is ready for external release when the internal debut has already occurred, the concept has been reviewed for anything that should not be public, and Developer Relations is coordinating the release.
Channel guide
Slack is for conversation after a debut has happened. It is not a preview channel or a substitute for a planned introduction. Sharing work-in-progress in Slack, even in a small group, counts as an early release if a formal debut is planned.
The Loop is for broader GitLab awareness. Use it for concepts that have completed their internal debut and are ready for the full company audience.
External channels (blog posts, conference talks, developer community content) are coordinated with Developer Advocacy. Design Strategy does not publish externally without that coordination in place.
Debut formats
Offsites, team all hands, and leadership reviews are high-value debut moments. Work scheduled for these should not be shared beforehand, including with executives. The debut is the point.
Concept manifesto videos are a format for introducing a concept to a broader internal audience, and sometimes externally. A manifesto frames the effort, the target, and the change the concept is designed to inspire. They are produced once there is something to show and a debut moment is defined, and are introduced through a planned moment rather than released informally.
Working with collaborators
Concept work regularly requires people outside Design Strategy: a security engineer who understands a trust model, a stage group designer who knows a domain, an engineer who can assess what is technically plausible. Bringing those people in is expected and does not conflict with release discipline.
The distinction to maintain is collaborator versus audience. A collaborator is inside the work, contributing to something still being formed. An audience is someone being introduced to something ready to be seen. Release phases apply to audiences. Collaborators join the dark phase alongside the concept team.
When someone from another team joins active concept work, they are part of the working group. That means the work stays within that group until a debut has been planned. It should not be referenced in other channels, shared with other teams, or mentioned in conversations with leadership outside the working group.
A brief note at the start of the collaboration sets that expectation clearly: “We are in early exploration on this and keeping it close for now. Once we are ready to share more broadly, we will do that together.”
Whoever brings a collaborator into the work is responsible for setting that expectation at the start of the engagement.
Default position
When in doubt, hold. A concept that reaches its audience at the right moment, with the right framing, does more for Design Strategy and for GitLab than one that circulates early and arrives at its intended debut already familiar.
If someone asks for a walkthrough or preview before a concept’s planned debut, redirect them to the debut. That moment exists for a reason.
c4452569)
