Modernize Shipley

If you run a government contracting firm, you already know the Shipley Process can work. It brings discipline to pursuits, forces hard decisions, and creates a common language across BD, capture, and proposal teams.

So why do so many organizations still feel like forecasting is a “best guess,” gate reviews are subjective, and the same mistakes repeat quarter after quarter?

Because most firms treat Shipley like a set of meetings.

High-performing firms treat it like an operating system: a repeatable process, measured in real time, reinforced through coaching, and improved through a feedback loop.

That shift—process to operating system—is how you turn Shipley from a compliance exercise into a performance engine.

The Exec Problem: You Don’t Have a Shipley Issue. You Have an “Evidence” Issue.

In too many GovCon organizations, gate reviews sound like this:

• “We feel good about this one.”
• “The customer likes us.”
• “The competitor is weak.”
• “We’re at 70% PWIN.”

The problem isn’t optimism. The problem is no shared standard for what ‘good’ looks like—so every PWIN is based on subjective opinion, not objective proof.

Each phase of Shipley should produce specific, verifiable outcomes. Those outcomes become your evidence trail. Without them, the process collapses back into gut feel, heroic proposal sprints, and surprise losses.

Step 1: Separate Confidence (Probability) from Timing (Award)

Executives need forecasts that answer two different questions:

• Confidence (Probability / PWIN): How likely are we to win?
• Timing (Forecast Category): When will this project be awarded and turn into revenue?

Most teams combine these into a single number and call it a forecast. That’s how you get inflated PWIN, missed quarters, and resource whiplash.

A cleaner model:

• Probability (confidence) is calculated by outcomes (evidence).
• Timing is understood by acquisition realities (procurement stage, funding, protest risk, customer calendar, and internal readiness).

When you decouple them, you get two powerful benefits:

• You can have high confidence with low timing certainty (a great capture, an uncertain award date).
• You can have low confidence with high timing certainty (the award is coming, but you’re not positioned to receive it).

That clarity changes how you invest, staff, and bid.

Step 2: Define Outcome-Based Gates (Not Activity-Based Gates)

Activities matter—calls, meetings, drafts, storyboards. But activities don’t predict wins.

Outcomes predict wins. Outcomes are the measurable achievements that prove you’re positioned, qualified, and ready.

Below is an executive-friendly approach to modernizing Shipley by defining phase outcomes that you can inspect during a gate review.

Outcome-Based Shipley Scorecard (Sample)

The point is not to create a bureaucratic checklist. The point is to establish a small set of outcomes that are non-negotiable for your must-win pursuits.

Step 3: Convert Outcomes into a Simple KPI Stack (Action → Interim → Result)

If you want performance improvement, you need metrics that a team can act on before results are final.

Use three levels:

1) Action KPIs (What the team does)

These are controllable behaviors:

• Meaningful customer interactions (not just touches)
• Competitive intel updates
• Partner syncs with documented decisions
• Drafts/reviews completed on cadence

2) Interim KPIs (What the team accomplishes)

These are outcome indicators that predict success:

• Hot buttons verified (not assumed)
• Funding confidence improved (evidence captured)
• Decision-maker access achieved
• Solution discriminators validated
• Compliance matrix maturity

3) Result KPIs (What the business gets)

These are lagging outcomes:

• Win rate by agency/contract vehicle /customer
• Award value and margin quality
• Forecast accuracy (confidence and timing tracked separately)
• Pipeline coverage quality (not just volume)

Executives should demand a system that ties these together. If win rates are down, the question is not “try harder.” The question is: Which interim outcomes are missing, and what actions will produce them?

Step 4: Enable Shipley Inside Your CRM (Stop Running Capture in PowerPoint)

If you conduct Shipley in slide decks and spreadsheets, you’re guaranteeing three things:

• Lagging visibility
• Inconsistent data
• Lost institutional knowledge when people leave

The goal is not “more fields.” The goal is a guided workflow that makes doing the right thing the easiest thing to do.

Practical CRM enablement moves:

• Add outcome fields as simple checkboxes with required evidence links (notes, call reports, artifacts)
• Use standardized definitions for stages/phases across the firm
• Create an executive scorecard dashboard: confidence drivers + timing drivers
• Automate prompts: “If you claim 60% PWIN, show these outcomes.”
• Centralize artifacts: competitor profiles, debriefs, win themes, compliance matrices

If your team can’t pull an executive-ready gate review from the system in minutes, the system is not serving the business.

Step 5: Establish a Coaching Cadence (Because Process Without Reinforcement Decays)

Professional sports teams have coaches. High-performing GovCon teams need the same discipline—not to micromanage, but to build repeatable excellence.

A simple cadence that works:

Weekly (30–45 minutes): Capture Execution Review

Ask three questions:

• What did we do? (Action KPIs)
• What did we accomplish? (Interim outcomes)
• What’s the plan next week? (Next best actions to create outcomes)

Monthly: Executive Gate Review (Decision-Focused)

Keep it ruthless and simple:

• Are the outcomes present?
• Is confidence justified?
• Is timing realistic?
• Is this pursuit worth the investment?

When you run cadence consistently, two things happen:

• Teams stop “performing for the meeting” and start executing for outcomes.
• You get a feedback loop that improves the process based on real wins and losses.

Step 6: Start Small, Then Scale (Simplicity Wins Adoption)

The fastest way to kill adoption is to design a perfect system that nobody uses.

Instead:

• Pick one business unit or one pursuit type (e.g., recompetes, IDIQ task orders, set-asides).
• Define 3–5 outcomes that truly predict success for that pursuit type.
• Build scorecards and dashboards around those.
• Coach weekly for 6–8 weeks.
• Form habits around the system and introduce additional measurements once the data is trusted.

The Bottom Line

Shipley is already a strong framework. Modernizing it is not about reinventing the process—it’s about operationalizing it:

• Define outcome-based gates
• Separate confidence from timing
• Measure what predicts wins
• Enable it in your system of record
• Reinforce it with coaching
• Continuously improve based on evidence

When you do that, gate reviews become faster and cleaner, forecasts become credible, and win rates improve because you’ve replaced subjectivity with a repeatable, evidence-driven operating system.