Building a Team: Interviewing
-Introduce yourself.
-Ask open ended questions that covering the following aspects:
- Behavioral - Conflict, challenges, prioritization, pride project
- Technical - Process work flow, instructional design, instructional theories and their application
-While the interviewee grapples with the questions take additional notes on:
- Communication skills
- Individual dynamic and the impact it might have on your team
- Skillset that the candidate adds to the team
-If you are a panel of interviewers, divide the questions. Allow some overlap.
-Provide an overview of the company's operation and function.
-Address the any questions that the interviewee might have. Which area do the questions fall in?
-Fill out a predefined evaluation format that covers the parameters that are important for your team.
-Debrief
Comments
Clear communication therefore, in my opinion becomes the key to having a smooth workflow. Unless, the ID is required to work in isolation (does that happen?)where s/he can dig into their rich experience to generate value for the project.
What do you think?
In the absence of confidence and communication skills, IDs may feel safer with their Managers making decisions for them.
I think its important for us to be mindful of the parameters and contraints under which a project is operating and check if our ideas actually add value.
Once we are convinced ourselves, we need to be able to effectively communicate the idea to the team - how its implementation would enhance learners' experience, how the idea can be developed within the organization's constraints and the time required. With thorough homework done, I see no reason why our ideas would not be heard, though not necessarily accepted (a team member may build on the idea or might bring to light a constraint that one had not considered).
If one's ideas are not respected despite putting in a matured thought, its probably time to move on to an organization that would. :-)
Will reply to it over the weekend ..loads of work ya:(