Category: Product Management

  • Designing a B2B Gift Card Portal

    Products are typically built for a wider userbase. But sometimes, value is unlocked when you tailor a product for a specific user. 😎

    ☕ 5 min read


    From Market Signal to Product Launch

    Gift cards are often treated as simple consumer products. Someone buys one card for a birthday, a thank-you, a holiday, or a personal reward. But when I looked more closely at purchasing behaviour, I saw another kind of customer hiding in the data: organizations buying gift cards at scale.

    As a Product Manager (and UX Designer), I explored how this behaviour could become a new growth opportunity. The result was a B2B Gift Card Portal designed to help business buyers place, manage, and repeat large orders while reducing the manual work required from internal teams.

    The opportunity

    The existing gift card product served a broad B2C audience. Anyone could buy a gift card without creating an account, which made the experience fast and accessible for everyday purchases.

    That model worked well for one-time buyers. However, it did not fully support organizations that needed to buy multiple cards, manage repeat orders, or send rewards on behalf of a company.

    I started with a simple product question:

    What would change if we designed the gift card experience for business buyers instead of individual consumers?

    The opportunity was not only to increase order value. It was also to create a more useful experience for customers who already had different needs.

    What the data showed

    Order data revealed patterns that pointed to a distinct B2B customer segment. These buyers behaved differently from individual purchasers.

    Common signals included:

    • Orders with more than 10 cards
    • Repeat purchases over time
    • Messages that included phrases like “thanks” or “on behalf of”
    • Sender names entered as company names
    • Business email domains
    • Generic card designs rather than highly personal ones

    These patterns suggested that some customers were not buying gifts for a single occasion. They were using gift cards as part of broader business workflows, such as employee recognition, client appreciation, customer rewards, or promotional campaigns.

    From manual process to scalable product

    The company had already started serving some B2B demand through manual operations. This was a practical first step. It allowed the team to validate demand without immediately investing in a full product build.

    However, the manual process had clear limits. It worked best for pre-vetted buyers and required internal teams to handle tasks that customers could eventually manage on their own.

    That created a strong case for a self-serve portal. The product needed to help business buyers move faster while also reducing operational overhead.

    Defining the MVP

    The B2B Buyer Portal launched in late 2021 after six months of product discovery and design.

    The MVP focused on the highest-value workflows:

    • Registering and reviewing business buyers
    • Placing eGift and physical gift card orders
    • Applying custom discount structures in real time
    • Searching historical orders
    • Viewing order details
    • Supporting multiple brands with configurable styling

    The goal was not to build every possible feature at once. The goal was to create a strong foundation that solved the most painful parts of the business buying experience.

    Designing for buyers, brands, and internal teams

    The UX had to serve several audiences at the same time.

    Business buyers needed a clear and efficient purchasing flow. They also needed enough flexibility to customize orders with sender information, messages, card designs, and delivery details.

    Brand clients needed the portal to reflect their own visual identity. Since the company often operated behind the scenes, the experience had to support configurable logos, colours, fonts, and styling.

    Internal teams needed a product that reduced manual work and created better visibility into buyer activity.

    As a designer, I focused on making these needs feel simple to the end user. The experience had to handle complex business rules without making the interface feel complicated.

    Prototyping the customer journey

    I built the prototype in Figma to test the core workflows before development began. The prototype covered both purchase flows and account management tasks, including searching for historical orders and reviewing order details.

    This helped the team move faster in several ways:

    • Prospective buyers could react to a realistic experience instead of abstract requirements
    • Stakeholders could understand product scope through screens and flows
    • Development and QA teams could align around expected behaviours
    • Feedback could be gathered and incorporated before build decisions became expensive

    The prototype also helped shift conversations from “what should the product include?” to “how should this experience work for the customer?”

    Building accessibility into the product

    Accessibility was a core requirement, not a final layer of polish.

    The portal needed to follow WCAG 2.1 AA guidelines. Buyers had to be able to complete key tasks using keyboards, assistive technologies, and mobile devices.

    This influenced the structure of the purchase flow, the clarity of form fields, the use of colour, and the way users moved through each step. A business tool still needs to be easy to use, especially when buyers are placing high-value or time-sensitive orders.

    Key product features

    The launched portal included features designed specifically for B2B use cases:

    • Multi-brand styling so clients could present their own logos, colours, and visual systems
    • Buyer registration with review and audit checkpoints
    • eGift and physical card ordering
    • Real-time discount structures based on cart contents
    • Accessible purchase flows designed for a wide range of users and devices
    • Custom messaging and sender information
    • Custom card imagery
    • Historical order search and order detail views

    After the MVP launched, the product continued to evolve. Later features included reporting, custom photo uploads for gift cards, and scheduled direct delivery of eCards by email.

    What this project demonstrates

    This project shows how product strategy and UX design can work together to uncover a new market.

    The opportunity started with behavioural data. Product discovery helped define the customer segment and the business case. UX design translated that opportunity into workflows that buyers, clients, and internal teams could understand and use.

    The B2B Gift Card Portal turned an operational workaround into a scalable product experience. Within 6 months, the Company saw a growth in revenue. Three clients extended their product dept, to include B2B Portal in their offering.

    More importantly, it showed that even a familiar consumer product can open new growth opportunities when we look closely at how different customers actually use it.

  • 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.