← Technical Documentation — P1

Goal templates — Technical Documentation — P1

Technical Documentation · Technical Documentation · P1 — Entry-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 (P1)

Updates existing documents and formats content for clarity and consistency under the direction of senior writers.

Specific
Deliver: "Updates existing documents and formats content for clarity and consistency under the direction of 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: "Handles routine editing and formatting tasks with standard answers and clear precedent. Problems encountered are well-defined with established solutions."
Relevant
Advances the Technical Documentation · Technical Documentation mandate for a P1 — Entry-Level Professional.
Time-bound
⟨date⟩

JFM responsibility (P1)

Owns small, well-bounded surfaces such as a single guide, a feature page, or a section of the knowledge base.

Specific
Deliver: "Owns small, well-bounded surfaces such as a single guide, a feature page, or a section of the knowledge base."
Measurable
Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable
Scoped to this level's jfm complexity/problem-solving rubric: "Handles routine editing and formatting tasks with standard answers and clear precedent. Problems encountered are well-defined with established solutions."
Relevant
Advances the Technical Documentation · Technical Documentation mandate for a P1 — Entry-Level Professional.
Time-bound
⟨date⟩

JFM responsibility (P1)

Drafts user guides, knowledge base articles, and internal process documentation from source material provided by SMEs and senior writers.

Specific
Deliver: "Drafts user guides, knowledge base articles, and internal process documentation from source material provided by SMEs and 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: "Handles routine editing and formatting tasks with standard answers and clear precedent. Problems encountered are well-defined with established solutions."
Relevant
Advances the Technical Documentation · Technical Documentation mandate for a P1 — Entry-Level Professional.
Time-bound
⟨date⟩

JFM responsibility (P1)

Learns the team's authoring tools (e.g., MadCap Flare, Markdown, Confluence) and applies the existing style guide and templates to assigned tasks.

Specific
Deliver: "Learns the team's authoring tools (e.g., MadCap Flare, Markdown, Confluence) and applies the existing style guide and templates to assigned tasks."
Measurable
Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable
Scoped to this level's jfm complexity/problem-solving rubric: "Handles routine editing and formatting tasks with standard answers and clear precedent. Problems encountered are well-defined with established solutions."
Relevant
Advances the Technical Documentation · Technical Documentation mandate for a P1 — Entry-Level Professional.
Time-bound
⟨date⟩

JFM responsibility (P1)

Collaborates closely with senior writers and technical staff to gather source information and verify factual accuracy of edits.

Specific
Deliver: "Collaborates closely with senior writers and technical staff to gather source information and verify factual accuracy of edits."
Measurable
Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable
Scoped to this level's jfm complexity/problem-solving rubric: "Handles routine editing and formatting tasks with standard answers and clear precedent. Problems encountered are well-defined with established solutions."
Relevant
Advances the Technical Documentation · Technical Documentation mandate for a P1 — Entry-Level Professional.
Time-bound
⟨date⟩
Copy / print as textshow ▾
1. Updates existing documents and formats content for clarity and consistency under the direction of senior writers.  [source: JFM responsibility (P1)]
   Specific:    Deliver: "Updates existing documents and formats content for clarity and consistency under the direction of 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: "Handles routine editing and formatting tasks with standard answers and clear precedent. Problems encountered are well-defined with established solutions."
   Relevant:    Advances the Technical Documentation · Technical Documentation mandate for a P1 — Entry-Level Professional.
   Time-bound:  ⟨date⟩

2. Owns small, well-bounded surfaces such as a single guide, a feature page, or a section of the knowledge base.  [source: JFM responsibility (P1)]
   Specific:    Deliver: "Owns small, well-bounded surfaces such as a single guide, a feature page, or a section of the knowledge base."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Handles routine editing and formatting tasks with standard answers and clear precedent. Problems encountered are well-defined with established solutions."
   Relevant:    Advances the Technical Documentation · Technical Documentation mandate for a P1 — Entry-Level Professional.
   Time-bound:  ⟨date⟩

3. Drafts user guides, knowledge base articles, and internal process documentation from source material provided by SMEs and senior writers.  [source: JFM responsibility (P1)]
   Specific:    Deliver: "Drafts user guides, knowledge base articles, and internal process documentation from source material provided by SMEs and 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: "Handles routine editing and formatting tasks with standard answers and clear precedent. Problems encountered are well-defined with established solutions."
   Relevant:    Advances the Technical Documentation · Technical Documentation mandate for a P1 — Entry-Level Professional.
   Time-bound:  ⟨date⟩

4. Learns the team's authoring tools (e.g., MadCap Flare, Markdown, Confluence) and applies the existing style guide and templates to assigned tasks.  [source: JFM responsibility (P1)]
   Specific:    Deliver: "Learns the team's authoring tools (e.g., MadCap Flare, Markdown, Confluence) and applies the existing style guide and templates to assigned tasks."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Handles routine editing and formatting tasks with standard answers and clear precedent. Problems encountered are well-defined with established solutions."
   Relevant:    Advances the Technical Documentation · Technical Documentation mandate for a P1 — Entry-Level Professional.
   Time-bound:  ⟨date⟩

