Goal templates — IT Support — P1

IT Operations & Support · IT Support · 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)

Serves as first point of contact for users facing technical issues (Tier 1), performing initial issue assessment and triage by collecting user details and determining urgency

Specific: Deliver: "Serves as first point of contact for users facing technical issues (Tier 1), performing initial issue assessment and triage by collecting user details and determining urgency"
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Resolves routine, well-defined problems with standard answers (login issues, password resets, email configuration); recognizes when an issue exceeds scripted resolution and escalates."
Relevant: Advances the IT Operations & Support · IT Support mandate for a P1 — Entry-Level Professional.
Time-bound: ⟨date⟩

JFM responsibility (P1)

Resolves basic technical issues using predefined scripts, decision trees, and the knowledge base — including login problems, email configuration, password resets, hardware requests, and software upgrades

Specific: Deliver: "Resolves basic technical issues using predefined scripts, decision trees, and the knowledge base — including login problems, email configuration, password resets, hardware requests, and software upgrades"
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Resolves routine, well-defined problems with standard answers (login issues, password resets, email configuration); recognizes when an issue exceeds scripted resolution and escalates."
Relevant: Advances the IT Operations & Support · IT Support mandate for a P1 — Entry-Level Professional.
Time-bound: ⟨date⟩

JFM responsibility (P1)

Creates and manages tickets with proper categorization, and communicates and follows up with users to ensure SLA compliance

Specific: Deliver: "Creates and manages tickets with proper categorization, and communicates and follows up with users to ensure SLA compliance"
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Resolves routine, well-defined problems with standard answers (login issues, password resets, email configuration); recognizes when an issue exceeds scripted resolution and escalates."
Relevant: Advances the IT Operations & Support · IT Support mandate for a P1 — Entry-Level Professional.
Time-bound: ⟨date⟩

JFM responsibility (P1)

Performs initial triage for network connectivity issues and escalates to Tier 2 with proper documentation

Specific: Deliver: "Performs initial triage for network connectivity issues and escalates to Tier 2 with proper documentation"
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Resolves routine, well-defined problems with standard answers (login issues, password resets, email configuration); recognizes when an issue exceeds scripted resolution and escalates."
Relevant: Advances the IT Operations & Support · IT Support mandate for a P1 — Entry-Level Professional.
Time-bound: ⟨date⟩

JFM responsibility (P1)

Handles 30-50 tickets per day, resolving 60-70% without escalation under close supervision

Specific: Deliver: "Handles 30-50 tickets per day, resolving 60-70% without escalation under close supervision"
Measurable: Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
Achievable: Scoped to this level's jfm complexity/problem-solving rubric: "Resolves routine, well-defined problems with standard answers (login issues, password resets, email configuration); recognizes when an issue exceeds scripted resolution and escalates."
Relevant: Advances the IT Operations & Support · IT Support mandate for a P1 — Entry-Level Professional.
Time-bound: ⟨date⟩

Copy / print as textshow ▾

1. Serves as first point of contact for users facing technical issues (Tier 1), performing initial issue assessment and triage by collecting user details and determining urgency  [source: JFM responsibility (P1)]
   Specific:    Deliver: "Serves as first point of contact for users facing technical issues (Tier 1), performing initial issue assessment and triage by collecting user details and determining urgency"
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Resolves routine, well-defined problems with standard answers (login issues, password resets, email configuration); recognizes when an issue exceeds scripted resolution and escalates."
   Relevant:    Advances the IT Operations & Support · IT Support mandate for a P1 — Entry-Level Professional.
   Time-bound:  ⟨date⟩

2. Resolves basic technical issues using predefined scripts, decision trees, and the knowledge base — including login problems, email configuration, password resets, hardware requests, and software upgrades  [source: JFM responsibility (P1)]
   Specific:    Deliver: "Resolves basic technical issues using predefined scripts, decision trees, and the knowledge base — including login problems, email configuration, password resets, hardware requests, and software upgrades"
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Resolves routine, well-defined problems with standard answers (login issues, password resets, email configuration); recognizes when an issue exceeds scripted resolution and escalates."
   Relevant:    Advances the IT Operations & Support · IT Support mandate for a P1 — Entry-Level Professional.
   Time-bound:  ⟨date⟩

3. Creates and manages tickets with proper categorization, and communicates and follows up with users to ensure SLA compliance  [source: JFM responsibility (P1)]
   Specific:    Deliver: "Creates and manages tickets with proper categorization, and communicates and follows up with users to ensure SLA compliance"
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Resolves routine, well-defined problems with standard answers (login issues, password resets, email configuration); recognizes when an issue exceeds scripted resolution and escalates."
   Relevant:    Advances the IT Operations & Support · IT Support mandate for a P1 — Entry-Level Professional.
   Time-bound:  ⟨date⟩

