← Product Designer (UI/UX Designer) — P4

Goal templates — Product Designer (UI/UX Designer) — P4

Product Designer (UI/UX Designer) · Product Designer (UI/UX Designer) · P4 — Senior 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 (P4)

Leads design across multiple products or high-complexity product areas, selecting methods and approaches for the team.

Specific: Deliver: "Leads design across multiple products or high-complexity product areas, selecting methods and approaches for the team."
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Performs in-depth analysis of complex variables, deliberately using design decisions to move business metrics across multiple product areas — a scope step up from P3's single-initiative ownership."
Relevant: Advances the Product Designer (UI/UX Designer) · Product Designer (UI/UX Designer) mandate for a P4 — Senior Professional.
Time-bound: ⟨date⟩

JFM responsibility (P4)

Builds and implements design systems with reusable components, maintaining them in Storybook and Zeroheight.

Specific: Deliver: "Builds and implements design systems with reusable components, maintaining them in Storybook and Zeroheight."
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Performs in-depth analysis of complex variables, deliberately using design decisions to move business metrics across multiple product areas — a scope step up from P3's single-initiative ownership."
Relevant: Advances the Product Designer (UI/UX Designer) · Product Designer (UI/UX Designer) mandate for a P4 — Senior Professional.
Time-bound: ⟨date⟩

JFM responsibility (P4)

Understands business metrics and uses design decisions to deliberately affect them, communicating user-centered rationale to stakeholders.

Specific: Deliver: "Understands business metrics and uses design decisions to deliberately affect them, communicating user-centered rationale to stakeholders."
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Performs in-depth analysis of complex variables, deliberately using design decisions to move business metrics across multiple product areas — a scope step up from P3's single-initiative ownership."
Relevant: Advances the Product Designer (UI/UX Designer) · Product Designer (UI/UX Designer) mandate for a P4 — Senior Professional.
Time-bound: ⟨date⟩

JFM responsibility (P4)

Owns the technical handoff — produces UX specs, ensures accessibility (WCAG) conformance, and partners with engineering on implementation.

Specific: Deliver: "Owns the technical handoff — produces UX specs, ensures accessibility (WCAG) conformance, and partners with engineering on implementation."
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Performs in-depth analysis of complex variables, deliberately using design decisions to move business metrics across multiple product areas — a scope step up from P3's single-initiative ownership."
Relevant: Advances the Product Designer (UI/UX Designer) · Product Designer (UI/UX Designer) mandate for a P4 — Senior Professional.
Time-bound: ⟨date⟩

JFM responsibility (P4)

Mentors mid-level and junior designers and may lead the design portion of cross-functional projects.

Specific: Deliver: "Mentors mid-level and junior designers and may lead the design portion of cross-functional projects."
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Performs in-depth analysis of complex variables, deliberately using design decisions to move business metrics across multiple product areas — a scope step up from P3's single-initiative ownership."
Relevant: Advances the Product Designer (UI/UX Designer) · Product Designer (UI/UX Designer) mandate for a P4 — Senior Professional.
Time-bound: ⟨date⟩

Copy / print as textshow ▾

1. Leads design across multiple products or high-complexity product areas, selecting methods and approaches for the team.  [source: JFM responsibility (P4)]
   Specific:    Deliver: "Leads design across multiple products or high-complexity product areas, selecting methods and approaches for the team."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Performs in-depth analysis of complex variables, deliberately using design decisions to move business metrics across multiple product areas — a scope step up from P3's single-initiative ownership."
   Relevant:    Advances the Product Designer (UI/UX Designer) · Product Designer (UI/UX Designer) mandate for a P4 — Senior Professional.
   Time-bound:  ⟨date⟩

2. Builds and implements design systems with reusable components, maintaining them in Storybook and Zeroheight.  [source: JFM responsibility (P4)]
   Specific:    Deliver: "Builds and implements design systems with reusable components, maintaining them in Storybook and Zeroheight."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Performs in-depth analysis of complex variables, deliberately using design decisions to move business metrics across multiple product areas — a scope step up from P3's single-initiative ownership."
   Relevant:    Advances the Product Designer (UI/UX Designer) · Product Designer (UI/UX Designer) mandate for a P4 — Senior Professional.
   Time-bound:  ⟨date⟩

