RSuite is exhibiting at booth #34 from June 1^st through the 3^rd at The Society for Scholarly Publishing (#SSP)!

 

Schedule your time with us today and see how publishers have done the following things with RSuite:

• reduced book production time-to-market by 8 weeks
• automated aggregation and distribution of journal articles to licensing clients
• Increased website traffic by more than 35%
• and much more

Tweet about us at #SSP using the #RSuite hashtag.

Book Expo America is coming up in just a few weeks and we’re so excited to be part of it. RSuite Cloud will be representing Really Strategies, Inc.

At Book Expo America, Book publishers can see RSuite Cloud and understand how it is helping some of the leading publishers:

• Increase revenues with faster time-to-market
• Produce pages in minutes not weeks
• Simultaneously output to print, web, ipad, and more
• Automatically Convert Word files to XML
• Translate and publish to more than 200 languages

People from all  around the world within the publishing industry will be there and we want to see you between May 24^th and May 26^th. We’ll be in the IDPF Digital Zone at Kiosk #2309. Schedule your time with us today!

Tweet about us at #BookExpo using the #RSuiteCloud hashtag.

Really Strategies just returned from Publishing Business Conference and Expo in New York City where thousands of publishing professionals came together for 2 days of education and networking. While our cheerful staff pictured here had various  conversations with publishers, the recurring theme was definitely ebooks.

• How do I generate ebooks for my back list?
• How do I create ebooks and publish along with my print version?
• How do I publish to multiple languages?

Hint: RSuite Cloud

Lightbulb moment for me was hearing so many publishers still ask, "what is XML?". Clearly the fact that I've been embedded in the technology aspects of publishing solutions for the past 15 years has made me overlook the fact that XML is still a mystery for many publishing folks. It's understandable. The great thing about RSuite Cloud, a cloud-based production system, means that XML can remain in the background. At the end of the day, publishers need to publish their work...output formats, file formats, technologies...these can stay in the background, allowing publishers to stay focused on the content.

I get in my car and drive to work everyday, but I certainly don't understand the details of my car's engine.

Learn how RSuite Cloud is helping publishers to publish to ebooks, print, and web in an automated way that improves productivity while reducing cost. Click here to recieve your free white paper.

Address the top 3 digital publishing challenges with XML. Most content producers no longer rely on a single channel for content distribution. To efficiently and competitively expand digital offerings, publishers are looking to re-use existing content to create new products. Whether creating new content “mash-ups” out of existing content repositories or ensuring consistency between publications that share information, content re-use is a powerful capability allowing content to achieve its maximum value. XML provides an anchor for coping with a diverse and expanding number of channels.

Download our latest white paper, "Make XML a Solution Instead of a Challenge."

The success of a CMS implementation is ultimately determined by thousands of individual choices made every day by team members - developers, PMs, analysts, and so on. Many of these choices are based on design principles with which business managers might strongly disagree but of which they are often unaware. Occasionally one of these decisions has inordinate impact - a complexity of design that results in a complexity of implementation, testing, and maintenance that is radically inappropriate relative to the value of the feature in question.

