Mixing
As a new Team Leader, what should I talk about in an initial, introductory, one on one meeting? [closed]
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
5
down vote
favorite
I've started new position on my company, and I need to get to know the team members (although I'm already familiar with some of them).
What items should we discuss in an initial one on one meeting to help make this transition successful?
team meetings employees team-role
edited Oct 7 '13 at 0:54
jmort253♦
10.4k54376
asked Oct 6 '13 at 9:04
Adam
2912
closed as too broad by Jim G., jmort253♦ Oct 7 '13 at 0:50
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |Â
up vote
5
down vote
favorite
I've started new position on my company, and I need to get to know the team members (although I'm already familiar with some of them).
What items should we discuss in an initial one on one meeting to help make this transition successful?
team meetings employees team-role
edited Oct 7 '13 at 0:54
jmort253♦
10.4k54376
asked Oct 6 '13 at 9:04
Adam
2912
closed as too broad by Jim G., jmort253♦ Oct 7 '13 at 0:50
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
3
Hi Adam, this is a broad question, but I've edited it a bit to focus on the fact that this is an initial one on one, introductory meeting. It's always a good idea to put important information from the title of your post also in the body. Can you take a look and, if there's any more pertinent details you can add that will help get better answers, edit that info in and flag the post and I'll reopen. Hope this helps! :)
– jmort253♦
Oct 7 '13 at 0:56
add a comment |Â
up vote
5
down vote
favorite
up vote
5
down vote
favorite
I've started new position on my company, and I need to get to know the team members (although I'm already familiar with some of them).
What items should we discuss in an initial one on one meeting to help make this transition successful?
team meetings employees team-role
edited Oct 7 '13 at 0:54
jmort253♦
10.4k54376
asked Oct 6 '13 at 9:04
Adam
2912
I've started new position on my company, and I need to get to know the team members (although I'm already familiar with some of them).
What items should we discuss in an initial one on one meeting to help make this transition successful?
team meetings employees team-role
edited Oct 7 '13 at 0:54
jmort253♦
10.4k54376
asked Oct 6 '13 at 9:04
Adam
2912
edited Oct 7 '13 at 0:54
jmort253♦
10.4k54376
edited Oct 7 '13 at 0:54
jmort253♦
10.4k54376
edited Oct 7 '13 at 0:54
jmort253♦
10.4k54376
10.4k54376
asked Oct 6 '13 at 9:04
Adam
2912
asked Oct 6 '13 at 9:04
Adam
2912
asked Oct 6 '13 at 9:04
Adam
2912
2912
closed as too broad by Jim G., jmort253♦ Oct 7 '13 at 0:50
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
closed as too broad by Jim G., jmort253♦ Oct 7 '13 at 0:50
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
3
Hi Adam, this is a broad question, but I've edited it a bit to focus on the fact that this is an initial one on one, introductory meeting. It's always a good idea to put important information from the title of your post also in the body. Can you take a look and, if there's any more pertinent details you can add that will help get better answers, edit that info in and flag the post and I'll reopen. Hope this helps! :)
– jmort253♦
Oct 7 '13 at 0:56
add a comment |Â
3
Hi Adam, this is a broad question, but I've edited it a bit to focus on the fact that this is an initial one on one, introductory meeting. It's always a good idea to put important information from the title of your post also in the body. Can you take a look and, if there's any more pertinent details you can add that will help get better answers, edit that info in and flag the post and I'll reopen. Hope this helps! :)
– jmort253♦
Oct 7 '13 at 0:56
3
3
Hi Adam, this is a broad question, but I've edited it a bit to focus on the fact that this is an initial one on one, introductory meeting. It's always a good idea to put important information from the title of your post also in the body. Can you take a look and, if there's any more pertinent details you can add that will help get better answers, edit that info in and flag the post and I'll reopen. Hope this helps! :)
– jmort253♦
Oct 7 '13 at 0:56
Hi Adam, this is a broad question, but I've edited it a bit to focus on the fact that this is an initial one on one, introductory meeting. It's always a good idea to put important information from the title of your post also in the body. Can you take a look and, if there's any more pertinent details you can add that will help get better answers, edit that info in and flag the post and I'll reopen. Hope this helps! :)
– jmort253♦
Oct 7 '13 at 0:56
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
3
down vote
I am assuming that these one-on-one meetings supplement a full-team meeting where you've communicated about broader issues (where the team is going, any changes in goals or processes, etc). Covering that stuff in each one-on-one meeting would be inefficient; do it once where the whole team can benefit from the conversation, including hearing others' questions and the answers.
When I've gotten new leads (most recently a couple months ago), we've talked about the following in one-on-one meetings:
My performance goals for the year. Two reasons: (a) in case we need to adjust any of them because of the leadership change, and (b) to highlight any where I'll need my lead's help in order to meet the goal.
What I've been doing on the team so far and how I feel about it. This is a great time to say "I'm really excited about X" or "I've been doing Y for a while and I'd kind of like the chance to do something new" or "I've been helping so-and-so ramp up on Z".
Developments the new lead knows about that might affect me (e.g. we're planning to increase our internal training, so think about topics you might teach). Sometimes the lead volunteers information here, but sometimes my questions started the conversation.
Misc. process stuff, e.g. do you want to meet regularly to chat? My new lead is not local to me, so we talked about meetings and travel.
This usually takes 30-60 minutes in my experience.
There's another set of useful topics: how things are going on the team, meaning the things that don't make it into official reports -- minor process problems, requirements churn, particularly-buggy parts of the code, the difficulty of getting conference rooms, whatever. I've found that it's generally better to wait for a second meeting unless something is particularly urgent; you'll have enough other stuff to worry about, most likely, and you'll be better-equipped to handle things of this nature once you've met with everybody and have a sense of the team.
answered Oct 6 '13 at 21:51
Monica Cellio♦
43.7k17114191
add a comment |Â
up vote
1
down vote
What items should we discuss on that meeting? (my expectation from the
team, their expectation from me.. etc)
Yes, yes, and etc...
As a new leader, you need to convey to your team what you expect of them and how they can deliver on those expectations. You need to tell them what they need to do in support of your team goals, and the company goals.
As a new leader, you also need to learn what they need from you in order to be successful personally, and to succeed in their role.
You and the team also need to understand each others' personalities, learning styles, customs, culture, and methods of working together.
Whenever a team has a new leader, there is uncertainty and sometimes apprehension. Team members need to understand what has changed, their role, how they fit in, where the team is going, etc. Sometimes change is good, sometimes it's bad. You are in a position to paint a picture of what you see for the team, why it is good for the company, and why it is good for them as well.
answered Oct 6 '13 at 12:01
Joe Strazzere
224k107661930
+ 1 for setting expectations
– the_reluctant_tester
Oct 6 '13 at 23:32
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
I am assuming that these one-on-one meetings supplement a full-team meeting where you've communicated about broader issues (where the team is going, any changes in goals or processes, etc). Covering that stuff in each one-on-one meeting would be inefficient; do it once where the whole team can benefit from the conversation, including hearing others' questions and the answers.
When I've gotten new leads (most recently a couple months ago), we've talked about the following in one-on-one meetings:
My performance goals for the year. Two reasons: (a) in case we need to adjust any of them because of the leadership change, and (b) to highlight any where I'll need my lead's help in order to meet the goal.
What I've been doing on the team so far and how I feel about it. This is a great time to say "I'm really excited about X" or "I've been doing Y for a while and I'd kind of like the chance to do something new" or "I've been helping so-and-so ramp up on Z".
Developments the new lead knows about that might affect me (e.g. we're planning to increase our internal training, so think about topics you might teach). Sometimes the lead volunteers information here, but sometimes my questions started the conversation.
Misc. process stuff, e.g. do you want to meet regularly to chat? My new lead is not local to me, so we talked about meetings and travel.
This usually takes 30-60 minutes in my experience.
There's another set of useful topics: how things are going on the team, meaning the things that don't make it into official reports -- minor process problems, requirements churn, particularly-buggy parts of the code, the difficulty of getting conference rooms, whatever. I've found that it's generally better to wait for a second meeting unless something is particularly urgent; you'll have enough other stuff to worry about, most likely, and you'll be better-equipped to handle things of this nature once you've met with everybody and have a sense of the team.
answered Oct 6 '13 at 21:51
Monica Cellio♦
43.7k17114191
add a comment |Â
up vote
3
down vote
I am assuming that these one-on-one meetings supplement a full-team meeting where you've communicated about broader issues (where the team is going, any changes in goals or processes, etc). Covering that stuff in each one-on-one meeting would be inefficient; do it once where the whole team can benefit from the conversation, including hearing others' questions and the answers.
When I've gotten new leads (most recently a couple months ago), we've talked about the following in one-on-one meetings:
My performance goals for the year. Two reasons: (a) in case we need to adjust any of them because of the leadership change, and (b) to highlight any where I'll need my lead's help in order to meet the goal.
What I've been doing on the team so far and how I feel about it. This is a great time to say "I'm really excited about X" or "I've been doing Y for a while and I'd kind of like the chance to do something new" or "I've been helping so-and-so ramp up on Z".
Developments the new lead knows about that might affect me (e.g. we're planning to increase our internal training, so think about topics you might teach). Sometimes the lead volunteers information here, but sometimes my questions started the conversation.
Misc. process stuff, e.g. do you want to meet regularly to chat? My new lead is not local to me, so we talked about meetings and travel.
This usually takes 30-60 minutes in my experience.
There's another set of useful topics: how things are going on the team, meaning the things that don't make it into official reports -- minor process problems, requirements churn, particularly-buggy parts of the code, the difficulty of getting conference rooms, whatever. I've found that it's generally better to wait for a second meeting unless something is particularly urgent; you'll have enough other stuff to worry about, most likely, and you'll be better-equipped to handle things of this nature once you've met with everybody and have a sense of the team.
answered Oct 6 '13 at 21:51
Monica Cellio♦
43.7k17114191
add a comment |Â
up vote
3
down vote
up vote
3
down vote
I am assuming that these one-on-one meetings supplement a full-team meeting where you've communicated about broader issues (where the team is going, any changes in goals or processes, etc). Covering that stuff in each one-on-one meeting would be inefficient; do it once where the whole team can benefit from the conversation, including hearing others' questions and the answers.
When I've gotten new leads (most recently a couple months ago), we've talked about the following in one-on-one meetings:
My performance goals for the year. Two reasons: (a) in case we need to adjust any of them because of the leadership change, and (b) to highlight any where I'll need my lead's help in order to meet the goal.
What I've been doing on the team so far and how I feel about it. This is a great time to say "I'm really excited about X" or "I've been doing Y for a while and I'd kind of like the chance to do something new" or "I've been helping so-and-so ramp up on Z".
Developments the new lead knows about that might affect me (e.g. we're planning to increase our internal training, so think about topics you might teach). Sometimes the lead volunteers information here, but sometimes my questions started the conversation.
Misc. process stuff, e.g. do you want to meet regularly to chat? My new lead is not local to me, so we talked about meetings and travel.
This usually takes 30-60 minutes in my experience.
There's another set of useful topics: how things are going on the team, meaning the things that don't make it into official reports -- minor process problems, requirements churn, particularly-buggy parts of the code, the difficulty of getting conference rooms, whatever. I've found that it's generally better to wait for a second meeting unless something is particularly urgent; you'll have enough other stuff to worry about, most likely, and you'll be better-equipped to handle things of this nature once you've met with everybody and have a sense of the team.
answered Oct 6 '13 at 21:51
Monica Cellio♦
43.7k17114191
I am assuming that these one-on-one meetings supplement a full-team meeting where you've communicated about broader issues (where the team is going, any changes in goals or processes, etc). Covering that stuff in each one-on-one meeting would be inefficient; do it once where the whole team can benefit from the conversation, including hearing others' questions and the answers.
When I've gotten new leads (most recently a couple months ago), we've talked about the following in one-on-one meetings:
My performance goals for the year. Two reasons: (a) in case we need to adjust any of them because of the leadership change, and (b) to highlight any where I'll need my lead's help in order to meet the goal.
What I've been doing on the team so far and how I feel about it. This is a great time to say "I'm really excited about X" or "I've been doing Y for a while and I'd kind of like the chance to do something new" or "I've been helping so-and-so ramp up on Z".
Developments the new lead knows about that might affect me (e.g. we're planning to increase our internal training, so think about topics you might teach). Sometimes the lead volunteers information here, but sometimes my questions started the conversation.
Misc. process stuff, e.g. do you want to meet regularly to chat? My new lead is not local to me, so we talked about meetings and travel.
This usually takes 30-60 minutes in my experience.
There's another set of useful topics: how things are going on the team, meaning the things that don't make it into official reports -- minor process problems, requirements churn, particularly-buggy parts of the code, the difficulty of getting conference rooms, whatever. I've found that it's generally better to wait for a second meeting unless something is particularly urgent; you'll have enough other stuff to worry about, most likely, and you'll be better-equipped to handle things of this nature once you've met with everybody and have a sense of the team.
answered Oct 6 '13 at 21:51
Monica Cellio♦
43.7k17114191
answered Oct 6 '13 at 21:51
Monica Cellio♦
43.7k17114191
answered Oct 6 '13 at 21:51
Monica Cellio♦
43.7k17114191
answered Oct 6 '13 at 21:51
Monica Cellio♦
43.7k17114191
43.7k17114191
add a comment |Â
add a comment |Â
up vote
1
down vote
What items should we discuss on that meeting? (my expectation from the
team, their expectation from me.. etc)
Yes, yes, and etc...
As a new leader, you need to convey to your team what you expect of them and how they can deliver on those expectations. You need to tell them what they need to do in support of your team goals, and the company goals.
As a new leader, you also need to learn what they need from you in order to be successful personally, and to succeed in their role.
You and the team also need to understand each others' personalities, learning styles, customs, culture, and methods of working together.
Whenever a team has a new leader, there is uncertainty and sometimes apprehension. Team members need to understand what has changed, their role, how they fit in, where the team is going, etc. Sometimes change is good, sometimes it's bad. You are in a position to paint a picture of what you see for the team, why it is good for the company, and why it is good for them as well.
answered Oct 6 '13 at 12:01
Joe Strazzere
224k107661930
+ 1 for setting expectations
– the_reluctant_tester
Oct 6 '13 at 23:32
add a comment |Â
up vote
1
down vote
What items should we discuss on that meeting? (my expectation from the
team, their expectation from me.. etc)
Yes, yes, and etc...
As a new leader, you need to convey to your team what you expect of them and how they can deliver on those expectations. You need to tell them what they need to do in support of your team goals, and the company goals.
As a new leader, you also need to learn what they need from you in order to be successful personally, and to succeed in their role.
You and the team also need to understand each others' personalities, learning styles, customs, culture, and methods of working together.
Whenever a team has a new leader, there is uncertainty and sometimes apprehension. Team members need to understand what has changed, their role, how they fit in, where the team is going, etc. Sometimes change is good, sometimes it's bad. You are in a position to paint a picture of what you see for the team, why it is good for the company, and why it is good for them as well.
answered Oct 6 '13 at 12:01
Joe Strazzere
224k107661930
+ 1 for setting expectations
– the_reluctant_tester
Oct 6 '13 at 23:32
add a comment |Â
up vote
1
down vote
up vote
1
down vote
What items should we discuss on that meeting? (my expectation from the
team, their expectation from me.. etc)
Yes, yes, and etc...
As a new leader, you need to convey to your team what you expect of them and how they can deliver on those expectations. You need to tell them what they need to do in support of your team goals, and the company goals.
As a new leader, you also need to learn what they need from you in order to be successful personally, and to succeed in their role.
You and the team also need to understand each others' personalities, learning styles, customs, culture, and methods of working together.
Whenever a team has a new leader, there is uncertainty and sometimes apprehension. Team members need to understand what has changed, their role, how they fit in, where the team is going, etc. Sometimes change is good, sometimes it's bad. You are in a position to paint a picture of what you see for the team, why it is good for the company, and why it is good for them as well.
answered Oct 6 '13 at 12:01
Joe Strazzere
224k107661930
What items should we discuss on that meeting? (my expectation from the
team, their expectation from me.. etc)
Yes, yes, and etc...
As a new leader, you need to convey to your team what you expect of them and how they can deliver on those expectations. You need to tell them what they need to do in support of your team goals, and the company goals.
As a new leader, you also need to learn what they need from you in order to be successful personally, and to succeed in their role.
You and the team also need to understand each others' personalities, learning styles, customs, culture, and methods of working together.
Whenever a team has a new leader, there is uncertainty and sometimes apprehension. Team members need to understand what has changed, their role, how they fit in, where the team is going, etc. Sometimes change is good, sometimes it's bad. You are in a position to paint a picture of what you see for the team, why it is good for the company, and why it is good for them as well.
answered Oct 6 '13 at 12:01
Joe Strazzere
224k107661930
edited Nov 8 '13 at 15:57
answered Oct 6 '13 at 12:01
Joe Strazzere
224k107661930
answered Oct 6 '13 at 12:01
Joe Strazzere
224k107661930
answered Oct 6 '13 at 12:01
Joe Strazzere
224k107661930
224k107661930
+ 1 for setting expectations
– the_reluctant_tester
Oct 6 '13 at 23:32
add a comment |Â
+ 1 for setting expectations
– the_reluctant_tester
Oct 6 '13 at 23:32
+ 1 for setting expectations
– the_reluctant_tester
Oct 6 '13 at 23:32
+ 1 for setting expectations
– the_reluctant_tester
Oct 6 '13 at 23:32
add a comment |Â
3
Hi Adam, this is a broad question, but I've edited it a bit to focus on the fact that this is an initial one on one, introductory meeting. It's always a good idea to put important information from the title of your post also in the body. Can you take a look and, if there's any more pertinent details you can add that will help get better answers, edit that info in and flag the post and I'll reopen. Hope this helps! :)
– jmort253♦
Oct 7 '13 at 0:56