9. Defects require users to compensate
for expected functionality that no
longer works
Didn’t auto-save
use to work?
10. New or modified UI elements or
functionality impose a learning cost
What’s this
ribbon
thing?!?
11. Consumption costs can lead to
production costs (e.g., training)
Uh, no one seems
to know how to
use our system…
No problem! We’ll just
do more training!
17. To reduce production transaction
costs: smaller batches, build-in-
quality, design for production
18. To reduce consumption transaction
costs: smaller batches, built-in-
quality, design for consumption
19. Your customer won’t accept smaller
releases?
How might you reduce the cost you
impose on them for receiving it?
20. What are the quality of the releases?
How easy is it to learn how to use the
product or service?
Notas do Editor
Hello my name is Jason Yip, I’m a Principal Consultant at ThoughtWorks. Today I’d like to talk about a common refrain that I’m sure you’ve all heard before. “My customers won’t accept smaller releases.” I will suggest that this is not the real problem.
The real problem is that our consumption transaction cost is too high. That phrase might not sound too familiar so left me try to explain. To do that let’s look at something we should be more familiar with.