1. Define the accepted outcome
In a sales funnel program, define the accepted outcome so that the team can distinguish activity from accepted value. Record the assumption, responsible owner, evidence source, deadline and stop condition before moving to the next step.
The output of this step should be reviewable by someone who did not configure the workflow. That requirement makes sales funnel easier to audit, compare and improve over time.
2. Map observable stages
In a sales funnel program, map observable stages so that the team can distinguish activity from accepted value. Record the assumption, responsible owner, evidence source, deadline and stop condition before moving to the next step.
The output of this step should be reviewable by someone who did not configure the workflow. That requirement makes sales funnel easier to audit, compare and improve over time.
3. Assign audiences and questions
In a sales funnel program, assign audiences and questions so that the team can distinguish activity from accepted value. Record the assumption, responsible owner, evidence source, deadline and stop condition before moving to the next step.
The output of this step should be reviewable by someone who did not configure the workflow. That requirement makes sales funnel easier to audit, compare and improve over time.
4. Match channels and content
In a sales funnel program, match channels and content so that the team can distinguish activity from accepted value. Record the assumption, responsible owner, evidence source, deadline and stop condition before moving to the next step.
The output of this step should be reviewable by someone who did not configure the workflow. That requirement makes sales funnel easier to audit, compare and improve over time.
5. Implement event measurement
In a sales funnel program, implement event measurement so that the team can distinguish activity from accepted value. Record the assumption, responsible owner, evidence source, deadline and stop condition before moving to the next step.
The output of this step should be reviewable by someone who did not configure the workflow. That requirement makes sales funnel easier to audit, compare and improve over time.
6. Establish baselines
In a sales funnel program, establish baselines so that the team can distinguish activity from accepted value. Record the assumption, responsible owner, evidence source, deadline and stop condition before moving to the next step.
The output of this step should be reviewable by someone who did not configure the workflow. That requirement makes sales funnel easier to audit, compare and improve over time.
7. Run one controlled improvement
In a sales funnel program, run one controlled improvement so that the team can distinguish activity from accepted value. Record the assumption, responsible owner, evidence source, deadline and stop condition before moving to the next step.
The output of this step should be reviewable by someone who did not configure the workflow. That requirement makes sales funnel easier to audit, compare and improve over time.
8. Reconcile downstream value
In a sales funnel program, reconcile downstream value so that the team can distinguish activity from accepted value. Record the assumption, responsible owner, evidence source, deadline and stop condition before moving to the next step.
The output of this step should be reviewable by someone who did not configure the workflow. That requirement makes sales funnel easier to audit, compare and improve over time.
9. Document handoffs and exceptions
In a sales funnel program, document handoffs and exceptions so that the team can distinguish activity from accepted value. Record the assumption, responsible owner, evidence source, deadline and stop condition before moving to the next step.
The output of this step should be reviewable by someone who did not configure the workflow. That requirement makes sales funnel easier to audit, compare and improve over time.
10. Scale the complete system
In a sales funnel program, scale the complete system so that the team can distinguish activity from accepted value. Record the assumption, responsible owner, evidence source, deadline and stop condition before moving to the next step.
The output of this step should be reviewable by someone who did not configure the workflow. That requirement makes sales funnel easier to audit, compare and improve over time.