← Technical Documentation — P2

Goal templates — Technical Documentation — P2

Technical Documentation · Technical Documentation · 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)

Creates and maintains product documentation, technical manuals, and user-facing content with minimal supervision across an assigned documentation set.

Specific
Deliver: "Creates and maintains product documentation, technical manuals, and user-facing content with minimal supervision across an assigned documentation set."
Measurable
Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable
Scoped to this level's jfm complexity/problem-solving rubric: "Exercises judgment in familiar contexts — deciding content placement, sequencing, and review coordination — escalating genuinely ambiguous cases."
Relevant
Advances the Technical Documentation · Technical Documentation mandate for a P2 — Developing Professional.
Time-bound
⟨date⟩

JFM responsibility (P2)

Runs documentation projects end-to-end — writes, edits, coordinates SME interviews, and manages the review cycle for a defined feature area.

Specific
Deliver: "Runs documentation projects end-to-end — writes, edits, coordinates SME interviews, and manages the review cycle for a defined feature area."
Measurable
Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable
Scoped to this level's jfm complexity/problem-solving rubric: "Exercises judgment in familiar contexts — deciding content placement, sequencing, and review coordination — escalating genuinely ambiguous cases."
Relevant
Advances the Technical Documentation · Technical Documentation mandate for a P2 — Developing Professional.
Time-bound
⟨date⟩

JFM responsibility (P2)

Makes day-to-day judgment calls about what belongs in docs versus product UI or support, escalating ambiguous cases to senior writers.

Specific
Deliver: "Makes day-to-day judgment calls about what belongs in docs versus product UI or support, escalating ambiguous cases to senior writers."
Measurable
Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable
Scoped to this level's jfm complexity/problem-solving rubric: "Exercises judgment in familiar contexts — deciding content placement, sequencing, and review coordination — escalating genuinely ambiguous cases."
Relevant
Advances the Technical Documentation · Technical Documentation mandate for a P2 — Developing Professional.
Time-bound
⟨date⟩

JFM responsibility (P2)

Applies single-sourcing and structured authoring conventions (DITA topics, content reuse) within an established framework.

Specific
Deliver: "Applies single-sourcing and structured authoring conventions (DITA topics, content reuse) within an established framework."
Measurable
Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable
Scoped to this level's jfm complexity/problem-solving rubric: "Exercises judgment in familiar contexts — deciding content placement, sequencing, and review coordination — escalating genuinely ambiguous cases."
Relevant
Advances the Technical Documentation · Technical Documentation mandate for a P2 — Developing Professional.
Time-bound
⟨date⟩

JFM responsibility (P2)

Participates in project and release planning meetings and begins mentoring junior writers on tooling and style basics.

Specific
Deliver: "Participates in project and release planning meetings and begins mentoring junior writers on tooling and style basics."
Measurable
Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable
Scoped to this level's jfm complexity/problem-solving rubric: "Exercises judgment in familiar contexts — deciding content placement, sequencing, and review coordination — escalating genuinely ambiguous cases."
Relevant
Advances the Technical Documentation · Technical Documentation mandate for a P2 — Developing Professional.
Time-bound
⟨date⟩
Copy / print as textshow ▾
1. Creates and maintains product documentation, technical manuals, and user-facing content with minimal supervision across an assigned documentation set.  [source: JFM responsibility (P2)]
   Specific:    Deliver: "Creates and maintains product documentation, technical manuals, and user-facing content with minimal supervision across an assigned documentation set."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Exercises judgment in familiar contexts — deciding content placement, sequencing, and review coordination — escalating genuinely ambiguous cases."
   Relevant:    Advances the Technical Documentation · Technical Documentation mandate for a P2 — Developing Professional.
   Time-bound:  ⟨date⟩

2. Runs documentation projects end-to-end — writes, edits, coordinates SME interviews, and manages the review cycle for a defined feature area.  [source: JFM responsibility (P2)]
   Specific:    Deliver: "Runs documentation projects end-to-end — writes, edits, coordinates SME interviews, and manages the review cycle for a defined feature area."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Exercises judgment in familiar contexts — deciding content placement, sequencing, and review coordination — escalating genuinely ambiguous cases."
   Relevant:    Advances the Technical Documentation · Technical Documentation mandate for a P2 — Developing Professional.
   Time-bound:  ⟨date⟩

3. Makes day-to-day judgment calls about what belongs in docs versus product UI or support, escalating ambiguous cases to senior writers.  [source: JFM responsibility (P2)]
   Specific:    Deliver: "Makes day-to-day judgment calls about what belongs in docs versus product UI or support, escalating ambiguous cases to senior writers."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Exercises judgment in familiar contexts — deciding content placement, sequencing, and review coordination — escalating genuinely ambiguous cases."
   Relevant:    Advances the Technical Documentation · Technical Documentation mandate for a P2 — Developing Professional.
   Time-bound:  ⟨date⟩

