The first 30 days as a new UK sales manager

The first 30 days of a new sales-manager role establish the team's baseline expectations of how this manager will run their book. Done well, the first month produces a coaching cadence, a deal-review rhythm, and a forecast process that hold for 12-18 months. Done poorly, the first month produces a manager seen as performative or absent, and the team disengages.

This piece is a practitioner walkthrough of the first 30 days.

Week 1: listen, don't act

The objective: understand the team you've inherited before you change anything.

By end of week 1:

• 30-minute 1:1 with every direct report. Three questions, repeated: 'What's working that I should keep?'; 'What's not working that I should change?'; 'What support do you need that you haven't been getting?'
• Review of the team's recent quarter: pipeline coverage, attainment, win rate, key deals that closed and key deals that lost, current forecast.
• Conversation with your peer managers (other sales managers, RevOps, marketing) to understand cross-functional context.
• Conversation with your VP / CRO to align on expectations: what does success look like at 30 days, 90 days, 180 days.

What NOT to do in week 1: announce major changes; replace named tools or processes; reassign accounts; restructure the team.

The temptation to act early is strong. Resist. The team is reading you for whether you'll actually listen or whether the listening is performative.

Week 2: lock the cadences

The objective: install the rhythm that you'll run the team on.

The two key cadences to lock:

Weekly 1:1. 30 minutes per AE per week. Standard agenda: deal updates, blockers, coaching opportunity, professional development. The 1:1 is yours and the AE's; protect it.

Deal walkthrough cadence. Weekly format (see prior piece on deal walkthroughs). One deal per week, rotating across the team. Manager facilitates; team learns.

Both cadences should be on the team calendar by end of week 2. Skipping or rescheduling them in the first 90 days signals that the cadence isn't real; protect them aggressively.

Week 3: lock the forecast process

The objective: install the forecast cadence that produces accurate predictions.

The forecast process to install:

• Monday morning: AEs update their CRM forecasts (commit / best-case / pipeline) by a defined time.
• Tuesday morning: forecast call with the team. Each AE presents their commit. Manager challenges. Team learns the forecast standard.
• Friday afternoon: forecast accuracy review. Last week's commits vs actual outcomes. Corrections noted.

The forecast call is where the team's forecast credibility is built or destroyed. AEs over-forecasting in week 3 should be challenged in week 4; manager who lets it slide loses forecast control by month 3.

By end of week 3: the manager has facilitated the first weekly deal walkthrough and the first forecast call. The cadence is real.

Week 4: document the 'how I work' note

The objective: make your management style legible to the team.

The manager 'how I work' note is a 1-2 page document covering:

• How you run 1:1s. What you'll talk about; what you won't.
• How you run forecast calls. What standard of commit you expect. What disqualifies a commit.
• How you run deal walkthroughs. What format. What you're looking for.
• What earns escalation to you (deal blockers, customer escalations, internal cross-functional issues).
• What doesn't earn escalation (small administrative issues; AE-to-AE friction the AEs should resolve themselves).
• Your communication style: what you respond to in real time, what waits.
• What you measure (specific metrics) and what you don't (politics, presence, performative urgency).

Share the note with the team in week 4 1:1s. Discuss. Refine. The note becomes the operating manual for the team's relationship with you.

What to assess at day 30

By the end of week 4, you should know:

• Which AEs are at risk on attainment. Why.
• Which deals are real and which are no-decision risk.
• What's working in the team's existing process and what isn't.
• Where you'll invest the next 60 days.

You should NOT have made major changes yet. Day 30 is the inflection point: decisions made before day 30 are usually wrong; decisions made after day 30 with the context you've built are usually right.

What goes wrong in the first 30 days

Three patterns:

Premature reorganisation. The new manager arrives, sees the team's structure, and announces changes in week 1. The team disengages because the manager hasn't yet earned the right to change things. Resolution: hold the changes until at least day 45; build the relationship first.

Performative cadence. The manager installs the cadence (1:1s, forecast calls, deal walkthroughs) but skips them under pressure of urgent issues. The team learns the cadence isn't real; engagement falls. Resolution: protect the cadence aggressively; reschedule conflicting commitments rather than the team's cadence.

Absent listening. The manager starts with strong views about how the team should run and listens performatively in week 1 without integrating the input. Team feedback in week 1 should visibly shape week 2-4 decisions; if it doesn't, the team learns the listening was theatre.

What to operationalise

Five habits:

1. 30-minute 1:1 with every report in week 1. Three questions, listened to.
2. Cadence locked by end of week 2. 1:1s and deal walkthroughs on calendar.
3. Forecast process locked by end of week 3. Tuesday calls, Friday accuracy review.
4. 'How I work' note shared by end of week 4.
5. No major structural changes before day 30.

The first 30 days are foundation, not action. Acting before the foundation is laid produces motion without progress.

This is editorial coverage of public sales-management methodology. For specific advice on managing your team, work with your VP and HR partners.