Goal templates — Product Designer — P3

Product Designer · Product Designer · P3 — Mid-Level Professional

These are canon-derived frames, not advice: every line is either verbatim JobFrame canon text or a fixed template wrapping it. ⟨target⟩ / ⟨baseline⟩ / ⟨date⟩ are placeholders for the manager to fill in. Nothing here is generated by AI — rows are omitted, never invented, when the canon lacks the underlying field.

SMART goals

One row per canon core output / responsibility this level owns.

JFM responsibility (P3)

Executes the full design process independently on product flows of average complexity, from discovery through high-fidelity UI delivery.

Specific: Deliver: "Executes the full design process independently on product flows of average complexity, from discovery through high-fidelity UI delivery."
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Evaluates identifiable factors from research and constraints to solve diverse problems with moderate independence."
Relevant: Advances the Product Designer · Product Designer mandate for a P3 — Mid-Level Professional.
Time-bound: ⟨date⟩

JFM responsibility (P3)

Conducts typical discovery and validation research — competitive benchmarking, A/B testing, and usability testing using tools such as Maze, UserTesting, and Optimal Workshop — and identifies problems surfaced during that research.

Specific: Deliver: "Conducts typical discovery and validation research — competitive benchmarking, A/B testing, and usability testing using tools such as Maze, UserTesting, and Optimal Workshop — and identifies problems surfaced during that research."
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Evaluates identifiable factors from research and constraints to solve diverse problems with moderate independence."
Relevant: Advances the Product Designer · Product Designer mandate for a P3 — Mid-Level Professional.
Time-bound: ⟨date⟩

JFM responsibility (P3)

Plans own day-to-day work and brainstorms and executes product development against milestones set by the PM and design lead.

Specific: Deliver: "Plans own day-to-day work and brainstorms and executes product development against milestones set by the PM and design lead."
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Evaluates identifiable factors from research and constraints to solve diverse problems with moderate independence."
Relevant: Advances the Product Designer · Product Designer mandate for a P3 — Mid-Level Professional.
Time-bound: ⟨date⟩

JFM responsibility (P3)

Articulates design decisions and the reasoning behind them to engineers and PMs, drawing on familiarity with HTML/CSS and front-end concepts to align on technical constraints.

Specific: Deliver: "Articulates design decisions and the reasoning behind them to engineers and PMs, drawing on familiarity with HTML/CSS and front-end concepts to align on technical constraints."
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Evaluates identifiable factors from research and constraints to solve diverse problems with moderate independence."
Relevant: Advances the Product Designer · Product Designer mandate for a P3 — Mid-Level Professional.
Time-bound: ⟨date⟩

JFM responsibility (P3)

Builds and refines reusable design-system components using Figma Variables and Components to ensure consistent implementation.

Specific: Deliver: "Builds and refines reusable design-system components using Figma Variables and Components to ensure consistent implementation."
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Evaluates identifiable factors from research and constraints to solve diverse problems with moderate independence."
Relevant: Advances the Product Designer · Product Designer mandate for a P3 — Mid-Level Professional.
Time-bound: ⟨date⟩

Copy / print as textshow ▾

1. Executes the full design process independently on product flows of average complexity, from discovery through high-fidelity UI delivery.  [source: JFM responsibility (P3)]
   Specific:    Deliver: "Executes the full design process independently on product flows of average complexity, from discovery through high-fidelity UI delivery."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Evaluates identifiable factors from research and constraints to solve diverse problems with moderate independence."
   Relevant:    Advances the Product Designer · Product Designer mandate for a P3 — Mid-Level Professional.
   Time-bound:  ⟨date⟩

2. Conducts typical discovery and validation research — competitive benchmarking, A/B testing, and usability testing using tools such as Maze, UserTesting, and Optimal Workshop — and identifies problems surfaced during that research.  [source: JFM responsibility (P3)]
   Specific:    Deliver: "Conducts typical discovery and validation research — competitive benchmarking, A/B testing, and usability testing using tools such as Maze, UserTesting, and Optimal Workshop — and identifies problems surfaced during that research."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Evaluates identifiable factors from research and constraints to solve diverse problems with moderate independence."
   Relevant:    Advances the Product Designer · Product Designer mandate for a P3 — Mid-Level Professional.
   Time-bound:  ⟨date⟩

