Outcomes over output.

It had unintentionally become a waterfall project: one large scope, no incremental milestones. I restructured the work into deliverable chunks and mapped cross-functional dependencies that had never been aligned.

The PM leading it held a different view of the process, so I brought him along incrementally rather than by mandate. The structure proved itself later during a transition, when the project held momentum because the work was already decomposed. That framework now powers our integrations marketplace, including Marketing Center inside Keap's Automation Builder.

We promoted a two-way sync, and it was a genuine commercial claim, which is why nobody wanted to touch it. Experience with integrations told me two-way syncs are fragile, but I didn't make the call on instinct.

I pulled customer care tickets and quantified how many customers were hitting sync failures. Once the cost in customer pain was visible, the conversation changed. We moved to one-way, stabilized the product, and drove that error to zero. The people who resisted weren't wrong to resist. A claim that breaks in production isn't a selling point, it's a churn risk.

I inherited a declining product that was constantly confused with other products carrying the Sprint Mobile name. When I went looking for data to confirm it, customer care records were nearly impossible to search, because the naming confusion had contaminated the data.

So I made the call on pattern recognition and renamed it. The same product humbled me that year. A feature I was convinced customers needed scored dead last in survey. The product grew by 7,000 subscribers over 18 months on the rename and survey-driven enhancements, with no new investment beyond normal marketing. Intuition earns the right to move fast. Every bet still gets validated.