Most publishers organize around editorial and business departments. Editorial creates content, business handles revenue. This made sense for print but it leaves gaps in digital operations.

Product management fills those gaps by focusing on reader experience, technical product development, and optimizing how journalism is delivered through digital products.

What Product Managers Do

Product managers define what gets built and why. They prioritize features for websites, apps, and digital products based on user needs and business goals.

In publishing context, this means deciding which site improvements matter most, what newsletter formats to test, how paywalls should behave, what analytics to prioritize.

They work between editorial, engineering, design, and business teams to align everyone on what you’re building and why it matters.

Why Publishers Need This

Editorial teams focus on content quality and coverage. They’re not typically thinking about user flows, technical architecture, or product optimization.

Engineering teams can build what they’re asked to build but need someone defining what to build and why. Without product management, requirements are often vague or conflicting.

Business teams understand revenue goals but may not understand technical constraints or user experience implications of their requests.

Product managers bridge these gaps, translating between different functional perspectives.

The Reader Experience Gap

Nobody at many publishers has explicit responsibility for reader experience across touchpoints. Articles might be great but navigation is confusing, or subscription flows are frustrating.

Product managers own this holistic experience. They ensure technical implementation, editorial content, and business requirements combine into coherent reader journey.

This is distinct from editorial judgment about content quality. It’s about how readers discover, consume, and interact with that content.

Data-Informed Decisions

Product managers use data to validate decisions rather than relying solely on opinions. What features do readers actually use? Where do subscription funnels break down? What content formats drive engagement?

They run experiments, analyze results, and iterate based on evidence. This complements editorial judgment with empirical validation.

Different from pure analytics roles because product managers make decisions based on data rather than just reporting numbers.

Prioritization Framework

Publishers have endless potential improvements and limited resources. Product managers prioritize what to build based on impact and effort.

High-impact, low-effort improvements get prioritized. Low-impact, high-effort projects get deferred regardless of how interesting they seem.

This prevents teams from building features that nobody asked for or optimizing things that don’t matter while ignoring major friction points.

Roadmap Management

Product managers maintain roadmaps showing what’s being built when and why. This creates transparency and alignment across teams.

Editorial knows what technical capabilities are coming. Engineering knows what business priorities drive their work. Leadership sees how resources are allocated.

Roadmaps change based on new information, but having an explicit plan that can be discussed and adjusted beats ad-hoc decision making.

User Research Integration

Product managers ensure reader feedback and behavior inform product decisions. This might be formal user research or analyzing support tickets and behavioral data.

They identify friction points readers experience and prioritize fixes. They validate whether proposed features actually solve problems readers have.

This prevents building features teams think are good ideas but readers don’t actually want or use.

Technical Feasibility Balance

Product managers need enough technical understanding to have informed conversations with engineering about what’s possible and at what cost.

They can’t just dream up features without considering implementation complexity. But they also push engineering to find solutions rather than accepting “that’s impossible” when it’s really “that’s hard.”

This balance ensures ambition stays grounded in reality while reality doesn’t become excuse for lack of ambition.

A/B Testing and Experimentation

Good product management is iterative. Test hypotheses, measure results, learn, adjust. Don’t build major features without validation.

Product managers design tests, define success metrics, analyze results, and decide whether to ship, iterate, or abandon based on evidence.

This reduces risk of major investments in features that don’t deliver expected value.

Subscription Product Optimization

For subscription publishers, the subscription product itself needs active management. Pricing, packaging, trial periods, onboarding, retention tactics.

Product managers optimize conversion funnels, identify churn risks, test retention strategies. This complements marketing’s acquisition work with product-based retention improvement.

Small improvements in conversion or retention rates have compounding business impact. Product management focus here directly affects sustainability.

Newsletter as Products

Email newsletters are products requiring product thinking. Format, frequency, content mix, segmentation, personalization - all product decisions.

Product managers help editorial teams think about newsletters as products serving specific reader needs, not just additional distribution channels.

They track engagement metrics and run tests to improve performance rather than assuming current format is optimal.

Mobile App Management

For publishers with apps, product managers ensure apps serve reader needs and support business goals rather than just replicating website functionality.

Apps have different usage patterns and capabilities than web. Product thinking identifies what makes sense to build native versus web.

App store dynamics, platform requirements, update cycles - product managers handle these operational aspects that don’t fit neatly in editorial or engineering.

Platform Relationship Management

Relationships with Apple News, Google News, social platforms require product thinking. What content to provide, how to optimize for platform requirements, whether participation makes sense.

Product managers evaluate these opportunities against strategic goals and resource costs rather than just accepting every platform partnership.

Content Management System Decisions

CMS selection and optimization significantly impacts editorial productivity and what’s possible to publish. Product managers ensure technical systems support editorial and business needs.

They gather requirements from editorial, evaluate options, manage implementation, and continuously optimize CMS workflows.

This prevents situations where editorial teams struggle with inadequate tools because nobody with authority is focused on improving them.

Analytics and Measurement

Product managers define what to measure and why. They ensure teams have data needed for decisions without drowning in irrelevant metrics.

They work with analytics teams or vendors to implement tracking, build dashboards, and make data accessible and actionable.

Revenue Product Integration

Advertising implementation, paywall behavior, subscription flows, sponsor content systems - these are products requiring management.

Product managers ensure monetization systems work well without degrading reader experience more than necessary. They find balance between revenue optimization and user experience.

Stakeholder Management

Product managers communicate upward to leadership about product strategy and progress. They manage expectations about what’s possible and educate about product thinking.

They also work across to peers in editorial, engineering, design, and business to build consensus around priorities.

Hiring Product Talent

Publishers struggle to hire product managers because they’re competing with tech companies offering higher salaries.

Successful hires often come from people passionate about journalism willing to accept lower pay for mission-driven work. Or from within organizations - journalists, editors, or business staff who develop product skills.

Pure tech background without media experience often doesn’t work. Product managers need to understand journalism values and publishing economics.

Building Product Culture

Product management is cultural as much as functional. It requires organization-wide acceptance that product thinking matters.

Editorial teams need to collaborate with product rather than viewing it as business interference. Engineering needs to see product as partner rather than just requirements source.

Leadership needs to empower product decisions and accept data-driven iteration over executive intuition for product questions.

When You Don’t Need It

Very small publishers might not justify dedicated product management. Editorial leaders can incorporate product thinking into their roles.

Publications that are pure content plays without significant technical product surface might not need product management. If you’re just producing articles and distributing through third parties, product management is less critical.

Getting Started

If you don’t have product management, start by identifying the gaps. Who makes decisions about digital experience? Who prioritizes technical work? Who optimizes conversion and retention?

If answers are “nobody” or “whoever’s loudest,” you have a problem product management would solve.

Start small. Product management doesn’t require large teams. One good product manager can have significant impact by bringing structure and user focus to product decisions.

Publishers who’ve added product management generally see improvements in reader experience, technical execution, and business performance. It’s an investment that pays off through better product decisions across the organization.