Key Takeaways
Treat the screen as a constraint, not a clue to user intent.
A device reveals little. A phone does not tell you whether someone is rushing, relaxing, researching, or trying to finish a complicated task. People use mobile devices at home and at work, and they may read deeply or simply look up one fact. In the book's 2012 evidence, 86 percent of smartphone owners had used their phone to seek information, while 31 percent of Americans who accessed the internet by phone said they mostly or always did so that way. Those figures are historical, but they illustrate a lasting risk: designing around an imagined mobile persona instead of real user needs.
Access changes the stakes. Mobile-first internet use was more common among lower-income users, young adults, and racial minorities. For some, a phone was not a convenient second screen. It was the main route online. A desktop-first assumption could therefore exclude the very people an organization needs to reach.
What's useful here is the distinction between a device and a goal. Treating phone users as a single behavioral segment confuses the channel with the person, much as assuming every library visitor wants the same book because they entered through the same door would. A better research question is what people are trying to accomplish, then how their device affects that effort. The access argument also widens the design brief: mobile compatibility can be a matter of inclusion, not just convenience. The caution is that demographic patterns describe groups, not individual intent, so they should guide inquiry rather than dictate design.
Give mobile readers the same essential information, not a stripped-down detour.
Information is a task. Mobile design often prioritizes quick transactions and location tools while omitting explanatory content. But users also search, compare, read, and make decisions on phones. The book's United Airlines example makes the failure concrete: a search result for membership details redirected a mobile user to the site's homepage, where the answer was hard to find. The user wanted one piece of information, not a flight-booking feature.
Parity is about access. Content parity means users can get substantially equivalent information across platforms, even when each platform presents it differently. The author argues against hiding material merely because a team assumes mobile users will not need it. In practice, a useful mobile experience may emphasize common tasks, but it should not make other valuable content disappear or force users to restart their search on a desktop site.
This principle resembles a basic rule of public service design: preserve access to the underlying service even when the interface changes. It also guards against a common measurement trap. If a mobile site omits a topic, low visits to that topic cannot prove that users do not want it. Yet parity need not mean identical prominence. A phone interface has limited space, and prioritization can reduce clutter without denying access. The important distinction is between organizing information for a screen and deciding, without evidence, that certain readers do not deserve it.
Store content as reusable assets, not separate versions of every site.
Build once, adapt deliberately. Adaptive content is content created and managed so it can be reused across platforms, assembled in different ways, and presented in forms suited to each destination. It depends on reusable material, meaningful structure and metadata, presentation separate from the text, and tools that support authors in creating it.
Duplication compounds. A retailer that maintains separate desktop and mobile homepages can end up showing seasonal messages that contradict each other. A publisher may multiply labor even more: Condé Nast staff prepared print layouts and then reworked editions for tablet orientations, while the additional effort did not guarantee readership. NPR offers a different model. Its story elements, including text, audio, images, and summaries, could be selected and displayed by websites, apps, and audio players. Reuse does not mean every outlet looks alike. It means one maintained source can support distinct experiences.
The shift from pages to reusable assets echoes modular software design: stable components can serve different interfaces without requiring a separate copy for each one. The organizational payoff is not simply fewer edits. A shared source makes consistency easier to achieve and clarifies which team owns an update. Reuse does have limits. A message written for one setting may lose tone or meaning elsewhere, so a content system needs room for purposeful alternatives, not just one universal version. The strongest model treats reuse as a choice supported by structure, rather than an automatic command to recycle everything.
Model content in meaningful pieces before asking platforms to rearrange it.
Replace blobs with defined parts. Content modeling is the process of identifying content types, their fields, limits, and relationships. Instead of one large body field holding text, images, and tables, a model might give a product its own description, specifications, images, and summary. Those pieces can then be assembled for different needs.
Structure unlocks new uses. Tumblr's editing interface, for instance, treated photos, quotes, audio, and links as distinct types, with fields suited to each. The book's Tech Guy Labs case began with a wiki where episode details and caller questions were buried in unstructured text. Reorganizing the site around episodes and segments made the material easier to browse and opened the possibility of a smartphone listening app and maps based on caller locations. More structure asks more of authors, so the model must reflect how they work and what readers need.
A content model is a form of domain modeling: it makes an organization's ideas explicit enough for software to use. That can improve both retrieval and product development because relationships are no longer hidden in prose. The useful test is whether a field captures a real distinction that matters to authors, readers, or downstream systems. Over-modeling creates its own burden, however. If authors face dozens of confusing fields, they may avoid the system or enter unreliable data. Structure succeeds when it represents the subject faithfully and makes the work easier, not when it merely satisfies a technical diagram.
Put meaning in metadata, not in formatting that disappears elsewhere.
Appearance is fragile. A bold label may look like an author name, a date, or a priority marker, but styling alone does not tell another platform what that element means. Metadata is information attached to content that identifies or describes it, such as topic, author, date, or priority. It lets systems sort, select, and present material without relying on one layout.
Structure can outlast a format. TV Guide separated its program information from the magazine presentation, storing show titles, genres, and multiple summaries in a database. That made the information searchable and reusable beyond print. The book contrasts the database's enduring value with the magazine brand's sale for one dollar. The Guardian also translated editorial judgments into data so an iPad edition could use them, rather than depending on the original print layout to convey which stories mattered.
Metadata acts like a semantic layer between an idea and its display. That separation is central to accessible technology, too: a screen reader or a search system needs explicit meaning, not just visual emphasis. The TV Guide story makes the economic point sharply. A format can be valuable in its moment, while structured information can support products not yet imagined. But metadata is not free. Categories and priorities can become inconsistent or stale, so assigning fields without ownership merely moves ambiguity into a database. The durable asset is not data alone, but data whose meaning is maintained.
Use the mobile audit to improve the whole content estate.
Count before judging. A content inventory records what exists, where it lives, who owns it, and relevant facts such as age, visits, and format. A content audit evaluates quality and usefulness. Looking through a mobile lens can reveal oversized pages, unreadable tables, outdated documents, or content that depends on unsupported media. For very large sites, a representative sample of sections and content types can expose recurring patterns without inspecting every page first.
Turn findings into decisions. A gap analysis compares current content with what the organization needs and assigns an action: keep, revise, remove, or create. The goal is not a beautiful spreadsheet. It is agreement about what should change. The author also recommends using mobile constraints to sharpen writing for everyone: state the main point early, use plain language, and give each paragraph one clear job.
This process resembles an organizational audit more than a copyediting pass. It surfaces ownership, duplication, and neglect alongside writing problems, which explains why the spreadsheet can become a tool for negotiation. A mobile review also exposes hidden dependencies, such as information trapped in PDFs or content that only works in a wide table. One caution: deleting low-traffic material can be premature. A page may serve a small audience with high stakes, or receive little traffic because it is difficult to find. Analytics should inform editorial judgment, not replace it.
Write headlines and summaries as reusable navigation, not accidental excerpts.
Links need useful clues. A page title may appear as a heading, a search result, a social post, or a link on a small screen. One headline may not fit every setting, but creating a separate version for every device invites needless work. A small system of alternatives, such as shorter and longer versions or human-focused and search-focused versions, can cover many uses.
Summaries deserve authorship. A navigation teaser should help someone decide whether to tap, not be a random slice of body text followed by an ellipsis. The book contrasts Amazon's truncated product copy with Netflix's use of just two summary lengths across more than 400 device types. Progressive disclosure means revealing information in stages while giving users enough context to choose the next step. Clear labels and concise summaries make that choice easier.
This is information scent in editorial form: people follow labels that signal a credible path to what they need. A teaser is not merely a smaller piece of content; it is a decision aid, and its quality affects whether readers trust the next tap. The design insight is to create a few purposeful variants rather than a bloated menu of device-specific fields. Still, summaries can oversell or flatten nuance. Their usefulness depends on editorial accuracy, especially when a short description stands in for a complex policy, product, or health topic.
Let readers scroll long content, but give them ways to jump.
Do not confuse small screens with short attention. The book rejects automatic pagination as a mobile solution. On touchscreens, scrolling can be easier than repeatedly tapping through pages, and forced breaks can interrupt a recipe or even split a sentence. Long text should remain readable when length serves the subject.
Make the structure navigable. Readers looking for one detail need headings, anchor links, or expandable sections that let them move directly to it. Tables need special treatment because turning side-by-side comparisons into a narrow column can destroy their meaning. Images and infographics may need alternative crops or a text explanation; shrinking a dense graphic can make its information unreadable while still consuming bandwidth. The author suggests developing a limited system of image sizes rather than producing a unique crop for each device.
This is a useful correction to the idea that a phone is only for brief encounters. Reading length should follow the user's purpose, while navigation should reduce the effort of finding a particular section. That distinction matters in reference material, instructions, and comparisons, where a short page can be less usable than a long but well-organized one. Scrolling is not automatically ideal, though. Very long pages can make orientation difficult, and images may require genuine redesign rather than resizing. The governing question is whether the presentation preserves the relationships that make the information understandable.
Treat publishing as an organizational system, not a device launch.
Tools cannot fix ownership alone. Multi-channel publishing needs clear responsibility for editing, metadata, media alternatives, approvals, and urgent updates. A coupled CMS ties authoring and content display closely together, while a decoupled CMS separates content management from the systems that present it. The right arrangement depends on the organization, but its workflow must support reuse without making authors fight the interface.
The mission can justify the change. The American Cancer Society decided that its health information needed to be available on phones, especially because communities with lower broadband access could depend on mobile. It used a single publishing workflow and separate mobile templates rather than waiting for a costly CMS overhaul or responsive redesign. After launch, mobile visits nearly doubled. The example shows how research, a defined goal, and a pragmatic technical choice can make broad access achievable.
The book's strongest operational insight is that publishing technology is sociotechnical: software, roles, incentives, and review practices jointly determine whether content stays accurate. That perspective helps explain why a technically elegant app can fail if updates are duplicated or legal review cannot follow content into new formats. The cancer organization case also shows the value of a pragmatic path, not a perfect architecture. Its increased visits indicate demand, though they do not by themselves prove improved health outcomes. Measurement should connect reach to the actual mission, especially when the subject is consequential.
Analysis
The book's central move is to redefine mobile publishing as a content and organizational problem, rather than a screen-design problem. Once users can arrive through phones, tablets, social links, or search, a website is no longer a single destination. The durable unit becomes a managed package of information that can be selected and presented in multiple settings. That shift links editorial practice to information architecture, software design, accessibility, and governance.
Its most persuasive argument is against guessing what a mobile user wants and then withholding everything else. The United Airlines example makes the cost vivid: a searcher asking a specific question is sent to a generic homepage. The framework that follows is practical: inventory content, judge its usefulness, model it into reusable parts, attach meaning through metadata, and change the workflows that govern it. The book also avoids prescribing one universal front-end solution. Responsive design, separate templates, and different CMS arrangements are treated as choices shaped by local constraints.
The work's key tension is between parity and prioritization. Making all content accessible is not the same as displaying all content at once. Good structure enables a simpler interface without turning simplicity into exclusion. Likewise, reuse reduces duplicate maintenance, but it cannot guarantee that one version will fit every audience or context. The strongest application combines a shared source of truth with carefully chosen variants and research-based presentation.
The evidence needs historical context. Many statistics and examples describe 2012, so the percentages should not be mistaken for current usage estimates. The case studies are persuasive illustrations, not controlled tests proving that a particular content architecture caused every reported outcome. The deeper claim survives those limits: organizations should build publishing systems around their information and users, rather than around the assumption that the desktop page is the original and every other channel is an afterthought. For contemporary teams, the book is most valuable as a method for exposing the hidden work behind apparently simple digital experiences.
Review Summary
Content Strategy for Mobile receives mostly positive reviews, with readers praising its practical advice on creating adaptive content for multiple platforms. Many appreciate McGrane's arguments for separating content from presentation and structuring it with metadata. The book is seen as valuable for content strategists and web professionals, offering insights on improving overall content quality. Some readers find the content repetitive or outdated, but most consider it a useful guide for organizations transitioning to mobile-friendly content strategies. The book's emphasis on making all content available across devices resonates with many readers.
People Also Read
Glossary
Adaptive content
Reusable, structured contentContent created and managed for use across multiple platforms and contexts. It is organized into meaningful pieces, kept separate from any single visual presentation, and accompanied by metadata that helps systems select and display it. Adaptive content supports different experiences without requiring teams to maintain a separate copy of every page for every device.
Content parity
Equivalent access across platformsThe principle that users should be able to access substantially equivalent information on different devices. The content does not need to look identical everywhere. Where a format cannot be reused, an appropriate alternative can provide the same essential information, rather than sending users to another device or omitting it.
Create Once, Publish Everywhere (COPE)
One source, many presentationsAn approach associated in the book with NPR. Content is created and stored as structured elements, then delivered to different platforms that can select and present those elements in ways suited to their needs. A story might combine text, audio, images, and summaries differently in a website, app, or audio player.
Content modeling
Defining content structureThe process of specifying the types of content an organization manages, the attributes each type contains, limits on those attributes, and relationships among types. A model might define an episode, its segments, guest details, and topics. This structure makes content easier to search, reuse, and publish in different combinations.
Content package
Related reusable content elementsA managed collection of content elements associated with one subject or item, such as an article or product. It can include a main text, headlines, summaries, images, or alternative media. Keeping related elements together lets authors and editors update them as one maintained unit instead of managing disconnected copies across sites.
Metadata
Information describing contentData that identifies or describes a content item or element, such as its author, topic, date, format, or priority. Metadata makes content searchable and helps publishing systems filter, organize, or select it. It expresses meaning explicitly, rather than relying on visual styling or placement to communicate what an element represents.
Coupled CMS
Content and display combinedA content management system in which authoring, storage, presentation, and delivery are closely connected within one system. Such a setup may be designed primarily for the desktop website, making it difficult to select and present content differently across channels without substantial customization.
Decoupled CMS
Content separated from presentationA content management arrangement that separates the systems used to create and store content from the applications that display and deliver it. This separation can make multi-channel publishing more flexible because each delivery platform can decide how to present structured content, while drawing from a shared managed source.
Progressive disclosure
Reveal information in stagesA design approach that presents information in steps, allowing users to see enough to make a choice before revealing more detail. In content navigation, a concise description beside a link can help users judge whether to continue. Expandable sections can also let readers choose which parts of a longer page to open.
Content inventory
A record of existing contentA quantitative record of an organization's content assets. It can track where each item lives, its owner, dates, format, visits, and other objective facts. An inventory establishes what exists and how much there is. It does not, by itself, judge whether the content is useful or well written.
Content audit
Evaluation of content qualityA qualitative review of content against criteria such as accuracy, usefulness, clarity, length, structure, and currency. An audit helps an organization decide whether content should remain as it is, be revised, or be removed. It may use inventory data, but its purpose is evaluation rather than counting.
Gap analysis
Plan from current to neededA comparison between the content an organization currently has and the content it needs to meet its goals and serve users. The analysis turns audit findings into actions, such as keeping, revising, deleting, or creating content, and helps teams plan the work required to reach a desired state.
FAQ
1. What is "Content Strategy for Mobile" by Karen McGrane about?
- Holistic content strategy: The book explains how to develop a content strategy that works across all platforms—mobile, tablet, desktop, and beyond—rather than focusing solely on mobile devices.
- Adaptive content focus: It introduces the concept of adaptive content, which is structured, reusable, and presentation-independent, allowing content to be published anywhere.
- Practical guidance: The book provides actionable steps for auditing, editing, structuring, and managing content to ensure it is accessible and effective on any device.
- Organizational change: It emphasizes the need for changes in workflow, tools, and organizational structure to support multi-channel publishing.
2. Why should I read "Content Strategy for Mobile" by Karen McGrane?
- Mobile is unavoidable: The book demonstrates that users increasingly access content on mobile devices, making it essential for organizations to adapt.
- Avoid common pitfalls: It helps readers understand why simply creating a "lite" mobile site or forking content is unsustainable and inefficient.
- Future-proof your content: The advice prepares organizations for new platforms and devices by focusing on content flexibility and reuse.
- Improve user experience: By following the book’s strategies, you can deliver a better, more consistent experience to users regardless of how they access your content.
3. What are the key takeaways from "Content Strategy for Mobile" by Karen McGrane?
- Content parity is crucial: Aim for content parity across platforms—users should never be forced to visit the desktop site for information.
- Adaptive content is the future: Structure content for reuse, with meaningful metadata and presentation independence, to support multi-channel publishing.
- Process and tools matter: Success requires changes in content management systems, editorial workflows, and organizational roles.
- Start with strategy: Even small steps, like analytics and content audits, can move your organization toward a robust mobile content strategy.
4. How does Karen McGrane define "adaptive content" in "Content Strategy for Mobile"?
- Reusable content: Content is created with the intention of being reused across multiple platforms and contexts.
- Structured content: Information is broken into meaningful chunks, not blobs, making it easier to combine and display in different ways.
- Presentation-independent: Content is separated from its visual styling, allowing each platform to present it optimally.
- Metadata-driven: Rich metadata enables platforms to query and display the most appropriate content elements for each context.
- Supportive CMS: The content management system should encourage and facilitate the creation and management of adaptive content packages.
5. What are the main problems with creating separate mobile websites, according to "Content Strategy for Mobile"?
- Content forking: Maintaining separate sites leads to duplicate content, inconsistent updates, and increased workload.
- Unsustainable maintenance: Every change must be made in multiple places, which is inefficient and error-prone.
- User experience issues: Users may encounter missing or outdated information on one version of the site.
- CMS limitations: Most content management systems are not designed to easily support multiple versions of content for different platforms.
6. How does "Content Strategy for Mobile" by Karen McGrane recommend structuring content for multi-channel publishing?
- Content modeling: Define content types, attributes, data limits, and relationships to break content into manageable chunks.
- Packages, not pages: Create content packages with multiple versions (e.g., headlines, summaries, images) for different uses.
- System of headlines and summaries: Write multiple headline and summary versions to fit various contexts and platforms.
- Alternative formats: Prepare alternative content (e.g., text for audio/video, different image crops) to ensure accessibility across devices.
7. What is the role of metadata in "Content Strategy for Mobile" by Karen McGrane?
- Enables flexibility: Metadata allows content to be filtered, sorted, and displayed appropriately on different platforms.
- Supports reuse: Well-defined metadata makes it easier to repurpose content without manual intervention.
- Encodes meaning: Metadata communicates the purpose, priority, and relationships of content elements beyond visual styling.
- Facilitates automation: Metadata-driven systems can automate content delivery and presentation, reducing manual workload.
8. How does "Content Strategy for Mobile" suggest organizations should change their internal processes and teams?
- Leadership alignment: Leaders must evangelize mobile, allocate resources, and break down silos between teams.
- Clear roles and responsibilities: Define who creates, edits, manages, and maintains content packages, metadata, and media assets.
- Editorial workflow updates: Adapt workflows to support multi-channel publishing, including legal review and quality assurance for all platforms.
- Continuous measurement: Implement analytics and user research processes to inform ongoing content strategy decisions.
9. What practical steps does "Content Strategy for Mobile" recommend for getting started with mobile content strategy?
- Analyze analytics: Review data on mobile usage, search queries, and user behavior to identify gaps and opportunities.
- Conduct content inventory and audit: Systematically document and assess all content, focusing on what needs to be revised, deleted, or created for mobile.
- Prototype and test: Use user research and usability testing to validate content decisions and improve the mobile experience.
- Competitive review: Study competitors’ mobile sites and apps to learn best practices and avoid common mistakes.
10. How does "Content Strategy for Mobile" by Karen McGrane address writing and editing for mobile?
- Good writing is universal: There’s no special way to write for mobile—clarity, conciseness, and relevance matter on all platforms.
- Mobile as a lens: Use mobile’s constraints to prioritize and tighten content, removing jargon and unnecessary information.
- Structure for scanning: Use headings, summaries, bullet points, and clear calls to action to facilitate quick reading and navigation.
- Edit ruthlessly: Ensure every word earns its place, and that the main message is immediately clear to the reader.
11. What are some of the most important quotes from "Content Strategy for Mobile" by Karen McGrane, and what do they mean?
- “Get your content ready to go anywhere because it’s going to go everywhere.” (Brad Frost) — Emphasizes the need for content flexibility and future-proofing.
- “The more structure you put into content the freer it will become.” (Rachel Lovinger) — Highlights the paradox that structured content is more adaptable and reusable.
- “Metadata is a love note to the future.” (Jason Scott) — Stresses the long-term value of investing in rich metadata for content.
- “If it shouldn’t be on the mobile site, it shouldn’t be on the desktop site either!” — Encourages organizations to use mobile as a catalyst for improving all content, not just mobile content.
12. What real-world examples and case studies does "Content Strategy for Mobile" by Karen McGrane provide?
- NPR’s COPE model: NPR’s “Create Once, Publish Everywhere” approach demonstrates how structured content and metadata enable multi-platform publishing.
- American Cancer Society: ACS prioritized content parity and mobile accessibility to reach underserved audiences, doubling mobile visits and improving outcomes.
- Retailers and publishers: Examples like Gap, American Eagle, and Condé Nast illustrate the pitfalls of content forking and the benefits of unified workflows.
- Industry-specific insights: The book covers challenges and solutions for advertisers, retailers, publishers, financial services, healthcare, universities, and restaurants, showing the universal need for adaptive content strategy.
A Book Apart Series Series
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.