Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

Traditional design processes like formal crits were built for a slower, larger-scale era. At Cash App, they systematically delete processes that don't add value, finding that many have become performative rituals that slow down high-velocity, AI-powered teams.

Related Insights

With AI agents completing development tasks in minutes, two-week agile sprints are inefficient. A new "Heartbeat Protocol," replacing stand-ups with hourly telemetry checks, is needed to manage rapid, agent-driven progress.

The traditional, linear handoff from product (PRDs) to design to dev is too slow for AI's rapid iteration cycles. Leading companies merge these roles into smaller, senior teams where design and product deliver functional prototypes directly to engineering, collapsing the feedback loop and accelerating development.

AI tools dramatically reduce the resources needed for idea validation. Leaders should restructure teams by creating small, nimble 'discovery' pods (1-2 people) for rapid idea generation and validation. Successful ideas are then passed to larger, traditional 'execution' teams for scaling and implementation.

In a competitive market, prioritizing speed forces a team to be resourceful and figure out how to maintain quality under pressure. This mindset prevents the design team from becoming a bottleneck and keeps the company's momentum high.

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.

The classic, linear design process is obsolete because AI tools allow engineers to build and iterate so quickly. Designers must shift from a gatekeeping, mock-heavy process to a more fluid, collaborative role that supports rapid execution.

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.

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.

AI co-pilots have accelerated engineering velocity to the point where traditional design-led workflows are now the slowest part of product development. In response, some agile teams are flipping the process, having engineers build a functional prototype first and then creating formal Figma designs and UI polish later.

Don't just plug AI into your current processes, as this often creates more complexity and inefficiency. The correct approach is to discard existing workflows and redesign them from the ground up, based on the new paradigms AI introduces, like skipping a product requirements document entirely.

High-Velocity Teams Should Delete Performative Processes Like Design Crits | RiffOn