Build a Help Desk Career Path From Tier 1 to Tier 2

Choose the Work Your Desk Needs

The service lead owns the development scope. Start with the Tier 2 responsibilities your desk actually needs, then inspect relevant tickets with the technician. Keep this about a technical step rather than quietly adding dispatch or team management to the promotion.

Choose tasks that require the technician to investigate within your supported stack and explain the next action. Define the access and approval boundaries alongside the technical work. A development ticket still belongs to a real client, with the usual service commitments.

The model assigns 22% of tickets to Tier 2 resolution for workload planning. That isn't a personal quota or a promotion threshold. Don't route that share to a learner just to make the staffing assumption appear in their record.

Erick Simpson describes investigating categorization and assignment alongside competence when first-line work was escalating. He also checks documentation and necessary access. That is his diagnostic approach, and a reason to examine the work system before declaring a technician unready.

Write the Standard Before Assigning Stretch Work

The service lead owns the assessment standard; the designated coach confirms it is observable. Agree what a competent result looks like for the selected work. Put the same standard in front of the technician before the practice begins.

Avoid 'be more proactive' as a development objective. Give the technician an action that can be observed on a suitable ticket. A confident explanation needs to agree with the actual record before the coach accepts it.

Observe, Then Let the Technician Do the Work

The coach owns the demonstration. Choose a suitable case and explain the reasoning as well as the action. Have the technician identify the next check before the coach carries it out, so the discussion shows whether the reasoning is understood.

Then assign supervised work with the technician doing the investigation. Agree where the coach must review a proposed action before it happens. Keep the coach available through that agreed route, rather than relying on an unannounced interruption of someone else's queue.

Use a lab or another appropriate controlled setting for practice that should not be attempted on a client system. Give practice work its own objective and review record. Don't call a live service ticket a training exercise to excuse an unsafe change.

The technician owns the working notes and the explanation at review. The coach checks the result and records what still needs practice. A certificate doesn't answer the escalation queue.

Protect Time for Both People

The scheduler owns the bookings for coaching and reviewed work. Account for the coach's time as well as the learner's, and keep their remaining assignments realistic. If you cancel the session for service demand, rebook it visibly instead of treating the missing practice as a technician failure.

Choose the review dates from the actual opportunities to practice and the work the desk can cover. The proposed plan does not need a guaranteed duration. Where the role requires experience the learner has not yet had a chance to demonstrate, record that gap and arrange an appropriate opportunity.

My test is simple: what does this do to the board on Monday morning? It should identify the learner's suitable work and the coach who is available to review it. If those assignments are absent, the development plan is a document waiting for spare time.

Review the Reasoning Across Suitable Work

The service lead owns the readiness decision, using the coach's records and the technician's work. Look for demonstrated judgment across the responsibilities you agreed. A ticket solved by the coach cannot stand as evidence that the learner can independently handle it.

Keep a material gap specific. Record the task or decision that still needs support, then agree the practice and review that address it. Don't replace that explanation with an impression that the technician needs more seasoning.

Preserve good escalation as part of the standard. If the technician recognizes that an action exceeds their authority or expertise and makes a useful handoff, assess that judgment on its merits. Refusing to ask for help is not evidence of independence.

Budget the Role and State the Pay Decision

The owner owns the role budget and pay approval. Treat the model's salaries as planning inputs, not as a universal pay band for your local market. Set your actual band and the point at which the new responsibilities and pay would take effect.

On the US model's general burden factor of 1.25, $50,000 becomes $62,500 in annual burdened pay. At the same factor, $62,000 becomes $77,500. The budget difference is $15,000 a year before other costs outside that factor, including recruiting, training, equipment, and software.

If a promotion replaces the person's existing role, don't budget it as an additional whole employee unless you also intend to backfill that work. Show the actual staffing change. The desk still needs someone to carry the responsibilities that move off the promoted technician.

Tell the technician whether a suitable role exists and who can approve it. If the skills are demonstrated but no role is available, say that plainly and discuss the actual options. Avoid using an indefinitely expanding practice plan to hide a budget decision.

Start with the technician and the coach looking at the same selected ticket. Write the observable standard, book the next practice, and record who decides readiness and pay. That gives the technician a next step they can actually take.