Managers who aren't deeply engaged with their teams tend to over-simplify such discussions by saying things like, "So-and-so engineer always makes things more complicated than they need to be." It's true some engineers are hard to manage (and that some managers start almost every new project with unrealistic expectations, and that some users won't give up complicated requirements). But I believe this difference in philosophy is also in play, and a PM or other manager would do well to understand and talk about how a team's varying philosophies impact its members' choices, and where change might be in order.

An interesting article on this topic by Eliot Kimber is here.

Such discussions might seem esoteric, but they absolutely are not.

I've been working in content management for more than ten years, and thinking back over that time I realized that the dream of a true, standards-based, central repository for all of an organization's assets I naïvely espoused in the late 90s still hasn't become a reality except in the most narrow of applications. When I used to write and teach XML classes I was sure that open markup standards were going to revolutionize the way we created and managed assets. Around 2003 I started to become a bit disillusioned with my vision for content utopia. By 2008 I had all but thrown in the towel. Despite herculean efforts content kept worming its way into proprietary, tactical-level production systems and often was never seen nor heard from again, a victim of legacy of "fire and forget" publishing approaches common prior to the rise of the Internet.

 

Fortunately, just as I had resigned myself to living in a world of content silos, new strategic ways of managing content started to emerge that rekindled my ideals. The idea is more modest than my grandiose vision of pure standards I once embraced, but offers a new, more practical approach that can survive in the real world.

 

Rather than insist that every asset be centralized in a consistent, preferably open, format practicality may dictate that we instead work to build a centralized asset repository that shares common representations for all assets. The actual bits and bytes making up the asset (Word documents, InDesign files, photos, videos, etc.) can still be developed and stored in traditional systems where applicable, but a new system takes on the responsibility of cataloging relevant features and details about the asset in a centralized repository. So instead of insisting that every asset be physically managed in a central repository, we instead insist on the much more modest - and realistic - demand that all assets make relevant, common data and metadata available in a consistent format through a centralized system. This distinction means that rather than try to replace the tactical systems we use to create, manage or distribute content we instead develop a parallel, complementary content management strategy that reflects data in these systems and presents a common, consistent view of the asset regardless of type. 

 

So an image file may exist as a TIFF or PSD formatted file in a production system or on some hard drive somewhere, but the centralized repository maintains a record for this image with all of its relevant metadata and a standard image format readily accessible to any system (i.e. PNG, JPG in thumbnail and applicable preview formats). For a lot of applications, centralized lighter-weight representations of content is enough to create new products without returning to . For example, if I want to rapidly re-use images or stories on a new microsite, I don't have to resort to tracking down all of the content in its silos, but instead rely on these common representations to collect the assets together and send them into my Web CMS for the new microsite. Formats, conversions, and so forth can either be provided to the central system through traditional manual conversion or, preferably, through automated mechanisms built in to existing content workflows.

 

This sort of approach was attempted using search technologies at one time, but lacked an important ability to offer the depth of content management required to not just find the asset but also to be able to use and transform it. It gave us the ability to view the content but not any tools to do anything once we saw it. Search remains important, but a real central repository needs to actually have usable representations of content that can be managed, transformed and distributed as assets on their own. This requires a full content management system.

 

So my new vision of a centralized asset repository is not the end-all be-all "do everything" system that becomes impossible to design and build, it's a "do-some-things" central system that maintains some consistent, common format that can be readily transformed and transmitted and becomes an organization's strategic content reserve. It can answer questions like "what assets do we have about Egypt?" quickly, and serve as a baseline for those assets so that after finding them they can be used in our various tactical systems.

 

To build such a thing, consistent representations are needed. When looking for data standards we of course start with XML. When only a binary will do, ensuring that pointers are accurately maintained to the original assets and appropriate renditions of the binaries are created for things like the user interface of the central repository is an obviously useful model. Even if re-work is required the assets are already under active management. 

 

The RSuite Content Management System happens to be a great foundation for building shared, managed centralize repositories of content. The system is flexible, built on an XML standard database with a metadata model that can not only leverage existing metadata but also be extended in arbitrary ways to adapt to evolving requirements. It is built on open standards and is a good corporate citizen, ready to interoperate with existing systems. The native XML database and pointer management features ensure that consistent representations are available. This approach creates a solid foundation for a strategic, centralized asset repository. 

 

Part of my role as Product Manager for Really Strategies will be to focus on the ways that our existing clients have adopted XML-based content management. I'll be reporting in with our client success stories at building these content repositories here on the blog. 

 

Does your organization have a vision for managing content strategically? It’d be great hearing how others are working to address this challenge.

All of us have been involved at one point or another in our careers with that “death project” that just seems to lack any real conclusion and no one seems to know how or why it is in the state of limbo.  Vendors who serve the publishing industry have many reasons why a project is in jeopardy or has failed altogether including lack of proper resources, no project management discipline,  etc.   From a vendor’s perspective there are some telltale signs that were evident from the very beginning of the project but everyone overlooked them in the excitement of project kickoff.  Following are my top 5 reasons (from a vendor perspective) on why CMS projects fail at publishers:

1. Solution/Technology was not the right fit – Almost no one will admit to selecting the wrong solution or technology.  We all know that buying technology is sometimes a mystery.  Some vendors are really good at selling a vision only to have the publisher realize in the middle of the project that reaching that vision is going to cost three times more than they budgeted.  In other cases publishers already have a preferred technology or product and force that product on all groups.  On more than one occasion we were told point blank by a larger publisher that we love your RSuite technology but corporate is forcing us to use Documentum because we bought a site license.  Economically that makes sense. But functionally this may be trying to shoehorn a technology that was built to manage documents into a publishing environment that requires content management.  Different requirements, different solution required.  It is that simple.  It is no surpise when we hear back from the publisher 9 months later that the project failed or the system is not being used because the system does not meet expectations.
2. Buying a vision that is unattainable – Publishers get excited by vendor demos.  And they should!  What they are seeing in a demo is something they generally don’t have in place.  Some vendors are outstanding at selling a vision by demonstrating slick end-user applications.  The problem with this is that a publisher needs to ask the question “how much is it going to cost me to reach that vision?”  Seeing a technology vendor show really cool functionality does not mean there is a good business or production model behind it.  It is good to see demonstrations that push the envelope, but understand what it will take to implement such a vision (time, money, and business model changes).  I have seen several publishers purchase certain technology to build really cool end user applications only to have the technology sitting around because the vision was not attainable to begin with because it just cost way more than they could ever budget.  Investing in a vision is fine, just be able to break that vision down into logical, cost-effective projects.  Be realistic about what you would like to accomplish and what you can actually accomplish.
3. Poor project budgeting – Along with vague requirements goes poor budgeting.  If you went to a home builder and said "I want a two story house built, give me a quote." How much confidence would you have in the quote you would receive back when the requirements for the house were so vague?  Well, from a vendor’s perspective, we get this level of vague requirements for a CMS on a regular basis and are expected to provide a budget to implement the software.  It is generally couched with “we are only looking for a ballpark.”  OK, great, but if you are looking for a ballpark price that you would have a low level of confidence in, why are you putting that ballpark price into your next fiscal years’ budget?  Immediately you are putting the project at risk.  Again, vague requirements will lead to ballpark estimates that can be misconstrued in budgets. There can be pressure on the vendor to implement a solution based on an unrealistic budget.  Because the system does not operate according to some vague vision there is a real risk of project failure and unhappy customers.  See the chain of events?
4. Inherent conflict between IT and editorial  – My colleague, Lisa Bos, wrote several years back in one of our website newsletters that software development and editorial processes are in direct conflict with one another.  Think about it.  Software developers are used to an environment where they work up to the very last minute making changes on the fly and moving the system to production with an acceptable level of bugs.  The software is never 100%, but it is operational.  On the other hand, the editorial team has a defined process to complete edits on a deadline with the goal of 100% accuracy.  This inherent conflict between these operational approaches comes out during a CMS project implementation.  Understanding the cultural differences between the two organizations is important.
5. No definition of CMS project success – Why do publishers implement CMSs?  There are many reasons of course, but how often are the goals of the CMS project discussed: during the budget cycle, RFP stage, kickoff only, never?  If you hold a CMS project kickoff meeting and ask the group the definition of success when the system is operational and no one in the room knows the answer, you have a problem.  How can a CMS project be successful if the project team does not know the measurement of success?  Installing a CMS is not a success criteria.  Managing XML better is not a measurable goal.   Re-using X% of content in new derivative products, or reducing time-to-market by X days are real, measurable success criteria.  One exercise I like to do at the project kickoff meeting is to make the team draft a press release announcing the completion of the project.  After the team gets over the silliness of the initial request, most teams have fun with the exercise and actually contribute to the writing of the press release.  This simple exercise allows the team to verbally communicate among peers what their interpretation of success is for the project.  If you cannot articulate the definition of project success for the CMS project from the outset, you may be in trouble of ever meeting expectations of management.  Know the success criteria, communicate the success criteria, and celebrate the success with your team.

There are many reasons that CMS projects fail, but over the past decade these five are top of mind.  You will not be able to avoid all of them, but recognizing an issue early on and addressing it will benefit you in the long run and make everyone happier because of the ultimate success your team will achieve.

"Push-Button Publishing System” for Print, Web, and eBook Production in 70 Languages

We are pleased to announce the availability of RSuite Cloud - a complete end-to-end hosted editorial and production system for book publishers.  If you are looking to shorten your book production time to market, want to publish to multiple channels (print, HTML, eBook) at once, and publish in 70 different languages, I suggest you take a look for yourself.  Online demo here.

Here is what one of our clients said about RSuite Cloud:

“We saw the time to produce PDF proofs drop from a week to just a few minutes. This improvement in productivity allowed us to dramatically shorten our production cycle and even recognize revenue in 2010 for a book that was originally scheduled for 2011," stated Stephen Driver, vice president of production services, Rowman & Littlefield Publishing Group. “We are excited about our ability to scale with this solution and the new scheduling flexibility that we could never have dreamed of in our old environment."

A  CMS project in most cases comprises a cross-departmental team with a varied set of personalities assigned to get the project done.  Over the past decade I've noticed some trends in the type of people who make up these teams and five specific types have come to the surface.  I thought I would have some fun and describe these team member personalities and how they interact with other team members.

Disclaimer:  The following is a characterization and does not reflect anyone in particular at any of our clients.  Any resemblance to a specific RSuite or DocZone client is purely coincidental.

In my experience the 5 people you will meet [in CMS Project] heaven include:

The Actor/Actress – For this person, everything is an issue above and beyond the comprehension of everyone in the room.  This person cannot believe the group just doesn’t "see it" and he/she will have to elevate the issue to higher authorities in order to provide yet another brilliant solution that the executive team can implement.  In general every meeting entails at least one outburst just to make sure committee members know he/she is present.

The Authority – A "seasoned professional" who has been with the company for as long as anyone can remember – probably since said publisher created content with chisel and tablet. This type provides a level-headed look at things and can recite quotes from executives who have passed through the hallowed hallways explaining why this is the exact strategy the publisher should take only to see that executive depart publisher for “other opportunities.”

The Thinker (#1) – Generally a meek and mild person sitting at the table who knows her/his stuff inside and out but does not like to be the center of attention.  Would rather be sitting in the row of chairs in the back of the conference room than sitting at the table.   Unfortunately (in their eyes) their boss made them sit at the table.

The Thinker (#2) – In general, this person thinks everyone on the project team or committee is stupid and if you would just leave them alone they would have a new system built in about a week (if an appropriate level of pizza and soda were supplied).

The Leader – This person can lead the construction of a sky scraper or CMS project, it just doesn’t matter.  They are obsessive about details, impatient, and can synthesize more information in 30 seconds than your iPad can download in an hour.  The leader is vocal but polite and can generally marginalize the Actor/Actress on the team.  He/She has the ability to manage up to executives and down to line employees.  In general this person may not always be embraced across the organization because they tend to get too much done and make other people look bad.

Each department at a publisher has its own culture and each person from these departments has their own unique personality.  Your success or failure as a CMS Project Team Leader will be dependent on how well you identify each personality type and know what makes them tick to best leverage their strengths and marginalize their weaknesses.

I often run across articles in various trade publications that provide best practices for evaluating technology and managing projects.  While I think these article are a great starting point for a company, I think they overlook the vendor side of running a project.  In other words, if you look at both the publisher's and the vendor's perspective, you're more likely to achieve a successful implementation, which is the mutual goal. 

So with that background, here are my top five best practices to implement a CMS at a publisher (from a vendor's perspective):

1. Assign one project champion to manage the CMS vendor (not a committee or group) – Content management projects touch many departments.  At publishers, this means that IT, Production, and Editorial will have a say in the project.  Publishers should assign a single project champion (not a group or committee) who has a solid understanding of the business, can manage through the political atmosphere, and is able to make decisions (technical, time, and budget) in a timely fashion.  As a vendor, it is best to have one person in charge who will be that single point of contact.
2. Whatever you budget for your CMS project, multiply it by 2 – The old saying “your eyes are bigger than your belly” rings true when publishers budget for a CMS project.  Content management is complex.  Systems are not plug and play, especially the enterprise scale systems.  Generally the CMS project is an excuse to throw everything anybody has ever wanted into the requirements specification.  Prioritize, delete, reorder, do whatever you have to do to get within your budget, but make sure you budget enough money and don’t try to beat-up the CMS vendor because your budget was too small to begin with.
3. Budget enough money for after the CMS launch – Too many times we have worked with publishers who do not think past the initial launch of the CMS.  When users begin to use the system, there will be changes.  Generally some requirements get deferred after launch because of complexity or budget reasons. Be prepared to have additional funds set aside after you accept the system and users begin to use it.  My rule of thumb has always been to budget between 25% - 50% of the original project for the follow-on phases.
4. Be organized and respect everyone's time – There is nothing worse, from a vendor's perspective, than kicking off a project and realizing the customer is disorganized and cannot fulfill their obligations in a timely manner.  When a vendor allocates resources to a project and has the green light from the publisher, the vendor is ready to start!  That means the publisher needs to be prepared to start as well.  If a publisher is disorganized, it eventually leads to poor requirements, timelines that extend, and cost impacts.  It will impact the time and energy of all parties, including the publisher's editorial and production staff. Don’t start a project unless you have your ducks lined up and are really ready to begin.
5. Tell the rest of the organization there is a CMS project – The acronym CMS in some publishing organizations is a bad, bad word.  In all honesty, we have been at some publishers where we were forbidden from using the acronym all together.  We had to disguise the CMS project as a “new production system” or “finished goods repository.”  We don’t care if you come up with a clever code name for the CMS project, but having a good internal communications plan will make the vendor's job much easier when we need to interact with other groups and derive appropriate requirements.  It is not good as a vendor to start a meeting with a publisher and get “what CMS project?” as a reply to a request for information.

I’m pretty sure you will not see this list of best practices for running a CMS project for publishers in a trade publication, but I thought I would share some of the best practices we would like to see publishers embrace to make projects run more smoothly.