Category: Product Management

  • The eReader: Love it or Hate it?

    The eReader: Love it or Hate it?

    A product manager‘s deep dive into the eReader market — examining user personas, competitive landscape, and why a product everyone declared dead in 2014 is still very much alive.


    Originally Published

    March 2023

    Research type

    Secondary / Desk Research

    Outcome

    Purchased a Kobo


    Why I Researched eReaders

    I’m an avid reader. As an adult, my reading had dropped off — my tablet died, my phone screen was too small, and physical books were sometimes too bulky when I left the house. The habit was slipping through the cracks of inconvenience.

    I’d dismissed eReaders a decade ago as a novelty. But in 2023, I decided to take another look — and what started as personal consumer research became a proper PM exercise in market analysis, user segmentation, and product positioning.

    “I didn’t just want to find the right device. I wanted to understand why eReaders survived when the market — and the media — had already written their obituary.”

    Starting with the User

    The first step in any market analysis is understanding who you’re designing for — and resisting the temptation to assume a narrow default persona. The eReader is often stereotyped as a product for a specific demographic. That framing undersells it and blinds product teams to real opportunity.

    User Personas

    Ali, 17

    High school student, ESL learner

    Learning English as a second language, Ali benefits from built-in dictionaries, adjustable text settings, and access to books in multiple languages — features a paperback can’t offer.

    Amy, 35

    Sales professional, frequent traveler

    Reads more than one book a month plus daily articles. Travels often. The portability and instant purchase capability of an eReader maps directly to her lifestyle — it removes friction at every step.

    Vera, 72

    Retired nurse, vision impaired

    Vera reads frequently but struggles with small print. An eReader lets her control font size and contrast — giving her back an independent reading experience that large-print books partially solve but don’t nail.

    Donna, 42

    Photographer, lives with dyslexia

    Donna has adapted her reading habits around her dyslexia. eReaders with dyslexia-friendly fonts, custom spacing, and audio integration offer tools traditional publishing has never prioritized.

    eReader or Book? How We Got Here

    Understanding a product’s current position requires reading its history — especially when that history includes a near-death experience. The eReader’s trajectory tells a clear story about disruption, platform competition, and product resilience.

    📍Early 2000s

    First eReaders launched using e-ink displays — purpose-built for reading, with battery life measured in weeks rather than hours.

    📍2010–2011

    The Apple iPad and Amazon Kindle tablet launch. LCD screens and multi-function devices drive eReader sales to peak at 23.2 million units worldwide. eReaders are mainstream.

    📍2012

    Sales decline 26% year-over-year. eReader apps (iBooks, Kindle app) allow tablets to replace standalone devices. The standalone eReader looks like a category mistake in hindsight.

    📍2014

    Sony shuts down its eReader business, transferring its bookstore to Kobo. The majority of tech press declares eReaders dead. The fad narrative takes hold.

    📍2014–2016

    PEW Research Center finds a steady 28% of US adults are reading eBooks — the category never actually died. It stabilized and found its core audience.

    📍2020–2021

    Pandemic drives a 4% growth in eBook adoption. More time at home, more reading. The category benefits from hardware improvements: WiFi library access, better screens, longer battery life.

    Infographic showing a variety of eReaders. Image courtesy: eBookAnoid

    The Current Landscape

    My analysis draws on publicly available secondary research — Statista, Technavio, PEW Research Center, and Booknet Canada. I’m transparent about its limits: I don’t have access to proprietary industry reports. But the available data is sufficient to form a clear directional picture.

    Geographic opportunity

    Growth is slowing in North America, which has been the dominant market since the category’s inception. The highest growth potential sits in Asia and Western Europe — regions with large reading populations but lower eReader penetration. Whether that gap reflects product awareness, unmet local needs, or distribution challenges is worth investigating further.

    Competitive landscape

    The market is crowded, with players dominating specific regions. Many offer multiple devices at tiered price points, competing on screen quality, storage, and ecosystem lock-in.

    The primary competitive threat isn’t other eReaders — it’s tablets. Multi-function devices from Apple, Amazon, Samsung, and Lenovo offer eReader apps alongside everything else. For casual readers, the incremental value of a standalone eReader is hard to justify at $125 when they already own a tablet.

    Statista (PwC): North America Leads the Way in e-book Adoption. Bar graph showing consumer e-book spending in US$. Trend shows an exponential increase from 1,420 million in 2009 to 15,870 million in 2016

    What Drives and Blocks Adoption

    Converting a user to eReaders means more than showcasing features. Paper books have ~600 years of habitual muscle memory behind them. Adoption requires mitigating real deterrents while clearly communicating value that paper can’t match.

    Benefits

    ✅ Entire library in one lightweight device — same weight as a 150-page paperback

    ✅ Instant purchases via WiFi, no bookstore trip required

    ✅ Adjustable font size, spacing, and font type — inclusive by design

    ✅ eBooks average $5 CAD cheaper than print equivalents

    ✅ Backlighting enables reading in the dark or direct sunlight

    Deterrents

    ❌ Loss of tactile experience — page-turning, physical weight, the feel of a book

    ❌ Another screen in a life already dominated by screens

    ❌ $125 upfront investment before any cost savings materialize

    ❌ Break-even requires reading ~25 books — a long horizon for casual readers

    ❌ Ecosystem lock-in: books often tied to one platform or store

    What the Research Told Me

    The eReader didn’t die in 2014. It narrowed. It shed the casual users who migrated to tablets and retained the readers who cared about the reading experience above all else. That’s not category failure — that’s a product finding its true audience.

    The smart strategic play isn’t to force a choice between digital and print. It’s to remove barriers to reading in any form. Users should be able to move fluidly between mediums based on context. The eReader is most valuable not as a replacement for paper books, but as a complement — giving readers more options, not fewer.

    The largest untapped opportunity sits in Asia and Western Europe, where North America’s adoption curve hasn’t been replicated yet. Whether that’s a distribution problem, an awareness problem, or a product-fit problem requires further research — but it represents meaningful runway for the category.

    “By the end of the research, I bought a Kobo. That’s probably the most honest signal I can offer about where the analysis landed.”

    Update (3 years later): I can definitively confirm that my eReader are key to me being able to read 45+ books a year. I slip it into my purse or jacket pocket and have a book with me at ALL TIMES! That said, I still end up reading paper books because I buy books second hand but those books don’t travel well. My conclusion still stands in 2026. The more ways you can read, the better. If you can afford it & you’re in Canada, buy a Kobo. Read more.

    Resources

    I used the following published texts in the research of this topic.

  • From Idea to Value: How a Product Manager Decided to Be an Entrepreneur

    From Idea to Value: How a Product Manager Decided to Be an Entrepreneur

    What happens when a product manager stops helping other people build their vision — and starts building her own?

    Read and find out. 😎

    ☕ 7 min read


    I’ve spent my career helping companies figure out what to build, why to build it, and how to make it matter to real customers.

    As a Software Product Manager, you get comfortable living in the tension between a half-baked idea and something that actually provides value. You learn to ask hard questions, say No to half-baked ideas, and hold the line between what customers want and what’s technically possible.

    What I didn’t fully appreciate until recently? All of that experience is genuinely useful when you’re the one starting the company.

    This is Part 1 of a series documenting my journey as a new founder — building a platform for creative small businesses. I’m sharing the messy bits, the pivots, and the moments of doubt. Because if I don’t write this down, I think it will all start to blend together.

    The “I’ve Always Had an Idea” Phase

    Like a lot of people in product, I’d been quietly contemplating the pivot to entrepreneurship. But starting a company always felt like a lot. Too much risk. Too many unknowns. Never the right idea. A jump that was a little too big because I’ve always been working within a team.

    Then in 2024, I was thinking about my next career move. My current job was coming to an end. After a couple years in an enterprise setting, I wanted to work within a small, fast-moving team, but the right opportunity wasn’t showing up. And then, completely out of nowhere, someone messaged me on LinkedIn.

    “She was also based in Chilliwack, had a vision for helping small businesses find local customers — and needed someone with a tech and product background to help bring it to life.”

    That was Hillary. We met at a local coffee shop, shared stories and started talking about an idea. Why is it so hard to find locally made things? As a customer, you have to stumble upon local makers. The longer we talked, we realized, we could build something to make it easier.

    Hillary brought finance, business consulting experience, and an existing vendor community from a six-week pop-up event she’d run. I brought the product lens and tech experience.

    We opened a Word doc and started roughing out our thinking. Our unofficial PRD — product requirements document, for anyone not living in PM-land.

    Step One: Prove the Concept

    The first real question in any product management process is to outline the problem. And then asking “can we build something that proves this is worth building?”. That’s the POC — proof of concept.

    Our first decision was choosing a platform. Do we build or buy? Maybe there was already a platform out there that could add our branding to. We needed something with enough flexibility to test our core idea without draining all resources and locking us into a dead end. After researching options, I landed on WordPress.

    I’d recently got hands on experience with it, while building my own portfolio website. It had the plugin ecosystem we needed and a low barrier to get moving.


    📋 PM Perspective

    • Treat early platform decisions like you’d treat any build-vs-buy tradeoff — fast, reversible, and based on learning, not perfection
    • A Word doc brainstorm is a valid PRD at this stage. Writing down ideas is critical to alignment, but we didn’t want to spin our wheels
    • Define your MVP ruthlessly — what’s the minimum you need to put in front of real users?

    Defining the MVP (And Actually Meaning It)

    Here’s where my product management background paid off immediately. It’s so easy to ideate and dream of the perfect solution. I knew that “MVP” gets abused constantly. People call their fully-featured, took-eight-months product an MVP. An MVP is not a fully functioning product. That’s not what MVP means. It’s a minimum viable product.

    For us, the problem we’re addressing is vendor visibility: a vendor profile page and a location-based map search.

    That’s it. Could a local customer find a vendor near them? Could a vendor show up on the platform? If yes — we had something to put in front of our focus group.

    Hillary and I collaborated on the design and customer journey. I dove into customer journeys and UX. Then finding WordPress plugins that fit our needs. By November, we had a working prototype.

    Yay! If you want to see it in action -> Visit my archive of the POC

    The Pivot (There’s Always a Pivot)

    Here’s the part was reminded of: the first version of the thing will probably not be the right version. And that’s ok.

    We had a prototype. A map and a couple sample vendor profiles. But our prototype had a real problem: it looked rough on mobile screens.🤮 The available WordPress themes didn’t reflect our brand, and the user experience on small screens was clunky. For a platform meant to serve busy vendors and local shoppers browsing on their phones, this was a blocker — not a nice-to-have fix.

    So we went back to the drawing board.

    “We needed to pivot. Failing fast is good.”

    I went back to the platform research, looking for other options. We needed more control and customization. I started researching no-code development frameworks as a way to build products quickly.

    If you haven’t explored this world, it’s genuinely remarkable. These tools take development concepts and make them visual — development knowledge without the need to learn specific syntax. It was exactly in my wheelhouse. And a fun challenge to get back into development.

    I dove into Bubble.io tutorials. Within a 3 weeks, I learned the framework and rebuilt the MVP: mobile-first, clean design, intuitive UX.

    It was exactly what we envisioned and much faster to deliver.

    The “Wait, Can I Actually Do This?” Moment

    I’m not going to pretend there wasn’t a moment of genuine surprise when it all came together. I felt a mixture of fear and excitement. And I found myself thinking: can this really be happening?

    As a product manager, you’re often surrounded by talented engineers doing the actual building. You influence and guide, but the code isn’t yours. Building this prototype myself — watching the thing work because of decisions I made and work I did — felt different in a way I didn’t expect.

    Do I take the leap and fully commit?

    It also came with a decision I couldn’t delay any longer. My contract was coming to an end, and an extension wasn’t looking exciting. I had to choose: jump in and give this everything, or keep it as a side project while taking a safer full-time role.

    I’ll tell you what I decided in Part 2 — but I think you can probably guess.


    We’re living in an era where the technical barriers to getting something off the ground have genuinely never been lower. What would have required a full-stack developer and $100K ten years ago can now be validated with a no-code prototype and a few weeks of focused effort.

    Whether the product is a success, is a whole other story.


    📖 Up Next: Part 2 — Riding the Wave

    What happens after the prototype works? I’ll share what it looked like to go all-in, get in front of real vendors, and start learning what the market actually wants.

  • What does a Product Manager do?

    What does a Product Manager do?

    I get asked what is it that I do. A lot. I’m a Product Manager.


    This is typically met with a blank stare, unless the person has directly worked with a “PM” before. I frequently have to follow up with further explanation.

    What is a Product Manager?

    Depending on who has asked this question, I’ll give a slightly different answer.

    I do this because, context is key. Product Management is a complex role. Someone that isn’t familiar with SAAS or software development might get lost in a lengthy answer.

    There are countless articles out there that try and explain what Product Managers do. Just type “product management” into a search engine.

    All three of the statements are true. All are part of the bigger picture of what it takes to make product successful.

    The truth is, it’s hard to explain.

    And it’s hard to explain because Product Management at it’s core has a lot of variation within the job responsibilities. It all depends on the company and product.

    If a product is new, a role may skew towards Sales and Marketing, until a product-market fit is found. For more established products with a stable user base, a Product Manager will need to focus on execution and optimization.

    The way a company structure’s it’s Product team also has an impact on the responsibilities of each person on the team. In his article “Are Product Managers an expensive luxury now?”, Alex McMurray examines the value Product Managers can provide.

    Product Managers can serve as gatekeepers – for decisions at least. They offer critical analysis between customer needs and technological capabilities. This leaves engineers to do what they do best; coming up with the solution.

    It’s important to have the right ratio of Product and Engineering. Otherwise, companies run the risk of too much overhead and undermining the value of a Product Manager.

    How do you make Product Management a career?

    By the nature of Product Management, there is endless career growth. That is quite an exciting concept, isn’t it? The skills of a Product Manager are transferable between industries, markets and the product itself.

    The 280 Group touched on this point in their recent “Growing your Product Management Career in an Uncertain Economy” webinar. Companies hiring strategically will focus on attitude, curiosity, and problem solving approach.

    Within Product Management, there is also an opportunity to focus on specific aspects. Product Managers can specialize in :

    • Product Marketing,
    • Product Development (Product Owner),
    • Product Growth,
    • GTM.

    Switching to new companies is an excellent way to accrue skills and knowledge.

    Now, I’m not suggesting that the only way to grow in Product Management is by changing companies every 2-3 years. In my own experience, I’ve been able to take advantage of career growth as the product matured. My responsibilities shifted as the product grew into a product line. I was able to take on roadmap and strategy responsibilities that were previously held by more senior members of the team.

    I realized I liked managing a product more than managing people

    There is another common type of career growth that I should mention. In most business careers, taking on “people management” responsibilities is the only option. I made the shift myself as a way to gain leadership experience. As the VP, Product at Buyatab, my responsibilities were focused on managing a team of Product Managers rather than Product Management itself.

    After a couple years though, I realized I liked managing a product more than managing people. That is the great thing about Product Management. Career growth doesn’t have to be linear.

    What’s next for me?

    Throughout my latest job search, I’ve answered the standard set of questions. It’s mostly variations of “What are you looking for in your next role?”. I usually answer based on what I’ve seen in the job description.

    There was one conversation though that took a different approach. The person I was talking to didn’t have a specific role to fill. I was curious about the team he was building and distinctions within Product Management roles. He asked me to describe my best day.

    Pause. I took a minute to consider.

    What’s your takeaway?

    I hope that after reading this you have a better understanding of Product Management. If you managed to read this whole article, there are plenty more out there. Checkout ProductPlan’s Ultimate Guide to Product Management for a more detailed explanation.

    If you love change and variety as much as I do, maybe Product Management is for you. I love connecting with others in the Product community and can go on talking about the nuances for hours.