Life of a Business Principal in Consulting

Team leadership in self-organised teams In a typical self-organised team, Team leadership is not appreciated. However, there are going to be instances when you would need this capacity and have to understand how to appreciate and inculcate this important characteristic as well.

User Personas are a very good tool for the product owners, business analysts or product managers to be able to co-create with designers. It is predominantly a product of the user research and should not be an amalgamation of demographic data. It is the best way for us to list all scenarios that a persona would take when they want to attain a goal. It is predominantly used to build empathy with user, focus the team and build consensus in a large diverse stakeholder group. The website I referred to is here:  https://www.smashingmagazine.com/2014/08/a-closer-look-at-personas-part-1/

Lean PMO in everyday agile from Prashanth Madhavan Narasimhan

Consumer Vs Enterprise Every time there is a consumer use product, we see that the enterprise comes up with a very customized version so that the enterprise does not have to adapt. This is with good reason. Enterprise is an entity that is too complex and having it to change would mean a disruption to the business  - something that the stakeholders are not very happy about. For example, take the iPhone and Blackberry. iPhone is a consumer centric product while Blackberry is a very enterprise centric product. However, iPhone introduced major disruptions to the way the enterprise security functions and forced enterprises to be more flexible with the way they allow employees to view email. This increased productivity since employees could view their emails at home or anywhere on the move and respond more quickly. Another example is Microsoft word Vs Google docs. The days when a simple document would have to go through multiple revisions with the whole track changes turn...

One of my first projects as a scrum master was to develop a product that would be used by teenage girls and mothers who are afraid of an unexpected pregnancy. I had to work with my clients on this project that was sensitive in nature on multiple grounds. Sensitivity #1: I was working with women on a topic related to measuring menstrual cycles and ovulation periods. It is not easy for people in India to hear a guy talk about menstrual cycles so openly. I had to balance between being sensible on how do we treat the entire topic as an objective discussion to shape the product while at the same time not seem like turning women into objects. It was a tight rope but we did it. Sensitivity #2: This was a realm that fell between medical and religious. The stand that the product took was not overtly endorsed by the medical fraternity in India. It was a new methodology that had data that was not collected by medical fraternity and hence concerns were there. This was a blessing ...

The 2 skillsets that a product manager needs a lot are Analysis and Synthesis. I am a business analyst who turned into a product manager. It is easier for me to be reliant on my analysis skills since that is what I am trained as a business analyst. However, what is also equally important is the synthesis skills. How are they different Analysis refers to the ability to break down a problem into constituents and start attacking them. This helps the product manager a lot when there is enough feedback from users and all the product manager has to do is just carry it out. There is no need for prioritisation from the side of the product manager since the user’s preference would clearly give that information as well. This works well when the product is an already released product and it is not difficult to understand what is needed and why it is needed. Synthesis, on the other hand, refers to the ability to piece together multiple pieces of information to understand t...

Pivoting is a very painful decision for Product Managers. It is also a decision that we , as product managers, dread. Pivoting in essence is one of the key decision points that a product manager needs to always be on the look-out for. A little bit of Context The job of the product manager, at various levels, is also to look at it from a 30,000 feet level, understand the context the product is perceived by the customer and understand how he can make the product better for the customer. This is easily said that done. Product managers tend to get lost in the daily details of running the show that their interactions are always on the transactional level. Irrespective of whether the product is doing well or not, a product manager needs to watch out for the changing landscape. To Pivot ot Persevere The product manager needs to make a hypothesis on whether there needs to be a revision on what problem it is solving. The hypothesis needs to provide a result that will hel...

How would you decide what is the best business model for your product? Deciding on the right business model is very important for the product. It does not necessarily mean what is the price of your product. There could be no price for your product - though that is a myth. For example, we think google or Facebook is free. However, we are never the customers for Google or Facebook. It is the advertisers that are its customers. What we need to figure out when we decide on a business model are as follows: Who is my target audience? Who is my customer What is the price. How is the support model going to work Who are my partners While we do not absolutely need to price a product, we need to understand how we would make money. For example Open ERP does not price its product. However, its product is not the ERP software but really the hosting, service and training that it offers. While pricing is an important part, what is more important is in realising who is you...

How do you do your job as a product manager every day if you do not know what problems you have set your product to solve? One of the most important tasks of a product manager it to catalog problems that prospects / target user base faces. Just follow the steps and you can get really good at it. Step 1: Listen to potential users When you go out to meet people - either potential users or potential customers - you need to listen to what they speak. If you are really good, write it down as soon as possible as you keep listening. That is just step 1. Step 2: Look at what they do As they keep talking, chip in once in a while and ask them what they do and why they do what they do. While this might seem an innocuous question, it is the most powerful question and has enormous power. Reason: You are going to get actions from the customer. Step 3: Listen carefully to the one key thing that they say they are actually looking for. When customers actually demonstrate to yo...

What is in it for your customer and user to buy and use your product? While we all would have answers for this question, we need to understand what the users think of our product. When we started our product, this is what we came up with: We were all excited and would roll our tongues and try to convince our prospects that this is the business value that it was providing. Turns out we were wrong. While we are providing these value adding aspects in our product, these are not the real “ BUSINESS " values. Notice that the word business is in bold. What they really wanted was a simple web page that tells them how their business is doing without jumping through hoola hoops. The biggest business value for saving time on doing mundane calculations. They did not want to manually consolidate sales of 3 stores every month or every time they needed to take a decision. Once you have captured the business value, how would you track how you are doing on that business val...