Find what is actually broken in the workflow.

“What exactly is the problem to solve? We keep saying we need another hire.”

Cuts past the symptom to the real workflow that is costing you, whether that is lead scoring, enrichment, or reps buried in prep, and names the real problem.

RUN THE OPERATOR SYSTEMEASYCRMPRODUCT-ANALYTICS TOOLSEQUENCER✓ APPROVED 4/4
EXAMPLE PROMPTS
>My team is stretched and I want to hire an SDR. What is the real problem?
>Find the one workflow worth fixing first. Here is where my reps spend their week
>We say lead scoring is broken. Help me name the problem as a workflow, not a headcount
ABOUT THIS SKILL

What this skill does

Finds the one workflow worth fixing first and writes the problem as a workflow instead of a headcount. The reflex when a GTM team is stretched is to add a role. That names a hire, not a problem. This move points you at the work.

Inputs

A list of where work moves between your GTM functions. No connectors. You can do this from memory or a whiteboard: the handoffs and shared jobs across marketing, sales, CS, and RevOps.

How it works

  1. 1
    1. List the crossings, not the org chart. Walk the revenue lifecycle end to end and write down every place work passes between functions or is shared by more than one. Those are your workflows.
    1. Find the leaks two fast ways. Follow the spreadsheets: every recurring manual export, copy-paste, or cleanup job is a workflow with no system. Follow the "whoever has five minutes" work: anything that falls to whoever is free is unowned by definition.
    2. Size each in cost, not annoyance. Hours per week, pipeline leaked, or churn. Rank them.
    3. Pick the single most expensive one. That is the only workflow worth a project this quarter.
    4. Write the problem as a workflow sentence. "Inbound leaks between marketing and sales" is a workflow. "We need a GTM Engineer" is a headcount. If your sentence names a person, rewrite it until it names the work.
RELATED SKILLS
ALL RUN THE OPERATOR SYSTEM SKILLS →