Priority #1

Posted Leave a commentPosted in management

How often do you ask your main stakeholders about first priority features?

Should we analyse feature A first or feature B first? Should we start working on A, B or C?

Do you think that prioritization would remain the same with following options (assuming that we know potential users and revenue)?

  • Option 1
    • A – 1 month; B – 1 month; C – 1 month.
    • Teams involved: A – 1 team; B – 1 team; C – 1 team.
  • Option 2
    • A – 1 month; B – 1 month; C – 1 month.
    • Teams involved: A – 3 teams; B – 4 teams; C – 2 teams.
  • Option 3
    • A – 3 months; B – 2 months; C – 4 months.
    • Teams involved: A – 3 teams; B – 5 teams; C – 2 teams.

What additional information apart intuition do you use in decision making? Do you use spikes to improve decision making?

Product Manager

Posted Leave a commentPosted in management

– What are your responsibilities?

– Who are your stakeholders? What techniques would you use to balance to balance out needs?

– How these are different: urgent and important?

– How will you roll out in Thailand?

– How and what to measure?

– What is success?

– What is value?

– How to ensure quality of a product?

– With whom and how are you going to communicate about the product?

– What is mutual-dependency? Why it is important in a development of a big product?

– Problem statement and Feature. What is the difference?

Leave developers alone

Posted Leave a commentPosted in management

If you are working in a product development company most probably you are doing something wrong if start changes and improvements in a technology departments/teams. Little by little i start to understand that.

Leave developers alone, let them do the work they love and focus instead on the flow and other challenges which require attention and might be missed:

  • Understand and communicate the essence of the product
  • Identify business value and stakeholders’ needs and make sure this is delivered regularly
  • Clarify, negotiate and communicate the important priorities and dates
  • Balance the needs
  • Work effectively with development team(s)
  • Identify, track and address things blocking progress
  • Gather and spread information

Developers can help with all these activities, but most probably they don’t love this type of work. That is why they are not managing the product and don’t want to act as Product Owner or Product Manager.