The CDO argues that one-size-fits-all structures are ineffective. He believes management's true job is to thoughtfully and dynamically create the right rituals, structures, and processes for each unique combination of problem, people, and timeline, rather than forcing teams into a pre-defined box.

Related Insights

To avoid stifling teams with bureaucracy, leaders should provide slightly less structure than seems necessary. This approach, described as "give ground grudgingly," forces teams to think actively and prevents the feeling of "walking in the muck" that comes from excessive process. It's a sign of a healthy system when people feel they need a bit more structure, not less.

To increase agility, Shopify is dismantling permanent teams tied to specific product surfaces. It's creating a centralized pool of high-impact individual contributors ('strategic ICs') who are deployed dynamically to own entire user journeys, a model exemplified by its acquisition of the MOLLY studio.

To move beyond static playbooks, treat your team's ways of working (e.g., meetings, frameworks) as a product. Define the problem they solve, for whom, and what success looks like. This approach allows for public reflection and iterative improvement based on whether the process is achieving its goal.

In an AI-driven world, product teams should operate like a busy shipyard: seemingly chaotic but underpinned by high skill and careful communication. This cross-functional pod (PM, Eng, Design, Research, Data, Marketing) collaborates constantly, breaking down traditional processes like standups.

The team avoids traditional design reviews and handoffs, fostering a "process-allergic" culture where everyone obsessively builds and iterates directly on the product. This chaotic but passionate approach is key to their speed and quality, allowing them to move fast, make mistakes, and fix them quickly.

Company-wide processes like annual planning often become bland and unopinionated to appease all stakeholders and avoid criticism. In contrast, companies with strong cultures often have opinionated leaders who champion specific, quirky rituals, which infuses the entire organization with a distinct and effective character.

The company's design leadership is pushing back against justifying design solely through business metrics, arguing it signals a lack of confidence in craft. They foster a culture where the primary measure of success is the team's own high bar for taste, trusting this will ultimately drive long-term value.

Countering conventional wisdom, Shopify's design leader argues that deep, long-held context often leads to incrementalism. He believes designers can onboard to new problems quickly, and their resulting naivety and fresh perspective are more valuable assets for driving true innovation.

Leaders readily design tangible elements like incentives, job ladders, and meeting agendas. However, they often feel uncomfortable with the idea of intentionally designing the overall "process" or "environment," fearing it's overly controlling or manipulative, despite it being a logical extension of their other design activities.

The traditional "assembly line" model of product development (PM -> Design -> Eng) fails with AI. Instead, teams must operate like a "jazz band," where roles are fluid, members "riff" off each other's work, and territorialism is a failure mode. PMs might code and designers might write specs.