4. Applies single-sourcing and structured authoring conventions (DITA topics, content reuse) within an established framework.  [source: JFM responsibility (P2)]
   Specific:    Deliver: "Applies single-sourcing and structured authoring conventions (DITA topics, content reuse) within an established framework."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Exercises judgment in familiar contexts — deciding content placement, sequencing, and review coordination — escalating genuinely ambiguous cases."
   Relevant:    Advances the Technical Documentation · Technical Documentation mandate for a P2 — Developing Professional.
   Time-bound:  ⟨date⟩

5. Participates in project and release planning meetings and begins mentoring junior writers on tooling and style basics.  [source: JFM responsibility (P2)]
   Specific:    Deliver: "Participates in project and release planning meetings and begins mentoring junior writers on tooling and style basics."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Exercises judgment in familiar contexts — deciding content placement, sequencing, and review coordination — escalating genuinely ambiguous cases."
   Relevant:    Advances the Technical Documentation · Technical Documentation 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)

Creates and maintains product documentation, technical manuals, and user-facing content with minimal supervision across an assigned documentation set.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Creates and maintains product documentation, technical manuals, and user-facing content with minimal supervision across an assigned documentation set."
  • Evidence at this level's scope bar: "Defined deliverables / small features" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P2)

Runs documentation projects end-to-end — writes, edits, coordinates SME interviews, and manages the review cycle for a defined feature area.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Runs documentation projects end-to-end — writes, edits, coordinates SME interviews, and manages the review cycle for a defined feature area."
  • Evidence at this level's autonomy bar: "General supervision; reviewed at milestones" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P2)

Makes day-to-day judgment calls about what belongs in docs versus product UI or support, escalating ambiguous cases to senior writers.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Makes day-to-day judgment calls about what belongs in docs versus product UI or support, escalating ambiguous cases to senior writers."
  • Evidence at this level's complexity bar: "Some non-routine problems; applies established patterns" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P2)

Applies single-sourcing and structured authoring conventions (DITA topics, content reuse) within an established framework.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Applies single-sourcing and structured authoring conventions (DITA topics, content reuse) within an established framework."
  • Evidence at this level's impact bar: "Own and immediate-team deliverables" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P2)

Participates in project and release planning meetings and begins mentoring junior writers on tooling and style basics.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Participates in project and release planning meetings and begins mentoring junior writers on tooling and style basics."
  • Evidence at this level's decision rights bar: "Routine technical choices within guidance" — ⟨target⟩ by ⟨date⟩
