The Reverse-Delegate Method: How to EA Delegate Tasks Before They Are Fully Defined

Many founders and operators reach a tipping point where their to-do list becomes a bottleneck, yet they hesitate to hand off responsibilities. The common culprit is the belief that before you can delegate, you must first create a perfect, exhaustive Standard Operating Procedure (SOP). This creates a cycle of procrastination: you are too busy to document the process, so you keep doing it yourself, which ensures you remain too busy to ever document it.

The secret to breaking this cycle is the Reverse-Delegate method. Instead of handing off a finished playbook, you partner with a high-level executive assistant to co-create the process while they perform the work. By treating the delegation process as a collaborative pilot rather than a static hand-off, you can offload complex or undefined tasks immediately, allowing your assistant to turn raw requirements into refined, repeatable workflows as they go.

The Core Philosophy of Reverse-Delegation

Reverse-delegation shifts the burden of documentation from the founder to the assistant. The goal is to provide enough context to get started, then have the assistant observe, question, and document the workflow in real-time. This turns your EA into an architect of your systems rather than just an operator of them.

• Focus on outcomes, not mechanics: Tell your assistant what the result should be, rather than dictating every keystroke.
• The 'Capture' phase: Have your assistant record their first attempts at the task, noting where they encounter confusion or missing information.
• Iterative refinement: Use the assistant’s questions as the foundation for the eventual process document.
• Feedback loops: Establish a brief check-in to review their proposed process after the first run-through.

How to Start a Reverse-Delegation Workflow

When you identify a task you need to offload—perhaps managing an recurring reporting cycle or sourcing vendors—start by scheduling a 'brain dump' meeting. During this session, talk through your thought process out loud while your assistant records the steps. You do not need a document; you just need to explain why you do what you do and what the quality standards are.

At Marlow, we find that the best delegation happens when the founder acts as the visionary and the EA acts as the systems builder. Once the conversation is recorded, ask the assistant to draft a process document based on your call. The first draft will never be perfect, but it will be a functional starting point that your assistant can refine over the next few cycles.

Turning Ambiguity into Repeatable Processes

Once the assistant is handling the task, the documentation should be updated dynamically. If an edge case arises or a tool changes, the assistant updates the process document first, then executes the change. This proactive approach ensures that your operations remain resilient and that your team’s institutional knowledge grows, rather than staying trapped in your inbox.

• Create a living document: Use a shared folder for SOPs that the assistant manages, not you.
• Empower the EA to challenge assumptions: Encourage your assistant to suggest better, faster ways to get the job done.
• Define the 'Definition of Done': Ensure both of you are aligned on exactly what a high-quality finished product looks like for that specific task.
• Trust the process: Accept that the first iteration might be 80% correct, and the last 20% will come from collaborative refinement.

Frequently Asked Questions

Delegation is not an event; it is a relationship. By adopting the Reverse-Delegate method, you stop viewing your EA as a person who simply follows directions and start viewing them as a partner in scaling your business. When you give your assistant the autonomy to refine the 'how' while you focus on the 'why,' you unlock significant time to focus on the high-leverage activities that only a founder can perform.