Goal templates — Product Manager — P2
Product Manager · Product Manager · P2 — Developing 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 (P2)
Researches and understands customer needs, gathering feedback directly from product users and reporting research results back to the senior product manager.
- Specific
- Deliver: "Researches and understands customer needs, gathering feedback directly from product users and reporting research results back to the senior product manager."
- Measurable
- Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
- Achievable
- Scoped to this level's jfm complexity/problem-solving rubric: "Handles conventional, well-scoped problems on one feature; exercises judgment in familiar contexts with guidance from a senior PM."
- Relevant
- Advances the Product Manager · Product Manager mandate for a P2 — Developing Professional.
- Time-bound
- ⟨date⟩
JFM responsibility (P2)
Writes user stories and assists with roadmap updates under defined direction.
- Specific
- Deliver: "Writes user stories and assists with roadmap updates under defined direction."
- Measurable
- Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
- Achievable
- Scoped to this level's jfm complexity/problem-solving rubric: "Handles conventional, well-scoped problems on one feature; exercises judgment in familiar contexts with guidance from a senior PM."
- Relevant
- Advances the Product Manager · Product Manager mandate for a P2 — Developing Professional.
- Time-bound
- ⟨date⟩
JFM responsibility (P2)
Coordinates with the engineering team to ensure an individual feature is delivered on time, focusing on execution and launch.
- Specific
- Deliver: "Coordinates with the engineering team to ensure an individual feature is delivered on time, focusing on execution and launch."
- Measurable
- Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
- Achievable
- Scoped to this level's jfm complexity/problem-solving rubric: "Handles conventional, well-scoped problems on one feature; exercises judgment in familiar contexts with guidance from a senior PM."
- Relevant
- Advances the Product Manager · Product Manager mandate for a P2 — Developing Professional.
- Time-bound
- ⟨date⟩
JFM responsibility (P2)
Uses analytics tools such as Amplitude to monitor user behavior and surface basic usage observations for a single feature.
- Specific
- Deliver: "Uses analytics tools such as Amplitude to monitor user behavior and surface basic usage observations for a single feature."
- Measurable
- Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
- Achievable
- Scoped to this level's jfm complexity/problem-solving rubric: "Handles conventional, well-scoped problems on one feature; exercises judgment in familiar contexts with guidance from a senior PM."
- Relevant
- Advances the Product Manager · Product Manager mandate for a P2 — Developing Professional.
- Time-bound
- ⟨date⟩
JFM responsibility (P2)
Prepares mockups in Figma or Balsamiq and tracks delivery tasks in Jira to support feature execution.
- Specific
- Deliver: "Prepares mockups in Figma or Balsamiq and tracks delivery tasks in Jira to support feature execution."
- Measurable
- Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
- Achievable
- Scoped to this level's jfm complexity/problem-solving rubric: "Handles conventional, well-scoped problems on one feature; exercises judgment in familiar contexts with guidance from a senior PM."
- Relevant
- Advances the Product Manager · Product Manager mandate for a P2 — Developing Professional.
- Time-bound
- ⟨date⟩
Copy / print as textshow ▾hide ▴
1. Researches and understands customer needs, gathering feedback directly from product users and reporting research results back to the senior product manager. [source: JFM responsibility (P2)] Specific: Deliver: "Researches and understands customer needs, gathering feedback directly from product users and reporting research results back to the senior product manager." Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩. Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Handles conventional, well-scoped problems on one feature; exercises judgment in familiar contexts with guidance from a senior PM." Relevant: Advances the Product Manager · Product Manager mandate for a P2 — Developing Professional. Time-bound: ⟨date⟩ 2. Writes user stories and assists with roadmap updates under defined direction. [source: JFM responsibility (P2)] Specific: Deliver: "Writes user stories and assists with roadmap updates under defined direction." Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩. Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Handles conventional, well-scoped problems on one feature; exercises judgment in familiar contexts with guidance from a senior PM." Relevant: Advances the Product Manager · Product Manager mandate for a P2 — Developing Professional. Time-bound: ⟨date⟩ 3. Coordinates with the engineering team to ensure an individual feature is delivered on time, focusing on execution and launch. [source: JFM responsibility (P2)] Specific: Deliver: "Coordinates with the engineering team to ensure an individual feature is delivered on time, focusing on execution and launch." Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩. Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Handles conventional, well-scoped problems on one feature; exercises judgment in familiar contexts with guidance from a senior PM." Relevant: Advances the Product Manager · Product Manager mandate for a P2 — Developing Professional. Time-bound: ⟨date⟩ 4. Uses analytics tools such as Amplitude to monitor user behavior and surface basic usage observations for a single feature. [source: JFM responsibility (P2)] Specific: Deliver: "Uses analytics tools such as Amplitude to monitor user behavior and surface basic usage observations for a single feature." Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩. Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Handles conventional, well-scoped problems on one feature; exercises judgment in familiar contexts with guidance from a senior PM." Relevant: Advances the Product Manager · Product Manager mandate for a P2 — Developing Professional. Time-bound: ⟨date⟩ 5. Prepares mockups in Figma or Balsamiq and tracks delivery tasks in Jira to support feature execution. [source: JFM responsibility (P2)] Specific: Deliver: "Prepares mockups in Figma or Balsamiq and tracks delivery tasks in Jira to support feature execution." Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩. Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Handles conventional, well-scoped problems on one feature; exercises judgment in familiar contexts with guidance from a senior PM." Relevant: Advances the Product Manager · Product Manager mandate for a P2 — Developing 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 (P2)
Researches and understands customer needs, gathering feedback directly from product users and reporting research results back to the senior product manager.
- From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Researches and understands customer needs, gathering feedback directly from product users and reporting research results back to the senior product manager."
- Evidence at this level's scope bar: "Defined deliverables / small features" — ⟨target⟩ by ⟨date⟩
JFM responsibility (P2)
Writes user stories and assists with roadmap updates under defined direction.
- From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Writes user stories and assists with roadmap updates under defined direction."
- Evidence at this level's autonomy bar: "General supervision; reviewed at milestones" — ⟨target⟩ by ⟨date⟩
JFM responsibility (P2)
Coordinates with the engineering team to ensure an individual feature is delivered on time, focusing on execution and launch.
- From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Coordinates with the engineering team to ensure an individual feature is delivered on time, focusing on execution and launch."
- Evidence at this level's complexity bar: "Some non-routine problems; applies established patterns" — ⟨target⟩ by ⟨date⟩
JFM responsibility (P2)
Uses analytics tools such as Amplitude to monitor user behavior and surface basic usage observations for a single feature.
- From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Uses analytics tools such as Amplitude to monitor user behavior and surface basic usage observations for a single feature."
- Evidence at this level's impact bar: "Own and immediate-team deliverables" — ⟨target⟩ by ⟨date⟩
JFM responsibility (P2)
Prepares mockups in Figma or Balsamiq and tracks delivery tasks in Jira to support feature execution.
- From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Prepares mockups in Figma or Balsamiq and tracks delivery tasks in Jira to support feature execution."
- Evidence at this level's decision rights bar: "Routine technical choices within guidance" — ⟨target⟩ by ⟨date⟩
Copy / print as textshow ▾hide ▴
Objective 1: Researches and understands customer needs, gathering feedback directly from product users and reporting research results back to the senior product manager. [source: JFM responsibility (P2)] KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Researches and understands customer needs, gathering feedback directly from product users and reporting research results back to the senior product manager." KR2. Evidence at this level's scope bar: "Defined deliverables / small features" — ⟨target⟩ by ⟨date⟩ Objective 2: Writes user stories and assists with roadmap updates under defined direction. [source: JFM responsibility (P2)] KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Writes user stories and assists with roadmap updates under defined direction." KR2. Evidence at this level's autonomy bar: "General supervision; reviewed at milestones" — ⟨target⟩ by ⟨date⟩ Objective 3: Coordinates with the engineering team to ensure an individual feature is delivered on time, focusing on execution and launch. [source: JFM responsibility (P2)] KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Coordinates with the engineering team to ensure an individual feature is delivered on time, focusing on execution and launch." KR2. Evidence at this level's complexity bar: "Some non-routine problems; applies established patterns" — ⟨target⟩ by ⟨date⟩ Objective 4: Uses analytics tools such as Amplitude to monitor user behavior and surface basic usage observations for a single feature. [source: JFM responsibility (P2)] KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Uses analytics tools such as Amplitude to monitor user behavior and surface basic usage observations for a single feature." KR2. Evidence at this level's impact bar: "Own and immediate-team deliverables" — ⟨target⟩ by ⟨date⟩ Objective 5: Prepares mockups in Figma or Balsamiq and tracks delivery tasks in Jira to support feature execution. [source: JFM responsibility (P2)] KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Prepares mockups in Figma or Balsamiq and tracks delivery tasks in Jira to support feature execution." KR2. Evidence at this level's decision rights bar: "Routine technical choices within guidance" — ⟨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 |
|---|---|---|---|
| Researches and understands customer needs, gathering feedback directly from product users and reporting research results back to the senior product manager. | Consistent with this level's jfm knowledge-application rubric: "Applies foundational product-management knowledge — user-story writing, basic analytics in Amplitude, and Jira/Figma usage — to a single assigned feature under defined procedures." | ⟨target⟩ | ⟨date⟩ |
| Writes user stories and assists with roadmap updates under defined direction. | Consistent with this level's jfm knowledge-application rubric: "Applies foundational product-management knowledge — user-story writing, basic analytics in Amplitude, and Jira/Figma usage — to a single assigned feature under defined procedures." | ⟨target⟩ | ⟨date⟩ |
| Coordinates with the engineering team to ensure an individual feature is delivered on time, focusing on execution and launch. | Consistent with this level's jfm knowledge-application rubric: "Applies foundational product-management knowledge — user-story writing, basic analytics in Amplitude, and Jira/Figma usage — to a single assigned feature under defined procedures." | ⟨target⟩ | ⟨date⟩ |
| Uses analytics tools such as Amplitude to monitor user behavior and surface basic usage observations for a single feature. | Consistent with this level's jfm knowledge-application rubric: "Applies foundational product-management knowledge — user-story writing, basic analytics in Amplitude, and Jira/Figma usage — to a single assigned feature under defined procedures." | ⟨target⟩ | ⟨date⟩ |
| Prepares mockups in Figma or Balsamiq and tracks delivery tasks in Jira to support feature execution. | Consistent with this level's jfm knowledge-application rubric: "Applies foundational product-management knowledge — user-story writing, basic analytics in Amplitude, and Jira/Figma usage — to a single assigned feature under defined procedures." | ⟨target⟩ | ⟨date⟩ |
Copy / print as textshow ▾hide ▴
1. Area: Researches and understands customer needs, gathering feedback directly from product users and reporting research results back to the senior product manager. [source: JFM responsibility (P2) — reused, no distinct responsibility content] Standard: Consistent with this level's jfm knowledge-application rubric: "Applies foundational product-management knowledge — user-story writing, basic analytics in Amplitude, and Jira/Figma usage — to a single assigned feature under defined procedures." Target: ⟨target⟩ Due: ⟨date⟩ 2. Area: Writes user stories and assists with roadmap updates under defined direction. [source: JFM responsibility (P2) — reused, no distinct responsibility content] Standard: Consistent with this level's jfm knowledge-application rubric: "Applies foundational product-management knowledge — user-story writing, basic analytics in Amplitude, and Jira/Figma usage — to a single assigned feature under defined procedures." Target: ⟨target⟩ Due: ⟨date⟩ 3. Area: Coordinates with the engineering team to ensure an individual feature is delivered on time, focusing on execution and launch. [source: JFM responsibility (P2) — reused, no distinct responsibility content] Standard: Consistent with this level's jfm knowledge-application rubric: "Applies foundational product-management knowledge — user-story writing, basic analytics in Amplitude, and Jira/Figma usage — to a single assigned feature under defined procedures." Target: ⟨target⟩ Due: ⟨date⟩ 4. Area: Uses analytics tools such as Amplitude to monitor user behavior and surface basic usage observations for a single feature. [source: JFM responsibility (P2) — reused, no distinct responsibility content] Standard: Consistent with this level's jfm knowledge-application rubric: "Applies foundational product-management knowledge — user-story writing, basic analytics in Amplitude, and Jira/Figma usage — to a single assigned feature under defined procedures." Target: ⟨target⟩ Due: ⟨date⟩ 5. Area: Prepares mockups in Figma or Balsamiq and tracks delivery tasks in Jira to support feature execution. [source: JFM responsibility (P2) — reused, no distinct responsibility content] Standard: Consistent with this level's jfm knowledge-application rubric: "Applies foundational product-management knowledge — user-story writing, basic analytics in Amplitude, and Jira/Figma usage — to a single assigned feature under defined procedures." 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
- "Researches and understands customer needs, gathering feedback directly from product users and reporting research results back to the senior product manager."→ ⟨target⟩ by ⟨date⟩
- "Writes user stories and assists with roadmap updates under defined direction."→ ⟨target⟩ by ⟨date⟩
- "Coordinates with the engineering team to ensure an individual feature is delivered on time, focusing on execution and launch."→ ⟨target⟩ by ⟨date⟩
- "Uses analytics tools such as Amplitude to monitor user behavior and surface basic usage observations for a single feature."→ ⟨target⟩ by ⟨date⟩
- "Prepares mockups in Figma or Balsamiq and tracks delivery tasks in Jira to support feature execution."→ ⟨target⟩ by ⟨date⟩
Role calibration
- Meets the scope bar: "Defined deliverables / small features"→ ⟨target⟩ by ⟨date⟩
- Meets the autonomy bar: "General supervision; reviewed at milestones"→ ⟨target⟩ by ⟨date⟩
- Meets the complexity bar: "Some non-routine problems; applies established patterns"→ ⟨target⟩ by ⟨date⟩
- Meets the impact bar: "Own and immediate-team deliverables"→ ⟨target⟩ by ⟨date⟩
- Meets the decision rights bar: "Routine technical choices within guidance"→ ⟨target⟩ by ⟨date⟩
- Meets the leadership bar: "May guide interns"→ ⟨target⟩ by ⟨date⟩
Copy / print as textshow ▾hide ▴
Internal process - "Researches and understands customer needs, gathering feedback directly from product users and reporting research results back to the senior product manager." → ⟨target⟩ by ⟨date⟩ [source: JFM responsibility (P2)] - "Writes user stories and assists with roadmap updates under defined direction." → ⟨target⟩ by ⟨date⟩ [source: JFM responsibility (P2)] - "Coordinates with the engineering team to ensure an individual feature is delivered on time, focusing on execution and launch." → ⟨target⟩ by ⟨date⟩ [source: JFM responsibility (P2)] - "Uses analytics tools such as Amplitude to monitor user behavior and surface basic usage observations for a single feature." → ⟨target⟩ by ⟨date⟩ [source: JFM responsibility (P2)] - "Prepares mockups in Figma or Balsamiq and tracks delivery tasks in Jira to support feature execution." → ⟨target⟩ by ⟨date⟩ [source: JFM responsibility (P2)] Role calibration - Meets the scope bar: "Defined deliverables / small features" → ⟨target⟩ by ⟨date⟩ [source: level dimension (Scope)] - Meets the autonomy bar: "General supervision; reviewed at milestones" → ⟨target⟩ by ⟨date⟩ [source: level dimension (Autonomy)] - Meets the complexity bar: "Some non-routine problems; applies established patterns" → ⟨target⟩ by ⟨date⟩ [source: level dimension (Complexity)] - Meets the impact bar: "Own and immediate-team deliverables" → ⟨target⟩ by ⟨date⟩ [source: level dimension (Impact)] - Meets the decision rights bar: "Routine technical choices within guidance" → ⟨target⟩ by ⟨date⟩ [source: level dimension (Decision rights)] - Meets the leadership bar: "May guide interns" → ⟨target⟩ by ⟨date⟩ [source: level dimension (Leadership)]