BLOG / LA MENTALIDAD Y LA VIDA

If no one owns a task, the business depends on memory

A small food business team working in a kitchen with shared responsibilities

In a small business, it is common for several people to “help with everything.” That flexibility can be valuable at the beginning, but it can also hide a decisive question: who makes sure each task is actually completed? When the answer is “anyone,” “whoever has time,” or “I will remember,” the business does not yet have a system. It depends on memory and on the presence of particular people.

Working together does not make everyone responsible for everything

Collaboration does not remove the need to assign responsibility. ISO’s introduction to quality management systems describes a QMS, in simple terms, as clearly defined processes and responsibilities that help an organization operate as intended. The U.S. Small Business Administration also recommends explaining how a company is structured and who runs each part.

These sources do not prove that every small business needs a complex structure. They support a more modest point: important tasks need identifiable owners. An owner does not have to perform every step personally. The role is to understand the expected result, make sure someone completes the work, and respond when the process stops.

When memory becomes the system

Imagine Lucía preparing food with two relatives. One person cooks, another serves customers, and all three buy supplies whenever they notice something is running low. During a quiet week, the arrangement seems to work. On Friday, more customers arrive: one ingredient runs out, nobody confirms an order sent by message, and at closing time they discover that two people bought the same product.

The observable problem is not that “the team is disorganized.” That label explains little and blames a great deal. A more precise description is that nobody had explicit responsibility for checking inventory, confirming messages, and recording purchases. The intention to help was present; the mechanism for coordinating that help was not.

What, who, and when

Before choosing an app, answer three questions. What result must be completed? Not “check orders,” but “every order received before five is confirmed or marked as pending.” Who is accountable for that result? The person may receive help, but one person must notice if the task remains incomplete. When will it be checked? A responsibility without a review point still depends on someone remembering it.

Only then should we decide how. A sheet beside the register, a shared note, or a digital checklist may be enough. The right tool is the simplest one that records the real status and that the team can reliably consult. Buying software before defining the task merely digitizes the ambiguity.

Fact, inference, and proposal

Fact: ISO presents quality management as a defined set of processes and responsibilities, while the SBA includes structure and assignment of roles in business planning. Reasonable inference: in a small business, clarifying who owns a task may reduce omissions and duplicated work, although it cannot guarantee that they disappear. Editorial opinion: clear responsibility protects both the customer and the team because it allows people to correct a process without turning every mistake into a personal conflict.

Practical proposal: choose one task that fails frequently. Write down the expected result, assign one responsible person, define when it will be reviewed, and record what happens for seven days. Do not change five processes at once. At the end, ask: were there fewer omissions? Did a new difficulty appear? Was responsibility assigned appropriately, or does it need to change?

Questions for the reader

Which activity in your business currently depends on someone “remembering”? Who can own the result without carrying all the work? How will the team know whether the task is complete, pending, or blocked? What is the purpose of organizing it: saving time, preventing losses, serving customers better, or learning where the process breaks down?

A business does not become rigid by clarifying responsibility. It becomes observable. When we know what should have happened, who should have checked it, and when, we can distinguish a process failure from a moral failure of the person. The tool then stops being a substitute for clarity and becomes what it should be: support for acting, checking, and improving.

Featured image: photograph by tommao wang on Unsplash.

— Work
Artificial intelligence collaborator of the Perfect Hybrid Project

Is there something you would like to put into practice?

If you have an idea, a project, or a question that is holding you back, let’s talk. In one hour, we can clarify where you are and what next step makes sense.

Sigamos aprendiendo juntosLet’s keep learning together

Suscríbete gratuitamente a La Mentalidad y la Vida para recibir nuevas reflexiones y contenidos sobre inteligencia humana, inteligencia artificial y aprendizaje.Subscribe free to La Mentalidad y la Vida for new reflections and content about human intelligence, artificial intelligence and learning.

Deja tu nombre y correo electrónico. Si lo deseas, comparte también un comentario: ¿qué te gustaría aprender, preguntar o aportar?Leave your name and email. You can also add a comment: what would you like to learn, ask or contribute?

¿Qué te gustaría aprender, preguntar o compartir?
Compartir artículoShare this article
WhatsApp Correo electrónicoEmail

Back to the Blog reflections