General Assembly / Go-to-market operations
Turning launch readiness into a business capability.
Why this was a business priority
A launch process connects responsibilities, dependencies and resources across teams. ISO’s process guidance and GitLab’s launch practice show why that matters: consistent execution depends on coordinated work, clear ownership and learning. GA recognized the need for a shared approach to that work.
Context: ISO process approach guidance; GitLab Product Launch handbook.
The business stakes
A launch commitment depended on readiness across the teams bringing it to market.
At General Assembly, Product needed clarity on when to involve Marketing and what launch planning required. Marketing and Sales needed earlier visibility into upcoming products and audiences, along with the preparation required of each team.
The work made those expectations explicit: what each launch tier included, who was responsible and how much time each team needed. A GTM task force brought that shared understanding into how launches were formulated and executed.
The organizational change
How the organization changed
Teams knew what a launch required of them.
Tiering connected the ambition of a launch to the work required to support it. Clear responsibilities and lead times gave teams a common basis for planning, and the GTM task force carried that structure into execution.
01 / Launch tiers defined the commitment
Teams knew what was included in each tier and what level of preparation a launch required. The scope of a launch became an explicit shared expectation.
Why it mattered: teams faced less uncertainty about what each launch required.
02 / Ownership and lead times made readiness concrete
Each team understood its expected contribution and the time needed to deliver it. Scope, responsibilities and preparation time could be considered together.
Why it mattered: launch planning could account for the work across functions, with handoffs and dependencies visible before execution.
03 / A GTM task force put the model to work
A cross-functional GTM task force was established to ensure launches were formulated and executed with processes and feedback loops in mind.
Why it mattered: the organization had a group responsible for carrying the launch approach into practice and keeping learning part of the process.
Strategy in practice / AI courses
Preparing AI courses for the US and international markets.
Making AI learning relevant to the people responsible for putting it to work.
The launch work
Turn a broad category into a relevant offer
The AI materials framed a practical adoption barrier: organizations needed the skills to put AI to work. Positioning differentiated the needs of leaders, technical specialists and business teams, connecting the offer to the decisions and work each audience faced.
That audience structure gave messaging a sharper purpose. Leaders needed to make informed strategic decisions; technical teams needed implementation capabilities; business teams needed practical applications. International adaptability was considered through language, industry context and local delivery.
The wider engagement included detailed IT and cybersecurity competitive analysis, translating market comparisons into differentiation and sales messaging.
A capability that carries forward
Launch execution became part of a learning process.
The GTM task force brought process and feedback loops into launch formulation and execution. Performance review and feedback had a place in the operating approach, connecting each launch to how the organization prepared for the next.
The operating cycle
01 / Define
Establish launch scope and the expectations for its tier.
02 / Coordinate
Align team responsibilities, dependencies and lead times.
03 / Execute
Bring the plan into practice through the GTM task force.
04 / Learn
Use feedback to inform future launch processes and preparation.
Conceptual view of the operating approach.
Make time to market measurable
The model gave GA the ability to measure time to market and streamline domestic and international launches. Tiered expectations, team ownership and lead times provided a common structure for that work. Feedback loops connected execution with future launch SOPs, giving the organization a way to improve its process as it learned.
Adoption beyond a single launch
6+ launches. Five teams. An organization-wide standard.Measurable time to market. A repeatable approach across domestic and international launches.