13:22 . . | Strategy as Tires: How much infrastructure will we build to support that role? . | |
13:29 . . . . | Strategy as Tires: How much changes between the user and functional boss perspective? Between the user and the generalist boss perspective? Does your data sort out these three groups of people? . | |
13:41 . . . | Strategy as Tires: Do all the users in the same roles want the same things? Is there more than one theory underlying the same work? . | |
14:43 . . . . . | Strategy as Tires: Only one user disagrees with that theory? That user is aware of another theory. Ask them to write a literature review on that theory. We can do the math once we have that review and have done our own. . | |
14:41 . . . . | Strategy as Tires: That new theory turned up in a new tail. The user kept leaving the application after copying some data. When they came back they pasted. Good catch. . | |
14:41 . . . | Strategy as Tires: That user never imported or exported anything? We should be looking for that. At a minimum it is a training problem. . | |
14:51 . . . | Strategy as Tires: Importing or exporting might mean that we need some other data structures, or support for some infrastructure that we don’t support yet. |
…