Previous KTP Article leads to KTP Induction Program
A previous article covering issues with KTP development received such strong support via Linked In that it has spawned this article. One of the responders suggested that a finely tuned induction program for KTPs could alleviate issues. Because every company is different, a one size fits all coverage of as many issues as possible follows here, but it is intended that the reader cherry picks to suit his/her situation.
What’s the Objective?
An academic joining a new company, especially a technical SME, may not have a complete picture of the skills, experience and limitations of the company in question. Equally, depending on the technical profile of the staff in the company in question, the company may have a limited notion of the skills, experience and limitations of the academic.
A basic assumption of this article is that the KTP is involved with the delivery of a physical product in some way. This could be hardware, software, firmware or any combination of these.
The objective of this article is to cover the major functions of a technical SME from the perspective of a KTP employee, and to scope the capabilities of a KTP person from the perspective of an SME. Its generic nature means it can’t serve as a universal induction program or manual, but it is hoped that it might cause such to be written for the companies in question.
The key requirement for SME and KTP employee alike is that
KTP – Academic
There are general qualities and capabilities that
SME Management
