Vizually
GuideProject Lifecycle3 min read

The Go/No-Go Question Enterprise Marketing Executives Should Ask Before Greenlight

Enterprise creative greenlights are gated by budget and concept. They should also be gated by one estimation question. A short preventive playbook for marketing executives.

Vizually Team·
Initiation & Chartering

Greenlight what you can ship, not what you can imagine

Enterprise creative greenlight should be gated on the team's track record, not on the campaign's ambition.
Vizually editorial

Enterprise marketing executives sit through campaign greenlight conversations that focus on concept, budget, and timeline. The conversation that's almost always missing is about the team's history with the estimation pattern: how often have past campaigns from this team shipped on the original timeline they pitched, and by how much have they slipped?

The question is uncomfortable because it implicates the team's reliability, not the campaign's quality. That's exactly why it should be asked. Most enterprise creative slippage is not driven by bad concepts — it's driven by predictable estimation bias that a one-line check at greenlight could catch.

The single greenlight question

At greenlight, ask: for the last three campaigns this team has shipped, what was the original committed launch date, and what was the actual launch date?

The answer is data. If the team's last three campaigns shipped on time, you can take their estimate at face value. If they slipped by an average of two weeks, the right action is not to refuse the greenlight — it's to formally add two weeks to the campaign's commitment date before signing it.

This converts an implicit estimation problem into an explicit one. The team isn't being criticized; their pattern is being incorporated. Most teams are relieved when this happens, because the alternative is the same slip happening anyway, but treated as a failure each time.

  1. Greenlight prep
    Pull the team's last three launch records
    Original committed dates and actual ship dates. PM compiles. 30 minutes.
  2. Greenlight meeting, minute 1
    Ask the question
    The exec asks: 'What's our team's average slip on the last three campaigns?'
  3. Greenlight meeting, minute 2
    Apply the data
    If average slip is more than zero, the new campaign's committed date moves out by that average. Document it.
  4. Greenlight meeting, minute 3
    Sign with the adjusted date
    Both committed and stretch dates documented. Stretch is the original; committed is original-plus-historical-slip.

Three-minute greenlight discipline

0 / 5
  • The team's last three campaigns have a documented original-vs-actual launch date
  • The new campaign's committed date is adjusted by the team's average historical slip
  • Both stretch and committed dates appear in greenlight documents
  • External commitments are made only against the committed date
  • If the team has zero historical slip, the stretch date can be the committed date — but the check is still done

The reason this works at the enterprise level is that the executive has visibility into team history that the project team does not — or doesn't want to apply to their own current pitch. The exec's role is to make the historical data part of the greenlight, not to override the team's confidence with skepticism.

For the same pattern surfaced in different ways, see the retrospective version and the hardware checklist. For executive-level mistakes that bypass this discipline, see five executive go/no-go mistakes.

More in
CategoryProject Lifecycle

Related reading

Articlethe hardware checklist versionArticlethe retrospective version of this workArticlefive executive go/no-go mistakes