Product vs. IT Mindset

Marty Cagan argues that established companies often lose their capacity for continuous innovation, and that a deeper root cause than the usual focus on scale and execution is an "IT mindset" applied to product work. He contrasts IT organizations, which serve internal business requests through funded projects, requirements gathering, and slow waterfall processes, with product organizations, which discover solutions, are measured by outcomes, and collaborate across functions. He traces how pre-Internet companies and big-name hires from them import these habits into growing tech firms. The stakes are high because companies that stop innovating can coast on their brand for years before declining. The piece offers a ten-point diagnostic for leaders to examine their own purpose, funding, process, structure, accountability, and culture.

01Key takeaways

• Diagnose whether your teams serve internal stakeholder requests or customer problems, since this single distinction shapes most other behaviors.
• Shift funding from projects delivered to product teams measured by business outcomes.
• Replace requirement gathering and roadmap delivery with continuous discovery to test which ideas actually work.
• Ensure strong product managers and designers are present, since weak product roles are a telling sign of IT mindset.
• Organize around cross-functional product teams rather than functional silos like engineering, QA, and design.
• Be wary of hiring leaders whose playbook comes from large pre-Internet companies without adapting it to product work.

02Key sections

Innovation as a survival requirement

Cagan opens by framing continuous value creation as essential, noting that established product teams often drift into minor optimizations. He draws on Reid Hoffman's view that a company not investing in tomorrow is already dying.

Existing explanations: war time and scale

He credits Ben Horowitz's war-time versus peace-time analogy and Steve Blank's critique of execution processes that crowd out innovation as partial explanations.

The IT mindset as a deeper root cause

Drawing on his HP experience, Cagan explains that IT departments building internal tools behave differently from teams building commercial products, and that this difference becomes a business continuity problem once the Internet arrives.

Ten contrasts between IT and product organizations

He compares the two across purpose, passion, requirements, staffing, funding, process, silos, organization, accountability, and leadership, showing how most differences stem from the first one: serving the business versus serving customers.

Leadership and the path forward

Cagan notes that large companies like Apple, Google, Amazon, and Netflix innovate consistently, and concludes that leadership must build the culture that nurtures continuous innovation.

03From the post

“A partnership dedicated to teaching best practices to product teams and product leaders”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.