Re:Jobs to Be Done Framework Is More Useful Than Personas
by troelsSteegin on Thursday August 06, 2020 @06:43AM
(#24069744)
My thinking about user frameworks reduces to two dimensions: intentions and capabilities.
Intentions express what a given population of users is trying to acheive. As a designer you need to situate where your interfaces are relation to that. Jobs to be done is useful for modeling intentions in part because it expressly looks at utility from a subjective (user's or buyer's) perspective and because the metric is simple.
Capabilities express what the user knows, is used to, and is motivated to learn. What skills and mindset does a user bring to thinking about and working with your solution. I have found personas useful as a shorthand for modeling capabilities.
In both dimensions, intentions and capabilities, there is a mixture across a given target market. You can look at different products as addressing different clusters in that space.
From a design/dev perspective, I think about intentions as the benefit side of what we're building, features provide benefits through satisfying intentions, and the capabilities on the cost side, that features should be "free" in terms of the percieved tax that our solution levies in terms of user's effort, attention, or learning.
Intentions express what a given population of users is trying to acheive. As a designer you need to situate where your interfaces are relation to that. Jobs to be done is useful for modeling intentions in part because it expressly looks at utility from a subjective (user's or buyer's) perspective and because the metric is simple.
Capabilities express what the user knows, is used to, and is motivated to learn. What skills and mindset does a user bring to thinking about and working with your solution. I have found personas useful as a shorthand for modeling capabilities.
In both dimensions, intentions and capabilities, there is a mixture across a given target market. You can look at different products as addressing different clusters in that space.
From a design/dev perspective, I think about intentions as the benefit side of what we're building, features provide benefits through satisfying intentions, and the capabilities on the cost side, that features should be "free" in terms of the percieved tax that our solution levies in terms of user's effort, attention, or learning.