Setup
Three orgs were arguing through one login surface.
Security needed friction. Product needed conversion. Fraud needed signals. None of those teams were wrong, but the organization lacked a shared language for deciding which risk mattered most.
This draft keeps the structure ready for refinement: setup, diagnosis, tradeoff, proof, artifacts, and reflection. The final narrative should show how Tre led through evidence without formal authority over the full system.
Diagnosis
The design problem was really a decision problem.
The question was not whether phone verification added friction. It was which risk Walmart wanted to own without it.
Undeliverable email, missing phone numbers, and account-takeover signals made identity a business platform problem.
Blanket security would punish good customers. Pure conversion logic would leave the platform exposed.
Tradeoff System
Move the room from preference to evidence.
- Name the shared risk
- Build the cost-benefit case
- Test mandatory verification
- Add phone collection moments
- Risk-tier the Walmart+ flow
- Codify design principles
The final version should make the leadership move clear: Tre did not win the room by arguing for friction. He reframed friction as a measurable business decision and designed flows that applied it only where the risk justified it.
The article should stay sharp about influence. This was leadership without direct authority, built through data, prototypes, language, and repeated cross-functional decisions.
Result
Trust became a platform capability.
The final proof layer should connect the business outcomes to the leadership behavior: building the evidence, making tradeoffs legible, and giving teams principles they could use without escalating every decision.
