Here is a couple of questions to ask before you want to build a feature.

If we built <feature name>, what measurable business benefit or other positive outcome would be achieved?

If we built <feature>, which roles or user personas would use it, and how often would they use it?

When being a Product Owner what else do you treat as important before you start building something?

Would highlight following reasons based on my experience:

  • Wears multiple hats – marketer, designer, sales expert, business analyst, …
    • must learn delegate and educate others to avoid becoming a bottleneck
  • Must be domain expert so others and teams would trust in decisions
  • Defines demand of investments into development
  • Has to be perfect communicator as needs to clarify and negotiate important priorities and delivery dates
  • Has to love his product and be passionate about it

What is your opinion?

Very short question i have, please help me to answer:

How Gantt charts or strategic plans can be good when you try to build value structure? Do you use these tools in your personal life? If not, why do you think it’s useful within your organisation?


Want to learn a topic – try to explain it to others. Actually I underestimated this practice or idea I heard from teachers in school and university. But had a chance to prove myself wrong. Several conversations I had recently regarding value structure helped me to understand what things needs to be done and which approach is better to use. Trying to share or explain ideas to others helps to shape up thinking, find answers for grey zones and bring up new ideas from others.

That’s why communities and meetups work – you learn. Took me too long to understand that.

I don’t want that personalities would tell me what to do, instead I want market tells me what to do  

WordPress SEO fine-tune by Meta SEO Pack from Poradnik Webmastera