There is no place like production

Value is such a subjective thing that we will often be wrong, and there is no way around that wrongness. In order to minimise the wrongness and maximise the amount of value that we deliver we need to have a clear understanding of what our users need, how they are using the product, and validate our new value as soon as we can. Without validation we only have assumptions and assumptions can be dangerous.

As a start we can collect some qualitative data to validate some of our assumptions:

  • Customer Satisfaction – is a key measure as it is an indication of the happiness of your users with the features that you currently have in your product.
  • Product Usage – Its key to see just how much of our product is being used by our users. There is no point in trying to add features to areas that are not being used. Features are only valuable if they fulfil some need for users and the business and usage is a key indicator of value.
  • Employee Satisfaction – is another key indicator. If our employees feel that they understand how their work contributes to the overall product vision then they will leverage that focus and understanding towards building a better product.

For additional ways to measuring value to enable improvement and agility check out The Evidence-Based Management Guide

Real-Users create real-feedback

The only way to validate our assumptions is to get our perceived value in front of some subset of real users and gather feedback. I want to also be 100% clear that the term “real-users” does not mean Staging or UAT; it means production. When you ask someone to test something they do not use it in the same way that they would if they were using it for real. Following a test-script is not a real user.

Releasing is the only way to deliver value

Without getting our increment in front of those real-users we also don’t have any value. Its effectively sitting on our shelf in the warehouse and is depreciating. What is the cost of delay for your feature? If you could get this value, this new business feature, into the hands of real users and make their lives easier how much money would you save? You cant save that money until users can actually use that feature.

A financial reason to release early

And speaking of depreciation all of the software that you are creating, these new features, are capital expenditure. Your finance department is able to offset capital expenditure, and indeed often experimental features, against your tax! However, you are only generally allowed to do that once your features are in production. if you can get a smaller capital expendature into production and start writing it down on a monthly basis early you can compound that write-down by the end of the year. This could be a masive saving for your organisation.

There is no place like production

My favourite quote is from Brian Harry, the product unit manager at Microsoft and technical fellow:

“There is no place like production”

-Brian Harry

No mater how much testing, UX discovery, and UAT, that you do there will always be more things that you discover once you get into production. It is just not possible to simulate a production environment. We are much more likely to be successful and create value by getting the smallest piece of value into production and validating that it is indeed as valuable as we thought.

Upcoming Training Opportunities

These are the next five classes we have, and you can check out our full public schedule of classes.

Live virtual Professional Scrum with UX online on 5th December over four half-days
Virtual Advanced 5
5 - 8 Dec, 2022
09:30-13:00 GMT
Live Virtual Applying Professional Scrum Minecraft on  12th December 2022
Virtual Beginner 12
12 - 15 Dec, 2022
14:00-17:30 GMT

We can deliver any of our courses as private in-house training over Microsoft Teams & Mural. We also recommend training based on your accountabilities or role, you can go directly to recommended courses for Scrum MastersProduct OwnersDevelopers and Agile Leaders.

Create a conversation around this article

Share on Facebook
Share on Twitter
Share on Linkdin

Related Courses

No items found

Read more

Martin Hinshelwood (He/Him)
To my understanding there is a frustrating misunderstanding of reality when one thinks that the Product Owner can reject a single story at the Sprint Review. This is the fallacy of the rejected backlog item.
Martin Hinshelwood (He/Him)
There is no such thing as an Agile Transformation, Digital Transformation, DevOps Transformation, or any of the Whatever Transformation that you can think of or have been sold. You can’t buy agility, and you certainly can’t install it. There is no end state, no optimal outcome, No best practices. We …
Martin Hinshelwood (He/Him)
In light of the new normal and the last 20 years of technological progress, we need to re-define co-location as we no longer need to be in the same room as each other to get the 80% of communication that is non-verbal. If we are participating in an online event, …
Martin Hinshelwood (He/Him)
Gathering the metrics for Evidence-based Management in software organisations can be a strenuous task and I have a number of customers that are fretting on what to collect and from where. Here I try to create an understanding of the ‘what’ that we need to collect.


We believe that every company deserves high quality software delivered on a regular cadence that meets its customers needs. Our goal is to help you reduce your cycle time, improve your time to market, and minimise any organisational friction in achieving your goals.

naked Agility Limited is a professional company that offers training, coaching, mentoring, and facilitation to help people and teams evolve, integrate, and continuously improve.

We recognise the positive impact that a happy AND motivated workforce, that has purpose, has on client experience. We help change mindsets towards a people-first culture where everyone encourages others to learn and grow. The resulting divergent thinking leads to many different ideas and opportunities for the success of the organisation.