Question 1

How does McGrane's argument about content structure differ from the responsive design approach Marcotte popularized?

Accepted Answer

McGrane identifies a critical gap that responsive design alone cannot solve: adapting layout to different screens is ineffective if the underlying content lacks semantic structure, metadata, and separation between meaning and presentation. While Marcotte addressed the container (how layouts adapt), McGrane addressed what goes inside it—arguing that companies fail at mobile because their content is trapped in desktop-shaped blobs with no reusability across contexts.

Question 2

Why should product leaders view mobile challenges as organizational problems rather than design problems?

Accepted Answer

McGrane argues that mobile success depends on how content is structured and governed across the organization, not just visual adaptation. If your CMS, content model, and editorial workflow are built around desktop delivery, no amount of responsive design will create a functional mobile experience. The constraint is upstream—in how companies organize and think about their content.

Question 3

Is this book still relevant if our team already uses responsive design?

Accepted Answer

Yes. The distinction between adaptive presentation (responsive design) and adaptive content (McGrane's focus) remains underappreciated in product work. If your content strategy hasn't evolved since adopting responsive layouts, you're likely experiencing the same structural problems McGrane identified—content that doesn't reuse well, lacks metadata, and requires duplication across platforms.