Two years ago, I joined an enterprise company transforming the publishing industry from within. It’s different, for sure: new skills, methods and challenges. But there are also some under-sung benefits to the role of enterprise product manager. Here are the five I’ve discovered since joining Bibliocloud:

1. Enterprise users are much more invested in your product

Our end users may be in the hundreds rather than the millions, but they spend many hours per week using our software. For our clients, Bibliocloud is the hub of their business: the one place to find answers to business-critical questions, like ‘When are we publishing this book?’ and ‘What rights do we have?’

While this adds considerable pressure, it also means that our users care enormously about the product’s ongoing evolution, giving up considerable time to participate in research. When your customers spend 8 hours a day on a service, small improvements have a big impact.

2. There is a growing need for both useful and delightful enterprise software

Executives in complex industries like publishing have traditionally been between a rock and a hard place when choosing software. On the one hand were the industry-specific systems. These offered the functionality required to save time or costs. But their clunky interfaces required top-down enforcement, at the cost of employee morale.

The emergent SaaS systems, though, were often no better. Basecamp, Asana and other such tools offered a delightful user experience but couldn’t bend to accommodate industry-specific data or workflows, or integrate with existing systems. They offered superficial benefits without touching the difficult problems and as such, didn’t merit expensive roll-outs.

There’s a growing need for beautiful yet industry-specific software. At Bibliocloud, we’re industry insiders, building beautiful, cloud-based software to solve problems we understand. The demand is rapacious because the system is useful and usable to customers in our particular niche.

alt

3. Good enterprise products transform working lives

Working lives matter. In enterprise product management, we’re in the business of vocations, promotions; the professional achievements that build lives.

Whereas a well-designed utilities app might save minutes from a routine task, an enterprise system can save a talented professional hours of time per week. Our system automates many of the tasks that beleaguer the publishing industry: it really is transformative.

Talented editors, marketers and salespeople report being able to actually ‘do their jobs’: the proactive, creative or strategic work that sells more books. And for an over-stretched industry, an hour saved means leaving work on time. That’s life-changing for them, and invigorating for us.

4. Helping businesses serve their customers is satisfying work

Working on an enterprise product means grappling with the business challenges of dozens of companies, all with different strengths and objectives. The best enterprise systems aren’t just functional and usable. They solve hard, specific problems. They help businesses make increasing amounts of money; save increasing amounts of time.

Really pushing the needle for my customers requires a wholehearted engagement with the business of publishing. Discussing strategy with business leaders is fascinating work, and I get a tremendous kick out of helping publishers serve their customers more efficiently.

On that note, it’s no accident that I’ve chosen this industry. Enterprise product management bears social responsibility, and I find meaning from the good that book publishers do in the world, from promoting the latest research on climate change to teaching children to read.

5. Relationships are long-term, collaborative and rewarding

As a product manager for consumer products, interactions with customers were one-off and fleeting. In enterprise product management, by contrast, relationships are long-term and require careful cultivation.

Each of our customers is precious, and the industry is small. It’s also a challenge to maintain a tight roadmap when balancing differing needs with one codebase. But over time, I’ve found our customers increasingly collaborative, supporting each other to raise the bar in the industry.

Diplomacy is required in enterprise product management, but it’s rewarded with a stable business model, high retention, referrals and immense goodwill.

At its best, therefore, enterprise product management is the best kind of symbiosis, offering long-term benefit on both sides.

It’s satisfying work, helping working people achieve their professional goals and build their lives, and supporting businesses to make an impact in the world.

Archives

    Most popular

  1. Ruby code and why you should care
  2. A quick look at data visualisation and analysis
  3. Menial publishing jobs are destroying our future
  4. It's us in the industry who need to be able to code
  5. A manifesto for skills
  6. Learning how to code, the long way around
  7. Company news

  8. New website
  9. 2018 Customer survey report
  10. 2017 in review
  11. Sara O'Connor to join the team!
  12. And now we are five
  13. Prizes galore
  14. Product news

  15. 'Continuing to solve real problems': Futurebook 40, London Book Fair 2018 and the Works page
  16. How many authors is too many?
  17. Better ONIX fragments
  18. Advanced advance information!
  19. Schedules page
  20. Publishers hack their own bibliographic data
  21. Case studies

  22. Burleigh Dodds Science Publishing
  23. Zed Books
  24. IOP Publishing
  25. Code

  26. A publisher’s guide to APIs
  27. What publishers need to know about Ruby on Rails
  28. How APIs can make publishing more efficient
  29. A day in the life of a programmer
  30. eCommerce

  31. To go direct, publishers must mean business
  32. Don’t outsource your publishing business away
  33. Who has the balance of power over data?
  34. Inbound marketing
  35. The business case for going direct
  36. Why publishers must use direct sales
  37. ONIX

  38. A hidden benefit
  39. Thema Subject Codes Update November 2017
  40. ONIX. Not very standard
  41. Three ways to do more with ONIX
  42. A non-technical, beginners’ guide to ONIX for Books
  43. ONIX Changes
  44. BIC, Thema and artificial intelligence...
  45. How to create a catalogue automatically using ONIX and InDesign
  46. Skills

  47. Embrace the code
  48. Mechanical sympathy
  49. Publishers can learn a few things from programmers
  50. A taste of code
  51. Strategy

  52. Rejuvenation
  53. Why ‘easy’ publishing solutions hardly ever are
  54. The right tool for the job
  55. No computer system can fix a broken publisher
  56. Five things I've learned since moving into enterprise product management
  57. Managing expectations
  58. Start with Why – How to refine your publishing mission
  59. The real price of a strategy shift
  60. Technical debt
  61. Decisions, decisions
  62. Creative industries and the division of labour
  63. A company of one's own.
  64. Responsibility, Authority, Capability
  65. Sometimes, size matters
  66. The search for publishing's holy grails