← Technical Documentation — P3

Goal templates — Technical Documentation — P3

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

Plans, writes, edits, and maintains documentation independently across multiple releases for a product or product area, managing scope and milestones.

Specific
Deliver: "Plans, writes, edits, and maintains documentation independently across multiple releases for a product or product area, managing scope and milestones."
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 to solve diverse documentation problems independently, such as reconciling specs with docs and designing content for findability."
Relevant
Advances the Technical Documentation · Technical Documentation mandate for a P3 — Mid-Level Professional.
Time-bound
⟨date⟩

JFM responsibility (P3)

Takes on complex documentation projects such as API guides and developer tutorials, reconciling OpenAPI specs with hand-written content.

Specific
Deliver: "Takes on complex documentation projects such as API guides and developer tutorials, reconciling OpenAPI specs with hand-written content."
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 to solve diverse documentation problems independently, such as reconciling specs with docs and designing content for findability."
Relevant
Advances the Technical Documentation · Technical Documentation mandate for a P3 — Mid-Level Professional.
Time-bound
⟨date⟩

JFM responsibility (P3)

Implements documentation strategies that measurably improve user experience (improved findability, reduced support tickets) within a cross-functional team.

Specific
Deliver: "Implements documentation strategies that measurably improve user experience (improved findability, reduced support tickets) within a cross-functional team."
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 to solve diverse documentation problems independently, such as reconciling specs with docs and designing content for findability."
Relevant
Advances the Technical Documentation · Technical Documentation mandate for a P3 — Mid-Level Professional.
Time-bound
⟨date⟩

JFM responsibility (P3)

Coordinates with engineering, product, and support to gather and validate technical information, networking with senior professionals to resolve gaps.

Specific
Deliver: "Coordinates with engineering, product, and support to gather and validate technical information, networking with senior professionals to resolve gaps."
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 to solve diverse documentation problems independently, such as reconciling specs with docs and designing content for findability."
Relevant
Advances the Technical Documentation · Technical Documentation mandate for a P3 — Mid-Level Professional.
Time-bound
⟨date⟩

JFM responsibility (P3)

Contributes to documentation standards and templates, and mentors junior writers on structured authoring and review workflows.

Specific
Deliver: "Contributes to documentation standards and templates, and mentors junior writers on structured authoring and review workflows."
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 to solve diverse documentation problems independently, such as reconciling specs with docs and designing content for findability."
Relevant
Advances the Technical Documentation · Technical Documentation mandate for a P3 — Mid-Level Professional.
Time-bound
⟨date⟩
Copy / print as textshow ▾
1. Plans, writes, edits, and maintains documentation independently across multiple releases for a product or product area, managing scope and milestones.  [source: JFM responsibility (P3)]
   Specific:    Deliver: "Plans, writes, edits, and maintains documentation independently across multiple releases for a product or product area, managing scope and milestones."
   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 to solve diverse documentation problems independently, such as reconciling specs with docs and designing content for findability."
   Relevant:    Advances the Technical Documentation · Technical Documentation mandate for a P3 — Mid-Level Professional.
   Time-bound:  ⟨date⟩

2. Takes on complex documentation projects such as API guides and developer tutorials, reconciling OpenAPI specs with hand-written content.  [source: JFM responsibility (P3)]
   Specific:    Deliver: "Takes on complex documentation projects such as API guides and developer tutorials, reconciling OpenAPI specs with hand-written content."
   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 to solve diverse documentation problems independently, such as reconciling specs with docs and designing content for findability."
   Relevant:    Advances the Technical Documentation · Technical Documentation mandate for a P3 — Mid-Level Professional.
   Time-bound:  ⟨date⟩

3. Implements documentation strategies that measurably improve user experience (improved findability, reduced support tickets) within a cross-functional team.  [source: JFM responsibility (P3)]
   Specific:    Deliver: "Implements documentation strategies that measurably improve user experience (improved findability, reduced support tickets) within a cross-functional team."
   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 to solve diverse documentation problems independently, such as reconciling specs with docs and designing content for findability."
   Relevant:    Advances the Technical Documentation · Technical Documentation mandate for a P3 — Mid-Level Professional.
   Time-bound:  ⟨date⟩

