What would you do?
-
So i'm keen to know what other people's take on the following situation\discussion I had today has made me think about what im doing, just keen to find out what others think. Background: I joined the company for 18 months as the Group IT Manager that has 5 individual business units, approx 200 users, manage a small IT team, responsible for the IT of $500m turnover pa. Directors wanted someone with a mixed background (management,developer,db,network) all of the skills I have. 2 Months in new Role: Business Unit 1, I identified issues with main system, company was expanding rapidly, systems(software) would not be able to cope, doubt they can do what the company will want. Reported to directors - No action taken 4 Months into new role: Business Unit 1, Directors requested more automated reporting. Investigated and reported that due to issues in the main system could not achieve what they wanted - No action taken. Business unit 3, requests small web api to exchange info between third party. 6 Months into new role: Business Unit 1, Directors fall out, 1 Director is asked to leave, reason: Systems are not what they are led to believe. They decide they need to look at the systems and improve system Action: hire an 'Architect' Business unit 3, I delivered on-time and on budget API project. 7 Months into new role: 'Architect' joins. 8 Months into new Role: 'Architect' reports to Directors that he is getting on well but the system looks to have problems. 9 Months into new Role: 'Architect' reports to Directors that he is getting on well but the system looks to have problems. 10 Months into new Role: 'Architect' reports to Directors that the system is 'bad' and needs overhaul. Directors are surprised (hang on??? I told them this within 2 months). Action: Rebuild. 11 Months into new Role: 'Architect' checks in code, I review and report (as requested) to the Directors that the code is poor, meeting is called 'Architect' agrees with me that for 5 months his work is 's**t", cost so far $80,000.00 for 's**t' Action: Directors do not react... and few days later ask me to no longer be involved in the project, 2nd Developer is taken on 14 Months into new role: 'Architect' misses project deadline 16 Months into new role: Still no delivery 17 Months into new role: Part one delivered, project still in progress Cost: $250,000.00 18 Months into new role Project still being worked on. Business unit 2, requests a new version of web system. Directors request Group IT manager
-
So i'm keen to know what other people's take on the following situation\discussion I had today has made me think about what im doing, just keen to find out what others think. Background: I joined the company for 18 months as the Group IT Manager that has 5 individual business units, approx 200 users, manage a small IT team, responsible for the IT of $500m turnover pa. Directors wanted someone with a mixed background (management,developer,db,network) all of the skills I have. 2 Months in new Role: Business Unit 1, I identified issues with main system, company was expanding rapidly, systems(software) would not be able to cope, doubt they can do what the company will want. Reported to directors - No action taken 4 Months into new role: Business Unit 1, Directors requested more automated reporting. Investigated and reported that due to issues in the main system could not achieve what they wanted - No action taken. Business unit 3, requests small web api to exchange info between third party. 6 Months into new role: Business Unit 1, Directors fall out, 1 Director is asked to leave, reason: Systems are not what they are led to believe. They decide they need to look at the systems and improve system Action: hire an 'Architect' Business unit 3, I delivered on-time and on budget API project. 7 Months into new role: 'Architect' joins. 8 Months into new Role: 'Architect' reports to Directors that he is getting on well but the system looks to have problems. 9 Months into new Role: 'Architect' reports to Directors that he is getting on well but the system looks to have problems. 10 Months into new Role: 'Architect' reports to Directors that the system is 'bad' and needs overhaul. Directors are surprised (hang on??? I told them this within 2 months). Action: Rebuild. 11 Months into new Role: 'Architect' checks in code, I review and report (as requested) to the Directors that the code is poor, meeting is called 'Architect' agrees with me that for 5 months his work is 's**t", cost so far $80,000.00 for 's**t' Action: Directors do not react... and few days later ask me to no longer be involved in the project, 2nd Developer is taken on 14 Months into new role: 'Architect' misses project deadline 16 Months into new role: Still no delivery 17 Months into new role: Part one delivered, project still in progress Cost: $250,000.00 18 Months into new role Project still being worked on. Business unit 2, requests a new version of web system. Directors request Group IT manager
ziwez0 wrote:
Action: Directors do not react... and few days later ask me to no longer be involved in the project, 2nd Developer is taken on
14 Months into new role:Shouldn't this be 3 months into new role? I'd say quit or wait a while, if the money and work is good, until they come begging back to you.
-
So i'm keen to know what other people's take on the following situation\discussion I had today has made me think about what im doing, just keen to find out what others think. Background: I joined the company for 18 months as the Group IT Manager that has 5 individual business units, approx 200 users, manage a small IT team, responsible for the IT of $500m turnover pa. Directors wanted someone with a mixed background (management,developer,db,network) all of the skills I have. 2 Months in new Role: Business Unit 1, I identified issues with main system, company was expanding rapidly, systems(software) would not be able to cope, doubt they can do what the company will want. Reported to directors - No action taken 4 Months into new role: Business Unit 1, Directors requested more automated reporting. Investigated and reported that due to issues in the main system could not achieve what they wanted - No action taken. Business unit 3, requests small web api to exchange info between third party. 6 Months into new role: Business Unit 1, Directors fall out, 1 Director is asked to leave, reason: Systems are not what they are led to believe. They decide they need to look at the systems and improve system Action: hire an 'Architect' Business unit 3, I delivered on-time and on budget API project. 7 Months into new role: 'Architect' joins. 8 Months into new Role: 'Architect' reports to Directors that he is getting on well but the system looks to have problems. 9 Months into new Role: 'Architect' reports to Directors that he is getting on well but the system looks to have problems. 10 Months into new Role: 'Architect' reports to Directors that the system is 'bad' and needs overhaul. Directors are surprised (hang on??? I told them this within 2 months). Action: Rebuild. 11 Months into new Role: 'Architect' checks in code, I review and report (as requested) to the Directors that the code is poor, meeting is called 'Architect' agrees with me that for 5 months his work is 's**t", cost so far $80,000.00 for 's**t' Action: Directors do not react... and few days later ask me to no longer be involved in the project, 2nd Developer is taken on 14 Months into new role: 'Architect' misses project deadline 16 Months into new role: Still no delivery 17 Months into new role: Part one delivered, project still in progress Cost: $250,000.00 18 Months into new role Project still being worked on. Business unit 2, requests a new version of web system. Directors request Group IT manager
IMHO you have no choice, your opinion is not worth shit to the directors, you are looking at a train wreck in action and I suspect, as IT manager, your arse is going to be in a crack. Get out NOW!
Never underestimate the power of human stupidity RAH
-
So i'm keen to know what other people's take on the following situation\discussion I had today has made me think about what im doing, just keen to find out what others think. Background: I joined the company for 18 months as the Group IT Manager that has 5 individual business units, approx 200 users, manage a small IT team, responsible for the IT of $500m turnover pa. Directors wanted someone with a mixed background (management,developer,db,network) all of the skills I have. 2 Months in new Role: Business Unit 1, I identified issues with main system, company was expanding rapidly, systems(software) would not be able to cope, doubt they can do what the company will want. Reported to directors - No action taken 4 Months into new role: Business Unit 1, Directors requested more automated reporting. Investigated and reported that due to issues in the main system could not achieve what they wanted - No action taken. Business unit 3, requests small web api to exchange info between third party. 6 Months into new role: Business Unit 1, Directors fall out, 1 Director is asked to leave, reason: Systems are not what they are led to believe. They decide they need to look at the systems and improve system Action: hire an 'Architect' Business unit 3, I delivered on-time and on budget API project. 7 Months into new role: 'Architect' joins. 8 Months into new Role: 'Architect' reports to Directors that he is getting on well but the system looks to have problems. 9 Months into new Role: 'Architect' reports to Directors that he is getting on well but the system looks to have problems. 10 Months into new Role: 'Architect' reports to Directors that the system is 'bad' and needs overhaul. Directors are surprised (hang on??? I told them this within 2 months). Action: Rebuild. 11 Months into new Role: 'Architect' checks in code, I review and report (as requested) to the Directors that the code is poor, meeting is called 'Architect' agrees with me that for 5 months his work is 's**t", cost so far $80,000.00 for 's**t' Action: Directors do not react... and few days later ask me to no longer be involved in the project, 2nd Developer is taken on 14 Months into new role: 'Architect' misses project deadline 16 Months into new role: Still no delivery 17 Months into new role: Part one delivered, project still in progress Cost: $250,000.00 18 Months into new role Project still being worked on. Business unit 2, requests a new version of web system. Directors request Group IT manager
I'm guessing but: Is the Architect related / friend of/ formerly worked with one or more of the directors? Is the Architect a contractor rather than permanent? If the answer to both of these questions is 'yes' then you're fucked; there's no point even being objective as the architect will have the directors ear outside of meetings where he will persuade them that it's not him, its you. I've been there. I chose to hang around, document everything with emails (cc directors and architect, being exceedingly positive), things like "As I'm not overly familiar with using Access and VB6 to provide a web service, I can't comment on its performance once we ramp up the number of users - perhaps Architect has some performance measurements?" or "Thanks for the design document, Architect, it should be great once it's finished! If you need any help writing the missing sections on security, performance, hardware requirements, licensing costs, cost benefits, etc. please just let me know and perhaps we can work together to get it finished?" I was made redundant, eventually, but had been keeping my eyes out and chose to take a while off before returning to the industry. YMMV
PooperPig - Coming Soon
-
So i'm keen to know what other people's take on the following situation\discussion I had today has made me think about what im doing, just keen to find out what others think. Background: I joined the company for 18 months as the Group IT Manager that has 5 individual business units, approx 200 users, manage a small IT team, responsible for the IT of $500m turnover pa. Directors wanted someone with a mixed background (management,developer,db,network) all of the skills I have. 2 Months in new Role: Business Unit 1, I identified issues with main system, company was expanding rapidly, systems(software) would not be able to cope, doubt they can do what the company will want. Reported to directors - No action taken 4 Months into new role: Business Unit 1, Directors requested more automated reporting. Investigated and reported that due to issues in the main system could not achieve what they wanted - No action taken. Business unit 3, requests small web api to exchange info between third party. 6 Months into new role: Business Unit 1, Directors fall out, 1 Director is asked to leave, reason: Systems are not what they are led to believe. They decide they need to look at the systems and improve system Action: hire an 'Architect' Business unit 3, I delivered on-time and on budget API project. 7 Months into new role: 'Architect' joins. 8 Months into new Role: 'Architect' reports to Directors that he is getting on well but the system looks to have problems. 9 Months into new Role: 'Architect' reports to Directors that he is getting on well but the system looks to have problems. 10 Months into new Role: 'Architect' reports to Directors that the system is 'bad' and needs overhaul. Directors are surprised (hang on??? I told them this within 2 months). Action: Rebuild. 11 Months into new Role: 'Architect' checks in code, I review and report (as requested) to the Directors that the code is poor, meeting is called 'Architect' agrees with me that for 5 months his work is 's**t", cost so far $80,000.00 for 's**t' Action: Directors do not react... and few days later ask me to no longer be involved in the project, 2nd Developer is taken on 14 Months into new role: 'Architect' misses project deadline 16 Months into new role: Still no delivery 17 Months into new role: Part one delivered, project still in progress Cost: $250,000.00 18 Months into new role Project still being worked on. Business unit 2, requests a new version of web system. Directors request Group IT manager
It sounds like you need to get better at building relationships and playing "politics". You haven't figured out how to talk to the directors. One bit of advice that I haven't had a chance to try out is that if you get passed up for something twice, then leave. You've been labeled as someone that should be passed over and that's a hard label to break out of.
Curvature of the Mind now with 3D
-
So i'm keen to know what other people's take on the following situation\discussion I had today has made me think about what im doing, just keen to find out what others think. Background: I joined the company for 18 months as the Group IT Manager that has 5 individual business units, approx 200 users, manage a small IT team, responsible for the IT of $500m turnover pa. Directors wanted someone with a mixed background (management,developer,db,network) all of the skills I have. 2 Months in new Role: Business Unit 1, I identified issues with main system, company was expanding rapidly, systems(software) would not be able to cope, doubt they can do what the company will want. Reported to directors - No action taken 4 Months into new role: Business Unit 1, Directors requested more automated reporting. Investigated and reported that due to issues in the main system could not achieve what they wanted - No action taken. Business unit 3, requests small web api to exchange info between third party. 6 Months into new role: Business Unit 1, Directors fall out, 1 Director is asked to leave, reason: Systems are not what they are led to believe. They decide they need to look at the systems and improve system Action: hire an 'Architect' Business unit 3, I delivered on-time and on budget API project. 7 Months into new role: 'Architect' joins. 8 Months into new Role: 'Architect' reports to Directors that he is getting on well but the system looks to have problems. 9 Months into new Role: 'Architect' reports to Directors that he is getting on well but the system looks to have problems. 10 Months into new Role: 'Architect' reports to Directors that the system is 'bad' and needs overhaul. Directors are surprised (hang on??? I told them this within 2 months). Action: Rebuild. 11 Months into new Role: 'Architect' checks in code, I review and report (as requested) to the Directors that the code is poor, meeting is called 'Architect' agrees with me that for 5 months his work is 's**t", cost so far $80,000.00 for 's**t' Action: Directors do not react... and few days later ask me to no longer be involved in the project, 2nd Developer is taken on 14 Months into new role: 'Architect' misses project deadline 16 Months into new role: Still no delivery 17 Months into new role: Part one delivered, project still in progress Cost: $250,000.00 18 Months into new role Project still being worked on. Business unit 2, requests a new version of web system. Directors request Group IT manager
My advice: - Document everything properly: Your actions, the (missing) actions of your directors etc, so no one can pi** your leg. - Keep doing your job: Invesigate, report, and make sure it reaches the directors - When it comes to "why did this or that fail?" and they ask you - say thing like "As I already said in my report from ..." - See if you find a new job And maybe I can comfort you a bit: You are not alone. This situation is quite usual.
-
So i'm keen to know what other people's take on the following situation\discussion I had today has made me think about what im doing, just keen to find out what others think. Background: I joined the company for 18 months as the Group IT Manager that has 5 individual business units, approx 200 users, manage a small IT team, responsible for the IT of $500m turnover pa. Directors wanted someone with a mixed background (management,developer,db,network) all of the skills I have. 2 Months in new Role: Business Unit 1, I identified issues with main system, company was expanding rapidly, systems(software) would not be able to cope, doubt they can do what the company will want. Reported to directors - No action taken 4 Months into new role: Business Unit 1, Directors requested more automated reporting. Investigated and reported that due to issues in the main system could not achieve what they wanted - No action taken. Business unit 3, requests small web api to exchange info between third party. 6 Months into new role: Business Unit 1, Directors fall out, 1 Director is asked to leave, reason: Systems are not what they are led to believe. They decide they need to look at the systems and improve system Action: hire an 'Architect' Business unit 3, I delivered on-time and on budget API project. 7 Months into new role: 'Architect' joins. 8 Months into new Role: 'Architect' reports to Directors that he is getting on well but the system looks to have problems. 9 Months into new Role: 'Architect' reports to Directors that he is getting on well but the system looks to have problems. 10 Months into new Role: 'Architect' reports to Directors that the system is 'bad' and needs overhaul. Directors are surprised (hang on??? I told them this within 2 months). Action: Rebuild. 11 Months into new Role: 'Architect' checks in code, I review and report (as requested) to the Directors that the code is poor, meeting is called 'Architect' agrees with me that for 5 months his work is 's**t", cost so far $80,000.00 for 's**t' Action: Directors do not react... and few days later ask me to no longer be involved in the project, 2nd Developer is taken on 14 Months into new role: 'Architect' misses project deadline 16 Months into new role: Still no delivery 17 Months into new role: Part one delivered, project still in progress Cost: $250,000.00 18 Months into new role Project still being worked on. Business unit 2, requests a new version of web system. Directors request Group IT manager
Leave as soon as possible.
-
Leave as soon as possible.
-
Check out Maslow's hierarchy of needs. Are you at level 2 or 4 ? They were in business before you came in, they will be after you leave. How long? Do you really care? They don't. Get a life. Cheers Vaclav
I don't really think you need any of that to know when something is fucked because, if you don't, then you are fucked!
-
Check out Maslow's hierarchy of needs. Are you at level 2 or 4 ? They were in business before you came in, they will be after you leave. How long? Do you really care? They don't. Get a life. Cheers Vaclav
Vaclav_Sal wrote:
Get a life.
"Ah, arrogance and stupidity in a single package, how very efficient". So, he must have hit a button with his remark, otherwise you would not be defending that "business". Let me hit your entire keyboard: The fact that a company can do without you does not mean it is a viable business in any way. Is this what you meant with bullying? You might have been on that forum too long - the forum has also gazed into you, by the tone of it. Welcome to CodeProject.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]