Leadership for Technical Professionals Training Course

Duration 5 days 10 modules · 33 contact hours
Level Intermediate Certificate on completion
Who attends Senior Technical Specialists, Technical Team Leaders and others
Fee from USD 1,100 KSh 95,000 for Kenyan organisations
Where 52 cities + online See dates by city
Next start 16 Nov 2026 Course code SD-LD-208

Before you join: Participants should have experience working in a technical, analytical, operational or professional specialist role and regular interaction with colleagues, customers or project stakeholders.

Dates & prices

Two start dates a month in every city, and live online on weekdays or weekends. Fees are per participant; classroom fees include tuition, materials, lunch and refreshments, and the certificate.

Suggest a date or city

Showing the next six months. Later dates, other cities and private deliveries for your team are available on request.

Course overview

Technical professionals are often promoted because they solve difficult problems, make sound decisions and deliver reliable work. Leadership requires a different set of behaviours: setting direction when requirements are incomplete, gaining commitment without relying on hierarchy, communicating risk to non-specialists, and developing people with different levels of technical confidence. Without these skills, capable specialists can become bottlenecks, teams can wait for decisions, and stakeholders can misunderstand technical trade-offs.

This course develops the practical leadership skills needed to lead technical teams, projects and cross-functional work. Participants examine the shift from expert contributor to leader, diagnose leadership approaches using Situational Leadership II, establish team roles through RACI, and communicate decisions through concise stakeholder messages. They practise structured feedback using the SBI model, coaching with GROW, delegation based on task readiness, conflict resolution, decision framing and change communication. The course addresses common technical leadership situations, including incident response, system implementation, regulatory remediation, engineering delivery and data-driven transformation.

Instruction combines short faculty briefings with sector-relevant cases, facilitated group work, role simulations and individual application planning. Participants work with realistic technical scenarios involving competing priorities, uncertain evidence, operational risk and diverse stakeholder interests. They leave with a personal leadership action plan, stakeholder communication tools, delegation and coaching templates, and a practical approach for applying course methods to a current team or project.

The course suits technical specialists moving into leadership, established supervisors of technical staff, project leads and managers who must coordinate experts across business, operational and control functions.

What you will be able to do

  • Diagnose leadership responses using the Situational Leadership II development-level model
  • Set team direction through clear outcomes, decision rights and RACI assignments
  • Communicate technical risks and trade-offs using audience-specific stakeholder messages
  • Delegate technical work using task clarity, authority boundaries and review checkpoints
  • Conduct performance conversations using the SBI feedback and GROW coaching models
  • Resolve technical disagreements through interest-based negotiation and decision criteria
  • Lead change adoption using stakeholder analysis, ADKAR actions and resistance responses
  • Produce a 90-day leadership application plan for a current workplace challenge

Benefits of attending

For you

  • A clearer transition plan from technical expert to trusted team leader
  • Practical language for explaining technical risk to senior non-specialists
  • A repeatable method for delegating without losing delivery control
  • Greater confidence conducting feedback, coaching and difficult performance conversations
  • A 90-day plan linked to an active leadership challenge

For your organisation

  • Fewer decision bottlenecks caused by over-reliance on senior technical experts
  • Clearer accountability between technical teams, projects and business stakeholders
  • More consistent feedback and development for specialist staff
  • Earlier escalation of technical risks, dependencies and delivery trade-offs
  • Stronger adoption of operational, digital and regulatory change initiatives

Course modules

10 modules over 5 days

Participants can distinguish expert contribution from leadership responsibilities and define their leadership remit.

  • Expert authority versus leadership authority in specialist teams
  • Leadership identity shifts after promotion from technical contributor
  • Expectations mapping for managers, peers, team members and stakeholders
  • Technical credibility maintained without personally solving every problem
  • The leadership operating system: direction, alignment and commitment
  • Personal strengths, derailers and habitual responses under delivery pressure

Participants can select an appropriate leadership approach for different people and tasks.

  • Situational Leadership II: matching style to development level
  • Diagnosing competence and commitment for a specific technical task
  • Directing, coaching, supporting and delegating behaviours compared
  • Avoiding over-supervision of experienced specialists and under-supporting newcomers
  • Task maturity differs across incidents, projects and operational work
  • Leadership style adjustments during deadlines, failures and uncertainty

Participants can translate technical work into clear priorities, accountabilities and decision boundaries.

  • Outcome statements separating business value from technical activity
  • SMART objectives written for delivery, quality and risk controls
  • RACI matrix assignments for cross-functional technical deliverables
  • Decision rights defined through authority thresholds and escalation paths
  • Prioritisation using impact, urgency, effort and risk criteria
  • Weekly operating rhythms for commitments, blockers and decisions

Participants can communicate technical issues, decisions and risks in terms relevant to each audience.

  • Audience analysis for executives, users, suppliers and technical peers
  • Message maps linking technical detail, business impact and decisions
  • Risk communication using likelihood, impact, controls and residual exposure
  • BLUF structure for concise briefings under time pressure
  • Translating architecture, data and security issues into decision language
  • Handling challenge questions without defensiveness or unnecessary technical detail

Participants can delegate technical work while retaining appropriate oversight and accountability.

  • Delegation briefing: outcome, constraints, authority, support and deadlines
  • Choosing delegation levels using competence, risk and reversibility
  • Control points built around milestones, evidence and acceptance criteria
  • Delegating decisions rather than merely reallocating technical tasks
  • Avoiding reverse delegation when team members bring problems upward
  • Recovery conversations when delegated work misses agreed expectations