Copy / print as textshow ▾
Objective 1: Creates and maintains product documentation, technical manuals, and user-facing content with minimal supervision across an assigned documentation set.  [source: JFM responsibility (P2)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Creates and maintains product documentation, technical manuals, and user-facing content with minimal supervision across an assigned documentation set."
  KR2. Evidence at this level's scope bar: "Defined deliverables / small features" — ⟨target⟩ by ⟨date⟩

Objective 2: Runs documentation projects end-to-end — writes, edits, coordinates SME interviews, and manages the review cycle for a defined feature area.  [source: JFM responsibility (P2)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Runs documentation projects end-to-end — writes, edits, coordinates SME interviews, and manages the review cycle for a defined feature area."
  KR2. Evidence at this level's autonomy bar: "General supervision; reviewed at milestones" — ⟨target⟩ by ⟨date⟩

Objective 3: Makes day-to-day judgment calls about what belongs in docs versus product UI or support, escalating ambiguous cases to senior writers.  [source: JFM responsibility (P2)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Makes day-to-day judgment calls about what belongs in docs versus product UI or support, escalating ambiguous cases to senior writers."
  KR2. Evidence at this level's complexity bar: "Some non-routine problems; applies established patterns" — ⟨target⟩ by ⟨date⟩

Objective 4: Applies single-sourcing and structured authoring conventions (DITA topics, content reuse) within an established framework.  [source: JFM responsibility (P2)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Applies single-sourcing and structured authoring conventions (DITA topics, content reuse) within an established framework."
  KR2. Evidence at this level's impact bar: "Own and immediate-team deliverables" — ⟨target⟩ by ⟨date⟩

Objective 5: Participates in project and release planning meetings and begins mentoring junior writers on tooling and style basics.  [source: JFM responsibility (P2)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Participates in project and release planning meetings and begins mentoring junior writers on tooling and style basics."
  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.

AreaStandardTargetDue
Creates and maintains product documentation, technical manuals, and user-facing content with minimal supervision across an assigned documentation set.Consistent with this level's jfm knowledge-application rubric: "Applies conventional documentation practices, single-sourcing, and structured authoring within established frameworks to a defined documentation set. Comfortable with core tooling."⟨target⟩⟨date⟩
Runs documentation projects end-to-end — writes, edits, coordinates SME interviews, and manages the review cycle for a defined feature area.Consistent with this level's jfm knowledge-application rubric: "Applies conventional documentation practices, single-sourcing, and structured authoring within established frameworks to a defined documentation set. Comfortable with core tooling."⟨target⟩⟨date⟩
Makes day-to-day judgment calls about what belongs in docs versus product UI or support, escalating ambiguous cases to senior writers.Consistent with this level's jfm knowledge-application rubric: "Applies conventional documentation practices, single-sourcing, and structured authoring within established frameworks to a defined documentation set. Comfortable with core tooling."⟨target⟩⟨date⟩
Applies single-sourcing and structured authoring conventions (DITA topics, content reuse) within an established framework.Consistent with this level's jfm knowledge-application rubric: "Applies conventional documentation practices, single-sourcing, and structured authoring within established frameworks to a defined documentation set. Comfortable with core tooling."⟨target⟩⟨date⟩
Participates in project and release planning meetings and begins mentoring junior writers on tooling and style basics.Consistent with this level's jfm knowledge-application rubric: "Applies conventional documentation practices, single-sourcing, and structured authoring within established frameworks to a defined documentation set. Comfortable with core tooling."⟨target⟩⟨date⟩
Copy / print as textshow ▾
1. Area: Creates and maintains product documentation, technical manuals, and user-facing content with minimal supervision across an assigned documentation set.  [source: JFM responsibility (P2) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies conventional documentation practices, single-sourcing, and structured authoring within established frameworks to a defined documentation set. Comfortable with core tooling."
   Target:   ⟨target⟩   Due: ⟨date⟩

2. Area: Runs documentation projects end-to-end — writes, edits, coordinates SME interviews, and manages the review cycle for a defined feature area.  [source: JFM responsibility (P2) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies conventional documentation practices, single-sourcing, and structured authoring within established frameworks to a defined documentation set. Comfortable with core tooling."
   Target:   ⟨target⟩   Due: ⟨date⟩

3. Area: Makes day-to-day judgment calls about what belongs in docs versus product UI or support, escalating ambiguous cases to senior writers.  [source: JFM responsibility (P2) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies conventional documentation practices, single-sourcing, and structured authoring within established frameworks to a defined documentation set. Comfortable with core tooling."
   Target:   ⟨target⟩   Due: ⟨date⟩

4. Area: Applies single-sourcing and structured authoring conventions (DITA topics, content reuse) within an established framework.  [source: JFM responsibility (P2) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies conventional documentation practices, single-sourcing, and structured authoring within established frameworks to a defined documentation set. Comfortable with core tooling."
   Target:   ⟨target⟩   Due: ⟨date⟩

5. Area: Participates in project and release planning meetings and begins mentoring junior writers on tooling and style basics.  [source: JFM responsibility (P2) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies conventional documentation practices, single-sourcing, and structured authoring within established frameworks to a defined documentation set. Comfortable with core tooling."
   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

  • "Creates and maintains product documentation, technical manuals, and user-facing content with minimal supervision across an assigned documentation set."→ ⟨target⟩ by ⟨date⟩
  • "Runs documentation projects end-to-end — writes, edits, coordinates SME interviews, and manages the review cycle for a defined feature area."→ ⟨target⟩ by ⟨date⟩
  • "Makes day-to-day judgment calls about what belongs in docs versus product UI or support, escalating ambiguous cases to senior writers."→ ⟨target⟩ by ⟨date⟩
  • "Applies single-sourcing and structured authoring conventions (DITA topics, content reuse) within an established framework."→ ⟨target⟩ by ⟨date⟩
  • "Participates in project and release planning meetings and begins mentoring junior writers on tooling and style basics."→ ⟨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 ▾
Internal process
  - "Creates and maintains product documentation, technical manuals, and user-facing content with minimal supervision across an assigned documentation set."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P2)]
  - "Runs documentation projects end-to-end — writes, edits, coordinates SME interviews, and manages the review cycle for a defined feature area."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P2)]
  - "Makes day-to-day judgment calls about what belongs in docs versus product UI or support, escalating ambiguous cases to senior writers."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P2)]
  - "Applies single-sourcing and structured authoring conventions (DITA topics, content reuse) within an established framework."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P2)]
  - "Participates in project and release planning meetings and begins mentoring junior writers on tooling and style basics."  →  ⟨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)]