Direkt zum Hauptbereich

Drill? Hole? Picture on the wall? The Principle of Jobs To Be Done (JTBD)

Provide what customers want and how they need it. The decisive success factor. And yet often out of focus. How to deal with that? The best way: Everyone in your company is to turn their attention to the customer. Jobs-to-be-done could be a great help for you.

Eine deutsche Version findet sich hier.

Ordered and delivered immediately - we've gotten used to it by now. Only rarely are we reminded of the (good?) old days when things were different. And so it's all over town by now: We are currently changing at breakneck speed from an industrial society of mass production to an industrialized service society. Everyone already has a very concrete idea of what that means - after all, we are modern, well-behaved and eager internet consumers with good and bad experiences. Nevertheless and surprisingly, once again it is shown that it takes a long time for mass knowledge from individuals to find its way into our organizations and institutions.

 

This isn't necessarily a bad thing. After all, you don't have to go along with every fashion. In general, it is even intelligent not to fall into fashionable actionism and ask instead: "Why change something? What in fact?" - Yes, why change anything about the way we work together? Or how we look at and run our business? Long before the internet age, there was an answer to these smart questions: Because people want satisfactory results. And they want them without hassle. The economist Theodore Levitt summarized this simple truth in his famous saying: "People don't want to buy a drill. They want a hole in the wall."/1/ This true finding should not have changed since then. But, again, if this has always been the case: Why should we change? Was it not good enough up to now?


The Main Thing: Black


Despite all the lamenting about competition: producers, trade, politics and public services have had a remarkably free hand in what they do over the last 150 years. This is particularly true when it comes to dealing with consumers. They had a very broad power of supply, and they did not hesitate to play it off mercilessly. Even if they wanted to understand that their customers and clients would rather buy a hole IN, or better still, the picture ON the wall - the drill was on offer. So it was sold. "You want a picture on the wall? You're not getting one." This unappreciative, uncooperative, customer-unfriendly approach was (and still is) rich in tradition. This tradition was and is very well illustrated by the legendary saying of the father of mass production, Henry Ford: "Every buyer can have a car in any color he wants. As long as it is black."/2/

 

Today, it is no longer so easy to fob off customers in this way. Why? Because today there is far-reaching information and market transparency. Today, networking business models are possible. Today, these business models can be digitally optimized and secured by algorithms. Today, consumers (us!) have more and more freedom and choice, with which partners, which products, which (digitalized) services we want to try to achieve what we are aiming at./3/ Especially when new, smart competitors appear on the market who have understood that the wind is blowing completely differently today, this naturally puts pressure on established organizations and institutions. Including those, we work for ourselves!


Algorithm Says Hello


So it makes sense to rethink all our activities in these organizations quickly: Unlike in the days of Henry Ford, today it is above all (!) a matter of knowing the customer and his or her wishes, offering the appropriate services and: delivering reliably (!). It is about analyzing (Data! Data! Data!), learning and, this time, really working together with the customer.

 

Those who have had this insight can easily despair of the inertia of their own company. ("Why on earth doesn't anyone realize that something urgently needs to change fundamentally?!") Despair is unpleasant and usually it serves little purpose. Let us therefore turn to more constructive things. For example, how we can shake up, inspire and motivate our colleagues in the team, department, organization, company: Come on, let's walk real service-oriented paths!


Service! Ok, but... HOW?!


Let "Jobs-To-Be-Done" (JTBD) help you. This framework has its origin (as often) in design, but it can easily be transferred to any other area. Yes, even to entire organizations. JTBD is all about thinking and deciding consistently from the customer's perspective and his/her needs. Opposing to the thinking of products, services and activities of one's organization. Accordingly, JTBD is based on principles that turn our organizational mindsets quite upside down, e.g.:

  • People only want our services and products to solve their own tasks and not to deal with us or our organization. (Ouch!)
  • People are always (!) interested in doing more things faster and/or with less hassle.

