Most teams that adopt Jobs To Be Done get the first half right and then quit before the part that matters. They run the interviews, they land on a tidy functional statement, and they stop there. The customer needs to book a table, the user needs to track their spending, they need to send money to family overseas. It all looks clean and defensible, but it rarely tells you enough to build something people actually choose.
The issue is that a Job To Be Done is the progress a person is trying to make in a given circumstance, and that progress runs across three dimensions at once. There is the functional dimension, which is the practical task. There is the emotional dimension, which is how the person wants to feel, or stop feeling. And there is the social dimension, which is how they want to be seen, whether by other people or by themselves. If you stop at the first one, you have described the task rather than the choice, and you have probably drawn the boundaries of your market in the wrong place.
Functional parity is the price of entry
The functional dimension looks like it tells you what business you are in. It hands you an obvious set of competitors, the other products that do the same task, and it sets the minimum level of performance your solution has to deliver to be taken seriously. That is also why it cannot be the thing that sets you apart because if every alternative lets you do the task, the task is not the reason anyone picks you.
There is a second, larger problem. The functional frame does not just fail to differentiate you, it quietly misleads you about who you are competing with. It hands you a list of look-alike products and lets you assume that is the market. But the customer was not choosing from that list. They were weighing options that do the same task in completely different ways, and often the option of doing nothing at all. The real competitive set is defined by the progress the person is trying to make, not by the category you filed yourself under, and that progress is mostly emotional and social.
The choice is emotional and social
The reason someone hires one option over another that does the same task is almost never the task itself. It is how the option makes them feel, and what it says about who they are. This should not be surprising. Psychologists have understood for a long time that we do not make decisions in the logical, calculating part of the brain and then check how we feel about them afterwards. It works the other way around because emotion is bound up in the choice from the start. So a product that solves only the functional dimension is answering a question the customer was never really asking. It addresses the task while ignoring the machinery people actually use to choose.
Take someone sending money home to family overseas. The functional Job is simple, and every provider does it: move the money from here to there. Framed that way, you end up competing on fee and speed forever, and so does everyone else. But when you sit with the actual person, a different picture appears. When the transfer clears, they want to feel like someone who provides, who has not let anyone down, who is holding things together from a distance. And they want their family to see them as reliable, as the one who comes through. A provider that understands it is in the business of dignity and reliability, rather than the business of moving money, ends up building a very different product. It sends the confirmation that lets them tell their mother it is done. It removes the moment of doubt at the counter. It competes on something no fee can match.
The moment you understand that, the competition changes shape. You are no longer just fighting over fees and speed. You are competing with anything that helps that person feel like a reliable provider from a distance, and with the quiet alternative of sending less, less often, and carrying the guilt. Some of those alternatives sit in categories you would never have listed if you had stopped at the functional Job. This is really the point. Emotional and social drivers do not only tell you how to stand out inside a fixed market. Once they are clear, the full set of alternatives comes into focus, and your understanding of which segment you are competing in can shift entirely. More often than not, you discover you were in a different competitive set than the one you thought.
Why teams miss it
Emotional and social progress is harder to see, which is most of the reason it gets skipped. It does not surface when you ask people which features they want. It shows up in the story of the day they decided to switch, in the thing they were quietly embarrassed about, in the version of themselves they were trying to become. You have to interview for it, and you have to keep going past the first functional answer to reach it. Many teams do not, because that first answer arrives quickly and feels like enough. So they optimise the task and leave the more important part of the choice untouched.
Do it properly, not deeply
One caution. The fix is not to attach an emotional story to every Job so it sounds more profound. Not every Job has all three dimensions, and some are purely functional. When you need to cut a straight line in a piece of timber, you need to cut a straight line, and there is no hidden emotional destination underneath. Inventing one is worse than leaving it out, because a fabricated dimension sends you building for a person who does not exist.
The discipline is to find the dimensions that are genuinely there in the evidence, name them precisely, and leave out the ones that are not. Ground every emotional and social claim in real moments from real conversations, not in whatever would make a good slide. Where those dimensions are real, they are where your product wins and where the shape of your market becomes clear. Where they are absent, say so, and compete honestly on the functional task.
Functional gets you into the game so you get considered - the emotional and social are where you differentiate to win. They will often also tell you which game you are really playing. If your Jobs work stops at the tasks the customer needs to do, the analysis is not finished. You have described the starting line, and you may not even be standing on the right track.