Participants can hold constructive feedback and coaching conversations with technical professionals.

  • SBI feedback model: situation, behaviour and impact
  • GROW coaching questions for performance, development and problem-solving
  • Separating observable evidence from assumptions about technical capability
  • Feedforward requests focused on future actions and support
  • Addressing defensiveness during quality, conduct and delivery conversations
  • Documenting agreed actions, owners, dates and review points

Participants can create team conditions for speaking up, learning and reliable collaboration.

  • Psychological safety behaviours: invite input, acknowledge uncertainty, respond productively
  • Team working agreements for challenge, escalation and decision-making
  • Blameless incident review focused on systems, evidence and learning
  • Trust equation applied to credibility, reliability, intimacy and self-orientation
  • Inclusive meeting practices for quieter experts and remote participants
  • Repairing trust after missed commitments, errors or communication failures

Participants can resolve disagreements and build commitment around contested technical decisions.

  • Interest-based negotiation separates positions, interests, options and criteria
  • Conflict diagnosis: task, process, relationship and values disputes
  • Decision criteria weighted before comparing technical solution options
  • DACI roles clarify drivers, approvers, contributors and informed parties
  • Influence mapping identifies supporters, blockers and undecided stakeholders
  • Escalating unresolved conflict with evidence, alternatives and recommendation

Participants can plan leadership actions that support adoption of technical and operational change.

  • ADKAR model applied to new systems, controls and processes
  • Stakeholder analysis identifies change impacts, concerns and influence
  • Change messages explain rationale, consequences and required behaviours
  • Resistance treated as data requiring listening, diagnosis and response
  • Sponsor actions distinguish visible support from delegated communication
  • Adoption measures track usage, competence, compliance and performance

Participants can create a focused plan for applying leadership methods to a current technical challenge.

  • Current leadership challenge framed through outcomes, stakeholders and constraints
  • Leadership diagnosis identifies behaviours requiring immediate adjustment
  • Stakeholder communication plan schedules messages, owners and feedback channels
  • Delegation and coaching actions linked to named team members
  • Risk register records barriers, triggers, mitigations and escalation decisions
  • Ninety-day application plan includes measures, reviews and accountability partners

Exercises and examples are adapted to each cohort's sectors and roles.

What you take back to work

  1. Situational Leadership II diagnosis worksheet
  2. RACI and decision-rights template
  3. Technical stakeholder message map
  4. Delegation briefing checklist
  5. SBI feedback and GROW coaching guide
  6. 90-day leadership application plan

Who should attend

  • Senior Technical Specialists — preparing to lead colleagues while retaining technical credibility
  • Technical Team Leaders — managing delivery, performance and priorities across specialist teams
  • Project Managers — coordinating technical contributors, business sponsors and operational stakeholders
  • Engineers and IT Professionals — moving from expert roles into supervisory responsibilities
  • Risk, Data and Compliance Managers — leading specialists through regulated change and control work
  • Newly Appointed Managers — building practical people-leadership methods for technical teams

Skills and tools covered

Technical team leadershipStakeholder communicationPerformance coachingDelegation designConflict resolutionChange leadership

Tools and standards

Situational Leadership II, RACI matrix, SBI feedback model, ADKAR model

How the course runs

Training methodology

Faculty-led briefings introduce each leadership method before participants apply it to technical management situations. Cases draw on technology delivery, engineering operations, data governance, cyber incidents, regulatory remediation and service improvement. Small-group analysis, role simulations and structured peer feedback build communication, coaching, delegation and conflict-resolution skill. Participants use their own current leadership challenges to test decision tools, stakeholder messages and action plans. Facilitators provide practical feedback on clarity, authority, stakeholder alignment and follow-through.

Requirements and prerequisites

Participants should have experience working in a technical, analytical, operational or professional specialist role and regular interaction with colleagues, customers or project stakeholders. Some participants may already supervise staff or lead workstreams; formal line-management experience is not required. Familiarity with a current team, project or delivery challenge will help participants apply the methods during the course. No leadership qualification, management degree, psychometric assessment, prior coaching training or advanced presentation skill is required. The course does not require programming, engineering, financial modelling or other specific technical knowledge.

A typical training day

08:30 – 10:30First session
10:30 – 10:45Refreshment break
10:45 – 12:30Second session
12:30 – 13:30Lunch and networking
13:30 – 15:00Third session
15:00 – 15:15Refreshment break
15:15 – 16:30Workshop and daily review

Live online deliveries follow the same structure in East Africa Time, with shorter screen blocks and longer breaks.

What the fee includes

  • Instruction by a practitioner facilitator
  • Full course workbook and materials
  • Exercise files, templates and case studies
  • Refreshments and lunch on classroom deliveries
  • Certificate of completion
  • Post-course application plan

Frequently asked questions

Participants should have experience in a technical, specialist, analytical or operational role. They do not need formal management experience, but a current team, project or stakeholder challenge will make the application work more useful.

Participants should bring details of a current leadership challenge, such as a delivery issue, team-performance concern, stakeholder conflict or change initiative. Confidential information can be anonymised before discussion.

It is designed for technical specialists becoming leaders, team leaders, project managers and managers of expert staff. It is also suitable for experienced managers who need more effective methods for leading technical contributors.

The course focuses on issues common in technical settings: expert authority, technical risk communication, decision rights, delivery control and specialist performance. Cases and tools are selected for leaders who must connect technical work with business, operational or regulatory outcomes.

Participants leave with reusable templates for stakeholder communication, delegation, coaching and accountability. The final module converts a current challenge into a 90-day application plan with actions, measures and review points.

The programme contains ten modules delivered in teaching order across five training days, from 08:30 to 16:30. Each day includes approximately 6.5 contact hours, combining faculty input, cases, group work, simulations and application planning.

Questions about this course?

Ask about dates, fees, group bookings or running it for your team. Our training team replies by email.