Product Management

Writing Product Requirements in a Fast-Paced Environment One of the biggest misconceptions about product work is that documentation always happens in calm, well-planned conditions. In reality, many product managers operate in environments where things move quickly. Stakeholders want results. Engineers are already working on multiple tasks. New ideas appear in the middle of development. Timelines feel tight. And somewhere in the middle of all this movement, the product manager

The Difference Between Ideas and Building Ideas are exciting. They arrive suddenly, sometimes in the middle of a conversation, sometimes when you are quietly thinking about a problem. In that moment, the idea feels powerful. It feels like the beginning of something important. You can already imagine what it could become. You see the potential. You see the impact. You see how it could work. And for a moment, everything feels possible. But there is a quiet truth that people who

You Can’t Sprint Faster Than Your Team’s Capacity One thing I have noticed while working with development teams is that when people talk about delivery speed, they often assume the solution is simple: work faster . But in reality, software development rarely works that way. Most of the time, the real issue is not speed. It is capacity . Understanding the relationship between sprint velocity and team capacity can change the way teams plan work and set expectations. What sprint

The Product Manager in the Middle There is something about being a product manager that people do not always see from the outside. From the outside, it looks like you are simply coordinating teams, writing requirements, and making sure features get shipped. But when you are actually living the role, you quickly realize that a big part of the job is standing in the middle of everyone’s expectations . And sometimes, that middle position can be exhausting. On one side, there is

The Art of Writing Good Product Requirements Every product starts with an idea. Sometimes it comes from a problem users are facing. Sometimes it comes from a business opportunity. Sometimes it comes from observing a gap in the market. But an idea alone is never enough. For a product to move from an idea to something real, it needs to be clearly understood by the people who will build it. That is where product requirements come in. Writing good product requirements is not just

The Fear of Starting: Why Most People Never Begin There is something interesting about the moment before we start anything new. It could be learning a skill, starting a business, writing a book, launching a project, or even applying for an opportunity. The idea often excites us at first. We imagine the possibilities. We picture where it could lead. Then something happens. The excitement slowly turns into hesitation. The hesitation turns into doubt. And before we realise it, t

If you’ve ever been in a meeting where someone says, “What if we just add this?” you know how dangerous feature ideas can be. They usually sound smart. They often come from good intentions. And they regularly end up on roadmaps without anyone stopping to ask the hard questions. This is the simple framework I use to slow things down before a feature becomes “work.” Question 1. What problem is this really solving? Not the polished pitch. Not the slide headline. The real proble

Pricing is one of the most uncomfortable conversations in product. Not because it’s hard (it is), but because it forces clarity. And clarity is scary. As product managers, we are comfortable talking about users, roadmaps, features, experiments, and metrics. But the moment pricing comes up, many of us suddenly go quiet or defer. “Finance will handle it.” “Let’s launch first.” “We’ll copy what competitors are doing.” I’ve learned this the hard way: if you don’t own pricing

When building new features, speed and efficiency are everything, especially for startups and early-stage products. As a product manager, I’ve learnt thahe smartest ways to build quickly without burning through time and resources is by using APIs. APIs, or Application Programming Interfaces, allow you to connect existing tools or services to your product instead of building everything from scratch. This aligns perfectly with the lean startup approach, focus on what matters, va

When I worked on building a health tech product, one of the first challenges I faced was deciding what to measure. At the early stage, it’s tempting to track everything, from page views to downloads , but not everything truly reflects whether your product is moving in the right direction. Over time, I learnt that the right metrics depend on your product’s current stage and goal, not just what looks impressive on a dashboard. For our health tech product, the goal was simple, t

I had a chat with a friend who’s a product manager at a health tech company, and we both shared similar thoughts on this topic. I thought it would be nice to bring the discussion here. From a product development point of view, security and performance are both very important, but which one comes first depends on the type of product and what users expect. product management If a product handles sensitive user data like money, personal details, or medical records, then security