Starting from basic assumptions like this, in a very structured way, JTBD finds out what this means for the services, products and logistics to be offered. And for the entire value-adding (equals satisfying) process between customer and service provider or producer. From start to finish. It is all about the question: What exactly do customers want to have done? When? How? With whom? Why? To find out, JTBD takes a closer look at a few essential points:

  1. Who actually does the job or is responsible for it? Are several people involved? Who is involved? How? When?
  2. What is the actual job? Is it just one job? Or are there also preparing, adjoining measures to be considered? (JTBD, by the way, explicitly looks at so-called emotional jobs. This might seem revolutionary to us. After all, we are very much in love with processes and engineering, aren't we?)
  3. How is the job done? What are the steps, what is the process, what is the technology being used? (Ah, finally!)
  4. What true (!) needs are behind every (!) job and its detailed steps?


Because the procedure is very structured and understandable, the framework is well suited for process-driven organizations (All of us! Us! Us!). In a practical way, this directs us to always first consider the needs of customers and clients as a basis for decision-making. Thus, the culture becomes more and more customer-oriented over time. And ultimately, of course, the range of products and services on offer, which certainly is a good precondition for playing a leading role in a game in which you have already seen yourself the losing team.

 

Most of us know that nowadays it is a real business need to finally care for the customer. Because most of us have (too) often been frustrated and misunderstood customers (or citizens or employees or ...) ourselves. On the one hand. On the other, most of us have had a lot of good experiences with companies which are interested in the client’s needs. So, most of us know that today it really is about people and their affairs. In other words: Most of us know that if we don't take this seriously, we won't be successful in the foreseeable future. So we have a job to do. Let's do it!

 



Here you can find all articles by Edgar Rodehack.


PS: Thank you very much, Sebastian Moss, for the reference to JTBD. It definitely has added a very effective tool to my toolbox.

Notes


  •  /1/ The attribution is not completely clear, see: https://quoteinvestigator.com/2019/03/23/drill/
  •  /2/ https://de.wikipedia.org/wiki/Henry_Ford
  •  /3/ That at least seems to be the case.But we should wait a little longer until we celebrate this.  Because whether this is a rather good or rather bad development can probably only be judged with a few decades' delay.

Literatur

  • Christensen, Clayton M.: The Innovator's Dilemma. When Technologies Cause Great Firms to Fail. Boston, 1998.
  • Kalbach, Jim: The Jobs To Be Done Playbook. Align Your Markets, Organizations, and Strategy Around Customer Needs. New York, 2020.
 
 
Edgars eigener Blog: www.trellisterium.de
Edgars Podcast: trellisterium.podbean.com 

Edgar Rodehack ist Teamwork-Enthusiast mit einem Faible für agile Formen der Zusammenarbeit. Da trifft es sich natürlich gut, dass er das beruflich macht. Er ist Organisationsberater, Business und Agile Coach, Teamentwickler und Moderator. Außerdem ist er ein Mensch mit Frau und drei Kindern, der viel Spaß am Musikmachen, Schreiben und Lesen hat. Mehr über ihn: www.rodehack.de

 

 

Kommentare

Beliebte Posts aus diesem Blog

Microsoft Teams: Die neuen Besprechungsnotizen - Loop-Komponenten

  Haben Sie in letzter Zeit in einer Teams-Besprechung die Notizen geöffnet? Dort sind inzwischen die Loop-Komponenten hinterlegt. Die sind zwar etwas nützlicher als das, was zuvor zur Verfügung stand. Trotzdem ist noch Luft nach oben. Und es gibt sogar einige ernstzunehmende Stolperfallen. Hier ein erster, kritischer Blick auf das was Sie damit tun können. Und auch darauf, was Sie besser sein lassen.

Agile Sternbilder: Die Entdeckung kosmischer Agilitäts-Superkräfte

Hast du dich je gefragt, ob dein Sternzeichen deine Fähigkeiten in einer agilen Arbeitsumgebung beeinflusst? In diesem Blogpost tauchen wir ein in die faszinierende Welt der Astrologie und ihre mögliche Verbindung zu modernen Arbeitsweisen. Entdecke, wie die Sterne deine agilen Stärken prägen könnten. Ob überzeugter Agilist oder neugieriger Sternzeichenliebhaber – dieser Artikel kann dir neue Perspektiven eröffnen und vielleicht sogar dein nächstes Teamprojekt inspirieren!

Den passenden Job finden

Hier teile ich, wie ich daran arbeite, endlich den richtigen Job zu finden. Kleingedrucktes: Dieser Artikel richtet sich (natürlich) an jene, die gerade in der luxuriösen Position sind, dass sie nicht jedes Angebot annehmen müssen. Anstatt von Engagement zu Engagement zu hetzen und frustriert zu sein über Konzernstrukturen, fehlende Ausrichtung und die Erkenntnis, dass in einem selbst beständig die Hintergrundfrage nagt, ob es das ist, womit man seine immer knapper werdende Lebenszeit wirklich verbringen möchte, gibt es manchmal auch die Möglichkeit, die nächste berufliche Station etwas nachhaltiger auszusuchen - auch, um tatsächlich (etwas) mehr beitragen zu können.

Die Microsoft Teams-Not-To-Do-Liste

Viele hoffen, dass es  für die Einrichtung von Microsoft Teams  den Königsweg gibt, den perfekten Plan – doch den gibt es leider (oder glücklicherweise?) nicht. Genauso wenig, wie es jemals einen Masterplan für die Organisation von Gruppenlaufwerken gab, gibt oder je geben wird. Was gut und vernünftig ist hängt von vielen Faktoren und ganz besonders den Unternehmensprozessen ab. Sicher ist nur eines: Von alleine entsteht keine vernünftige Struktur und schon gar keine Ordnung. Dafür braucht es klare Entscheidungen.

Agilität ist tot. Ausgerechnet jetzt?

Agilität wird zurückgefahren, Hierarchien kehren zurück. Doch ist das wirklich der richtige Weg in einer Welt, die immer unberechenbarer wird? Oder erleben wir gerade eine riskante Rolle rückwärts?

Wie beschreibt man einen Workshop für eine Konferenz?

Konferenzen bieten immer ein gutes Forum, um sein Wissen und seine Erfahrungen zu teilen. Was für die Vortragenden selbstverständlich scheint, ist für die Besucher:innen oft unverständlich. Wie können Vortragende ihren Workshop in 2-3 Sätzen beschreiben, damit die Besucher:innen schnell einschätzen können, er sich für sie lohnt?

Gemeinsam eine Anwenderdokumentation erstellen

Unternehmenssoftware ist ein wichtiges Bindeglied zwischen Anwenderinnen und Anwendern, den Unternehmensprozessen und den Ergebnissen. Normalerweise schreibt der Hersteller der Software die Dokumentation für diejenigen, die die Software benutzen. Wenn die Software allerdings stark angepasst wurde, muss die Dokumentation von denen kommen, die die Prozessmaschine am besten verstehen - den Anwenderinnen und Anwendern. Wie könnte man das praktisch machen?

Scrum und Hardware: Es kommt auf die Basics an

Man kann Hardwareprodukte agil entwickeln. Zum einen kommt Scrum aus der Hardwareentwicklung. Die Softwerker haben die Hardwarekonzepte auf ihre Situation übertragen. Zum anderen hat Hardwareentwicklung heute ganz viel mit Software zu tun. Gerade in frühen Phasen kann man sich mit Simulationen noch viele Wege offen halten und mehrere Pfade parallel verfolgen. In diesem Beitrag empfehle ich eine Podcastfolge und ein Buch, für alle, die mit der Geschwindigkeit ihrer Hardwareentwicklung nicht zufrieden sind.