Goal setting framework

Goal Setting Framework

Structures professional development goals that are specific enough to execute and measurable enough to track. Most CSMs set goals that are either too vague ("get better at executive engagement") or too tactical ("complete the XYZ certification"). This skill finds the productive middle: goals connected to career progression with concrete actions and milestones.

How to Use

Provide:

• Your current role and level
• Your target (next role, specific skill you want to develop, capability you want to build)
• Timeline (this quarter, this half, this year)
• Your strengths (what you are already good at)
• Your gaps (what you know you need to develop)
• Context (what your manager has told you, what your performance review highlighted, what you observe about people at the level above you)

Goal Structure

The Progression Model

Every development goal follows a progression:

Awareness (I know this exists and why it matters) -> Understanding (I can explain the concept and recognise when it applies) -> Application (I can do it with guidance or templates) -> Proficiency (I can do it independently and consistently) -> Mastery (I can teach it, adapt it to novel situations, and improve on existing approaches)

When setting a goal, identify where you are on this progression and where you want to be by the deadline. Moving two levels in a quarter is realistic. Moving four is not.

Goal Template

For each goal:

Element	Content	Example
Goal statement	Specific capability you will develop	"Develop the ability to lead executive-level conversations that result in strategic alignment and commercial commitments"
Current level	Where you are on the progression	"Application -- I can prepare for executive meetings with a template but I rely on my manager for the actual conversation"
Target level	Where you want to be	"Proficiency -- I can lead an executive conversation independently, adapt in real-time, and achieve the defined outcome"
Why it matters	How this connects to your career	"Executive engagement is the primary skill gap between my current Senior CSM role and a Principal / Director path"
Success metric	How you will know you achieved it	"Led 3 executive conversations independently with positive outcomes (measured by: follow-up action agreed, relationship strengthened per customer feedback)"
Actions	Specific steps to get from current to target	See below
Timeline	Milestones with dates	See below

Action Planning

For each goal, define 4-6 actions across three categories:

Learn: Build the knowledge foundation

• Read, study, take a course, attend a training
• Example: "Complete the executive communication workshop by [date]"
• Example: "Study 5 recorded executive calls from senior CSMs to identify patterns"

Practice: Apply in progressively higher-stakes situations

• Start low-risk, increase stakes as confidence builds
• Example: "Lead the executive section of 2 QBRs with my manager observing (not leading) by [date]"
• Example: "Prepare and deliver an executive briefing to my VP on a key account by [date]"

Reflect: Process what you learn from practice

• Debrief with your manager or a peer after each practice opportunity
• Example: "After each executive conversation, write a 5-minute self-assessment: what worked, what I would change, what I need to improve"
• Example: "Monthly check-in with my manager specifically about this development goal"

Timeline

Map actions to a realistic timeline:

Month	Focus	Actions	Milestone
Month 1	Learn	[Learning actions]	Foundation built: can articulate the approach and have studied examples
Month 2	Practice (low-risk)	[First application attempts]	First practice completed: led a lower-stakes executive interaction
Month 3	Practice (higher-risk) + Reflect	[Independent application]	Goal achieved: led an independent executive conversation with a positive outcome

Common CSM Development Goals

Goal Area	What It Involves	Why It Matters for Career Growth
Executive engagement	Leading strategic conversations at VP/C-level	The primary differentiator between senior CSMs and CS leaders
Commercial acumen	Understanding financial impact, leading pricing discussions, building business cases	CSMs who can talk revenue, not just relationships, get promoted
Strategic thinking	Moving from reactive to proactive, building account strategies, seeing patterns across the portfolio	The shift from managing accounts to managing a business
Cross-functional influence	Getting product, engineering, and sales to act on CS intelligence without direct authority	The CSM's effectiveness multiplier -- you achieve outcomes through others
Data literacy	Interpreting analytics, building evidence-based arguments, using data to drive decisions	The baseline expectation for any senior CS role
Change management	Helping customers drive adoption, navigate organisational resistance, and implement new processes	The most consultative and highest-value skill a CSM can develop

Output Format

## Development Plan: [Name]
**Period:** [Quarter/Half/Year]
**Current Role:** [role and level]
**Target:** [what you are working toward]

### Goals (2-3 maximum)

**Goal 1: [Statement]**
Current: [level] -> Target: [level]
Why: [career connection]
Success metric: [measurable outcome]

Actions:
- Learn: [specific actions with dates]
- Practice: [specific actions with dates]
- Reflect: [specific actions with dates]

Timeline:
[Month-by-month milestones]

[Repeat for Goals 2-3]

### Review Schedule
Monthly self-assessment: [date]
Manager check-in: [date]
Quarter-end review: [date]

Quality Gates

• Is each goal specific enough to act on? "Get better at CS" is not a goal. "Develop the ability to build and present ROI evidence to CFO-level audiences" is
• Are you at the right level of ambition? Moving from Awareness to Mastery in one quarter is unrealistic. Moving from Application to Proficiency is achievable and meaningful
• Do the actions include all three categories (Learn, Practice, Reflect)? Learning without practice is theory. Practice without reflection is repetition. You need all three
• Is there a measurable outcome? If you cannot evaluate at quarter-end whether you achieved the goal, it was not specific enough
• Are you limiting to 2-3 goals? More than 3 development goals in a quarter means none get serious attention. Depth over breadth

Principles

• Development goals should make you uncomfortable. If you are confident you will hit every milestone without effort, the goals are too easy. The discomfort is the growth
• Your manager is a resource, not an audience. Share the plan with them. Ask for opportunities to practice. Request feedback after each application. A development plan that lives in your head and is never shared with your manager will not get the support or accountability it needs
• Development is not linear. You will have sessions where you regress from Proficiency back to Application because the situation was harder than expected. That is normal. The progression model is a direction, not a guarantee
• The best development happens on real accounts with real stakes. Simulations and training build the foundation. Applying the skill on a real executive conversation with a real customer is where learning converts to capability