Magdalena Firlit logo
Magdalena Firlit logo

Price is what you pay, value is what you get

Warren Buffett said once: ” Price is what you pay, value is what you get.  “


This Thought Concerns The Financial Market And Business Valuation (Price Value, Stock, Etc.). However, The Phrase Is Universal Enough That I Would Use It For Product Ownership And Features Usefulness In Products.

This statement profoundly resonates with me, and I believe it should also strike a chord with Product Owners.

Warren Buffett’s thought could be translated to Agile Product Management and reflected as the difference between the price that a customer has to pay and the value delivered to customers and users. 

What happens if a customer pays for a product or service yet doesn’t get any value (or little value)?

The answer would be obvious. However, I would like to emphasize it. For instance, customers will be frustrated and dissatisfied and will not recommend your product.

Moreover, the organization invested a budget, time, people’s skills & creativity to deliver waste. The production cost is mostly huge. 

Interestingly, in some organizations, Product Owners and stakeholders still seem to ignore this fact.

Some companies think that a good marketing campaign resolves some product issues. Obviously, ads may temporarily increase product usage and revenue but cannot guarantee that customers will value these products.

Remember, the majority of features in products are not or rarely used. The main reason is that organizations deliver unnecessary functionalities. 

But wait. What is value?

We define value as outcomes – measurable changes in customer/user behavior and their desired experience.

For example, if your customers are frustrated because the system requires a lot of effort to operate in, the outcome for them potentially would be ” for our customers to reduce their time spent on an activity “X”.

How to prevent this situation from happening?

  • Know your users and customers.
  • Focus on customers/users’ outcomes. Product Goals should reflect these outcomes, not only revenue. Read more here.
  • Experiment with functionalities before you will invest time & money to deliver them. Experimentation could be run directly with customers/users. More about experimentation in products you can read here.

Remember: the value is when your users and customers benefit from your product or service. The more value you deliver to the customers, the more revenue it should bring.1

In this short article, I have discussed only one perspective of value. I have focused on outcomes and customer value.

The business value is omitted in this text on purpose. Barely I have meant revenue. There will be a separate paper regarding this topic. Stay tuned!


This article was written by a human, me, not AI.


Leave a Comment

Your email address will not be published. Required fields are marked *

More To Explore

Business Value in Agile Organizations

Recently, I have been talking about customer value a lot. This perspective has been shared here. It is time to share some thoughts about business value for organizations. This paper is a continuation of the previous one, where I mainly focused on customers. It is widely known that companies exist to make money, satisfy shareholders,

Read More »

How to measure the success of the Agile Transformation?

Organizations have been taking their efforts toward Agility for many years. Some of them seem to be successful in this field, and some of them are not. So, how to measure the results and benefits of this effort?   This question is often asked when I discuss the results or ongoing endeavors of the Agile

Read More »

Is revenue a good Product Goal?

Interestingly, so many organizations have revenue or profit as their Product Goals as well as Strategic Goals. Some organizations do not consider using Product Goals at all. Or they are not aware of this need.What about your organization or product? Do you have a Product or Strategic Goal? If yes, does it revenue-oriented? From my

Read More »