5. Collaborates closely with senior writers and technical staff to gather source information and verify factual accuracy of edits.  [source: JFM responsibility (P1)]
   Specific:    Deliver: "Collaborates closely with senior writers and technical staff to gather source information and verify factual accuracy of edits."
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Handles routine editing and formatting tasks with standard answers and clear precedent. Problems encountered are well-defined with established solutions."
   Relevant:    Advances the Technical Documentation · Technical Documentation mandate for a P1 — Entry-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 (P1)

Updates existing documents and formats content for clarity and consistency under the direction of senior writers.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Updates existing documents and formats content for clarity and consistency under the direction of senior writers."
  • Evidence at this level's scope bar: "Own tasks within a defined component" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P1)

Owns small, well-bounded surfaces such as a single guide, a feature page, or a section of the knowledge base.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Owns small, well-bounded surfaces such as a single guide, a feature page, or a section of the knowledge base."
  • Evidence at this level's autonomy bar: "Close supervision; work reviewed frequently" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P1)

Drafts user guides, knowledge base articles, and internal process documentation from source material provided by SMEs and senior writers.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Drafts user guides, knowledge base articles, and internal process documentation from source material provided by SMEs and senior writers."
  • Evidence at this level's complexity bar: "Routine problems with known solutions" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P1)

Learns the team's authoring tools (e.g., MadCap Flare, Markdown, Confluence) and applies the existing style guide and templates to assigned tasks.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Learns the team's authoring tools (e.g., MadCap Flare, Markdown, Confluence) and applies the existing style guide and templates to assigned tasks."
  • Evidence at this level's impact bar: "Own deliverables" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P1)

Collaborates closely with senior writers and technical staff to gather source information and verify factual accuracy of edits.

  • From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Collaborates closely with senior writers and technical staff to gather source information and verify factual accuracy of edits."
  • Evidence at this level's decision rights bar: "Few independent decisions; escalates the rest" — ⟨target⟩ by ⟨date⟩
