A magazine editor, a newsroom lead, an e-commerce merchandiser, and a subscriptions operator walk into the same technical meeting. Each needs a platform that fits their work. As a rough design rule, I think of 70 to 80 percent of their capabilities as common: a way to model content or customers, a way to render or deliver, a way to measure, a way to monetize. The remaining 20 to 30 percent is where the individual brand or business lives. That combination makes shared platforms worth building and difficult to get right.
In my first year leading technology platforms across a group of media businesses, I kept coming back to this problem. Business units wanted autonomy over their product experience. Finance wanted shared infrastructure without paying for the same capability four times. Engineers wanted to ship something new instead of rebuilding something old. A well-designed platform could give each of them a reason to support the same investment.
Similar capabilities, different publications
A common software architecture puts a shared platform underneath specialized applications. In media, the applications can look almost identical from a distance and diverge sharply up close.
A fashion magazine site, a car enthusiast site, and a local news brand may all need an article page with images, author bios, related content, and a subscription call to action. The fashion brand cares about shoppable editorial and the visual density of hero images. The enthusiast brand cares about model specs, buying guides, and a reference library that readers return to over years. The news brand cares about recency, verification metadata, and the weight of a byline. Forcing those needs into a single rigid article template gives every editor something to work around.
I want a platform to make firm choices about its common foundation while giving brands room to shape the reader's experience. I would share content modeling, identity, entitlements, search infrastructure, analytics, and delivery across brands. Design systems, page composition, editorial tools, and revenue placement need flexibility. The boundary takes thought: a choice that looks local on a page may affect a promise made across several publications.
The three failures I watch for
Over decades of watching media platform efforts from inside and outside, I have seen three failure patterns recur.
The first is the universal CMS fantasy. A team builds one content management system intended to serve every brand. The effort to accommodate every committee leaves editors with a tool that fits none of their workflows well. They work around it. Product managers layer a second CMS on top of the first. The company can report that everyone shares a platform while its people do their work elsewhere.
The second is the per-brand fiefdom. Each business unit keeps its own stack for historical reasons, and the company pays for the same capabilities many times over. Familiarity becomes the argument for preserving each system. A cross-brand commerce, newsletter, or video initiative can then spend a year in integration before anything ships. The price of that autonomy includes the opportunities the portfolio cannot pursue together.
The third is the platform that is correct in principle and late in practice. The architecture is elegant and the capabilities are right, but the team delivers six months after the business need has moved. Platform work has to be sequenced against the commercial calendar. A technically sensible roadmap that misses the moment when a brand needs to launch can still fail the business.
Run the platform as a product
A healthy platform team serves internal customers with the attention a consumer product team gives its users. Editors, producers, commerce merchandisers, and subscription operators need a delivery cadence they can plan around. The team should measure adoption alongside availability. A service can stay online all year and still be a poor tool for the people expected to use it.
When a brand opts out, I want the platform team to investigate what the product failed to provide. Punishing the brand for a political loss will not reveal why an editor found another way to publish. Understanding that decision may improve the platform for several brands at once.
This work needs people who are often more senior and more generalist than business stakeholders expect. I look for engineers who have shipped at consumer scale, product managers who have managed a profit-and-loss statement, and designers who understand both editorial craft and interaction systems. Operations people keep the shared foundation dependable. Staffing this work with the cheapest available pool and then wondering why the results feel cheap is a poor economy.
Say yes to the outcome
When a request arrives from a brand, I ask our teams what it would look like to say yes to the intent while reconsidering the requested implementation. An editor asking for a new article template may need more editorial flexibility. A commerce lead asking for a new product page may be seeking better conversion. Configuration and composition can sometimes deliver those outcomes in a form other brands can use. Repeated bespoke implementations consume the team's capacity and make the next shared improvement harder.
I also ask: what will this look like across twenty brands in three years? A choice that helps one brand for one quarter can be the right choice. A choice that quietly hurts nineteen others for three years deserves a different discussion.
Consider two magazines using the same publishing software. One team wants to narrow its advertising column to give photographs more space. Its designers see a change to their page. Someone supplying an advertisement intended to run on both sites may see a change to what they were asked to deliver. I'd start by asking what the new layout still has to accommodate.
In its account of work with Hearst Magazines, Code and Theory describes a gallery module that can be adapted to different magazine identities. It also describes a common advertising arrangement that lets inventory be sold across publications. Reusing a capability and offering something collectively are different reasons to share. A collective offer brings obligations to the other participants.
For these two magazines, the promise might be that an advertisement supplied in an agreed shape will fit a particular placement on both sites. That is a contract in the engineering sense: a promise about how the parts work together. Each magazine can have its own design while making room for the formats it supports.
A 2017 IAB Tech Lab discussion of flexible ad containers describes an ad preserving its width-to-height ratio while fitting the available space. Both the publisher and the ad supplier have responsibilities: a wrongly prepared container can cause bad rendering, while leaving sizing entirely to the supplied ad can let the page shift as it loads.
I would compare the proposed and existing pages using the same sample advertisement, with an image and readable text. An empty rectangle can conceal clipping and legibility problems. Try the narrow and wide limits the format is supposed to support, and watch the surrounding story as the ad arrives. An ad can keep its proportions yet become unreadable. A story can move underneath the reader even when the advertisement looks right. Cover the variations the shared format permits; one successful sample cannot stand in for all of them.
If the new layout meets those expectations, the magazine should be free to use it. Fonts and colors also deserve attention for their effect on readability and usability. Judge the consequences of the change rather than treating everything made in a design tool as either harmless or centrally controlled.
A better page can also justify changing the shared promise. If a narrower format improves a photography-led magazine but cannot accommodate the existing advertisement, define a different supported format or keep that placement out of the shared offering. The people arranging a campaign need to know which magazines can accept it before supplying the ad. Put the commercial cost beside the benefit to the reader. Sharing software cannot decide how much advertising belongs next to a photograph; it can make that choice's consequences clear.
Invest in the quiet work
Platform work rarely makes press releases. A good year might mean ten brands moving onto shared infrastructure, lower costs, faster delivery of new features, fewer outages, and happier editors. Those are substantial achievements even when no individual release attracts much attention. The company should reward the people doing this work and treat the platform roadmap as part of its commercial strategy.
During that first year, I hired engineers, product managers, and designers who understood that platform progress has to be judged across quarters and years. I want them to deliver useful improvements along the way and build capabilities the next brand can adopt. That requires sustained investment in the team, attention to the brands it serves, and a leadership willingness to fund work whose value grows through repeated use.