3. Understands business metrics and uses design decisions to deliberately affect them, communicating user-centered rationale to stakeholders.  [source: JFM responsibility (P4)]
   Specific:    Deliver: "Understands business metrics and uses design decisions to deliberately affect them, communicating user-centered rationale to stakeholders."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Performs in-depth analysis of complex variables, deliberately using design decisions to move business metrics across multiple product areas — a scope step up from P3's single-initiative ownership."
   Relevant:    Advances the Product Designer (UI/UX Designer) · Product Designer (UI/UX Designer) mandate for a P4 — Senior Professional.
   Time-bound:  ⟨date⟩

4. Owns the technical handoff — produces UX specs, ensures accessibility (WCAG) conformance, and partners with engineering on implementation.  [source: JFM responsibility (P4)]
   Specific:    Deliver: "Owns the technical handoff — produces UX specs, ensures accessibility (WCAG) conformance, and partners with engineering on implementation."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Performs in-depth analysis of complex variables, deliberately using design decisions to move business metrics across multiple product areas — a scope step up from P3's single-initiative ownership."
   Relevant:    Advances the Product Designer (UI/UX Designer) · Product Designer (UI/UX Designer) mandate for a P4 — Senior Professional.
   Time-bound:  ⟨date⟩

5. Mentors mid-level and junior designers and may lead the design portion of cross-functional projects.  [source: JFM responsibility (P4)]
   Specific:    Deliver: "Mentors mid-level and junior designers and may lead the design portion of cross-functional projects."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Performs in-depth analysis of complex variables, deliberately using design decisions to move business metrics across multiple product areas — a scope step up from P3's single-initiative ownership."
   Relevant:    Advances the Product Designer (UI/UX Designer) · Product Designer (UI/UX Designer) mandate for a P4 — Senior 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 (P4)

Leads design across multiple products or high-complexity product areas, selecting methods and approaches for the team.

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Leads design across multiple products or high-complexity product areas, selecting methods and approaches for the team."
Evidence at this level's scope bar: "A system or set of related features" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P4)

Builds and implements design systems with reusable components, maintaining them in Storybook and Zeroheight.

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Builds and implements design systems with reusable components, maintaining them in Storybook and Zeroheight."
Evidence at this level's autonomy bar: "Self-directed; reviewed at critical decision points" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P4)

Understands business metrics and uses design decisions to deliberately affect them, communicating user-centered rationale to stakeholders.

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Understands business metrics and uses design decisions to deliberately affect them, communicating user-centered rationale to stakeholders."
Evidence at this level's complexity bar: "Complex, ambiguous problems; devises new approaches" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P4)

Owns the technical handoff — produces UX specs, ensures accessibility (WCAG) conformance, and partners with engineering on implementation.

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Owns the technical handoff — produces UX specs, ensures accessibility (WCAG) conformance, and partners with engineering on implementation."
Evidence at this level's impact bar: "Multi-team / function outcomes" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P4)

Mentors mid-level and junior designers and may lead the design portion of cross-functional projects.

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Mentors mid-level and junior designers and may lead the design portion of cross-functional projects."
Evidence at this level's decision rights bar: "Owns technical decisions for a system; influences adjacent design" — ⟨target⟩ by ⟨date⟩

Copy / print as textshow ▾

