Posts Tagged ‘acquired knowledge’

July 20, 2020

July 20, 2020
17:39
.
.
.
.
Strategy as Tires: Code is codified knowledge. Code is supposed to be the delivery of acquired knowledge in a functional form. How much knowledge did you acquire?
.
17:40
.
.
Strategy as Tires: So the knowledge you acquired was from the first user you ran across?
.
17:49
.
.

.
.
Strategy as Tires: Who among your users can teach the domain? Is that according to the brand new theory or is that according to the theory being replaced by the new theory?
.
17:51
.
.
.
.
.
.
Strategy as Tires: How does the new theory differ from the known theory? You cannot explain the new theory in terms of the known theory? That’s great! You’ve got a new ontology. You’ve got a discontinuous innovation on your hands. So explain it.
.
14:55
.
.
Strategy as Tires: You told me how it cannot be explained. You could have skipped that. Explain it.
.
14:58
.
.
.
.
.
Strategy as Tires: What constraints do we get to ignore with the new theory? What constraints do we face with the new theory? Does the new theory give us some new area to monetize? So we have some new value propositions that we can enable?
.
15:00
.
.
Strategy as Tires:  Well, that’s great, but you threw in another distraction. I still don’t know how the new theory works?