MMarketing Against The Grain
← All frameworks
LeadershipJason Lemkin

One-Cycle Points-on-the-Board Test

Require every functional leader to create measurable improvement within one cycle

Difficulty
Easy
Time to result
~weeks to results
Steps
6
Confidence
98%

This test evaluates a new leader against a baseline and asks for visible progress within one natural operating cycle, such as a sales cycle or quarter. The leader does not need to transform the company immediately; they need to show that they can turn the same inputs into a modestly better output. Sales might improve bookings from a fixed lead pool, marketing might generate more qualified opportunities, and customer success might raise customer sentiment. Qualitative signals arrive even earlier: shipping a neglected improvement, contacting customers, identifying a real problem, or tightening communication. The method favors small, attributable wins before grand redesigns and gives both founder and leader concrete evidence about whether the role is working.

Origin

Extracted from Marketing Against The Grain as Jason Lemkin described expecting roughly 20% improvement and immediate customer-facing action from newly hired functional leaders.

Core principles

  • 01Strong leaders improve constrained inputs rather than waiting for ideal conditions
  • 02Quantitative movement should appear within one operating cycle
  • 03Qualitative evidence appears through action and customer contact
  • 04Small early wins build credibility for larger changes

How to run it

  1. 1

    Freeze the Baseline

    Record the current inputs, outputs, and quality indicators before judging the new leader. Use metrics relevant to the function.

    Pro tip Choose metrics the leader can materially influence without requiring company-wide transformation.

    Watch out Do not move the goalposts after the leader begins.

  2. 2

    Set the Evaluation Cycle

    Define one natural business cycle in which evidence should appear, such as a sales cycle, campaign cycle, or quarter.

    Pro tip Also define qualitative expectations for the first one or two weeks.

    Watch out A long transformation horizon should not excuse a complete absence of early progress.

  3. 3

    Ship an Immediate Win

    Solve one visible, neglected problem in the first days or week. Favor something useful that has remained undone despite being straightforward.

    Pro tip Ask non-specialist teams which small issue has frustrated them longest.

    Watch out Do not spend the opening months only on plans, restructuring, or cosmetic changes.

  4. 4

    Engage Customers

    Speak with customers or listen to call recordings early enough to shape decisions. Surface real friction rather than relying on internal summaries.

    Pro tip Use both satisfied and dissatisfied customers to avoid a filtered view.

    Watch out Avoid QBRs that solicit feedback but resist hearing negative answers.

  5. 5

    Measure Incremental Lift

    Compare the cycle's results with the frozen baseline and look for a credible improvement, even if it is only about 20%.

    Pro tip Attribute the change to concrete actions rather than general effort.

    Watch out Do not require a miracle, but do require movement.

  6. 6

    Make the Role Decision

    Use quantitative movement and qualitative behavior to decide whether to continue, coach, redesign, or end the role.

    Pro tip Separate a hiring mismatch from an execution failure.

    Watch out Waiting indefinitely rarely turns persistent non-execution into strong performance.

In the wild

Improving a Fixed Lead Pool

A sales leader inherits 100 monthly leads that generate $10,000 in bookings. By removing weak deal owners, improving customer communication, learning competitive objections, and joining key calls, the leader raises bookings from the same lead volume to $12,000 or $13,000.

The leader demonstrates meaningful impact within one sales cycle without waiting for more leads or better market conditions.

The First-Week Admin Fix

A new engineer selects a small admin-console problem that has frustrated non-engineering colleagues for two years and ships the fix during the first week. The implementation takes only a few hours, but it removes recurring friction.

The engineer builds trust immediately and proves an ability to deliver before tackling larger projects.

Common mistakes

Leading With Grand Redesigns

Website overhauls and organizational changes can consume months without demonstrating that the leader can improve a customer or revenue metric.

Demanding Transformation

The test seeks credible incremental progress, not proof that a leader can remake the entire company in one cycle.

Avoiding Customers

A functional executive who spends the opening weeks without customer contact misses the fastest source of qualitative evidence.

Is it for you?

Best for

Founders evaluating new sales, marketing, customer-success, product, or other functional leaders.

Not ideal for

Roles where outcomes cannot reasonably be observed within a defined operating cycle or where foundational access is still unavailable.

From the transcript

you have to put points on the board in one sales cycle

Jason Lemkin · 30:00

I'm only looking for a 20% Improvement

Jason Lemkin · 31:30

first week ship a feature

Jason Lemkin · 34:00

From the episode

Everything You Need To Know To Grow A Startup In 2024 w/ Jason Lemkin

Jason Lemkin