In the realm of innovative ideas, the concept of creating res killing programs to facilitate the transition of non-tech employees into software, IT, and data positions has emerged. However, embarking on such a venture requires careful consideration. How does one prepare a cashier, customer service representative, or claim processor to effectively contribute to a software development team?
Recently, Don Jones, Head of Developer Skills at Pluralsight, and Jessica Schneider, VP at Develop Intelligence, shed light on this topic at a noteworthy event. Schneider acknowledged that res killing non-tech employees can appear daunting, given their lack of computer science degrees or foundational knowledge in coding. These individuals are embarking on a complete career shift, venturing into uncharted territory.
The planning process for such res killing endeavor encompasses multiple stakeholders across various departments, making it a complex undertaking. Schneider offered a three-step foundation to kick-start the process:
Firstly, it is essential to begin with the end in mind. Anticipate the culmination of the res killing program, envisioning the moment when graduates step into their new tech roles. What specific tasks should they be proficient in, independently? What knowledge and skills will their team and manager expect them to possess? Will they be involved in bug fixing or developing feature enhancements? Obtaining precise, detailed answers to these questions resembles the requirements phase of a software development project. Just as you meticulously articulate what a software solution should accomplish before commencing its development, a similar approach is required here.
Once the ultimate goal of the res killing initiative is defined, it becomes easier to determine the technologies that should be covered and the depth of their coverage in the program. Consequently, decisions about program length, structure, and content can be made more effectively.
Secondly, careful consideration must be given to selecting participants for the res killing program. Identifying candidates who possess both an interest in a coding career and the aptitude for it proves to be the most challenging aspect of such an endeavor. Establishing a recruitment strategy is imperative before outlining a timeline for the training program.
To begin, it is crucial to keep the end result in mind. Collaborate with the teams that will receive these reskilled graduates to define the attributes and skills necessary for success in their roles.
Additionally, it is important to provide clarity on the career prospects for program participants. Prospective applicants need a comprehensive understanding of what their roles will entail after completing the res killing program to make informed decisions. The more specific information provided about post-program opportunities, the more confident employees will feel when contemplating their application. Furthermore, it is crucial to consider the sources for recruiting these employees. If they are internal candidates, strategies must be devised to secure buy-in from managers who might be hesitant to let star performers transition into the res killing program. Plans must also be made to fill the positions left vacant by the participants.
Effective evaluation methods should be established to identify candidates who are likely to thrive or at the very least, persevere through the steep learning curve of a res killing program.
Thirdly, the identification and engagement of champions within the organization are vital. As Schneider emphasized, recruiting passionate champions who align with the res killing vision often goes unnoticed. These champions play a crucial role in brainstorming, decision-making, and overcoming obstacles during the planning and implementation stages. Early support and continuous engagement of these champions are crucial. They can assist with internal communication, recruit mentors to support students throughout the program, and collaborate on curriculum development.
In conclusion, the design of res killing programs for non-tech employees encompasses multiple layers. By establishing the foundation of program requirements, defining a robust recruitment strategy, and engaging passionate champions, organizations can confidently proceed with designing effective res killing programs. Schneider referred to these programs as "multi-layered" because they extend beyond technical training. In addition to equipping participants with job-specific technical knowledge, they must also develop the mindset and problem-solving abilities of programmers. For individuals accustomed to roles like cashiers or call center representatives, their daily interactions and work methods differ significantly from those of software developers. Effective res killing programs, therefore, focus not only on technical skills but also on teaching participants how to approach and solve problems, conduct research, collaborate within a software team, and more. When organizations consider implementing res killing programs for non-tech employees, it is crucial to maintain realistic expectations. Schneider highlighted that the goal is not to create experts by the end of the program but to prepare entry-level developers. The programs should equip participants with the necessary skills to begin their new roles and instill the confidence needed for success. Furthermore, these programs should foster a culture of continuous growth and skill development as individuals progress in their jobs.
By following the three-step foundation of program requirements, recruitment strategy, and champion engagement, organizations can proceed with designing comprehensive res killing programs. These programs provide the necessary technical knowledge while also cultivating the mindset and problem-solving abilities required in the tech industry. Ultimately, they empower non-tech employees to embark on a new career path and support their continued growth and success in their new roles.
You must be logged in to post a comment.