Skip to main content

The Insourcing Boom in Digital Publishing

Insourcing applies to digital publishing as much as to manufacturers
like GE, which recently restored this assembly line in Kentucky.
After decades in which it's seemed that all kinds of business tasks were inexorably moving offshore in pursuit of lower labor costs, publications like the Harvard Business Review and The Atlantic have begun to note a swing in the opposite direction.   “Insourcing” and “onshoring” are becoming buzzwords as manufacturers start to bring at least some kinds of jobs back in house.  The reasons are many, but key among them are the agility and time-to-market benefits of bringing most product development functions together under one roof.

We’re seeing the same thing in digital publishing, and if you think about it, it makes perfect sense.  Digital publishing is growing and changing as rapidly as any business, and at the same time, most publishing organizations now understand digital to be a core strategic activity essential to their future.

No longer is digital publishing primarily about shipping large backlists out for content conversion, or similar tasks that it has historically made sense to offshore.  Now the focus is on responding quickly to new market opportunities and exploiting the latest technologies.  From what we’re seeing among Tizra’s customers, the publishing organizations that do this best take a “big room” approach, with editorial, design, marketing, sales, production, finance and technology folks all collaborating closely.

Does this mean publishers should try to do everything in house?  Definitely not...any more than than it makes sense to build your own printing presses.  Just as with other publishing functions, you need to determine which functions truly differentiate you from competitors (including "free" information from non-professional sources), and cultivate in-house expertise in those areas.  The rest is all about providing your teams with the very best tools to empower them to carry out your organization's product vision.

For most publishers, this includes shifting many functions from outside or offshore service providers to a powerful, flexible, digital publishing platform like Tizra, which enables them to be self-sufficient and in direct control.  Advantages of the digital platform approach include...

  • Control -- When utilizing an offshore service provider, you lose the direct connection with your content and your audience, reducing control over the user experience, quality, timeliness, commerce options, and more.  Plus, with the rash of mergers and acquisitions in the offshore service provider market, you may find yourself in the position of dealing with turnover, or searching for a new partner.  With directly managed digital publishing software, you keep the key strategic expertise in house, and are in control of your brand, content and audience.
  • Time-to-market -- How many times do you need to add or update ebooks, change pricing and promotional copy, or implement new promotional codes or bundles?  With digital publishing software you can make these changes immediately, providing immediate gratification to your customers.  However, if you are working with an offshore service provider, you have to deal with time zone differences and delays related to submitting, scheduling, and implementing change requests.
  • Audience relationships -- With digital publishing software you are able to sell direct to your audience, meaning that you have full access to and control over all the information relating to your customers.  Instead of providing your digital content to an aggregator or online store such as Apple, Google, or Amazon, you can keep both your customer relationships, and your margins.  By utilizing digital publishing software, you can integrate your econtent storefront into your existing website, under your own design and branding.  You set the prices, offer the promotions, and even remix and rebundle content for targeted customer groups.  
  • Robust features -- The goal of a digital publishing software company is to deliver a quality self-service platform with a robust feature set that allows publishers to produce, market, and sell their econtent direct to their audience.  It is not something that has been adapted or retrofitted over time to serve that purpose. For example, Tizra was built from the ground up using digital document best practices and has been continuously expanded over the last five years to offer the features that publishers need to be effective.  These include mobile responsive design, search and discoverability, agile e-commerce, content remixing, detailed analytics, and much more.  An offshore service provider wants to sell you just that -- services -- with each new feature and requirement taking development time and money to implement. 
Are you publisher who feels that digital content is strategic to your business? Do you want to sell your content direct to your audience? Do you want control over the user experience, branding, pricing, and marketing? If the answer is yes, but developing digital publishing platforms is not your core strength, it's time to partner with a company like Tizra.  

Drop us a note if you'd like to learn more.

Comments

Popular posts from this blog

Technical Podcasts

If there is something the web as surely changed, it was the way that software engineers need to work. It is now a crucial aspect of our work to be able draw from the huge internet knowledge base out there in an efficient way to get to the right answers. Part of that information extraction is related to the keeping-up-to-date effort that every developer is required to accomplish to continue to be productive. While previous a software engineer could rely mostly on print material, nowadays we need to rely as well on content available on the net. Podcasts are such a source that can bring an amazing amount of information to the mix of knowledge one needs these days. If you are a software engineer and have not jumped into the podcast wagon yet, I suggest you do so. Here is a list some technical podcasts that we hear at Tizra: The Java Posse : a fantastic podcast on Java development. Containing news info update, analysis of tools, overall software development discussions. Software as She Dev...

Using XML to Create a Better Online Reading Experience for the American Payroll Association

Congrats to the American Payroll Association on their recent launch of XML-based publications on Tizra!  Thanks to this collaboration, APA's authoritative books for payroll professionals are now available in crisp, reflowable HTML, creating a user experience that feels like a truly digital native product, rather than a conversion from print. XML-based publishing also creates a better mobile reading experience, supports more precise search and navigation, and opens the door to better accessibility for users with low vision and other disabilities. Our partners at  Scribe  did a great job supporting APA through the process of producing the XML for loading into Tizra, and we’d definitely recommend them to anyone interested in such a transition. It’s hard to overstate what a big step forward this is for Tizra as a platform and a company. XML has long been planned for in the product's architecture, but now for the first time, we have a working example that demonstrates t...

The importance of continuous integration

Leading a team of developers in the effort of building a robust, quality software product should involve the establishment of some process and tools to assist the team effort and serve as a safety net for the errors of getting people to work together. Continuous integration is, I believe, a crucial element of that process. Introduced by Martin Fowler and Matt Foemmel (see article Continuous Integration ), continuous integration establishes the practice of frequent integration of work developed by the several team members verified by automated build and testing of integrated code within a clean sandbox. This practice is valuable for several reasons: It promotes the development of a clear process of building/deployment independent of any specificity of developer's platforms. Code that exists on a single platform only is bound to become dependent on specific aspects of that platform without anyone really noticing the dependencies until trying to port to other platforms. The existence ...