In the Jobs-to-be-Done framework, we think of products as being hired for jobs that arise in people’s lives. This gives us a way to design the product around the hiring criteria.
To practice thinking more this way, I’ve been analyzing products that I consume using the tools that I learned from Bob Moesta and Chris Spiek from the Rewired Group.
The first tool I used is the the progress making forces diagram
This diagram is used to understand the forces that are at play when a consumer seeks to make progress (by purchasing a product or service).
Each force is unpacked and discussed in detail:
- The Push of the Current Situation
- The Pull of the New Solution
- The Anxiety of the New Solution
- The Allegiance to the Current Situation
I am working on developing a back-end to my iPhone app, PaleoViz, and the web stacks I am most comfortable with (Django, ASP.NET and J2EE) are all not ideal for what I want to do.
The push from my current situation is composed of these sub-forces:
- I want to deploy on either Heroku or Amazon Web Services, and ASP.NET is expensive or not supported
- I don’t really want to go back to using J2EE for anything. I am most familiar with pre-RoR inspired frameworks, so I would have to learn something new anyway
- I am concerned that what I want to do isn’t right up Django/Python’s alley
The pull to clojure is
- I’ve been wanting to learn it
- The web frameworks seem to be similar to what I like about Python, but deploy to a JVM
My anxiety is
- clojure is quite a bit different from what I know
- Although Java libraries are available, clojure-native ones seem comparatively immature or non-existent
My allegiances
- My only real allegiance is to Django/python which I know would probably be “good enough”
The reason for the product designer explore these forces is that ones that come up again and again need to be addressed in the product or its messaging. The first two forces start to define a competitive advantage/differentiation that should be accentuated.
As a consumer, this exercise adds some rationality to a process that probably wasn’t all that rational during the consumption. I’ve been keeping an eye on clojure and waiting for an opportunity to play with it. You can see that in my “I’ve been wanting to learn it” bullet point — that is something that needs to be unpacked to get at the job I am hiring clojure to do.