In fast-paced environments, the primary concern isn't that craft will suffer, but that teams will cut the crucial time needed for strategic alignment. In cultures where high craft is a given, like at Vercel, the real risk of compressed timelines is building a beautiful solution to the wrong problem.
Related Insights
As articulated by Eric Ries in 'The Lean Startup,' raw speed of shipping is meaningless if you're building in the wrong direction. The true measure of progress is how quickly a team can validate assumptions and learn what customers want, which prevents costly rework.
A product roadmap's value is in the planning process and aligning the team on a vision, not in rigidly adhering to a delivery schedule. The co-founder of Artist argues that becoming a feature factory focused on checking boxes off a roadmap is a dangerous trap that distracts from solving real customer problems.
AI tools accelerate development but don't improve judgment, creating a risk of building solutions for the wrong problems more quickly. Premortems become more critical to combat this 'false confidence of faster output' and force the shift from 'can we build it?' to 'should we build it?'.
The conventional wisdom that you must sacrifice one of quality, price, or speed is flawed. High-performance teams reject this trade-off, understanding that improving quality is the primary lever. Higher quality reduces rework and defects, which naturally leads to lower long-term costs and faster delivery, creating a virtuous cycle.
Instead of killing underperforming products, Vercel's culture encourages teams to find the valuable "nugget" within an idea and continuously iterate. Products don't die; they evolve through collaborative feedback, avoiding the typical "product cemetery" seen at other tech giants.
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.
Similar to technical debt, "narrative debt" accrues when teams celebrate speed and output while neglecting shared understanding. This gap registers as momentum, not risk, making the system fragile while metrics still look healthy.
The popular tech mantra is incomplete. Moving fast is valuable only when paired with rapid learning from what breaks. Without a structured process for analyzing failures, 'moving fast' devolves into directionless, costly activity that burns out talent and capital without making progress, like a Tasmanian devil.
Don't accept the excuse that moving faster means sacrificing quality. The best performers, particularly in engineering, deliver both high speed and high quality. Leaders should demand both, framing it as an expectation for top talent, not an impossible choice.
The misconception that discovery slows down delivery is dangerous. Like stretching before a race prevents injury, proper, time-boxed discovery prevents building the wrong thing. This avoids costly code rewrites and iterative launches that miss the mark, ultimately speeding up the delivery of a successful product.
