Notes

Things worth writing down.

Short pieces on product decisions, mostly the ones that went sideways. Lessons are more useful than wins and I have more of them.

FiledSep 2026
OnInfluence, evidence, and org design
  • Decision-making
  • Influence

I lost that argument on the wrong axis

I once spent two quarters making a product-merit case for an investment I believed in. I brought partner feedback. I ran validation sessions with the actual target customer profile and found the offering did not serve them. I benchmarked two competitors and showed one of them had the capability we lacked. Each round I came back with more evidence than the last.

I lost. And the reason I lost is the part worth writing down: the decision was not being made on product merit at all. It was being made on budget ownership and organizational structure. The path that won was available because the license budget sat in a different function. I was arguing quality into a room that was deciding on cost center.

Two things I would now do before building any case of that kind.

Establish ground truth first. I was arguing from qualitative feedback and inference while the program’s own numbers sat unreconciled. Every version of my case was weaker than it needed to be, and that was avoidable. I went and got the data afterward and delivered it as an audit to the C-suite — which is exactly the thing that should have come first.

Diagnose where the decision actually gets made, and who owns the budget behind it. Not who has the title. Not who is in the meeting. Who absorbs the cost of a yes. That is a different question from “what is the right thing to build,” and answering it first changes what evidence you go and get.

I committed fully to the path that was chosen and delivered it. I still think I was right about the gap. Being right about the product and wrong about the room is a loss, and it is worth naming as one.

More coming. I would rather this page grow slowly with things I actually believe than fill up with posts written to have posted.