Copy / print as textshow ▾
Objective 1: Updates existing documents and formats content for clarity and consistency under the direction of senior writers.  [source: JFM responsibility (P1)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Updates existing documents and formats content for clarity and consistency under the direction of senior writers."
  KR2. Evidence at this level's scope bar: "Own tasks within a defined component" — ⟨target⟩ by ⟨date⟩

Objective 2: Owns small, well-bounded surfaces such as a single guide, a feature page, or a section of the knowledge base.  [source: JFM responsibility (P1)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Owns small, well-bounded surfaces such as a single guide, a feature page, or a section of the knowledge base."
  KR2. Evidence at this level's autonomy bar: "Close supervision; work reviewed frequently" — ⟨target⟩ by ⟨date⟩

Objective 3: Drafts user guides, knowledge base articles, and internal process documentation from source material provided by SMEs and senior writers.  [source: JFM responsibility (P1)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Drafts user guides, knowledge base articles, and internal process documentation from source material provided by SMEs and senior writers."
  KR2. Evidence at this level's complexity bar: "Routine problems with known solutions" — ⟨target⟩ by ⟨date⟩

Objective 4: Learns the team's authoring tools (e.g., MadCap Flare, Markdown, Confluence) and applies the existing style guide and templates to assigned tasks.  [source: JFM responsibility (P1)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Learns the team's authoring tools (e.g., MadCap Flare, Markdown, Confluence) and applies the existing style guide and templates to assigned tasks."
  KR2. Evidence at this level's impact bar: "Own deliverables" — ⟨target⟩ by ⟨date⟩

Objective 5: Collaborates closely with senior writers and technical staff to gather source information and verify factual accuracy of edits.  [source: JFM responsibility (P1)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Collaborates closely with senior writers and technical staff to gather source information and verify factual accuracy of edits."
  KR2. Evidence at this level's decision rights bar: "Few independent decisions; escalates the rest" — ⟨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
Updates existing documents and formats content for clarity and consistency under the direction of senior writers.Consistent with this level's jfm knowledge-application rubric: "Applies basic technical writing principles and learns the team's authoring tools and style guide. Knowledge is foundational; relies on senior writers and SMEs for context and accuracy."⟨target⟩⟨date⟩
Owns small, well-bounded surfaces such as a single guide, a feature page, or a section of the knowledge base.Consistent with this level's jfm knowledge-application rubric: "Applies basic technical writing principles and learns the team's authoring tools and style guide. Knowledge is foundational; relies on senior writers and SMEs for context and accuracy."⟨target⟩⟨date⟩
Drafts user guides, knowledge base articles, and internal process documentation from source material provided by SMEs and senior writers.Consistent with this level's jfm knowledge-application rubric: "Applies basic technical writing principles and learns the team's authoring tools and style guide. Knowledge is foundational; relies on senior writers and SMEs for context and accuracy."⟨target⟩⟨date⟩
Learns the team's authoring tools (e.g., MadCap Flare, Markdown, Confluence) and applies the existing style guide and templates to assigned tasks.Consistent with this level's jfm knowledge-application rubric: "Applies basic technical writing principles and learns the team's authoring tools and style guide. Knowledge is foundational; relies on senior writers and SMEs for context and accuracy."⟨target⟩⟨date⟩
Collaborates closely with senior writers and technical staff to gather source information and verify factual accuracy of edits.Consistent with this level's jfm knowledge-application rubric: "Applies basic technical writing principles and learns the team's authoring tools and style guide. Knowledge is foundational; relies on senior writers and SMEs for context and accuracy."⟨target⟩⟨date⟩
Copy / print as textshow ▾
1. Area: Updates existing documents and formats content for clarity and consistency under the direction of senior writers.  [source: JFM responsibility (P1) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies basic technical writing principles and learns the team's authoring tools and style guide. Knowledge is foundational; relies on senior writers and SMEs for context and accuracy."
   Target:   ⟨target⟩   Due: ⟨date⟩

2. Area: Owns small, well-bounded surfaces such as a single guide, a feature page, or a section of the knowledge base.  [source: JFM responsibility (P1) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies basic technical writing principles and learns the team's authoring tools and style guide. Knowledge is foundational; relies on senior writers and SMEs for context and accuracy."
   Target:   ⟨target⟩   Due: ⟨date⟩

3. Area: Drafts user guides, knowledge base articles, and internal process documentation from source material provided by SMEs and senior writers.  [source: JFM responsibility (P1) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies basic technical writing principles and learns the team's authoring tools and style guide. Knowledge is foundational; relies on senior writers and SMEs for context and accuracy."
   Target:   ⟨target⟩   Due: ⟨date⟩

4. Area: Learns the team's authoring tools (e.g., MadCap Flare, Markdown, Confluence) and applies the existing style guide and templates to assigned tasks.  [source: JFM responsibility (P1) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies basic technical writing principles and learns the team's authoring tools and style guide. Knowledge is foundational; relies on senior writers and SMEs for context and accuracy."
   Target:   ⟨target⟩   Due: ⟨date⟩

5. Area: Collaborates closely with senior writers and technical staff to gather source information and verify factual accuracy of edits.  [source: JFM responsibility (P1) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies basic technical writing principles and learns the team's authoring tools and style guide. Knowledge is foundational; relies on senior writers and SMEs for context and accuracy."
   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

  • "Updates existing documents and formats content for clarity and consistency under the direction of senior writers."→ ⟨target⟩ by ⟨date⟩
  • "Owns small, well-bounded surfaces such as a single guide, a feature page, or a section of the knowledge base."→ ⟨target⟩ by ⟨date⟩
  • "Drafts user guides, knowledge base articles, and internal process documentation from source material provided by SMEs and senior writers."→ ⟨target⟩ by ⟨date⟩
  • "Learns the team's authoring tools (e.g., MadCap Flare, Markdown, Confluence) and applies the existing style guide and templates to assigned tasks."→ ⟨target⟩ by ⟨date⟩
  • "Collaborates closely with senior writers and technical staff to gather source information and verify factual accuracy of edits."→ ⟨target⟩ by ⟨date⟩

Role calibration

  • Meets the scope bar: "Own tasks within a defined component"→ ⟨target⟩ by ⟨date⟩
  • Meets the autonomy bar: "Close supervision; work reviewed frequently"→ ⟨target⟩ by ⟨date⟩
  • Meets the complexity bar: "Routine problems with known solutions"→ ⟨target⟩ by ⟨date⟩
  • Meets the impact bar: "Own deliverables"→ ⟨target⟩ by ⟨date⟩
  • Meets the decision rights bar: "Few independent decisions; escalates the rest"→ ⟨target⟩ by ⟨date⟩
  • Meets the leadership bar: "None — building the craft"→ ⟨target⟩ by ⟨date⟩
Copy / print as textshow ▾
Internal process
  - "Updates existing documents and formats content for clarity and consistency under the direction of senior writers."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P1)]
  - "Owns small, well-bounded surfaces such as a single guide, a feature page, or a section of the knowledge base."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P1)]
  - "Drafts user guides, knowledge base articles, and internal process documentation from source material provided by SMEs and senior writers."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P1)]
  - "Learns the team's authoring tools (e.g., MadCap Flare, Markdown, Confluence) and applies the existing style guide and templates to assigned tasks."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P1)]
  - "Collaborates closely with senior writers and technical staff to gather source information and verify factual accuracy of edits."  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P1)]

Role calibration
  - Meets the scope bar: "Own tasks within a defined component"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Scope)]
  - Meets the autonomy bar: "Close supervision; work reviewed frequently"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Autonomy)]
  - Meets the complexity bar: "Routine problems with known solutions"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Complexity)]
  - Meets the impact bar: "Own deliverables"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Impact)]
  - Meets the decision rights bar: "Few independent decisions; escalates the rest"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Decision rights)]
  - Meets the leadership bar: "None — building the craft"  →  ⟨target⟩ by ⟨date⟩   [source: level dimension (Leadership)]