Archives par mot-clé : product management

Project review? Prepare the good scenarii

Image result for business meeting

I have just attended to a meeting regarding one project of my running program. This kind of meeting is called « Project Meeting ». Initiated by the project manager, it aims to discuss with the program manager and other selected stakeholders some important facts about the projects before the official Project Review. It aims to deal with important issues and collect options from important sponsors beforehand.

Really often the project team uses those meetings to announce:

  • a budget exceeding,
  • a delay

What I realize today is that in most of the meeting I have participated to, the project team forgive to bring important information that are keys to their counterparts: a plan.

Explaining that budget is going wild, planning is dead and gold-plated deliverables are everywhere is in a sense not really interesting to take decision about the project. What the project team should focus on are its strategy to take the project on track according to the available options:

  • Budget should remain unchanged
  • Planning should remain unchanged
  • Scope should remain unchanged

According to those 3 different strategy the team should provide scenarii to their stakeholders in order to have clear direction.

What is the plan to keep the budget unchanged while our scope is booming or delay is out of control?
What are the consequences if we keep the original planning (i.e. deliverables dates) regarding to the scope (descoping) or budget?

When experiencing troubles on projects, project teams should of course understand the reasons and act to stop the deviation but also work on alternative and scenarii about the future of its project. If not, the decision taken during a project review could be somehow definitive.

Do you see other things to focus on in that case?

 

thanks for reading.

 

 

No design, No tech products…

 

http://www.gfk.com/PublishingImages/Press/GfK-Infographic-Look-Technology-Countries-Web.jpg

In a recent study, GfK stated that design is one of the primary choice criteria for tech products. 1/3 of buyers says that design and style are an very important in their choice. Only 10% focus on technologies.

26 000 persons have been interviewed for this study which shows interesting differences among countries and ages. One should read the study if developing a B2C products. However, do you think that this is something new? I don’t.

 

Your next product idea is right here, in front of you.

Well, exactly it is in front of your future customer but as you are customer oriented you are in front of them so…

I have been asked lately about one product manager of my company about how to have great products ideas. I told him that I had no direct answer for him but I could try to help anyway.

To find good product ideas, follow the steps: 😉

  1. Talk to your customers.
    They will pay for your product so ask them what they want, what are their concern, what should be « Whahou!! »
  2. Find a problem to solve
    That’s key. No one will pay an extra € or $ for something that fix… nothing. So try to find an issue and solve it. An important issue of course. An issue for which people are ready to spend some money to avoid it. Pierre Valade, the founder of Sunrise, tells that he is focusing on everything that takes more than 5 min a day.
  3. Know your market
    What are the exisitng product? What are the leaders? Why? What are their advantages, their limits? Read online merchant website to know what people think about it…
  4. Focus on User Experience
    That makes sense. Focus on what will your customer feels when he/she will use your product. That’s key.
  5. Test it, refine it, reTest it (and rewind)
    testing is key for product development. Getting feedback is so more important that it should be your fist concern. By getting feedback you can adjust your product to your market needs and identify your market. Do and redoing it, both parameters will be assessed: market and product design.