3. Plans own day-to-day work and brainstorms and executes product development against milestones set by the PM and design lead.  [source: JFM responsibility (P3)]
   Specific:    Deliver: "Plans own day-to-day work and brainstorms and executes product development against milestones set by the PM and design lead."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Evaluates identifiable factors from research and constraints to solve diverse problems with moderate independence."
   Relevant:    Advances the Product Designer · Product Designer mandate for a P3 — Mid-Level Professional.
   Time-bound:  ⟨date⟩

4. Articulates design decisions and the reasoning behind them to engineers and PMs, drawing on familiarity with HTML/CSS and front-end concepts to align on technical constraints.  [source: JFM responsibility (P3)]
   Specific:    Deliver: "Articulates design decisions and the reasoning behind them to engineers and PMs, drawing on familiarity with HTML/CSS and front-end concepts to align on technical constraints."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Evaluates identifiable factors from research and constraints to solve diverse problems with moderate independence."
   Relevant:    Advances the Product Designer · Product Designer mandate for a P3 — Mid-Level Professional.
   Time-bound:  ⟨date⟩

5. Builds and refines reusable design-system components using Figma Variables and Components to ensure consistent implementation.  [source: JFM responsibility (P3)]
   Specific:    Deliver: "Builds and refines reusable design-system components using Figma Variables and Components to ensure consistent implementation."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Evaluates identifiable factors from research and constraints to solve diverse problems with moderate independence."
   Relevant:    Advances the Product Designer · Product Designer mandate for a P3 — Mid-Level Professional.
   Time-bound:  ⟨date⟩

OKRs

Objectives from this level's core outputs; key results only where a real dimension or capability backs them.

JFM responsibility (P3)

Executes the full design process independently on product flows of average complexity, from discovery through high-fidelity UI delivery.

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Executes the full design process independently on product flows of average complexity, from discovery through high-fidelity UI delivery."
Evidence at this level's scope bar: "Features or a sub-system end-to-end" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P3)

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Conducts typical discovery and validation research — competitive benchmarking, A/B testing, and usability testing using tools such as Maze, UserTesting, and Optimal Workshop — and identifies problems surfaced during that research."
Evidence at this level's autonomy bar: "Works independently on standard work; reviewed on the non-standard" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P3)

Plans own day-to-day work and brainstorms and executes product development against milestones set by the PM and design lead.

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Plans own day-to-day work and brainstorms and executes product development against milestones set by the PM and design lead."
Evidence at this level's complexity bar: "Diverse problems; adapts existing approaches" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P3)

Articulates design decisions and the reasoning behind them to engineers and PMs, drawing on familiarity with HTML/CSS and front-end concepts to align on technical constraints.

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Articulates design decisions and the reasoning behind them to engineers and PMs, drawing on familiarity with HTML/CSS and front-end concepts to align on technical constraints."
Evidence at this level's impact bar: "Project / team outcomes" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P3)

Builds and refines reusable design-system components using Figma Variables and Components to ensure consistent implementation.

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Builds and refines reusable design-system components using Figma Variables and Components to ensure consistent implementation."
Evidence at this level's decision rights bar: "Owns implementation decisions for own scope" — ⟨target⟩ by ⟨date⟩

Copy / print as textshow ▾

