I applaud this.

But it is susceptible to all the things that went wrong with the Agile Manifesto:

1. The principles are short maxims, and therefore easy to misinterpret and misapply - like bumper stickers. Even worse, people will likely interpret the statements as absolutes.

2. It is focused only on a slice of the problem. Just as the Manifesto focused on software and ignored product design, this appears focused on product design and ignoring how the product works.

When I read it, I find my self nodding to everything. But that is not what is needed. What is needed is a thoughtful and inclusive model of the whole problem. This is a piece of such a model, and it lacks depth. That depth can be added - but it is simply missing it at present.