How I Run Someone Else's Operations: The Ten Habits That Make the Difference

Clients rarely ask how I work before hiring me. They ask what I charge and whether I have done their industry. Then a month in, when things are going well, someone asks the actual question: what are you doing that the last person was not?

It is not talent. It is a set of habits that are individually unremarkable and collectively make the difference between an assistant you manage and one you forget about. Here they are.

1. I spend the first week watching, not doing

The instinct on a new engagement is to be visibly useful immediately. Clear the backlog, answer everything, demonstrate value.

It is the wrong move. You end up solving symptoms fast and permanently misunderstanding the system that produced them.

So week one I mostly ask questions and observe. What happens when this goes wrong? Who actually decides this? Why is it done this way, is there a reason, or is it just history? Output is low and it feels uncomfortable for both sides.

The payoff comes in month two, when I am making decisions correctly without asking, because I understand why the business is shaped the way it is. This is stage two of how I run every engagement.

2. I write down what I am allowed to decide

The single biggest determinant of whether an assistant relationship works is how explicit the authority boundaries are.

Vague delegation produces either constant permission-seeking or overstepping, and both erode trust. So early on we write an actual list. I can spend up to this amount without asking. I can reply on your behalf to these categories. I can reschedule anything except these three meetings. Anything touching pricing comes to you.

Then we expand it monthly. The list is the mechanism by which delegation actually increases over time rather than staying frozen at whatever felt safe in week one.

3. Everything recurring gets written down as I do it

Not afterwards, as a documentation project nobody ever completes. As I go, the first time I do a thing.

Partly this protects the client, if I disappear, the business has a written record rather than a mystery. Partly it is selfish, because I do not want to rediscover how something works in four months.

But the real reason is that writing a process down forces you to understand it. A task I cannot describe in six steps is usually a task I have not actually understood, and those are precisely the ones that break quietly later.

4. I surface, I do not queue

Bad assistants send questions. Good ones send decisions.

The difference: “What should I do about the Henderson invoice?” versus “The Henderson invoice is 40 days overdue. I have sent two reminders. I suggest we pause work until it clears, say no if you disagree, otherwise I will action it Thursday.”

The second version takes me longer to write and costs the client ten seconds instead of five minutes. It also means the default is progress rather than waiting, which matters enormously across a time-zone gap. More on how that works in practice.

5. One written summary a day, no status calls

Done, in progress, blocked, needs you. Four lines, end of my day, which is the client's morning.

This replaces almost all check-in meetings. Clients read it with coffee, reply to the one item that needs them, and get on with their work. Nobody schedules a call to find out what is happening.

6. I keep a list of things that are slightly wrong

Not urgent problems. The small irritations: the form field nobody fills in correctly, the report that gets rebuilt manually every month, the two tools that should talk to each other and do not.

Individually none is worth raising. Collectively they are where the automation opportunities live, and they never appear in a process audit because nobody thinks of them as problems. They are just how things are.

Once a month I look at the list and pick the one with the best ratio of annoyance to effort. That is how most of the automations I have built for clients actually started.

7. I automate my own job continuously

This is the part that sounds counterproductive and is the whole point.

If something I do is genuinely repetitive and rule-based, it should stop being something a person does. I build the automation, hand over the documentation, and that work leaves my hours.

The obvious objection is that I am reducing my own billable time. True. But an assistant whose hours climb with your growth is not giving you leverage, and clients who get real leverage stay for years and hand over more interesting problems. The economics work out.

8. I say no to things

Including work I could take.

If a client wants to automate something that needs judgement, I say so. If they want a brand identity from scratch, I tell them to hire a brand studio. If the honest answer is that they have a process problem rather than a software problem, I say that, knowing it means a smaller engagement.

This is not nobility, it is self-interest over a longer horizon. Taking work I will do badly buys one invoice and costs a reference.

9. I assume I will be wrong about something

Every engagement, I misjudge something in the first month. A process I assumed was broken turns out to have a reason. A person I assumed was the bottleneck turns out to be the only one holding it together.

So I hold early conclusions loosely and ask before acting on them. “This looks inefficient to me, is there a reason it is done this way?” About a third of the time there is an excellent reason and I have just avoided breaking something.

10. I make the handover possible from day one

The engagement should be structured so that ending it is not a catastrophe.

Documented processes, credentials in the client's own password manager, automations in accounts they own, recordings of anything complex. Nothing important sitting only in my head or my tools.

This is partly professional hygiene. It is also a commercial argument: a client who knows they could leave cleanly is a client who stays because the work is good, and that is a better relationship than one held together by switching costs.

None of this is clever

Watch before acting. Write down what you are allowed to decide. Document as you go. Bring decisions rather than questions. Keep a list of small broken things. Remove your own repetitive work. Say no. Assume you are wrong. Make yourself replaceable.

It reads like common sense. It is also, in eight years of taking over from other people, rarely what was happening before I arrived, usually because nobody set it up that way at the start, and by month three the pattern was set.

If you want to know how this would apply to your business specifically, tell me what your week looks like.