If You Do Not Assign the Work, You Will Do It Yourself

In a small company, silence is often treated as harmless. One person does not reply, another does not comment, someone reads but takes no position. It looks as if nothing is happening.

In reality, silence is a decision.

When there is a concrete problem — a closure to start, a client to manage, a cost to stop, a document to sign — not replying means letting someone else absorb the uncertainty. Not asking questions means implicitly delegating control to the person who is most worried. Not proposing a solution means accepting that one person will become the unpaid project manager of everything everyone else avoids.

The most frustrating part is not doing one extra thing. It is realizing that, if you stop remembering it, chasing it, and breaking it into smaller tasks, nobody will probably do it.

Many small businesses live inside WhatsApp groups, Telegram, Slack, or scattered emails. That is normal at the beginning: you need to move quickly. The problem starts when chat replaces process.

A message saying “we need to close the company” is not a plan. “We will talk tonight” is not a managed appointment. “Let’s proceed” is not a filing with the Business Register. “Someone should check” is not an assignment.

A chat records intentions. A process produces results.

For an activity to truly exist, it should contain at least five things:

1. An observable outcome: not “look into liquidation,” but “file the appointment of the liquidator.”
2. An owner: one person, not “we,” not “the partners,” not “the group.”
3. A deadline: a date and, when needed, a time.
4. An explicit dependency: documents, signatures, quotes, or information that must arrive first.
5. Proof of completion: a receipt, protocol number, signed document, bank statement, or sent email.

When one of these elements is missing, the activity is an intention. And intentions have an annoying characteristic: they remain open until someone takes their weight on.

Being the person who gets things done looks like a strength until it becomes a structure.

At first, you are seen as reliable: you reply to clients, fix the bug, send the message, make the list, call the professional, remember the deadline. Then, slowly, that reliability becomes an invisible service that everyone expects.

The problem is that this service has a cost:

• constant mental attention;
• time taken from work only you can do;
• anger accumulating toward people who do not move;
• difficulty disconnecting because you know something may remain stuck if you do not check it;
• confusion between collaboration and compensation;
• turning the operational founder into secretary, coordinator, support desk, and shock absorber.

That is not sustainable leadership. It is hyper-responsibility.

Hyper-responsibility is dangerous because it produces results in the short term. The company appears alive. Clients receive an answer. Emergencies get resolved. But the system does not improve: it gets used to one person compensating for its flaws.

For a long time, I confused assigning work with being demanding, insistent, or authoritarian. I thought that, among adult partners, some things should simply happen.

They do not.

Assigning means making the boundary between responsibility and expectation visible. It does not mean treating others as employees. It means avoiding a situation where everyone thinks someone else is doing an important thing.

The difference is huge:

• “We need to talk to the accountant” is a collective wish.

• “Marco calls the accountant by Wednesday at 6 p.m. and posts the summary in the group” is a responsibility.

• “We need to reduce costs” is a concern.

• “Luca reviews active subscriptions by Friday and proposes which ones to cancel” is an activity.

• “We need a product plan” is a meeting sentence.

• “Davide prepares a positioning, acquisition-channel, and budget proposal by October 15” is a deliverable.

Small companies do not fail because they use too little Trello, Notion, or spreadsheets. They fail because nobody wants to be named responsible for an outcome that can be verified.

Every important activity needs one owner. Not because that person must physically do everything, but because they must ensure that the outcome happens.

When the owner is a group, the owner is nobody.

For a small company, I would use a brutally simple table:

Activity	Owner	Deadline	Proof of completion
Appointing the liquidator	Designated liquidator	Defined date	Filing receipt
VAT/tax-payment position	Administrative owner	Defined date	Statement and receipts
List of subscriptions and services	Technical owner	Defined date	Shared sheet and actions
Closing the bank account	Liquidator	After outstanding items are settled	Bank confirmation
Final liquidation balance sheet	Accountant + liquidator	Defined date	Business Register filing

This table does not solve a lack of willingness. But it does something essential: it prevents that lack of willingness from hiding behind collective words such as “we will see,” “we will talk,” and “we need to.”

During the closure phase of a company, this risk becomes even more concrete. There may be a formal liquidator, partners, and an accountant, yet the person checking messages, asking for updates, preparing lists, chasing documents, and trying to reconstruct every step can become a shadow liquidator.

It is a terrible position: you do the coordination work without the role, the authority, the complete information, or the recognition. Meanwhile, you risk continuing to postpone your own future to keep moving a structure that should no longer depend on you.

Contributing is right. You can provide access, technical documentation, service lists, contracts, and information you know. You can sign when needed. You can ask for reasonable updates.

But you do not have to become the only person who makes the liquidation exist. If a liquidator is appointed, the next step should have their name on it. If an accountant is retained, the next document should come from their office.

If I could go back, I would not try to become even more available. I would do the opposite: turn every problem into an assigned, written, measurable action.

I would have introduced a 30-minute weekly ritual with one rule: nobody leaves the meeting with a generic point. Every point must end in one of three forms:

1. Assigned action: who does what, by when.
2. Decision made: what was chosen and which operational consequences it creates.
3. Explicit blocker: what prevents progress and who must remove it.

I would have ended meetings with a standard message in the group:

Summary:

• [Name] completes [action] by [date].
• [Name] sends [document/reply] by [date].
• [Name] chooses between [option A] and [option B] by [date].
• Next check-in: [date].

It only sounds bureaucratic to people who have never lost weeks to a sentence like “we will update each other later.”

The most uncomfortable lesson is not that other people will never do anything. It is that, if you keep compensating for everything silently, you are teaching the system that it can work without distributed responsibility.

Every time you take over an unassigned activity, you solve an emergency but make the next one more likely. Every time you send a reminder instead of the person who should send it, you prove that the activity can remain ownerless. Every time you close a problem without making visible who should have handled it, you turn a structural defect into a personal task.

This does not mean abandoning clients, companies, or people to make a point. It means stopping protecting a system from the cost of its own omissions.

Responsibility is not punishment. It is the mechanism through which a group stops being a chat and becomes an organization.