There are days when someone does not open an app in order to publish. They open it to find out whether they still have implicit permission to keep working. They look at yesterday's figures, compare them with last week's, and try to draw a conclusion about their project, their voice, or their future. The counter seems to offer an objective answer: it rises, falls, stalls. Yet the question handed to them is much larger than the available data. Is it worth continuing? Is there enough money? Does anyone care? Can they rest without disappearing? None of those questions fits inside a reach metric, even when the interface brings them so close together that they feel like the same thing.
Making work under that pressure is not an individual weakness or a simple lack of discipline. It is a working condition produced by a system that turns attention into a continuous signal and displays it as though it were a verdict. People who write, draw, research, code, organize events, or hold a community together know the temptation: adjust the calendar to what the platform seems to reward, rush out a post that needed more rest, simplify an idea so as not to miss the moment. The problem is not wanting work to find an audience. It begins when the uncertainty of a private company is transferred wholesale onto the shoulders of the person making the work.
A counter does not measure a career#
A number can describe something real: how many people saw a piece, reacted to it, or paused over it. But it cannot explain by itself what happened. A drop may reflect a change in the recommendation system, poor timing, an audience that is tired, a subject that needs slowness, or the fact that the work reached exactly the people most able to use it. A rise does not prove that the direction is sound either. It may come from a passing controversy, a format that sparks curiosity without building a relationship, or a subject that is misunderstood precisely because it travels quickly.
A number can describe something real: how many people saw a piece, reacted to it, or paused over it.
The mistake arrives when the number is used as a moral summary. When it goes up, the person grants themselves confidence; when it goes down, they suspect they have failed. That move is understandable because it saves uncertainty, but it is unfair. A project's continuity depends on resources, time, care, learning, distribution channels, and relationships that no dashboard captures completely. Reducing all that to a daily curve creates a feeling of control that often only deepens dependence.
Consider an illustrator publishing a series about a neighborhood. One image gets few reactions, but three people write because they recognize a family story, and a local group invites the illustrator to exhibit it. The counter records a modest day; the work has nevertheless opened a specific relationship and a possible source of support. In another case, a short video gets thousands of views through a provocative line, yet it draws hostile replies, requires hours of moderation, and leaves its maker with no greater financial or creative room. The high and low figures are not enough to tell us which day was better.
This is not an argument for dismissing data. It is an argument for giving data a proper scale. Metrics can help ask questions: which formats help people reach useful information, which subjects generate careful conversation, and when does access get lost? They stop helping when they claim to answer who deserves to keep creating. The distinction matters because the first attitude invites inquiry; the second submits a person's own judgment to the ruling of a screen.
The workday that never closes#
The logic of the counter changes time as well. Many jobs have a recognizable ending: a task is delivered, a meeting closes, a shift ends. On social platforms, a post continues to demand attention after it goes out. Someone has to see whether it lands, answer people, correct a misunderstanding, contain a conflict, or seize an opportunity that may not return. Rest becomes suspect because it might coincide with the moment the platform chooses to show the work.
This availability does not affect everyone equally. Someone with stable income, a team, or room to delegate can treat metrics as one piece of information among others. Someone dependent on irregular commissions, caring for other people, or working in precarity receives every fluctuation as a direct threat. Two creators may look at the same decline, but for one it is a signal to review next week and for the other it is a reason to accept worse-paid work or give up a day off. Talking about digital well-being without talking about material conditions leaves out the decisive part of the problem.
Constant attention also pushes aside work that does not perform visibly. Researching, editing, learning a tool, responding carefully, resting, handling a private conversation, or preparing a collaboration are all tasks that sustain a practice. Because they do not become a visible number immediately, they appear postponable. A paradox then takes hold: people publish more to demonstrate continuity and, by doing so, reduce the time that gives their craft real continuity.
One practical measure is to separate the time for making from the time for checking results. Not as a rigid personal rule, but as protection for the process. A small team can agree on a weekly slot to review data and another to discuss what it learned; a self-employed person can select two days each month for that work and put them inside the workday rather than at the edges of the night. Separation lets a figure become evidence to interpret rather than an alarm that interrupts every decision.
Defining what it means for the work to continue#
The more useful question is not, "How do I make everything grow?" It is, "What would need to remain in place for this project to be livable and worthwhile?" The answer changes with each practice. For a local magazine, it may mean maintaining a network of sources and allowing time for verification. For a craft maker, it may mean having uncommissioned hours to develop an independent line. For an association, it may mean people can find help and return when they need it. For a teacher, it may mean an explanation reaches particular students without turning every class into personal promotion.
Writing those conditions down changes the conversation. Instead of pursuing an abstract goal of visibility, people can see whether income is sufficient, whether the response burden is reasonable, whether the audience is spread across several channels, and whether time remains to improve the work. These are less spectacular indicators, but they sit closer to what makes a long career possible. They also reveal problems that reach conceals: a very active community may be exhausting the person caring for it; a growing account may depend on one kind of post; a successful campaign may leave no resources for the next one.
This exercise does not require turning creative life into another spreadsheet. On the contrary, it stops one spreadsheet from ruling it. It is enough to choose a few signals directly connected to the project's purpose. Someone doing public-interest education, for example, might track questions answered well, invitations that respect their time, subscriptions to an independent channel, and hours reserved for research. If a format brings visits while worsening all of those conditions, repeating it is not the only reasonable choice.
It also helps to set boundaries before urgency arrives. How many replies can a person sustain without damaging their rest? Which subjects need additional moderation? Which commissions do not pay off even if they promise visibility? A boundary is not a refusal to grow; it is a way to stop growth from destroying what it was meant to grow. Platforms often present every opportunity as exceptional. A prior criterion makes it possible to decide without treating every notification as a referendum on survival.
Responsibility cannot end with the creator#
It is easy to recommend personal habits: mute notifications, set hours, do not compare yourself. They can help, but they do not solve a design that rewards uninterrupted presence and makes it difficult to know why a post stops circulating. When a platform distributes thousands of people's work unevenly while presenting dashboards that invite compulsive reaction, it participates in organizing their working conditions. It is not a neutral observer.
That responsibility should become understandable information and real options. People who publish need to distinguish an ordinary variation from a change introduced by the company. They need to know whether a paid tool alters organic distribution, whether a restriction affects an account, and how to challenge it. They need controls that allow breaks or reduce response pressure without punishing their basic ability to reach their community. This is not a demand that a social network guarantee economic success. It is a demand that it not turn its opacity into one-sided risk for the people producing the material that makes it attractive.
Institutions that commission, fund, or distribute culture can correct this burden too. A contract that expects daily promotion without recognizing it as work is shifting costs. An open call that values only follower counts confuses the ability to attract attention with the quality of a proposal. A publication that expects every contributor to mobilize their own audience blurs its own distribution responsibility. Including time, budget, and clear criteria for promotion is one way to sustain plurality: it lets voices participate that are not available all day and do not begin with a huge community.
Looking at the counter without living inside it#
The answer is not to pretend that money, reach, or reception do not matter. They do, and it would be cruel to ask calm from someone who does not know whether they can pay next month's bills. The answer is to prevent that uncertainty from taking the form of a permanent, individual examination. Fees, support, contracts, rights of access to data, and distribution alternatives deserve the same serious discussion as creativity. Communities also need to understand that an immediate response is not proof of commitment and that a pause is not abandonment.
A simple practice is to review a project once each quarter with questions no counter can answer alone. Which part of the work gave us energy? Which part left us without room? Which relationships do we want to protect? What dependence has increased? What could we stop doing without losing our purpose? The answers may lead to publishing less, opening an email list, working with another person, charging differently, or reserving time away from exposure. All of those are editorial decisions, not failures of ambition.
Creating with one eye on the counter is understandable when that counter appears to guard the exit. But a culture that only lets people work if they remain visible every day is a fragile, less plural culture. Recovering judgment means looking at the data, placing it among other evidence, and deciding that the continuity of a voice cannot depend exclusively on instant reaction. The next step can be modest: reserve one afternoon without metrics and, before opening the app, write down the three conditions that would make the project sustainable over the next year. That note will not make uncertainty disappear, but it will return to the person making the work some power to name what really counts.
