# What developed traffic is, and why it eats your day [Home](https://theonlyaxelj.com/en) › [Study](https://theonlyaxelj.com/en/study) › [Articles](https://theonlyaxelj.com/en/study/articles) author: [Axel Jedlitschka](https://theonlyaxelj.com/en/about) published: 2026-10-13 updated: 2026-10-13 language: en reading time: 5 min topic: Personal source booklet: [Where the Day Went](https://theonlyaxelj.com/en/shop/introduction/personal-order-time) Developed traffic is everything that never needed to happen. It comes from confusion about what you are supposed to produce, so the fix is clarity. Developed traffic is any action that did not need to happen in the first place: a clarifying call, a repeat trip, a round of fixes nobody should have needed. According to the source, what produces it is confusion about what each person is supposed to produce, so the remedy is clarity. ## Normal work and work that should never have happened Most of your day is full of things that look like work. You replied, called, fixed, and sent again. Each took real time, so it is hard to separate what belonged to the job from what got added on top. That is why most time-management advice does not help here. It deals with how much time you have and says nothing about what is eating it. Without a name for that, you have no way to disconnect it. The source gives it a name, **developed traffic**, and defines it by contrast. Usual traffic is what any business needs in order to run. Developed traffic is unusual and unnecessary, and it appears only because something went wrong earlier. The two do not differ in volume. **What decides it is whether the thing needed to happen at all.** Suppose a customer orders work from you. The conversation about what they want is normal traffic, and it has to happen. If three clarifying calls follow about something that should have been clear in the first message, those calls are developed traffic. Both kinds take time, and only one kind was needed. Or take an installer who drives out to the same job twice because he left the right part behind the first time. The first trip is work. A mistake created the second. ## Every time it happens, somebody flubbed The source adds one short, sharp line: “Every time traffic is developed somebody has flubbed.” It sounds harsh, and it turns the definition into a tool. For any action you take, you can ask whether it was necessary in the first place. If it was not, someone made a mistake earlier, and it may have been you. Suppose a designer who gets three rounds of revisions on every project. The work in them is real, and the need for them was born in an incomplete brief. After she added four questions to her brief form, the same job went through in one round. ## Where it comes from: not knowing what you are supposed to produce The source gives developed traffic one cause and calls it unhattedness, which this booklet describes as role confusion. A person unsure of what their job is meant to produce takes on things that are not theirs, starts things that are none of their business, and sends them to people who will not deal with them either. Unsure of their role, they even pass along what should have stayed with them. The result, according to the source, is an organization that fills up with things not done, things half done, and backlogs. In a one-person business this sounds far away, because you know what you do. Look at the key word in the definition, though: **produce**. What you need to know is what your day is meant to turn out, which is a different question from what you do in it. An owner who never defined that will do whatever comes in, and this is how the mechanism works for him. Suppose an owner opens his inbox every morning. What is in it decides his day, and none of it is his product. Or a clinic owner who cannot say what an admin day at her clinic is supposed to produce. Every admin day looks different, and none feels finished. After she writes one line saying what must be closed by the end of such a day, she knows when it is over. ## There is rarely any malice in it, and that changes what you do Here the source says something that keeps the whole subject from turning into a hunt for someone to blame: “There is seldom any malice in it. It is just confusion.” The point is practical. If the mess comes from malice, the natural response is discipline: scold, supervise, punish. If it comes from confusion, what you need is **clarity**, and that is entirely different work. Suppose an owner is angry at a technician who never gives updates. It turns out the technician did not know what counts as worth an update, and nobody had told him. Or a baker who decided her flour supplier did not care. He simply did not know that the date she gave him was final. When she wrote on the order that the date was binding, the late deliveries stopped. So before you draw a conclusion about a person, check whether they ever received clarity from you. By the booklet's account, they mostly did not, and that changes what you do tomorrow morning. The same applies to you. Most of what eats your day grew out of confusion that was never resolved, which is why it comes back every week. ## What the booklet has on this The chapter this article draws on includes two exercises: the product, and the filter. After them comes a self-check, and from there the booklet moves on to the two basics of developed traffic and a list of its types. If you work all day and feel that most of it went to things that did not need to happen, start by checking whether you know what the day is supposed to produce. - [Where the Day Went](https://theonlyaxelj.com/en/shop/introduction/personal-order-time): Names for what eats the day, a sort you can mark against, and one structure that takes twenty minutes to set up. --- [עברית](https://theonlyaxelj.com/he/study/articles/work-that-should-never-have-happened) · [Español](https://theonlyaxelj.com/es/study/articles/work-that-should-never-have-happened)