1. Session 1 University of Southern California ISE544 May 21, 2009 Geza P. Bottlik Page 1 Outline Introduce Instructor Introduce TA Introduce yourselves Go over syllabus How to get a good grade Take roll Solicit Input Give Assignment Lecture

2. Session 1 University of Southern California ISE544 May 21, 2009 Geza P. Bottlik Page 2 How to get a good grade Create an organized three ring binder Read ahead Come to class Bring your texts and notebook to class Stay awake and participate Ask questions (there are no stupid questions) Take notes Do homework at leisure, make sure it is complete

3. Session 1 University of Southern California ISE544 May 21, 2009 Geza P. Bottlik Page 3 How to get a good grade If you have trouble with the homework (in this order): Ask a classmate E-mail the TA or go to her office hours E-mail the instructor Go to instructor’s office hours Compare your returned homework to the provided answers and resolve any differences Read for understanding, do exercises Work hard early in the semester, not at the end Start your assignments in plenty of time, rewrite and edit them several times Don’t let either the simplicity or apparent complexity of the material fool you Be critical of all information

4. Session 1 University of Southern California ISE544 May 21, 2009 Geza P. Bottlik Page 4 Homework The format of the homework is up to you, provided: It is typed, digital Neat, corrected for spelling and grammar Starts with conclusions and ends with supporting material Is contained in one document (no separate documents when electronic, no zip files) Contains the assignment ID, your name and anyone’s name you you worked with My personal preference is for double spaced, 12 point Ariel

5. Session 1 University of Southern California ISE544 May 21, 2009 Geza P. Bottlik Page 5 Course Outline The course is divided into three major parts along the lines of the three books that we will be using: Teams and Virtual Teams Managerial skills for engineers and scientists Negotiation

6. Session 1 University of Southern California ISE544 May 21, 2009 Geza P. Bottlik Page 6 Course Outline (continued) The second level of detail for each part: Teams and Virtual Teams Critical success factors of virtual teams Myths and realities of virtual teams Steps towards a virtual team Roles and competencies in teams Building trust

7. Session 1 University of Southern California ISE544 May 21, 2009 Geza P. Bottlik Page 7 Course Outline (continued) Managerial skills for engineers and scientist Fundamental principles for every technical manager Managing without authority – project, matrix, and cross functional organizations Career planning Developing Organizational Design Skills

8. Session 1 University of Southern California ISE544 May 21, 2009 Geza P. Bottlik Page 8 Course Outline (continued) Negotiation Fundamentals of decision analysis, behavioral decision making, game theory and negotiation analysis Two party distributive negotiations (win/lose) Two party integrative negotiations (win/win) External Help (mediation) Group Decisions (consensus, voting, coalitions)

9. Session 1 University of Southern California ISE544 May 21, 2009 Geza P. Bottlik Page 9 Some introductory thoughts on teams in general I had intended to have more reading material but got lots of advice that 3 books were enough One of the short books I meant to use was: “Team work and group dynamics” By Stewart, Mantz and Sims, John Wiley, 1999. I made a short summary about teams from that book.

10. Session 1 University of Southern California ISE544 May 21, 2009 Geza P. Bottlik Page 10 What is a team? A collection of individuals who exist within a large social system Who can be identified by themselves and others as a team Who are interdependent Who perform tasks with a common objective “A team is a small number of people with complementary skills who are committed to a common purpose, performance goals, and approach for which they are mutually accountable” Katzenbach and Smith, 1993

11. Session 1 University of Southern California ISE544 May 21, 2009 Geza P. Bottlik Page 11 What is a team? (cont) A team is a group of people who, for a specific period of time, are mutually dependent on one another to achieve a common goal Purpose –Various (engineering) tasks with MEASURABLE results Duration – Permanent or temporary Membership –Functional, cross-functional

12. Session 1 University of Southern California ISE544 May 21, 2009 Geza P. Bottlik Page 12 Important Distinctions Effective work group – Shared values, culture – Hierarchical leadership – Not outcome based Single leader group – Same as above, but: – Individual performance based – Single leader Real team – Shifting leadership – “Leader” engages in real work – Team performance based (and accountable)

13. Session 1 University of Southern California ISE544 May 21, 2009 Geza P. Bottlik Page 13 Advantages of teams

14. Session 1 University of Southern California ISE544 May 21, 2009 Geza P. Bottlik Page 14 Advantages of teams High quality results – More input, better informed, more responsive Increased ownership and buy-in – High likelihood of implementation of new ideas Improved communication – Widen circle of understanding and appreciation More learning opportunities – Share information to increase mutual learning More job satisfaction – Develop personal relationships and a sense of security

15. Session 1 University of Southern California ISE544 May 21, 2009 Geza P. Bottlik Page 15 Disadvantages of teams

16. Session 1 University of Southern California ISE544 May 21, 2009 Geza P. Bottlik Page 16 Disadvantages of teams Requires more time – More meetings; takes longer to make decisions Individual performance may suffer (initially) – An excuse for lack of individual performance Generate more conflicts – Personal conflicts magnified which causes strained relationships – Unhealthy group dynamics Split into subgroups Exclusivity “group think” can limit innovation

17. Session 1 University of Southern California ISE544 May 21, 2009 Geza P. Bottlik Page 17 Teamwork challenges

18. Session 1 University of Southern California ISE544 May 21, 2009 Geza P. Bottlik Page 18 Teamwork challenges Absence of trust –We are not willing to be vulnerable to others Fear of conflict –We are not comfortable in confrontations Lack of commitment –We tend to refuse things that we do not own Avoidance of accountability –We hate to be responsible for others Inattention to results –We hesitate in claiming collective results

19. Session 1 University of Southern California ISE544 May 21, 2009 Geza P. Bottlik Page 19 Why do people form teams?

20. Session 1 University of Southern California ISE544 May 21, 2009 Geza P. Bottlik Page 20 Why do people form teams? Functional perspectives (survival, evolutionary selection) produce food defense care for one another provide social support facilitate reproduction Interpersonal perspectives (innate social desires) need for affiliation power over others give and receive affection need for information from others social comparison