← All case studies
AWS Billing, line-of-credit pilot

Knowing When to Stop

A financing pilot had little evidence of customer demand. I challenged the expansion with data, then committed fully to objective reporting and documented operations after leadership made its decision.

Program ManagementOperations

The Problem

An AWS Billing pilot offered customers financing through a banking partner to spread out their AWS costs. Leadership wanted to expand it to additional banking partners. But when I inherited the pilot, there was little documentation on why it existed, and little evidence customers had asked for it.

Role
Program Manager

What I did

  • Went back to the business case: asked for the requirements, customer research, and evidence of demand, and dug into the pilot dashboard.
  • Found the demand wasn't there. Few customers even clicked through, fewer applied, and none of the applicants were approved during the time I ran it.
  • Recommended validating customer demand before expanding - support data, customer requests, targeted surveys.
  • When leadership chose to continue the original strategy, committed fully: automated the weekly reporting, documented the operational processes, and kept delivering objective updates.

The Outcome

Leadership made the call with a clear-eyed view of the pilot's real traction, and the program ran on automated reporting and documented processes while its future was decided.

Making a recommendation and making a decision are two different responsibilities. My job is to challenge assumptions with evidence, then commit fully once the call is made.

← Back to all case studies
Laura Barry — Operations & Program Management