4. Coordinates with engineering, product, and support to gather and validate technical information, networking with senior professionals to resolve gaps.  [source: JFM responsibility (P3)]
   Specific:    Deliver: "Coordinates with engineering, product, and support to gather and validate technical information, networking with senior professionals to resolve gaps."
   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 to solve diverse documentation problems independently, such as reconciling specs with docs and designing content for findability."
   Relevant:    Advances the Technical Documentation · Technical Documentation mandate for a P3 — Mid-Level Professional.
   Time-bound:  ⟨date⟩

5. Contributes to documentation standards and templates, and mentors junior writers on structured authoring and review workflows.  [source: JFM responsibility (P3)]
   Specific:    Deliver: "Contributes to documentation standards and templates, and mentors junior writers on structured authoring and review workflows."
   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 to solve diverse documentation problems independently, such as reconciling specs with docs and designing content for findability."
   Relevant:    Advances the Technical Documentation · Technical Documentation 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)

Plans, writes, edits, and maintains documentation independently across multiple releases for a product or product area, managing scope and milestones.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Plans, writes, edits, and maintains documentation independently across multiple releases for a product or product area, managing scope and milestones."
  • Evidence at this level's scope bar: "Features or a sub-system end-to-end" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P3)

Takes on complex documentation projects such as API guides and developer tutorials, reconciling OpenAPI specs with hand-written content.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Takes on complex documentation projects such as API guides and developer tutorials, reconciling OpenAPI specs with hand-written content."
  • Evidence at this level's autonomy bar: "Works independently on standard work; reviewed on the non-standard" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P3)

Implements documentation strategies that measurably improve user experience (improved findability, reduced support tickets) within a cross-functional team.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Implements documentation strategies that measurably improve user experience (improved findability, reduced support tickets) within a cross-functional team."
  • Evidence at this level's complexity bar: "Diverse problems; adapts existing approaches" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P3)

Coordinates with engineering, product, and support to gather and validate technical information, networking with senior professionals to resolve gaps.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Coordinates with engineering, product, and support to gather and validate technical information, networking with senior professionals to resolve gaps."
  • Evidence at this level's impact bar: "Project / team outcomes" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P3)

Contributes to documentation standards and templates, and mentors junior writers on structured authoring and review workflows.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Contributes to documentation standards and templates, and mentors junior writers on structured authoring and review workflows."
  • Evidence at this level's decision rights bar: "Owns implementation decisions for own scope" — ⟨target⟩ by ⟨date⟩