4. Performs initial triage for network connectivity issues and escalates to Tier 2 with proper documentation  [source: JFM responsibility (P1)]
   Specific:    Deliver: "Performs initial triage for network connectivity issues and escalates to Tier 2 with proper documentation"
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Resolves routine, well-defined problems with standard answers (login issues, password resets, email configuration); recognizes when an issue exceeds scripted resolution and escalates."
   Relevant:    Advances the IT Operations & Support · IT Support mandate for a P1 — Entry-Level Professional.
   Time-bound:  ⟨date⟩

5. Handles 30-50 tickets per day, resolving 60-70% without escalation under close supervision  [source: JFM responsibility (P1)]
   Specific:    Deliver: "Handles 30-50 tickets per day, resolving 60-70% without escalation under close supervision"
   Measurable:  Move the metric this drives from ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩.
   Achievable:  Scoped to this level's jfm complexity/problem-solving rubric: "Resolves routine, well-defined problems with standard answers (login issues, password resets, email configuration); recognizes when an issue exceeds scripted resolution and escalates."
   Relevant:    Advances the IT Operations & Support · IT Support 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)

Serves as first point of contact for users facing technical issues (Tier 1), performing initial issue assessment and triage by collecting user details and determining urgency

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Serves as first point of contact for users facing technical issues (Tier 1), performing initial issue assessment and triage by collecting user details and determining urgency"
Evidence at this level's scope bar: "Own tasks within a defined component" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P1)

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Resolves basic technical issues using predefined scripts, decision trees, and the knowledge base — including login problems, email configuration, password resets, hardware requests, and software upgrades"
Evidence at this level's autonomy bar: "Close supervision; work reviewed frequently" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P1)

Creates and manages tickets with proper categorization, and communicates and follows up with users to ensure SLA compliance

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Creates and manages tickets with proper categorization, and communicates and follows up with users to ensure SLA compliance"
Evidence at this level's complexity bar: "Routine problems with known solutions" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P1)

Performs initial triage for network connectivity issues and escalates to Tier 2 with proper documentation

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Performs initial triage for network connectivity issues and escalates to Tier 2 with proper documentation"
Evidence at this level's impact bar: "Own deliverables" — ⟨target⟩ by ⟨date⟩

JFM responsibility (P1)

Handles 30-50 tickets per day, resolving 60-70% without escalation under close supervision

From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Handles 30-50 tickets per day, resolving 60-70% without escalation under close supervision"
Evidence at this level's decision rights bar: "Few independent decisions; escalates the rest" — ⟨target⟩ by ⟨date⟩

Copy / print as textshow ▾

