Leading Magento Enterprise builds inside Magento's own ECG
Two Magento Enterprise engagements, Easton-Bell Sports and Longines, led as a member of the original Magento Expert Consulting Group in 2009–2011.
- Client
- Magento Inc. (Expert Consulting Group)
- Industry
- Sporting goods and luxury watches
- Period
- 2009–2011
- Role
- ECG consultant and team lead
Results
- Engineers led on Easton-Bell Sports
- 11
- Engineers led on Longines
- 4
- Years in the ECG
- 2
Challenge
Between 2009 and 2011 Magento Enterprise was new, and the merchants betting on it were large. The Expert Consulting Group (ECG) was Magento’s own consulting arm: a small group of engineers sent in when an Enterprise customer needed architecture, code review or delivery from people who knew the platform from the inside. I was a member of the original group.
Two engagements defined that period. Easton-Bell Sports ran one of the largest Magento Enterprise deployments of its time. Longines, part of the Swatch Group, needed a store built to the standards of a luxury watchmaker. Both were built on a platform that was still maturing, with few established patterns to borrow.
Approach
On Easton-Bell Sports I led an ECG team of 11 engineers; on Longines, a team of 4. The method was the same in both. Agree the architecture early. Decide what belongs in configuration and what needs custom code. Review every change against the platform’s own conventions. Leave the customer’s team able to run the store without the consultants.
Alongside the projects I served on the S.W.A.T. unit, the small group Magento sent to urgent escalations at Enterprise customers. The job there was narrow: find the cause quickly, fix it, and leave a fix the merchant’s own engineers understood.
Result
The lasting result is the method, not a dashboard. ECG work taught me to read an unfamiliar Magento codebase fast, to separate platform problems from customization problems, and to lead engineers on someone else’s codebase without losing sight of the business behind it.
The same habits shape my work today, 17 years later. Architecture reviews start from how the platform is meant to be extended. Audits rank findings by business impact, not by count. Long engagements such as Teabloom and MarketNation rest on the same rule as the ECG did: leave a team that can carry on without me.