Thirty days to listen and measure, thirty to pick three priorities, forty to deliver a first visible result. In that order, and with no redesign announced before day 60.
The benchmark
| Period | What it should produce |
|---|---|
| Days 1 to 30 | Your access, numbers you trust and a list of what's broken |
| Days 31 to 60 | Three priorities with numbers attached, approved by leadership |
| Days 61 to 100 | One shipped result and the roadmap for the year |
The first month starts with a down-to-earth question: who holds the keys?
When a team starts work at a brand, the launch checklist opens with nearly thirty lines of access and inventory (Shopify admin, Search Console, GA4, Tag Manager, Google Ads, Meta, Klaviyo, ERP, review and support tools) before the first question about the catalog.
It gets filled in during launch week, because the audit can't start without that access, and a single missing item is enough to push back the schedule.
A new head of e-commerce inherits the same problem, only less visible. In GA4, only the Administrator role can add or remove access. If that role belongs only to the previous person in the job, or to an agency that has since left, nothing breaks on your first day.
You find out weeks later, the day you need to fix a purchase event and no one on the team can give you the permission.
The rule
Your first win is a fix. Repair something everyone knew was broken and no one was dealing with.
Michael Watkins, whose book The First 90 Days is the go-to reference on starting a new role, advises aiming for early wins to earn the trust of leadership and teams.
In e-commerce, we read it this way: a fix earns credit fast, because it proves you listened. A collection filter that has shown sold-out products for a year, or a purchase counted twice in GA4, are good candidates.
The steps
- Measurement. Compare the number of orders in Shopify with the number of purchases in GA4 over the same month. As long as the gap is unexplained, no conversion rate deserves comment.
- Access. For each tool, note who holds admin rights, and ask to be added anywhere only one account has that role.
- Customer service. Read a month of messages: the complaints that come back every week already make up your first list of fixes.
- Teams and vendors. Meet with everyone and ask the same question, "What slows you down?", so the answers stay comparable.
- The P&L. Connect the site to margins by spotting which categories make money and which cost you in returns or acquisition.
- The three priorities. Present them with numbers attached, along with the list of what you won't do.
- The line for leadership:
"Here is the fix I'm delivering before day 100, and the two projects I won't launch until our numbers are reliable."
The trap
The most common temptation is to apply the playbook from your previous job, which was built for other customers, other margins and another team.
The other reflex is to switch agencies or launch a redesign in the first month to mark your territory.
You then inherit a project that will run for months before you've understood what was wrong, and the first fix waits for the launch.