Objective 1: Serves as first point of contact for users facing technical issues (Tier 1), performing initial issue assessment and triage by collecting user details and determining urgency  [source: JFM responsibility (P1)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Serves as first point of contact for users facing technical issues (Tier 1), performing initial issue assessment and triage by collecting user details and determining urgency"
  KR2. Evidence at this level's scope bar: "Own tasks within a defined component" — ⟨target⟩ by ⟨date⟩

Objective 2: Resolves basic technical issues using predefined scripts, decision trees, and the knowledge base — including login problems, email configuration, password resets, hardware requests, and software upgrades  [source: JFM responsibility (P1)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Resolves basic technical issues using predefined scripts, decision trees, and the knowledge base — including login problems, email configuration, password resets, hardware requests, and software upgrades"
  KR2. Evidence at this level's autonomy bar: "Close supervision; work reviewed frequently" — ⟨target⟩ by ⟨date⟩

Objective 3: Creates and manages tickets with proper categorization, and communicates and follows up with users to ensure SLA compliance  [source: JFM responsibility (P1)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Creates and manages tickets with proper categorization, and communicates and follows up with users to ensure SLA compliance"
  KR2. Evidence at this level's complexity bar: "Routine problems with known solutions" — ⟨target⟩ by ⟨date⟩

Objective 4: Performs initial triage for network connectivity issues and escalates to Tier 2 with proper documentation  [source: JFM responsibility (P1)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Performs initial triage for network connectivity issues and escalates to Tier 2 with proper documentation"
  KR2. Evidence at this level's impact bar: "Own deliverables" — ⟨target⟩ by ⟨date⟩

Objective 5: Handles 30-50 tickets per day, resolving 60-70% without escalation under close supervision  [source: JFM responsibility (P1)]
  KR1. From ⟨baseline⟩ to ⟨target⟩ by ⟨date⟩ — tied to: "Handles 30-50 tickets per day, resolving 60-70% without escalation under close supervision"
  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.

Area	Standard	Target	Due
Serves as first point of contact for users facing technical issues (Tier 1), performing initial issue assessment and triage by collecting user details and determining urgency	Consistent with this level's jfm knowledge-application rubric: "Applies foundational hardware, software, and operating-system troubleshooting knowledge using predefined scripts, decision trees, and the knowledge base; entry-level certification knowledge (e.g., CompTIA A+) applied to routine issues."	⟨target⟩	⟨date⟩
Resolves basic technical issues using predefined scripts, decision trees, and the knowledge base — including login problems, email configuration, password resets, hardware requests, and software upgrades	Consistent with this level's jfm knowledge-application rubric: "Applies foundational hardware, software, and operating-system troubleshooting knowledge using predefined scripts, decision trees, and the knowledge base; entry-level certification knowledge (e.g., CompTIA A+) applied to routine issues."	⟨target⟩	⟨date⟩
Creates and manages tickets with proper categorization, and communicates and follows up with users to ensure SLA compliance	Consistent with this level's jfm knowledge-application rubric: "Applies foundational hardware, software, and operating-system troubleshooting knowledge using predefined scripts, decision trees, and the knowledge base; entry-level certification knowledge (e.g., CompTIA A+) applied to routine issues."	⟨target⟩	⟨date⟩
Performs initial triage for network connectivity issues and escalates to Tier 2 with proper documentation	Consistent with this level's jfm knowledge-application rubric: "Applies foundational hardware, software, and operating-system troubleshooting knowledge using predefined scripts, decision trees, and the knowledge base; entry-level certification knowledge (e.g., CompTIA A+) applied to routine issues."	⟨target⟩	⟨date⟩
Handles 30-50 tickets per day, resolving 60-70% without escalation under close supervision	Consistent with this level's jfm knowledge-application rubric: "Applies foundational hardware, software, and operating-system troubleshooting knowledge using predefined scripts, decision trees, and the knowledge base; entry-level certification knowledge (e.g., CompTIA A+) applied to routine issues."	⟨target⟩	⟨date⟩

Copy / print as textshow ▾

1. Area: Serves as first point of contact for users facing technical issues (Tier 1), performing initial issue assessment and triage by collecting user details and determining urgency  [source: JFM responsibility (P1) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies foundational hardware, software, and operating-system troubleshooting knowledge using predefined scripts, decision trees, and the knowledge base; entry-level certification knowledge (e.g., CompTIA A+) applied to routine issues."
   Target:   ⟨target⟩   Due: ⟨date⟩

2. Area: Resolves basic technical issues using predefined scripts, decision trees, and the knowledge base — including login problems, email configuration, password resets, hardware requests, and software upgrades  [source: JFM responsibility (P1) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies foundational hardware, software, and operating-system troubleshooting knowledge using predefined scripts, decision trees, and the knowledge base; entry-level certification knowledge (e.g., CompTIA A+) applied to routine issues."
   Target:   ⟨target⟩   Due: ⟨date⟩

3. Area: Creates and manages tickets with proper categorization, and communicates and follows up with users to ensure SLA compliance  [source: JFM responsibility (P1) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies foundational hardware, software, and operating-system troubleshooting knowledge using predefined scripts, decision trees, and the knowledge base; entry-level certification knowledge (e.g., CompTIA A+) applied to routine issues."
   Target:   ⟨target⟩   Due: ⟨date⟩

4. Area: Performs initial triage for network connectivity issues and escalates to Tier 2 with proper documentation  [source: JFM responsibility (P1) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies foundational hardware, software, and operating-system troubleshooting knowledge using predefined scripts, decision trees, and the knowledge base; entry-level certification knowledge (e.g., CompTIA A+) applied to routine issues."
   Target:   ⟨target⟩   Due: ⟨date⟩

5. Area: Handles 30-50 tickets per day, resolving 60-70% without escalation under close supervision  [source: JFM responsibility (P1) — reused, no distinct responsibility content]
   Standard: Consistent with this level's jfm knowledge-application rubric: "Applies foundational hardware, software, and operating-system troubleshooting knowledge using predefined scripts, decision trees, and the knowledge base; entry-level certification knowledge (e.g., CompTIA A+) applied to routine issues."
   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

"Serves as first point of contact for users facing technical issues (Tier 1), performing initial issue assessment and triage by collecting user details and determining urgency"→ ⟨target⟩ by ⟨date⟩
"Resolves basic technical issues using predefined scripts, decision trees, and the knowledge base — including login problems, email configuration, password resets, hardware requests, and software upgrades"→ ⟨target⟩ by ⟨date⟩
"Creates and manages tickets with proper categorization, and communicates and follows up with users to ensure SLA compliance"→ ⟨target⟩ by ⟨date⟩
"Performs initial triage for network connectivity issues and escalates to Tier 2 with proper documentation"→ ⟨target⟩ by ⟨date⟩
"Handles 30-50 tickets per day, resolving 60-70% without escalation under close supervision"→ ⟨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
  - "Serves as first point of contact for users facing technical issues (Tier 1), performing initial issue assessment and triage by collecting user details and determining urgency"  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P1)]
  - "Resolves basic technical issues using predefined scripts, decision trees, and the knowledge base — including login problems, email configuration, password resets, hardware requests, and software upgrades"  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P1)]
  - "Creates and manages tickets with proper categorization, and communicates and follows up with users to ensure SLA compliance"  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P1)]
  - "Performs initial triage for network connectivity issues and escalates to Tier 2 with proper documentation"  →  ⟨target⟩ by ⟨date⟩   [source: JFM responsibility (P1)]
  - "Handles 30-50 tickets per day, resolving 60-70% without escalation under close supervision"  →  ⟨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)]