How to spend first month?
I am about to start my new job as IT manager in logistics company, with 2 members of my team.
What would be the best way to spend first month (or three?) on new job?
IT Employment
I am about to start my new job as IT manager in logistics company, with 2 members of my team.
What would be the best way to spend first month (or three?) on new job?
talk to everybody.
Learn the environment. Sit in with your people on the day to day stuff. Look through the call log. After the first month write your impressions down and go from there.
Take your two members for a beer, you can find out all sorts of useful stuff when people let their hair down.
In my experience the first thing a new manager does is get right up at least one person's nose.
Might be necessary, then again it might not.
Above all resist the temptation to be a new broom superstar in your first week.
by tim.doyle3
by ssabanis
I am involved in IT for 20 years.
The lesson that I learned is that:
- When you are a ne IT Manager, you must make something different than the previous one(s). One imprtant question is "Why/Where the previous failed?" Then try to avoid making the same mistakes
- Build a team/Build YOUR team. No matter how big is the IT dept. you must find your allies. Build a team with these few so you can trust them and they can trust you.
- Try to establish new Processes or new Applications in the Organization. You might gain power from this and definitely prove that "you can deliver".
Cheers
by unanikka
Being since works start till works stop.
Let them notice you.
Be faithful and patient.
Most of all, try to remember thier name.
by jaredh
First, let me say that I am impressed that as a new manager, you are looking to improve and better your self as a manager. Good for you.
Remember that management is teamwork and it is your job to help the team succeed. When the team does a good job, it means you are doing a good job. Here are 5 functions or ways to build good teams, thus building yourself to be a good manager.
1) Trust your people under you and help them to trust you.
2) Give good honest feedback and be willing to take feedback.
3) Make a committment to your team to help them in any way you can and they will committ to do all they can to help you succeed.
4) Hold your team accountable for their actions, not only for the bad actions but for the good ones too. Allow the people to hold you accountable for the same.
5) Never put yourself above the team! Even though you are the leader of the team, don't ever think that you are beyond the team. Such attitudes have only destroyed departments.
by liquidxit2
I was in your situation a few months ago (except I was the only IT proffesional). I would agree, if they already have a situation the worst thing you can do as the "new guy" is come in and tear it all up. Learn from them and gain trust. Work with them to "improve" how things work, and from thioer slowly gain control.
I on the other hand was thrown into a a mangerial position on a domain setup by a complete moron. So I had to dig deep and get my hands dirty the first day. But at my last job thats how I gained trust of the end users and IT staff.
hi,
I am working as a desktop/IT-Support engineer in an MNC.But I am not happy with the offer given by the company.The company made me as a billable resource to the client and giving me 1/4 th of the amount.IS this a good approach???
Please sent your comments
by jaqui
do nothing but learn the entire system.
how it works, where it doesn't.
document it.
after you have every bit of what's happening detailed, and seen how the people in the office work with it, then plan to fix any problem areas.
researching the system, 1-3 months
planning alterations, 2-4 months
implementing alterations 3-6 months.
rushing in and changing anything other than admin passwords and you name on your office / desk is not something to consider doing.
by mross01
As an IT Manager that has been there a few times already, don't only concentrate on IT issues. You have a small group so this is not as important, but for those of you coming into a larger group or have a larger group, watch the people dynamics.
I make sure that I know who works well together and can get things done. Larger groups are difficult enough to people manage, save yourself some headaches by putting people together who won't create more problems for you.
Excellent advice on "don't do anything" the first month. Make sure people realize you are interested in the system, but don't overload them with questions. For some reason IT worker bees get the impression that you know nothing if you ask to many questions.
Move slowly on changes, get buy in from the team the best you can. Include them in the change process, get their input. You are still the final say, but if you get the natural leader behind you things will be much easier (identifing this person is part of the watching the people interaction process). Explain your decision - COMMUNICATE, don't just make decisions and leave everyone in the dark. You'll find this is harder to do than it sounds, because sharing to much can get you in trouble with upper management, to little and your team will think you are autocratic.
Obviously I have a lot to say on this, considered writing a book just for this situation. I've seen to many people fail at the beginning, there is a completely different rules that apply later, once you are established. Management gives you a honeymoon period and then things change.
Contact me if you would like more input, I've been considered a very good manager by my teams, but I still make mistakes (LEARN FROM THEM).
I don't necessarily agree with getting up someone's nose - remember these people talk and a cancer can spread quickly and its difficult to recover from.
by lcm man
As a new Manager in my IT epartment (and the company), I took the initial direction from my new Manager and jumped right into making the changes we had discuss post interview and pre-start date (about a week). Now, the interesting thing here is, the changes that I implemented are what the IT staff had been requesting for at least a year prior to my arrival (the reason the old IT Manager is no longer here, procrastination).
However, I failed at taking the time to first, get to know my staff on a more professional level, second, understand the dynamics of the three different teams, and third, get the proper buy-in from the staff for the changes I was tasked with completing. I was the bull in the china shop.
It took me nearly a year to repair all that damage I had caused and to ease the friction between me and my employees.
mross011 is right on the money. Listen, learn and get involved. Get input from your staff. Make them feel just how important they are and they will give you their best.
by naser
Hi mross011,
It's really valuable advice, how can i contact you, can you post us your email?
I don't know if this is possible here, and it's not against the policy
Please let me know.
Best regards,
Naser
by jaqui
I've been in the situation of becomeing part of an existing team, as the leader. It isn't easy to integrate yourself without making mistakes, or stepping on people's toes.
My benefit in this area is that I use a flat management style. where someone excels at the duties, I let them have the responsibility of running the show for that area.
All team members get the credit when they do well,
all team members get the blame when they screw up.
I take the responsibility for the screwups.
[ with my boss / upper management ]
I've found that once the team learns you'll not steal credit, and you'll share the blame instead of letting them take the fall, they tend to bend over backwards to do things right, and work with you.
This also has the benefit of teaching the entire team the skills needed for management of a team. Which most realise is a boost for thier career in the long term.
I know a lot of people who think that the flat management style reduces thier authority, but I have found that it doesn't, it increases the flexibility of the entire team, reducing response times and increasing effectiveness.
I also partner people with someone they will learn from, so they work together quite often, then rotate the partners until the entire team has been pushed into learning as much as they can about each aspect from someone who is great at that aspect, as well, they learn who to turn to in the team when they need help with any problem to get the best resolution of it.
I am the Policy Maker currently for my it work, as a small business / sub-contractor, so while I don't have a team I work with all the time, I do constantly have to work with Teams I don't know very well. I have learned how to get them to work with me and give me thyier in depth knowledge to benefit the peroject, rather than have them fighting having an "outsider" that was called in.
by jdmercha
by madcow9597
by todder
I think there are a lot of posts that touch on this endeavor, but I would like to make it THE KEY process for going into a new management situation.
You were hired to manage a department and in order to do so effectively, you must gather information to know what circumstances you have been dealt with. I would gather the following information:
User/Employee feedback - Setup up a simple, anonymous survey that surveys your employees and end-users to see where service issues reside (users) and where the previous manager went astray (employees.)
Read the performance evaluations of your employees and look for their strengths, weaknesses, comments etc...
Do one-on-one interviews with your employees to get to know them better. Make it very informal, but take what they say very seriously.
Ask for a copy of all departmental documentation (i.e network, policy, procedural, change management.) If it doesn't exist, or is antiquated, this will tell you volumes!
Compile a current vendor list and contract terms.
Find out if there are any outstanding projects and get the current status on them.
Talk to your supervisors and determine, if possible, any functions they are wishing to see done better and what their expectations may be for the short and long-term.
I'm sure I have overlooked some items, but the general gist is to gather information like a squirrel gathers nuts. We are in IT and without the proper information you will be lost.
After you have compiled and absorbed this information, you will be much better suited to manage your team and make a dramatic difference.
by todder
I think there are a lot of posts that touch on this endeavor, but I would like to make it THE KEY process for going into a new management situation.
You were hired to manage a department and in order to do so effectively, you must gather information to know what circumstances you have been dealt with. I would gather the following information:
User/Employee feedback - Setup up a simple, anonymous survey that surveys your employees and end-users to see where service issues reside (users) and where the previous manager went astray (employees.)
Read the performance evaluations of your employees and look for their strengths, weaknesses, comments etc...
Do one-on-one interviews with your employees to get to know them better. Make it very informal, but take what they say very seriously.
Ask for a copy of all departmental documentation (i.e network, policy, procedural, change management.) If it doesn't exist, or is antiquated, this will tell you volumes!
Compile a current vendor list and contract terms.
Find out if there are any outstanding projects and get the current status on them.
Talk to your supervisors and determine, if possible, any functions they are wishing to see done better and what their expectations may be for the short and long-term.
I'm sure I have overlooked some items, but the general gist is to gather information like a squirrel gathers nuts. We are in IT and without the proper information you will be lost.
After you have compiled and absorbed this information, you will be much better suited to manage your team and make a dramatic difference.
by jerry pett
You should not look to change anything. Just to understand. Ask what, when, where, who and most importantly why. The best changes comes from looking to understand rather than looking to make changes.
Good luck!
by rjami
That great, and you are going to deal with 2 persons but remember to deal with their EI(Emotional Intelligence) and make yourself comfortable with them, if anything that you need to do in all this one month, that is only to make a soft corner in their Emotional Intelligence(Quotient) for you.
best wishes
-Ravikanth
by waheed
by rakheshrao
Ideally you would do what everyone has said but sometimes you may not have the time to.
However what you should really do is (Etched in stone if possible) not make any changes in the first 3 months! You are learning about your team and they are learning about you. If you make any changes to quickly it could make the team extremely defensive and create more problems for you later.
Know the politics otherwise you could be dead even before you started!
by mike_curtis
The best advice (in my opinion) is getting to know the people. Start with you staff but do not take to long before going out to the people in the company.
Get around! If you are seen to be out there you will quickly get to understand what needs to change or be improved within the IT area of responsibility, this in turn will help you deliver what is required to the company.
Base line you staff. get them to fill out a skills matrix - this is a great way of developing training and ensures you have the staff with the correct skills to deliver what's required.
Do not promise the world! Be realistic with what you agree to do. Go back to basics.
Last of all enjoy it!
by ou jipi je
Getting your staff to fill out skill matrix in your first month can get people killed :-)
Remember you should "fill in" _your_ skill matrix before you ask anything specific from your staff. Be smart. By "fill in" I mean - show that you are worthed your position first, before asking anyone to take an action. Read my other post here.
by mike_curtis
I disagree it is in no way wrong to understand what skills you staff have! The earlier you know exactly what skill sets you have the better! You know what assumptions make?
In my experience giving staff the opportunity to fill in a skills matrix not only gives you great info but also helps the staff know that you are interested in them right from the start. Their skills are synonymous with yours! In that they are the doer?s in your department.
Understand what they can do for you and what you can do for them! Build trust and communications with your staff; gain their respect it can only be gained by actions not commanded.
I agree with mike to an extent, you need this information early on to prevent you from asking too much from them. It is about how you ask for it. Rather than the formality of a "skills matrix"
I prefer an informal chat 1 to 1, explaining why you are asking often helps. This info is vital to make the most of your team and provide the best level of service to users. Hell i have once fired a techie in my first week because he was not upto the job & a liability!
by stephans
Identify top 5 headaches that your team face and see if you can attain some quick wins to build credibility and rapport with your new team.
Otherwise Jaqui's advice is good shaping your new role and developing any change initiatives.
by glyn
StephanS has this nailed. Most other comments are right too. However, you are only new once, you're in a uniqe period where people will be watching you to see what you are made of. Some will give you the benefit of the doubt, others will want to scupper you from the off. Find one of these quick wins Stepan talks about and implemet it in the style you want to set for the rest of your tenure. But do it soon, the hneymoon factor will mean you get to do it; once you've been there for six months you loose the momentum a new manager brings. The time for change is not today, but its gone in six months if you haven't done anything by then...
Good luck
by ou jipi je
1. Make sure that you are fully informed and you understand the goals set forth by senior management.
2. Learn about the history of the department. Try to learn about past successes/ caveats.
3. Take out your team for a dinner. Learn how they see the status of things and what they expect from you. A question: "What do you expect from a good management?" is a good way to start. Introduce yourself - don't stick behind and wait - make sure you introduce yourself properly. Learn what people do, how they see the company and compare for yourself vision and goals of your staff and vision of senior management.
4. Mention the way you operate - in many organizations people are used to work one specific way - many times when you try to change things you will meet "walls of resistance". 1|2|3 should give you enough information to reckognise whether this is a case at your new job.
5. Ask senior management about your team on individual basis and combine it with step 3. Perform a first "light" assesment of your staff only FYI, for now.
6. Money. Being manager is about the money (but you know that) - Ask questions regarding how does the internal finance flow looks like.
7. Where does the organization want to be in 3 years? ..You need to understand the vision, asses it and eventually come up with a plan.
8. A lot for your first month? Your first month defines your career at new company. I don't want to stress you out but it is true. Remember that you will be assessed by your staff more that you will assess anything yourself. You fail getting your (initial) respect and you can pack it up. Also find out if there are internal management HRM procedures. If there are, learn them by heart.
9. Don't promise anything - you promise anything in your first month and you will be hanging yourself....remember - road to hell is paved with good intentions...be smart.
Best piece of advice I've seen in years!
Fantastic insight. Couldn't agree more with Lardo.
by smrizwan
Get familiar with business
- Business Objective
- Business Process
- Revenue generation
- Expenses
Get the expectation right
- Senior Management
- Customers/Clients
Win People
- Meet subordinates and colleagues
- Meet key partners
- Make people feel secure
Risk Identification
- Determine risks & impacts
- Identify possible mitigation
Determine quickwins
- Quantify risks and benefits
- Determine cost of implementation
- Report resentation
by smrizwan
Get familiar with business
- Business Objective
- Business Process
- Revenue generation
- Expenses
Get the expectation right
- Senior Management
- Customers/Clients
Win People
- Meet subordinates and colleagues
- Meet key partners
- Make people feel secure
Risk Identification
- Determine risks & impacts
- Identify possible mitigation
Determine quickwins
- Quantify risks and benefits
- Determine cost of implementation
- Report presentation
by andrewv
Since our new CIO arrived there has been chaos. Making promises and not keeping them, failing to commit to anything, assuming everyone is very stupid, over sensitive to what people have to say about the IT department, not sticking up for staff.
My advice: go slowly, get to know the people and build relationships. There is plenty of time for technical bits later. Keep your word, and if you don't know something, say so.
by ou jipi je
I stand behind that performing any sort of staff assesment in your _first month_ as an IT manager is a bad idea. Just for an example, they might have performed one three weeks ago...assuming that you never bothered to find out it is easy to make a fool out of yourself. Or they perform one at every year that is a part of their yearly appraisal.
"Does this new guy thinks that he knows it all?" -- you will not gain any trust by showing your incompetence in your first month on the job ;-)
by welshbilly
I would be immediately suspicious if a new manager asked me to fill in a skills matrix in their first month.
I would feel better about filling one out once I had got to know them and trusted them.
by gprinsloo
Thats the first question. If it was poor performance top management should be able to indicate.
If it was due to them not being ablt to control their staff or the same just dont have the abilities such assesments WILL be a disaster. You may even have staff who believe they should have been promoted and were not. I agree a NO NO to assesments.
To investigate and establish the worth of each is a must but not in such a manner.
Rather take an existing situation or project and have a brain-storming workshop and let them do the talking to access who gets involved, the talkers, the do-ers, the thinkers and lastly but most importantly the ones who "idle but survive" those are your danger kids on the block. They will hang you in a day.
by she geek
I came on board 18 months ago.... and there wasn't time to "ease" into it. The network was a mess... the workstations all had public static Ip's, no firewall, no anti virus, everyone was an admin of the network. The average down time was 25%. Not to mention No IT staff.
With that said... if I had it to do over. I would start with understanding what you've got, where it is and how it works. A full systems audit, hands on sitting at the desktop talking to each user would be ideal. Get to know them and let them get to know you.
Spend time with you're staff.... if they've been there a while let them steer.... see how they handle the day to day.
Most of all.... ask questions. Here and at work. Let someone else's experience save you the pain of making mistakes.
Best of luck!
by talentonloan
I think an assessment is necessary - but maybe not in a formal way. Maybe more of asking what you do, what you can do, what you can do well (in your own opinion), what you want to do, what you don't like to do, what you were expecting to do but were never allowed to do, etc. Without making it sound like an Inquisition. In fact, many people would like the chance to speak about their skill set and their personal growth goals. It might be written down in a review somewhere, but there is nothing like getting it first hand.
tol
by iam4it4256
Here's a TechRepublic article written by a seasoned IT Manager that gives some good tips on what to do in those first 30 days:
https://www.techrepublic.com.com/5100-10878_11-1048878.html
by cedrics
Im waiting on an internal inteview for a management position for our hotline. Basically retailers call us when they have problems with our lottery terminals to cancel tickets or get basic help ( mainly a reboot or a PW reminder) or to report hardware issues that we then dispatch.
I moved in to system operations 7.5 months ago and have been working on the 'behind the scenes' stuff-overnight backups of the system, office PC maintenance, financial report tracking, and other stuff. I worked 6 on hotline when I started, got a .50 cent raise and moved into Ops when it bacame available, and when our company got a contract in another state the current hotline manager left for that one.
I know the other three people internally applying, the overall manager for customer service knows all of us-he interviewed all of us and we worked with he and the former lower manager on a daily basis. Office is about 50 people. I worked with all of the applicants and so know a lot about them and vice versa-the position has only been posted internally.
Is it different when you : know all the people you are interviewing against, they know you, you know their job and the one related to theirs ( behind the scenes Ops) and are friends/friendly with all others? I dont' think it will be easy to interview in any case, but I know I have more small team management experience from another job and military service. How do all of you handle being placed in a position (potentially) when you know the good and bad alreay of the people beneath you due to personal experience? It would be a team of 6 overall.
CAS
by jaqui
this is easier for a new manager.
1) you know the company and staff
2) you know the network and systems, where problems [ potential or actual ] are.
3) your Team knows you and will already have some respect for you.
4) the team will be happier at an internal promotion than an external hire, it bodes weill for thier career opportunities
in this situation you can start drawing up the plans for changes needed to resolve issues right away, with minimal resistance to them from both Management and the team.
I would still wait for a month before implementing and changes, and do a review of the entire system during that month, as well as work on building the rapport with the team.
by kj7gs
by keithmt
I've been here a few times myself and here's what I've done. First, talk to your staff and ask "what do we do well?", "what don't we do that we should?", what can we do better?". Second, get a good understanding of the environment you're now responsible for; technical/systems/budgets/people. Third, get out to the business and ask them the same questions above that you asked your department.
From this you should find some common threads that really hack people off (hopefully some the same for IT and the business). After a month to six weeks, look for the easy stuff you can fix that will have a real impact. I've yet to find an environment that doesn't have something you can change easily which can make a real difference. Don't under-estimate the power of your "honeymoon period". In the first 6 weeks you can get away with some things which will be harder later-on, so if something is hacking your guys off you should be able to wave a magic wand and build some early credibility.
by sys-arch
When looking for things to improve, I'd look for two winners: one that will help your department's standing in the company and one that will help your staff. As mentioned elsewhere, it's VERY important to spend time with folks outside your department learning who the players are and who has upper management's ear. After all, YOUR job depends upon meeting management's expectations. So.. you better ferret out what those are AND whose expectations count most! It does no good to satisfy someone that isn't listened to up the chain.
An example: in a previous job our department reported to the CFO, but the V.P. of sales had the greatest pull with the CEO and budget. (Took a little while to figure this out.) So... we worked hard on a project to improve sales and improve the company's relationships with its distributors. CFO saw the benefit, sales got the reward, and we shined because the CEO was pleased with the results. Made it much easier to go after projects later since we had already proved that we could deliver.
Gaining good graces with the department, we also worked to automate some system reporting that was driving the IT dept. crazy. We'd generate literally boxes of paper a day worth of prinout for a certain department that only used one or two pieces of information off each page. When we found out what the customer really was using, we were able to generate a file with this information that we could import into a spreadsheet for the user. Again, good brownie points for the department AND good morale booster within the dept. Department learned that manager was willing to go to bat for the employees, fighting the "always done it that way" mentality. That gave manager credibility within dept.; made it easier the next time he asked for something that required a little stretch on the employees' part.
I'd also add that your honeymoon period is often up to six months. But you better make it clear around month three that you have identified some areas for improvement and will be presenting an assessment in the next few weeks.
This is also a time to ask about setting up a round table / off-site discussion with other executives to discuss how they feel IT is supporting the company and their departments. (Is IT aligned with business need???) However, if only one or two executives carry most weight, better to meet just with them. Off-site meetings/events/golf outings/etc. are usually best, somewhere that people can speak a little more freely. Then you can begin discussing road maps and budgets.
by volp14
I've been an IT manager for about 8 years My advice to you would be to establish yourself and your leadership/management style with your team. You will learn that there is nothing you will need more than their support and confidence. Credibility is also important, and communicating with the team in the first month is crucial. Let them know your role and how you will support them. Make sure you understand their jobs and what they do on a daily basis, and help them come up with ideas that may make their lives easier. At the same time, you now have reporting responsibilities to upper management, so the things you do to enhance the operations and efficiencies of your staff should be regularly communicated to the folks you report to.
Remember one thing, you are not successful without the folks that report to you. If they do not perform well, then that is upper managements perception of your team.
Good luck to you.
by dbolte
Here's two of my favorites:
Seek first to understand and then to be understood.
People don't care how much you know until they know how much you care.
by rmarkel
by rita-eileen
A long term vision -- take the first 3-6 months to thoroughly learn what is expected of you and your team - intuitively, and then, the next 3-6 months to learn who impacts you, your team and your objectives. The first three months are traditionally the honeymoon. If you can successfully connect new faces with names and jobs... you're good. (Of course, that all depends on the size of the organization, I realize.)
Congratulations and good luck.
Enjoy it.
The honymoon period gives you margin for error, and time to think. Use it to find out how IT is percieved, who dislikes it the most, what your crew is able to do, what the company needs by priority.
priority 1. basic infrastructure...networks, desktops, backroom systems. keep them running. plan to fix holes after honeymoon.
priority 2. improve.
priority 3. add new capability.
If you are missing skills for priority 1. fix that right away, if not, be glad and plan to train and mentor for pri 2 and 3 after honeymoon.
Alway keep an eye on the "whiners", those who dislike IT, and will give you little slack. Those are the ones you have to give the "extra" attention too, when you least want to. If you dont, you will suffer.
by afranquesa
To me, the first thing is to know the mission of the company and then, how your job will contribute to achieve it. You have to align your effort to your objectives. Write down the objetives, politics and plan to perform them. Check which company resources are availabe to you to easy your tasks.
And then, as said by other members, learn and listen. Write down questions it may appear and ask them in a face2face meetings.
Good luck.
by it-why me?
What about Bob "Baby Steps"
Take it slow, learn the environment and the lay of the land. Understand your people. Support them and they will support you.
Take the time to learn from them and they will learn from you.
Understand your expectations from upper management and try to ascertain any pre-conceived notions about the people you have working for you. They may think they need to go and you are the one to do it. On the other hand, get to know your people and their side of the story, learn them both before you get caught in the middle of something you don't want to be in.
Good Luck!
by mross01
mross011@hotmail.com
I hope this does not break policies. I've been where you are and I would risk breaking a policy to help one person not make the mistakes I have made. On the other hand, I believe I have made good decisions too.
BTW, get in good with your boss and maybe even his. Find out how the reporting structure works, should you only go to your boss or if going to his boss would be ok or step on your bosses toes.
There are do many dynamics to management and its really hard to make the transission to Management from a technical background. Most techies don't suceed well doing this.
Don't forget one thing, eventually you have to do the reviews with those people you manage.
One mistake I did make in one of my first management stints was trying to be best friends with my employees. When I finally asked them to do something they would just laugh. Its a fine line. Its good to be friends and show you care about them and their families.
Oh I could go on and on. But I'll stop for now.
Contact me if you wish and good luck.
Marc
by wongfreeman
I am in the same situation where i am about to start my new job in a similar role for a small company in the medical imaging sector.
My plan is to spend the inital week or so to get my ahead around the products we provide and support and how IS sits within the company. Then I am going to spend some time with all the staff and understand each of their roles and functionalities with the organisation.
By then I am hoping to have a clear view of the goals and objectives of the IS department and its involvment at the business strategy level. And should be able to start making plans and new objectives in the area that needs improvement.
by wongfreeman
I am in the same situation where i am about to start my new job in a similar role for a small company in the medical imaging sector.
My plan is to spend the inital week or so to get my ahead around the products we provide and support and how IS sits within the company. Then I am going to spend some time with all the staff and understand each of their roles and functionalities with the organisation.
By then I am hoping to have a clear view of the goals and objectives of the IS department and its involvment at the business strategy level. And should be able to start making plans and new objectives in the area that needs improvement.
This process should take upto about first 3-6 months. Changes should only be introduced after careful consideration and all their assoiciated implications have been covered.
by mkanaan
by kzin1
Give your staff a reporters jotter pad and ask them to write down
everything they do for 1 week. Example
08:30 arrived at work
08:40 coffee
09:00 check backup logs
10:00 take support call from ...
etc
Be clear with them that they have to be honest, tell them that
being dishonest will be a bad way to start a new way forward,
explain that by them documenting everything for 1 week it will
help you and them to understand what happens and what you
need to do to help them develop and grow in there careers.
Yes - make them successful and you will be too!
Throughout the week ask them how is the logging going...
At the end of the week sit down with them and ask them to talk
through what there week consisted of, ask them what they
learn't from the excercise and ask them what should we do to
improve, put this goals on your new 90 day plan.
In the mean time you should interview your customers, ask them
how the feel about the service you provide, look for objective
sponsors not moaners as they will always moan..
david
by nancy.frank
I have been a member of teams that were "studied" and I will say two things:
1. The staff is going to busy doing their JOB!! Time to do this type of monitoring is really nothng more than a PITA.
2. No better way to get the title of MICRO-manager faster than this!
My 2 cents.
by jamesrl
This is definately putting the wrong foot forward. I agree with Nancy this is micromanagement and sends the absolute wrong singnal.
I started a couple of jobs where I sat down with each employee, asked them about themsleves, about the job they were doing - what did they like about it, what didn't they like about it. Ask them about the department, what works, what doesn't work. Ask the same thing of your new boss. Pretty soon patterns will emerge and you will find out what you need to work on.
James
by 3kl
by kzin1
I've done this excercise loads of times, I've grown companies from nothing to multimillion dollar businesses and I've promoted those people i met on day one to leaders and sometimes to be my boss. So I strongly disagree with your understanding,. Its a matter of selling, often organisations are overworked and under appreciated. How can you help them if you have no idea what they do. If the staff don't want to do it then there is no point and I wouldn't thrust it on them but if it is sold from a fun point of view at the end of the week we sit round the table throw the notebooks in the bin (yes i do not even read them and sometimes for fun set fire to them YES!) and ask each other what did we learn. So often people of got issues or need support to get things out in the open. Look I'm not saying you do this every time it depends on the people the atmosphere and the pressures however for sure in a case of a stretched IT support group it can if done correctly be a tool to help the staff take some time out to think about what they are doing rather than runnning round like headless chickens., Sure you can observe all you like but if they don't get it they never will.
And finally, the worst person to perform such a role is a consultant - no wonder they revolted.
by tfitzpatrick
The suggestion of having the team document their activities suggests that Management does not trust them. Before making this suggestion, try and put yourself in their shoes. Write down everything you do in a day and then see how useful the information is.
Most employees who are asked to document their day will either a)lie to cover up what they are really doing, b)exagerate their duties to appear more valuable, or c)revolt against the whole idea and start looking for new work.
In my opinion, asking them to 'diarize' their day is a huge mistake.
by jcritch
First Rule, engage you ears, then your mind before your mouth.
In every MGR position I held, I was given a set of goals/milestones my boss wanted accomplished. In one instance, I needed to determine if outsourcing the Help Desk was feasible. Another was to build a IT department from the ground up. In each instance, any and all outsourced labor was replaced by full time employees.
You need to remember what you job description is, verify the rules of engagement. If you do not have any direction, ask for it. Then follow your marching orders. Very difficult to answer what is best for you in your situation since we do not know what processes your are attempting to manage.
For me, I do not change anything in the first 45-90 days unless I am forced to due to dead weight on a team, strategic direction, or business mandates. After 180 days, I give every direct report a evaluation (for myself only). I then review how my evaluation differs or agrees with past evaluations. I never open a personnel file less then 180 days on the job unless I need to due to conduct, performance or behavior issues.
In most instances, I find being a new manager allows those who have been suppressed to reinvigorate themselves, those who have been leaders to continue to lead and those who have been skirting by to either fall face down or realign themselves with present processes.
Good luck, keep you eyes open, but most of all listen, think, listen again and then react
by amcol
I'm afraid you're going to need it.
I have nothing to add...many of the previous posts have offered fine advice.
One of the common ideas throughout all the posts is to listen and ask questions. You started this thread a week and a half ago, yet you've not re-engaged once. Do you have no questions at all for any of the posters? Do you understand every single thing everyone has said?
Part of being a great manager is making excellent use of all your resources. You're wasting this one.
I concur with good teamwork as one of the cornerstone of any success.
I like to add that this is probably the time to observe and listen to people. Build rapport with your team. Understand their strengths and weaknesses, what drives them.
Let them know you as well. Communicate your management style and your beliefs in what it takes to be successful. Communication is two ways.
by sifontese
by janicew
Most of the advice here has been really good. It is important to spend a lot of time learning (both from your team and from senior management), listen a lot, and not make too many changes too fast...USUALLY!
However, I encourage you to pay the most attention to what your team is saying. Sometimes what they want is change - NOW! The "quick wins" mentioned by another poster are a great idea. When I started this job as a manager, I entered in with the watch, look and listen attitude. But it became very obvious to me that the staff was actually looking for some changes. They wanted decisions made about things that had not been going well for some time. What it really comes down to then is getting to know your people and not being afraid to make decisions or changes if that seems like the thing that's needed.
Was the last person in the position successful? Then you most likely will need to spend some time learning and watching and not changing. If the last manager left staff feeling frustrated and wanting more, than you may need to implement some "quick win" changes much sooner.
The other piece of advice I would add is to find yourself a mentor in the organization and perhaps one out of the organization as well. Find someone willing to guide you through the new cultural climate, practices and issues that you are stepping into. Find someone you can discuss things with honestly and who will provide you good advice. If you have someone outside of the organization that's at least a sounding board for those hard issues, but be sure to find someone to help you understand how things "really" work in your new organization as well.
by fredbrillo
There are 2 avenues of approach....and I liken them to the days of the Vietnam war....
Approach 1....
The new 1st Leutenant shows up and immediately starts giving orders on how he wants the battles to be carried out....before long...all of his men are either dead or ready to kill him.
Approach 2....
The new 1st Leutenant shows up and quietly asks the top sergeant to keep him out of trouble for the first 60 days and everyone will be better off.
Your choice which one to be!
by itinstructor
by the admiral
Resistance is not futile.
You have to resist the urge to fix problems at the technical level and allow the technicians to perform the repairs. Your job is to handle the department problems, personal conflicts, customer complaints, and investigate problems.
You can get to know your people by having them come to a lunch and ask them questions about their personal life, or if you are scared they will get suspicious, have a meeting to introduce yourself and tell them about your history.
Then ask them what processes are followed and how loosely they are followed. Then lead them into a story about how you had to do this one process that took forever and you missed your kids birthday/birth/ or something special that you missed (to show that you are dedicated) from there you can degrade into a discussion at the personal level to get to know them better.
There are five leadership methods: Telling, Selling, Consulting, Deligating, and Joining. I never thought consulting was a leadership style, basically because you can not lead by consortum. You can figure out which one fits for each person. Some people like to be told what to do, and others need to be convinced (selling) that it is the best way to do a certain thing.
But never get involved in the technical aspects. That part of your career is done, when moving on don't forget where you came from, but don't look back.
by 3kl
First off, I said that I WAS a consultant. That was several years ago. If you notice my profile, I am not a systems engineer. I will not (and never will) argue that consultants are a fix-all. In house management needs to handle their business. Consultants are great for certain roles, however they are overused in technology today.
Now, to the meat of the response. The situation you descibe in the second comment sounds like it makes sense. I was merely relaying my experience. I never claimed to be a management expert. What, in my opinion (from the employee point of view) is important is that it is not forced upon them. Nothing will make we the employee angry more than a new guy forcing his platform upon us.
by kzin1
I've been a technical director in various companies for almost all of my 30 year career in IT. And I've hardly ever used any of the aforementioned "techniques", although I'm aware of most of them. So here's my alternative two-cents ...
1. Almost all techies are self-starting, highly-motivated people. Nothing turns them on more than doing a great job of allotted tasks. And nothing turns them off more than being messed around so they can't do their job.
2. You are *their* tool, not the other way round. Your job is to protect them from all the crap things that stop them doing their jobs. This comes in all sorts of shapes and sizes. You stop the CEO complaining when they turn up at mid-day, and make sure he understands that they were there until 5am the previous night. You fill the coffee machine, and you buy the apple pies. You make sure that they have fast PCs with enough RAM, and a decent high-resolution monitor. And the best software tools that money or effort can procure.
3. A major part of your job is communication. From everyone, to everyone. If your team knows exactly what the task is, and what the real deadlines are, and why, they'll work with you to make things happen (or they'll tell you why it can't be done -- in which case, you *listen*, and react). In the other direction, you make sure your management knows what's going on, so they don't have any nasty surprises. Don't forget talking to the users too. If your product is for selling, make sure you drink with the salesmen -- find out what they think the customer wants, and help them to understand what can and can't be done with the current developments. If your team ends up trying to deliver against an over-optimistic spec, it's *your* fault! N-way communications, all the time!
4. Make sure you have the information to know how things actually are going. Mostly that's being there and in touch with your team, but part of it is putting in the tools, and using them, to make sure that everyone knows how things are progressing. MS Project is not a bad high-level tool, a bug-tracking tool like RT is also useful. But you either use these things secretly for your own use, or you use them as a team, because *as a team* you agree that they will help to make life easier for everyone. Remember rule 2!!
5. Managing two people is not a mangement job at all. At least you must never think of it that way! You will end up doing some of the sharp-end work, for sure -- and make sure the bits you take on are the crap bits that everyone else hates the thought of doing, not the fun sexy bits that everyone wants to get their hands on.
That's a flavour of how I've always done my job, anyway. And it's always been a heck of a lot of fun. Which, in the end, is what it's really all about! I hope you have fun too!
by harrison67
Assuming that your know the Logistics business, and understand your departments Goals, Project and Workload.
I would have a one-on-one with each of my team members to find out: (1) How do they see themselves as members on the team. (2) What are their goals (3) What are their strengths and weaknesses. (4) What are their likes and dislikes
(5) Find out what you can do as a Manager to make their work day a more enjoyable adventure.
From the above conversation, you will walk away knowing who can perform any given task. You would know your resources, and if there is a need for additional resources.
There are good points made by a number of those who posted, on both sides of this topic -Observing and Taking Action.
What is really key in the first 30-90 days (length depends on organizational culture and team size) is to achieve a level of balance between observation, research (doing your homework on process, practice, etc.. which is documented) and action. If you appear to be idle for a long time (observing but no action or interaction) then you run the risk of setting a passive management expectation, while on the other hand you fail to observe, research and just begin to act you run the risk of setting a "do it thier own way" expectation. Niether of these expectations, whether real or percieved; translate to effective teamwork. In Summary within the first 30-90 days strive to achieve balance between observation and action, balance is a key performance indicator in effective high performance teams.
by tfitzpatrick
I agree 100% with JaredH. I have followed these simple rules in my Management role and they all hold true. I especially like number 4. I make it a point to empower the members of my team and let them make decisions on their own, based on their own experience. I am always there to throw them a lifeline if needed and would NEVER let them hang out to dry. By empowering them to make their own decisions, they are more likely to learn from their mistakes. Just be sure you have their backs at all times. As their Manager, that is part of your job.
One last thing, nobody likes to be micro-managed. You will need to find out whatever you can about each member of your team, but do not hover over them and watch them too closely.
Good luck.
by the ref
First up, I am a Software Development Manager who has worked with teams of two to twenty odd staff. I expect all my staff to have a personal workbook which they use as part of their work - and yes, I do it myself. The workbook is the property of the staff member, and is used to improve the way they work. Look into the PSP (Personal Software Process) by Watts Humphrey.
It also pays off for estimating - just lookup the last time you did a similar task. People always forget and underestimate how long things really take.
Using this has paid off so many times it is not possible to count. I take meeting notes on every ad hoc meeting, record how long it takes me to do things, and use it to improve the way I perform. It is invaluable when issues arise later and I can flick back to my meeting notes and read from them the outcome I recorded. This puts me in a position of strength, where I can justify actions and it diffuses issues that arise through misinterpretation. If I have misinterpreted I can show I did it at the time. If I have my notes and the other person doesn?t, well I am right ;-)
Logging everything such as toilet breaks are a waste of time - however logging interruptions are priceless. When anyone complains they get too many interruptions I ask them to log all disruptions for a week, then we sit together and work out where the disruptions are coming from and a way to prevent them.
When you get in the habit, it does not take any extra time to log what you do, but it does take some getting used to.
by staterh
by darko.jovin
First of all - thank you all for advices!
As you told me - I touched (almost) nothing, just looked and here are some notes I have.
General situation...
First of all - there is absolutely no documentation on anything.
Guys keep it inside their (confused) heads.
I'm forcing them at least to document new things they are working on now, and I will document the rest later.
There was no backup strategy at all, they just randomly preformad manual backups - so my first real acion was to create proper backups.
I also introduced asset management, this was in total mess.
Also there are some issues with licenses (yes, Bill, we will pay $oon).
About software..
It works, but we are not happy with software vendor and they are not happy with us. I had one meeting with them.
Management sometimes has unrealistic wishes for program and programmers sometimes think they know our business better than we do, so there were some conflicts in the past.
In a long term - it would be nice to replace them.
About my team...
As you told me - on my very first day I took them for drink and had a little introduction.
After that we spent few days together on one installation, so we had a chance to get to know each other better.
First one is just young, with no formal IT education, very disorganized, innovative but poor tester so he often creates a lot of overhead work.
I will have to control him more and try to make him more carefull.
The other one is actually former IT manager, he was demoted and I stepped into his position. I was not very happy with that situation, but it apperas that
he is not a bad guy. It's just that IT management is above his abilities.
He is excellent administrator, he built whole system and I would like to keep him.
I was offered to hire 3rd guy, but for now i think we don't need him.
About management...
So far - I think they are friendly and know their jobs, but I think they do not take enough care of me.
I was rejected few times when i wanted to meet them ("sorry, try later, we don't have time now").
Also i still didn't get company car, and we work in poor office (i was promised that will be fixed "soon").
So.. I think I did like 70% of what I have planned. I also did some tings I did not plan to (suport users, but that is good way to know them).
Things I must do ASAP - finish my walk thru all departments, talk to department leaders, try to understand and document processes and find out what can IT do for them. I plan to do it in next 2 weeeks.
One advice for those who may be in my position - keep a log on each important thing you see or do ("dead dragons").
I will help you to consolidate your thoughts and it is proof to your managers that you actually did someting.
Regards,
DJ
by staterh
by czalegowski
by staterh
I agree with you, the saying Jack of all trade
today must be taken positively...we shud say Jack of all trade & master of all. Now, an IT professional has to play multiple roles & knowing the business of the conpany & its function is a must.
by staterh
Hello,
Dont get upset. 1st thing list down all the benefits & exposure you are getting while working on client side. If the experience is good & work environment facilitates your growth then give your complete support to all their requirements. your hard work will definitely be appreciated by the client & they will pass this to your parent company. During that time you can communicate to them reg the pay & remunerations.
This discussion is closed to new replies.
Sort by Trending