Content Strategy for Mobile
Source: https://abookapart.com/products/content-strategy-for-mobile ↗
McGrane articulated what responsive design alone could not solve: that adapting layout to screen size is meaningless if the content itself was never structured for reuse across contexts.
The book argued that mobile is not a design problem but an editorial and organisational one — companies fail at mobile because their content is trapped in desktop-shaped blobs with no semantic structure, no metadata, and no separation between meaning and presentation.
Published a year after Marcotte's Responsive Web Design, it served as the necessary counterweight: where Marcotte addressed the container, McGrane addressed what goes inside it.
The distinction between adaptive presentation and adaptive content remains one of the most underappreciated ideas in product work.
Central argument
McGrane's central argument is that mobile failure is not a design or technology problem but an editorial and organisational one: companies cannot deliver content effectively across devices because their content was never structured to be device-agnostic in the first place. She distinguishes between adaptive presentation — resizing containers and layouts — and adaptive content, which requires semantic structure, metadata, and a clean separation between meaning and presentation. The book contends that CMS architecture, editorial workflows, and content modelling decisions made years earlier upstream are what actually determine whether a product can work on mobile, not the front-end implementation.
Critique
McGrane's argument is built almost entirely on the publishing and media context of 2012, where the content-as-blob problem was most acute, and it transfers less cleanly to transactional or application-centric products where content in the editorial sense is a minor surface rather than the core value delivery mechanism. The framework also assumes that organisations can converge on a single structured content model, which underestimates how legitimate business-unit divergence, regulatory constraints, or acquisition-driven fragmentation make that convergence politically and architecturally intractable — not merely a failure of will or literacy. A decade on, the rise of headless CMS and composable architectures has partially industrialised her prescriptions, which makes the book more historically instructive than operationally urgent.
Why it matters for product
For a CPO, the book reframes a class of mobile product failures that typically get diagnosed as design debt or engineering capacity problems — the real diagnosis is that no one ever owned content as a structured asset, and that gap sits in the seam between editorial, engineering, and product ownership that nobody's roadmap covers. It also has direct implications for platform strategy: a product organisation that separates content from presentation at the model level gains genuine optionality when new surfaces emerge — voice, native apps, third-party integrations — whereas one that doesn't will pay a structural tax on every new channel investment. McGrane gives CPOs the vocabulary to make that argument to editorial and technology leadership simultaneously, which is where the organisational design conversation actually needs to happen.