I Drove $31M in Bookings. The System Said I Needed Improvement.

Source: Dev.to

The performance review from my peers highlighted my impact:

“One of the better examples of what the Leadership Principles are all about.”
“A thought leader and transformation driver.”
“His ability to lead large‑scale cloud transformations, combining deep technical expertise with strategic long‑term vision.”
“A trusted advisor across organizations.”

In contrast, the system labeled my performance as Needs Improvement – Development Needed—the same review, the same year, the same company.

The Numbers

• Secured production access for our consultants in a customer environment—something never done before. Two predecessors tried and failed. I authored a 30‑page security narrative, presented to review boards for nine months, and achieved approval.
• Obtained third‑party consulting partner approval for production access, an unprecedented accomplishment.
• Reduced account vending time from 30 days to 45 minutes.
• Enabled the customer to access generative AI services early, thanks to the foundational work we built.
• The customer’s CIO showcased our work on the keynote stage at the industry’s largest conference.
• The platform earned Intelligent Digital Enterprise of the Year, Data Mesh of the Year, and a CIO 100 Award.

What I Didn’t Do

The system measured only the absence of certain metrics—not the $31 M in bookings, the reference architecture, the executive briefings at re:Invent, or the timecards.

Customer Satisfaction Score

The customer’s direct feedback was nuanced:

• Happy with the thought leadership (my team and me).
• Unhappy with the number of offshore resources—a staffing decision made by his boss and the sales team, not by us.

He later told me, “Brian, from now on just tell me what to put in the forms. I’m not trying to cause problems for you all.”

Nevertheless, the system recorded a low score and failed to capture this nuance.

Sales Credit Problem

When metrics focus on timecards and certifications, they reward those who excel at filling out forms rather than those who drive real outcomes.

Why This Matters Beyond My Story

Measuring what truly matters—time to outcome, customer success, business impact, architectural quality—reveals the individuals who actually advance the organization.

I created OutcomeOps because I’m done waiting for large organizations to get it right. The Outcome Engineer doesn’t exist within a stack‑ranking system; they operate in models that avoid local‑optimization traps and align everyone around a single question: Did the customer win?

My peers understood the answer; the system did not.