Copy / print as textshow ▾
Objective 1: Plans, writes, edits, and maintains documentation independently across multiple releases for a product or product area, managing scope and milestones.  [source: JFM responsibility (P3)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Plans, writes, edits, and maintains documentation independently across multiple releases for a product or product area, managing scope and milestones."
  KR2. Evidence at this level's scope bar: "Features or a sub-system end-to-end" — ⟨target⟩ by ⟨date⟩

Objective 2: Takes on complex documentation projects such as API guides and developer tutorials, reconciling OpenAPI specs with hand-written content.  [source: JFM responsibility (P3)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Takes on complex documentation projects such as API guides and developer tutorials, reconciling OpenAPI specs with hand-written content."
  KR2. Evidence at this level's autonomy bar: "Works independently on standard work; reviewed on the non-standard" — ⟨target⟩ by ⟨date⟩

Objective 3: Implements documentation strategies that measurably improve user experience (improved findability, reduced support tickets) within a cross-functional team.  [source: JFM responsibility (P3)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Implements documentation strategies that measurably improve user experience (improved findability, reduced support tickets) within a cross-functional team."
  KR2. Evidence at this level's complexity bar: "Diverse problems; adapts existing approaches" — ⟨target⟩ by ⟨date⟩

Objective 4: Coordinates with engineering, product, and support to gather and validate technical information, networking with senior professionals to resolve gaps.  [source: JFM responsibility (P3)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Coordinates with engineering, product, and support to gather and validate technical information, networking with senior professionals to resolve gaps."
  KR2. Evidence at this level's impact bar: "Project / team outcomes" — ⟨target⟩ by ⟨date⟩

Objective 5: Contributes to documentation standards and templates, and mentors junior writers on structured authoring and review workflows.  [source: JFM responsibility (P3)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Contributes to documentation standards and templates, and mentors junior writers on structured authoring and review workflows."
  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.

AreaStandardTargetDue
Plans, writes, edits, and maintains documentation independently across multiple releases for a product or product area, managing scope and milestones.Consistent with this level's jfm knowledge-application rubric: "Applies in-depth documentation craft across diverse problems — API documentation, structured authoring, IA — planning own work and selecting approaches within team standards."⟨target⟩⟨date⟩
Takes on complex documentation projects such as API guides and developer tutorials, reconciling OpenAPI specs with hand-written content.Consistent with this level's jfm knowledge-application rubric: "Applies in-depth documentation craft across diverse problems — API documentation, structured authoring, IA — planning own work and selecting approaches within team standards."⟨target⟩⟨date⟩
Implements documentation strategies that measurably improve user experience (improved findability, reduced support tickets) within a cross-functional team.Consistent with this level's jfm knowledge-application rubric: "Applies in-depth documentation craft across diverse problems — API documentation, structured authoring, IA — planning own work and selecting approaches within team standards."⟨target⟩⟨date⟩
Coordinates with engineering, product, and support to gather and validate technical information, networking with senior professionals to resolve gaps.Consistent with this level's jfm knowledge-application rubric: "Applies in-depth documentation craft across diverse problems — API documentation, structured authoring, IA — planning own work and selecting approaches within team standards."⟨target⟩⟨date⟩
Contributes to documentation standards and templates, and mentors junior writers on structured authoring and review workflows.Consistent with this level's jfm knowledge-application rubric: "Applies in-depth documentation craft across diverse problems — API documentation, structured authoring, IA — planning own work and selecting approaches within team standards."⟨target⟩⟨date⟩
Copy / print as textshow ▾
1. Area: Plans, writes, edits, and maintains documentation independently across multiple releases for a product or product area, managing scope and milestones.  [source: JFM responsibility (P3) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies in-depth documentation craft across diverse problems — API documentation, structured authoring, IA — planning own work and selecting approaches within team standards."
   Target:   ⟨target⟩   Due: ⟨date⟩

2. Area: Takes on complex documentation projects such as API guides and developer tutorials, reconciling OpenAPI specs with hand-written content.  [source: JFM responsibility (P3) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies in-depth documentation craft across diverse problems — API documentation, structured authoring, IA — planning own work and selecting approaches within team standards."
   Target:   ⟨target⟩   Due: ⟨date⟩

3. Area: Implements documentation strategies that measurably improve user experience (improved findability, reduced support tickets) within a cross-functional team.  [source: JFM responsibility (P3) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies in-depth documentation craft across diverse problems — API documentation, structured authoring, IA — planning own work and selecting approaches within team standards."
   Target:   ⟨target⟩   Due: ⟨date⟩

4. Area: Coordinates with engineering, product, and support to gather and validate technical information, networking with senior professionals to resolve gaps.  [source: JFM responsibility (P3) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies in-depth documentation craft across diverse problems — API documentation, structured authoring, IA — planning own work and selecting approaches within team standards."
   Target:   ⟨target⟩   Due: ⟨date⟩

5. Area: Contributes to documentation standards and templates, and mentors junior writers on structured authoring and review workflows.  [source: JFM responsibility (P3) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies in-depth documentation craft across diverse problems — API documentation, structured authoring, IA — planning own work and selecting approaches within team standards."
   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

  • "Plans, writes, edits, and maintains documentation independently across multiple releases for a product or product area, managing scope and milestones."→ ⟨target⟩ by ⟨date⟩
  • "Takes on complex documentation projects such as API guides and developer tutorials, reconciling OpenAPI specs with hand-written content."→ ⟨target⟩ by ⟨date⟩
  • "Implements documentation strategies that measurably improve user experience (improved findability, reduced support tickets) within a cross-functional team."→ ⟨target⟩ by ⟨date⟩
  • "Coordinates with engineering, product, and support to gather and validate technical information, networking with senior professionals to resolve gaps."→ ⟨target⟩ by ⟨date⟩
  • "Contributes to documentation standards and templates, and mentors junior writers on structured authoring and review workflows."→ ⟨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
  - "Plans, writes, edits, and maintains documentation independently across multiple releases for a product or product area, managing scope and milestones."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P3)]
  - "Takes on complex documentation projects such as API guides and developer tutorials, reconciling OpenAPI specs with hand-written content."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P3)]
  - "Implements documentation strategies that measurably improve user experience (improved findability, reduced support tickets) within a cross-functional team."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P3)]
  - "Coordinates with engineering, product, and support to gather and validate technical information, networking with senior professionals to resolve gaps."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P3)]
  - "Contributes to documentation standards and templates, and mentors junior writers on structured authoring and review workflows."  →  ⟨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)]