Life of a Business Principal in Consulting

The biggest task of the product manager is to find your target audience. Typically it is a very tight rope walk. You define it too narrowly and you would struggle to generalize the product later. You define it too broad and you would struggle to satisfy a lot of people and the product might not take off at all. There is this awesome post by Dave Mcclure on why Niche target segment works. Blog link here . What he says is mostly right and that is what we did as well. We did it mostly by accident. We had to define our niche because we could only talk to those kind of retailers and get data from them to start developing the data. It did have its upside. We were very clear on what we wanted to develop and we are slowly talking to retailers and adding more scenarios. As we are doing this, we are also talking to a slightly different set of retailers. This helps us incrementally build our product while also generalizing the existing features. In our case, we did not fin

What is the difference between a prototype and a product? I will try to summarise this based on our experiences and understanding. When we started building out this product, we did not have access to real data or to real customers. So we did the next next thing. We stubbed out the data. We presented the application on NRF, Big Show and received feedback from prospective users. Prototype#1: No real data and no real customers. Just functionality We received a real data set form a prospect and started out to develop based on the data set. What we missed out were the real-time scenarios based on the data. We showcased the prototype and received the next set of feedback. Prototype#2: Real data but not real-time scenarios. Functionality with limited scenarios. Once we understood the business of the customers and what they do, what they want, we continued building the prototype and now have a product with 2 customers. Product: A base-lined prototype that handles a

Being a business analyst is probably the easiest part of the product manager. I did not start out as a product manager and the role evolved naturally. When I started my role in the product team, the following questions kept coming back. Why are we doing this product? Is there enough need out there and do we know what returns we would get? Do we know who we are building for and what are we building? While these are innocuous questions that can be posed to a business analyst working on any IT project, what differed was there were no one person or team we could pose these questions to to arrive at answers. We could also not design workshops in case there were multiple stakeholders to arrive at these answers. I ended up doing the following and slowly what I started doing defined the role that I had taken up. I started doing market research to understand what are the market segments available for my product Visiting retailers and trying to understand their pain points h

I work as a Lead consultant at Thoughtworks and my role is usually called Business Analyst. This post is entirely about hoe I ended up becoming a Product Manager. Like what Steven Haines tells in this book: “THE PRODUCT MANAGER’S DESK REFERENCE”, Product Manager is an accidental profession. "You may have backed into Product Management from another field or business discipline.” I landed this position because of the following reasons: We are a services company. No one was interested in a product team. No one was sure what to do as a Business Analyst in the product team No one was convinced that this specific product would be successful. I ended up getting the job and was left to figure out what to do in the team. I was to be the business analyst trying to line up functional work for the product engineering team I have to manage the team - with respect to the team members and make sure I plan for the functional work to complete I was to interact with our current