Most advice is written for bigger teams
Nearly everything written about store operations assumes enough people that coordination is the bottleneck. Standups, RACI charts, escalation matrices, handover documents. All genuinely useful at six people, and almost all counterproductive at two.
With two people, coordination is nearly free. You know what the other is doing because you talk constantly, decisions take one conversation, and nothing needs routing because there is nowhere to route it. Adding process to that does not make it better, it adds a tax to a system that was working.
This is worth saying plainly because a lot of small-store owners feel guilty about not having process, and go looking for it, and adopt something designed for a team four times their size. Then they abandon it, reasonably, and conclude they are disorganised. They were not.
What genuinely matters at two people
Three things, and they are not the obvious ones.
1. Knowing who owns each recurring thing
Not a task list. A short answer to: who orders stock, who handles customer problems, who deals with the courier, who pays the bills. In a two-person store these usually sort themselves informally, and where they have not, it shows up as the same thing being done twice or not at all.
This takes ten minutes to write and does not need to be revisited often. It is the highest-value process a two-person store has.
2. A record of decisions you will need to remember
Not everything. Specifically the ones you will be asked about again in six months: what you agreed with a supplier about damaged goods, why you stopped using a courier, what your actual returns policy is beyond what is on the page.
Two people hold an enormous amount in their heads and it works until one of them is away, or until you hire, or until somebody misremembers with confidence. A short list of decisions, with dates, costs almost nothing to maintain and is the thing you will wish existed.
3. Knowing what happens if one of you is unavailable
The genuine structural risk of a two-person operation. Not a full handover document, but the small number of things only one of you can do: supplier logins, the bank, the carrier account, whatever has a password only one person knows.
If either of you being ill for a week would stop something important, that is the thing to fix, and it is usually fixed by sharing access rather than by writing a procedure.
What to skip until there are four of you
- Standups. You already know what the other is doing. A scheduled meeting to tell each other is pure overhead.
- Formal escalation paths. There is nobody to escalate to. If you are stuck, you ask the other person, which is what you were going to do anyway.
- A task board. Usually more effort to maintain than the coordination it saves. A shared list of the handful of things in flight is enough, and often a list in one place beats a board in another.
- Detailed SOPs for everything. Write them when you hire, not before. An SOP for a job only you do is a document you will never read, and it will be out of date by the time somebody else needs it.
- Role definitions beyond the ownership list. At two people the roles are "both of us, mostly", and formalising that is fiction.
The signals that it is time to add structure
Process should arrive in response to a problem, not in anticipation. The reliable signals:
- "I thought you were doing that." Once is a slip. Three times in a month means ownership is genuinely unclear and the ten-minute list is overdue.
- A question you have answered before and cannot find the answer to. The decision record is needed.
- You have started doing things twice. Both of you chasing the same supplier is a coordination failure, and it appears around the point a third person joins.
- Something waited because one of you was away. The availability risk has become real rather than theoretical.
- You are about to hire. This is the big one, and it is the point where nearly everything you skipped becomes worth doing, because the new person cannot absorb what is in your heads.
The one thing worth doing before you need it
The decision record, because it is the only item on this list you cannot create retroactively. Ownership can be written in ten minutes whenever it becomes unclear. Access can be shared the day you realise it is a risk. But a decision you made eight months ago and did not write down is gone, and you will not reconstruct it accurately.
It does not need a system. A single document, appended to whenever you decide something you might be asked about later, dated, one or two lines each. Ten minutes a month, and it is the difference between hiring somebody who can get useful in a fortnight and hiring somebody who has to ask you about everything for a quarter.
The month before your first hire
This is the point everything changes, and it is worth treating as a project rather than something that happens around the edges of a busy week.
Hiring exposes a two-person store's actual state. Everything that lived comfortably in two heads now has to be explained, and the explaining happens at the worst moment: while the new person is sitting there being paid to wait. Most of the frustration of a first hire is not about the person. It is the discovery of how much was undocumented, made visible all at once.
What is worth doing in the four weeks beforehand, in order:
- Write down the three or four jobs the new person will actually do, step by step, in whatever rough form you can manage. Not a complete SOP library. The specific things they will be asked to do in week one.
- Decide what they can do without asking. Refunds to a value, reships, answering a customer directly. Without this they ask about everything, which costs more of your time than doing the work yourself would have.
- Sort access before the start date, not on the morning. Check the staff account limit in particular, because discovering the cap on somebody's first day is a bad start for both of you.
- Pick who they ask. With two of you it needs to be one of you, named. "Ask either of us" means asking whoever looks less busy, which means both of you get interrupted and neither builds a picture of what they are struggling with.
What changes immediately at three people
The shift is sharper than the numbers suggest. At two, everybody hears everything: coordination is a by-product of being in the same conversation. At three, that stops being true, and it stops quietly.
Two consequences arrive in the first month. Things need to be said deliberately that were previously absorbed, and the third person will not know what they were not told, so they cannot flag the gap. And the informal ownership that worked at two becomes ambiguous at three, because "the other one does that" no longer identifies anybody.
This is why the ownership list matters more at three people than the work of writing it suggests. It is ten minutes of effort that removes the most common first-hire failure, which is a new person who does not know whose job something is and defaults to doing nothing about it. They will rarely tell you this is happening, because from the inside it looks like waiting rather than like a problem.
Related reading: RACI for a small Shopify team covers ownership when you do grow, and the SOP template is what to reach for at the point you hire.
Common questions
Do two people need any process at all?
Three things: who owns each recurring job, a record of decisions you will be asked about later, and knowing what breaks if one of you is unavailable. Everything else can wait, and adopting it early usually means abandoning it.
Should a two-person team run standups?
No. You already know what the other is doing. A scheduled meeting to exchange information you have already exchanged is overhead with no benefit at this size.
When should we start writing SOPs?
When you hire, not before. An SOP for a job only you do is a document nobody reads, and it will be out of date by the time a second person needs it.
What is the biggest risk in a two-person store?
Single points of failure in access rather than in knowledge. If one of you holds the only supplier login or bank access, a week of illness stops something important. That is usually fixed by sharing access, not by writing procedure.
What is the first sign we need more structure?
"I thought you were doing that", said three times in a month. Once is a slip. A pattern means ownership is genuinely unclear, and the ten-minute ownership list is overdue.