Technical Project Manager
Seattle, Wa
You can't manage what you don't measure, so we adopted one of Amazon's very first "two pizza team" metrics: reduce the number of customer contacts per order (later revised to number of contacts per dollar). We first developed the means to measure this, then executed toward the stated goal to great success. I managed the Customer Service portion of a number of efforts during this time including Amazon Prime, Return Authorizations, DVD Rentals in EU, Harry Potter Delivery on Publish Date, Multiple Accounts Same Email, and many, many more.In 2005, I was hired as the first TPM for the Marks and Spencer project. M&S is a large UK retailer who needed not only a web presence, but also an in-store tool for their sales associates and an ordering tool for their phone customer service agents. I was in charge of both the in-store tool and the phone tool. Amazon had never built an agent assisted ordering tool before. I traveled to London several times to meet with the client, work in their stores to understand the experience and help write requirements. When deploying to over 800 stores I recommended a "rolling thunder" approach rather than a "big bang" approach. This allowed us to validate the technology early with a small set of employees and also allowed us to train thousands of employees without significant operational disruption.M&S, like other websites we had built (e.g. Target, Gap, Toys R Us, Bebe), was built by identifying an existing site similar to our goal and branching from that code, an untenable approach. I spearheaded an effort to componentize the functionality of our websites starting with the Order PipeLine (OPL). The OPL we were replacing was 51k lines of code. We winnowed that down to 1500 lines and just a few hundred lines of configuration. Not only does this reduce maintenance costs, but we measured that implementing a new OPL with our technology reduced the effort from 2 years to 4 weeks. We repeated this success with detail pages and others.