Objective 1: Leads design across multiple products or high-complexity product areas, selecting methods and approaches for the team.  [source: JFM responsibility (P4)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Leads design across multiple products or high-complexity product areas, selecting methods and approaches for the team."
  KR2. Evidence at this level's scope bar: "A system or set of related features" — ⟨target⟩ by ⟨date⟩

Objective 2: Builds and implements design systems with reusable components, maintaining them in Storybook and Zeroheight.  [source: JFM responsibility (P4)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Builds and implements design systems with reusable components, maintaining them in Storybook and Zeroheight."
  KR2. Evidence at this level's autonomy bar: "Self-directed; reviewed at critical decision points" — ⟨target⟩ by ⟨date⟩

Objective 3: Understands business metrics and uses design decisions to deliberately affect them, communicating user-centered rationale to stakeholders.  [source: JFM responsibility (P4)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Understands business metrics and uses design decisions to deliberately affect them, communicating user-centered rationale to stakeholders."
  KR2. Evidence at this level's complexity bar: "Complex, ambiguous problems; devises new approaches" — ⟨target⟩ by ⟨date⟩

Objective 4: Owns the technical handoff — produces UX specs, ensures accessibility (WCAG) conformance, and partners with engineering on implementation.  [source: JFM responsibility (P4)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Owns the technical handoff — produces UX specs, ensures accessibility (WCAG) conformance, and partners with engineering on implementation."
  KR2. Evidence at this level's impact bar: "Multi-team / function outcomes" — ⟨target⟩ by ⟨date⟩

Objective 5: Mentors mid-level and junior designers and may lead the design portion of cross-functional projects.  [source: JFM responsibility (P4)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Mentors mid-level and junior designers and may lead the design portion of cross-functional projects."
  KR2. Evidence at this level's decision rights bar: "Owns technical decisions for a system; influences adjacent design" — ⟨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
Leads design across multiple products or high-complexity product areas, selecting methods and approaches for the team.	Consistent with this level's jfm knowledge-application rubric: "Brings in-depth expertise in design systems and business-metric-driven design, building and maintaining reusable component systems (Storybook, Zeroheight) and selecting methods spanning multiple product areas. Owns accessibility conformance and technical handoff."	⟨target⟩	⟨date⟩
Builds and implements design systems with reusable components, maintaining them in Storybook and Zeroheight.	Consistent with this level's jfm knowledge-application rubric: "Brings in-depth expertise in design systems and business-metric-driven design, building and maintaining reusable component systems (Storybook, Zeroheight) and selecting methods spanning multiple product areas. Owns accessibility conformance and technical handoff."	⟨target⟩	⟨date⟩
Understands business metrics and uses design decisions to deliberately affect them, communicating user-centered rationale to stakeholders.	Consistent with this level's jfm knowledge-application rubric: "Brings in-depth expertise in design systems and business-metric-driven design, building and maintaining reusable component systems (Storybook, Zeroheight) and selecting methods spanning multiple product areas. Owns accessibility conformance and technical handoff."	⟨target⟩	⟨date⟩
Owns the technical handoff — produces UX specs, ensures accessibility (WCAG) conformance, and partners with engineering on implementation.	Consistent with this level's jfm knowledge-application rubric: "Brings in-depth expertise in design systems and business-metric-driven design, building and maintaining reusable component systems (Storybook, Zeroheight) and selecting methods spanning multiple product areas. Owns accessibility conformance and technical handoff."	⟨target⟩	⟨date⟩
Mentors mid-level and junior designers and may lead the design portion of cross-functional projects.	Consistent with this level's jfm knowledge-application rubric: "Brings in-depth expertise in design systems and business-metric-driven design, building and maintaining reusable component systems (Storybook, Zeroheight) and selecting methods spanning multiple product areas. Owns accessibility conformance and technical handoff."	⟨target⟩	⟨date⟩

Copy / print as textshow ▾

1. Area: Leads design across multiple products or high-complexity product areas, selecting methods and approaches for the team. [source: JFM responsibility (P4) — reused, no distinct responsibility content]
Standard: Consistent with this level's jfm knowledge-application rubric: "Brings in-depth expertise in design systems and business-metric-driven design, building and maintaining reusable component systems (Storybook, Zeroheight) and selecting methods spanning multiple product areas. Owns accessibility conformance and technical handoff."
Target: ⟨target⟩ Due: ⟨date⟩

2. Area: Builds and implements design systems with reusable components, maintaining them in Storybook and Zeroheight. [source: JFM responsibility (P4) — reused, no distinct responsibility content]
Standard: Consistent with this level's jfm knowledge-application rubric: "Brings in-depth expertise in design systems and business-metric-driven design, building and maintaining reusable component systems (Storybook, Zeroheight) and selecting methods spanning multiple product areas. Owns accessibility conformance and technical handoff."
Target: ⟨target⟩ Due: ⟨date⟩

3. Area: Understands business metrics and uses design decisions to deliberately affect them, communicating user-centered rationale to stakeholders. [source: JFM responsibility (P4) — reused, no distinct responsibility content]
Standard: Consistent with this level's jfm knowledge-application rubric: "Brings in-depth expertise in design systems and business-metric-driven design, building and maintaining reusable component systems (Storybook, Zeroheight) and selecting methods spanning multiple product areas. Owns accessibility conformance and technical handoff."
Target: ⟨target⟩ Due: ⟨date⟩

4. Area: Owns the technical handoff — produces UX specs, ensures accessibility (WCAG) conformance, and partners with engineering on implementation. [source: JFM responsibility (P4) — reused, no distinct responsibility content]
Standard: Consistent with this level's jfm knowledge-application rubric: "Brings in-depth expertise in design systems and business-metric-driven design, building and maintaining reusable component systems (Storybook, Zeroheight) and selecting methods spanning multiple product areas. Owns accessibility conformance and technical handoff."
Target: ⟨target⟩ Due: ⟨date⟩

5. Area: Mentors mid-level and junior designers and may lead the design portion of cross-functional projects. [source: JFM responsibility (P4) — reused, no distinct responsibility content]
Standard: Consistent with this level's jfm knowledge-application rubric: "Brings in-depth expertise in design systems and business-metric-driven design, building and maintaining reusable component systems (Storybook, Zeroheight) and selecting methods spanning multiple product areas. Owns accessibility conformance and technical handoff."
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

"Leads design across multiple products or high-complexity product areas, selecting methods and approaches for the team."→ ⟨target⟩ by ⟨date⟩
"Builds and implements design systems with reusable components, maintaining them in Storybook and Zeroheight."→ ⟨target⟩ by ⟨date⟩
"Understands business metrics and uses design decisions to deliberately affect them, communicating user-centered rationale to stakeholders."→ ⟨target⟩ by ⟨date⟩
"Owns the technical handoff — produces UX specs, ensures accessibility (WCAG) conformance, and partners with engineering on implementation."→ ⟨target⟩ by ⟨date⟩
"Mentors mid-level and junior designers and may lead the design portion of cross-functional projects."→ ⟨target⟩ by ⟨date⟩

Role calibration

Meets the scope bar: "A system or set of related features"→ ⟨target⟩ by ⟨date⟩
Meets the autonomy bar: "Self-directed; reviewed at critical decision points"→ ⟨target⟩ by ⟨date⟩
Meets the complexity bar: "Complex, ambiguous problems; devises new approaches"→ ⟨target⟩ by ⟨date⟩
Meets the impact bar: "Multi-team / function outcomes"→ ⟨target⟩ by ⟨date⟩
Meets the decision rights bar: "Owns technical decisions for a system; influences adjacent design"→ ⟨target⟩ by ⟨date⟩
Meets the leadership bar: "Technical lead for focused efforts; mentors several"→ ⟨target⟩ by ⟨date⟩

Copy / print as textshow ▾

Internal process
  - "Leads design across multiple products or high-complexity product areas, selecting methods and approaches for the team."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P4)]
  - "Builds and implements design systems with reusable components, maintaining them in Storybook and Zeroheight."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P4)]
  - "Understands business metrics and uses design decisions to deliberately affect them, communicating user-centered rationale to stakeholders."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P4)]
  - "Owns the technical handoff — produces UX specs, ensures accessibility (WCAG) conformance, and partners with engineering on implementation."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P4)]
  - "Mentors mid-level and junior designers and may lead the design portion of cross-functional projects."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P4)]

Role calibration
  - Meets the scope bar: "A system or set of related features"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Scope)]
  - Meets the autonomy bar: "Self-directed; reviewed at critical decision points"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Autonomy)]
  - Meets the complexity bar: "Complex, ambiguous problems; devises new approaches"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Complexity)]
  - Meets the impact bar: "Multi-team / function outcomes"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Impact)]
  - Meets the decision rights bar: "Owns technical decisions for a system; influences adjacent design"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Decision rights)]
  - Meets the leadership bar: "Technical lead for focused efforts; mentors several"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Leadership)]