Platform leadership & decisions
Moving the platform forward.
Bringing teams with it.
Frontend modernization at Kohl’s
The situation
We were moving core ecommerce experiences onto a modern frontend platform while keeping the business running. Teams had real concerns about what they’d own, how much control they’d keep, and the move itself. People would nod in meetings, but that didn’t always carry through to the work. And with peak shopping season coming, we needed to agree on what was ready to scale.
Getting to a real commitment
I wrote a working agreement and walked through it with leads from each team. We got specific about what the platform team owned, what their teams would keep control of, and where they’d go for support or a decision. Then we asked them to commit. If they disagreed, I wanted to hear it so we could work through it. We were accountable for addressing their concerns, and they were accountable for following through on the commitment.
Deciding what could scale
Teams were used to waiting for a statistically significant A/B test win before scaling. For this move, we needed to ask what would give us enough confidence that the platform worked without materially hurting the business or making shopping harder. We looked at performance, customer behavior, and revenue per visit together. Equivalence testing helped us check whether revenue per visit stayed within an agreed tolerance. Customer behavior helped us spot any new friction. A faster platform mattered, but we needed the other signals too.
The result
We had clear commitments from teams and a shared way to decide what could roll out. For the new product listing experience, equivalence testing showed revenue per visit was within the agreed tolerance. That gave us evidence to keep moving. It didn’t show a revenue lift, and we were careful to keep that distinction clear.
What I took from it
People nodding in a meeting doesn’t tell you whether they’re committed. I’d rather get the disagreement out where we can do something about it. With the data, we also needed to agree on what was enough to move forward and what would make us stop. My job was to help teams work through those questions so we could keep moving and learning.