Objective 1: Executes the full design process independently on product flows of average complexity, from discovery through high-fidelity UI delivery.  [source: JFM responsibility (P3)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Executes the full design process independently on product flows of average complexity, from discovery through high-fidelity UI delivery."
  KR2. Evidence at this level's scope bar: "Features or a sub-system end-to-end" — ⟨target⟩ by ⟨date⟩

Objective 2: Conducts typical discovery and validation research — competitive benchmarking, A/B testing, and usability testing using tools such as Maze, UserTesting, and Optimal Workshop — and identifies problems surfaced during that research.  [source: JFM responsibility (P3)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Conducts typical discovery and validation research — competitive benchmarking, A/B testing, and usability testing using tools such as Maze, UserTesting, and Optimal Workshop — and identifies problems surfaced during that research."
  KR2. Evidence at this level's autonomy bar: "Works independently on standard work; reviewed on the non-standard" — ⟨target⟩ by ⟨date⟩

Objective 3: Plans own day-to-day work and brainstorms and executes product development against milestones set by the PM and design lead.  [source: JFM responsibility (P3)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Plans own day-to-day work and brainstorms and executes product development against milestones set by the PM and design lead."
  KR2. Evidence at this level's complexity bar: "Diverse problems; adapts existing approaches" — ⟨target⟩ by ⟨date⟩

Objective 4: Articulates design decisions and the reasoning behind them to engineers and PMs, drawing on familiarity with HTML/CSS and front-end concepts to align on technical constraints.  [source: JFM responsibility (P3)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Articulates design decisions and the reasoning behind them to engineers and PMs, drawing on familiarity with HTML/CSS and front-end concepts to align on technical constraints."
  KR2. Evidence at this level's impact bar: "Project / team outcomes" — ⟨target⟩ by ⟨date⟩

Objective 5: Builds and refines reusable design-system components using Figma Variables and Components to ensure consistent implementation.  [source: JFM responsibility (P3)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Builds and refines reusable design-system components using Figma Variables and Components to ensure consistent implementation."
  KR2. Evidence at this level's decision rights bar: "Owns implementation decisions for own scope" — ⟨target⟩ by ⟨date⟩

MBO areas

Key result areas from this level's responsibilities, each with a standard grounded in the canon leveling rubric where one exists.

Area	Standard	Target	Due
Executes the full design process independently on product flows of average complexity, from discovery through high-fidelity UI delivery.	Consistent with this level's jfm knowledge-application rubric: "Applies the full design process — UX, UI, interaction design, standard research methods, and basic web-technology familiarity — independently across diverse product flows of average complexity."	⟨target⟩	⟨date⟩
Conducts typical discovery and validation research — competitive benchmarking, A/B testing, and usability testing using tools such as Maze, UserTesting, and Optimal Workshop — and identifies problems surfaced during that research.	Consistent with this level's jfm knowledge-application rubric: "Applies the full design process — UX, UI, interaction design, standard research methods, and basic web-technology familiarity — independently across diverse product flows of average complexity."	⟨target⟩	⟨date⟩
Plans own day-to-day work and brainstorms and executes product development against milestones set by the PM and design lead.	Consistent with this level's jfm knowledge-application rubric: "Applies the full design process — UX, UI, interaction design, standard research methods, and basic web-technology familiarity — independently across diverse product flows of average complexity."	⟨target⟩	⟨date⟩
Articulates design decisions and the reasoning behind them to engineers and PMs, drawing on familiarity with HTML/CSS and front-end concepts to align on technical constraints.	Consistent with this level's jfm knowledge-application rubric: "Applies the full design process — UX, UI, interaction design, standard research methods, and basic web-technology familiarity — independently across diverse product flows of average complexity."	⟨target⟩	⟨date⟩
Builds and refines reusable design-system components using Figma Variables and Components to ensure consistent implementation.	Consistent with this level's jfm knowledge-application rubric: "Applies the full design process — UX, UI, interaction design, standard research methods, and basic web-technology familiarity — independently across diverse product flows of average complexity."	⟨target⟩	⟨date⟩

Copy / print as textshow ▾

1. Area: Executes the full design process independently on product flows of average complexity, from discovery through high-fidelity UI delivery.  [source: JFM responsibility (P3) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies the full design process — UX, UI, interaction design, standard research methods, and basic web-technology familiarity — independently across diverse product flows of average complexity."
   Target:   ⟨target⟩   Due: ⟨date⟩

2. Area: Conducts typical discovery and validation research — competitive benchmarking, A/B testing, and usability testing using tools such as Maze, UserTesting, and Optimal Workshop — and identifies problems surfaced during that research.  [source: JFM responsibility (P3) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies the full design process — UX, UI, interaction design, standard research methods, and basic web-technology familiarity — independently across diverse product flows of average complexity."
   Target:   ⟨target⟩   Due: ⟨date⟩

3. Area: Plans own day-to-day work and brainstorms and executes product development against milestones set by the PM and design lead.  [source: JFM responsibility (P3) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies the full design process — UX, UI, interaction design, standard research methods, and basic web-technology familiarity — independently across diverse product flows of average complexity."
   Target:   ⟨target⟩   Due: ⟨date⟩

4. Area: Articulates design decisions and the reasoning behind them to engineers and PMs, drawing on familiarity with HTML/CSS and front-end concepts to align on technical constraints.  [source: JFM responsibility (P3) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies the full design process — UX, UI, interaction design, standard research methods, and basic web-technology familiarity — independently across diverse product flows of average complexity."
   Target:   ⟨target⟩   Due: ⟨date⟩

5. Area: Builds and refines reusable design-system components using Figma Variables and Components to ensure consistent implementation.  [source: JFM responsibility (P3) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies the full design process — UX, UI, interaction design, standard research methods, and basic web-technology familiarity — independently across diverse product flows of average complexity."
   Target:   ⟨target⟩   Due: ⟨date⟩

Scorecard

Only perspectives with real canon backing are shown — no Financial or Customer perspective, since nothing in the canon grounds business-financial or customer measures for a role alone.

Internal process

"Executes the full design process independently on product flows of average complexity, from discovery through high-fidelity UI delivery."→ ⟨target⟩ by ⟨date⟩
"Conducts typical discovery and validation research — competitive benchmarking, A/B testing, and usability testing using tools such as Maze, UserTesting, and Optimal Workshop — and identifies problems surfaced during that research."→ ⟨target⟩ by ⟨date⟩
"Plans own day-to-day work and brainstorms and executes product development against milestones set by the PM and design lead."→ ⟨target⟩ by ⟨date⟩
"Articulates design decisions and the reasoning behind them to engineers and PMs, drawing on familiarity with HTML/CSS and front-end concepts to align on technical constraints."→ ⟨target⟩ by ⟨date⟩
"Builds and refines reusable design-system components using Figma Variables and Components to ensure consistent implementation."→ ⟨target⟩ by ⟨date⟩

Role calibration

Meets the scope bar: "Features or a sub-system end-to-end"→ ⟨target⟩ by ⟨date⟩
Meets the autonomy bar: "Works independently on standard work; reviewed on the non-standard"→ ⟨target⟩ by ⟨date⟩
Meets the complexity bar: "Diverse problems; adapts existing approaches"→ ⟨target⟩ by ⟨date⟩
Meets the impact bar: "Project / team outcomes"→ ⟨target⟩ by ⟨date⟩
Meets the decision rights bar: "Owns implementation decisions for own scope"→ ⟨target⟩ by ⟨date⟩
Meets the leadership bar: "Mentors juniors informally"→ ⟨target⟩ by ⟨date⟩

Copy / print as textshow ▾

Internal process
  - "Executes the full design process independently on product flows of average complexity, from discovery through high-fidelity UI delivery."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P3)]
  - "Conducts typical discovery and validation research — competitive benchmarking, A/B testing, and usability testing using tools such as Maze, UserTesting, and Optimal Workshop — and identifies problems surfaced during that research."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P3)]
  - "Plans own day-to-day work and brainstorms and executes product development against milestones set by the PM and design lead."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P3)]
  - "Articulates design decisions and the reasoning behind them to engineers and PMs, drawing on familiarity with HTML/CSS and front-end concepts to align on technical constraints."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P3)]
  - "Builds and refines reusable design-system components using Figma Variables and Components to ensure consistent implementation."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P3)]

Role calibration
  - Meets the scope bar: "Features or a sub-system end-to-end"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Scope)]
  - Meets the autonomy bar: "Works independently on standard work; reviewed on the non-standard"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Autonomy)]
  - Meets the complexity bar: "Diverse problems; adapts existing approaches"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Complexity)]
  - Meets the impact bar: "Project / team outcomes"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Impact)]
  - Meets the decision rights bar: "Owns implementation decisions for own scope"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Decision rights)]
  - Meets the leadership bar: "Mentors juniors informally"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Leadership)]