Keep reps making the calls that matter.

“If we automate this workflow, where do my reps still need to make the call?”

Marks the points where a rep owns the judgment, who to pursue, the relationship, the message, and gives the workflow an owner and a weekly check so it lasts.

RUN THE OPERATOR SYSTEMINTERMEDIATE✓ APPROVED 4/4
EXAMPLE PROMPTS
>Mark where a rep must own the judgment in this redesigned workflow [pastes workflow]
>Give this workflow an owner and a weekly check so it does not fall apart
>Which steps in our prospecting process should never be fully handed to AI?
ABOUT THIS SKILL

What this skill does

Hands the redesigned workflow to a human who owns it, with the four threads that keep it from falling apart. Cutting the drag is not the finish line. A workflow with no owner and no rhythm tears again in a month.

Inputs

One workflow that has been solved, stacked, and had its drag cut. No connectors required.

How it works

  1. 1
    1. Name the human judgment. The calls in this workflow that need context, judgment, or the relationship. That is what the person keeps.
    1. Thread 1, context. Write the shared brain for this one workflow: the ICP, the rules, the definitions, the messaging. The human and the AI pull from the same source, or the AI guesses confidently.
    2. Thread 2, tooling. Stand up the one automation that runs the drag. One workflow, not the whole stack.
    3. Thread 3, ownership. Put one name on the workflow. They own the human judgment and the system's output. No orphan workflows.
    4. Thread 4, rhythm. Set the recurring review where the owner checks the output and fixes drift. On the calendar, weekly or biweekly. A standing review, not a Slack channel.
RELATED SKILLS
ALL RUN THE OPERATOR SYSTEM SKILLS →