I was expecting to have beef with it, but enjoyed the Amazon vision thread.
Know your customers, understand problem space dynamics, understand constraints - those are all reasonable.
Where I raised an eyebrow was the idea that you can understand the first two by reading - by simply gathering information. The third he says you probe with engineers. I say you also need to probe for the first two!
The other eyebrow raise: within the space of customers/problem dynamics/system constraints you may find anywhere from 0 to hundreds of potential visions.
Oh yes, and also it seems to position this kind of work as something a special person can go off to do in a kind of a vacuum, and then deliver to the masses.
I might be wrong about that inference though. Need to know more :)
I was expecting to have beef with it, but enjoyed the Amazon vision thread.
Know your customers, understand problem space dynamics, understand constraints - those are all reasonable.
Where I raised an eyebrow was the idea that you can understand the first two by reading - by simply gathering information. The third he says you probe with engineers. I say you also need to probe for the first two!
The other eyebrow raise: within the space of customers/problem dynamics/system constraints you may find anywhere from 0 to hundreds of potential visions.
Oh yes, and also it seems to position this kind of work as something a special person can go off to do in a kind of a vacuum, and then deliver to the masses.
I might be wrong about that inference though. Need to know more :)