What to do when management doesn't consult relevant teams in major projects?
I work for a company that has > 200 employees, and in recent years we've noticed that management hasn't consulted with relevant teams for major projects, resulting in confusion, frustration and extra money spent.
For example in 2016 the company built a new office across town. The leader of the team who would be working there was asked by management about furnishings and gave their requirements, such as longer desks (to accommodate printers or a space for clients to spread out documents). When the building was 3/4 built the team leader asked about the requirements and found many had been changed or denied, such as desk length or shelving. As a result the company had to spend money on end tables, and some people have client meetings in an unused office just to have some more desk space.
In 2017 the company moved from key-based locks to card-based locks. IT was consulted for some of the technical aspects, but only after a system had been decided upon and quotes agreed upon by management. They hadn't considered things like our copiers which would need updating to work with the new format of cards, on top of turnaround times when a visitor came on site (as a keycard would need to be printed for them). The result was a mad rush to buy a new card printer and upgrade our existing copier card scanners.
And two weeks ago we discovered that management had been talking with an external company for the last 6 months to redevelop the company's (in-house) website. Our current webmaster was only informed when someone from the external company called up asking for login details so they could switch the website over, and now there's a mild panic such as will the new site integrate with other systems we've got? Who will maintain the content on the website? questions about why the change was necessary, why wasn't anyone (except management) consulted about it, and so forth.
We've raised this issue with our supervisor a few times, who have raised it with management a few times, but nothing seems to change. Projects keep going and those who are making the decisions don't consider the finer details of the project.
Is there anything we can do to ensure management speak with people before deciding on things? I worry that at some point our customer system will be replaced on a whim by management who sat through a five minute demo at a conference and we'll be struggling to understand why, or keep up.
I'm a firm believer in "let them fall flat on their face", but clearly that hasn't worked.
management projects
New contributor
add a comment |
I work for a company that has > 200 employees, and in recent years we've noticed that management hasn't consulted with relevant teams for major projects, resulting in confusion, frustration and extra money spent.
For example in 2016 the company built a new office across town. The leader of the team who would be working there was asked by management about furnishings and gave their requirements, such as longer desks (to accommodate printers or a space for clients to spread out documents). When the building was 3/4 built the team leader asked about the requirements and found many had been changed or denied, such as desk length or shelving. As a result the company had to spend money on end tables, and some people have client meetings in an unused office just to have some more desk space.
In 2017 the company moved from key-based locks to card-based locks. IT was consulted for some of the technical aspects, but only after a system had been decided upon and quotes agreed upon by management. They hadn't considered things like our copiers which would need updating to work with the new format of cards, on top of turnaround times when a visitor came on site (as a keycard would need to be printed for them). The result was a mad rush to buy a new card printer and upgrade our existing copier card scanners.
And two weeks ago we discovered that management had been talking with an external company for the last 6 months to redevelop the company's (in-house) website. Our current webmaster was only informed when someone from the external company called up asking for login details so they could switch the website over, and now there's a mild panic such as will the new site integrate with other systems we've got? Who will maintain the content on the website? questions about why the change was necessary, why wasn't anyone (except management) consulted about it, and so forth.
We've raised this issue with our supervisor a few times, who have raised it with management a few times, but nothing seems to change. Projects keep going and those who are making the decisions don't consider the finer details of the project.
Is there anything we can do to ensure management speak with people before deciding on things? I worry that at some point our customer system will be replaced on a whim by management who sat through a five minute demo at a conference and we'll be struggling to understand why, or keep up.
I'm a firm believer in "let them fall flat on their face", but clearly that hasn't worked.
management projects
New contributor
add a comment |
I work for a company that has > 200 employees, and in recent years we've noticed that management hasn't consulted with relevant teams for major projects, resulting in confusion, frustration and extra money spent.
For example in 2016 the company built a new office across town. The leader of the team who would be working there was asked by management about furnishings and gave their requirements, such as longer desks (to accommodate printers or a space for clients to spread out documents). When the building was 3/4 built the team leader asked about the requirements and found many had been changed or denied, such as desk length or shelving. As a result the company had to spend money on end tables, and some people have client meetings in an unused office just to have some more desk space.
In 2017 the company moved from key-based locks to card-based locks. IT was consulted for some of the technical aspects, but only after a system had been decided upon and quotes agreed upon by management. They hadn't considered things like our copiers which would need updating to work with the new format of cards, on top of turnaround times when a visitor came on site (as a keycard would need to be printed for them). The result was a mad rush to buy a new card printer and upgrade our existing copier card scanners.
And two weeks ago we discovered that management had been talking with an external company for the last 6 months to redevelop the company's (in-house) website. Our current webmaster was only informed when someone from the external company called up asking for login details so they could switch the website over, and now there's a mild panic such as will the new site integrate with other systems we've got? Who will maintain the content on the website? questions about why the change was necessary, why wasn't anyone (except management) consulted about it, and so forth.
We've raised this issue with our supervisor a few times, who have raised it with management a few times, but nothing seems to change. Projects keep going and those who are making the decisions don't consider the finer details of the project.
Is there anything we can do to ensure management speak with people before deciding on things? I worry that at some point our customer system will be replaced on a whim by management who sat through a five minute demo at a conference and we'll be struggling to understand why, or keep up.
I'm a firm believer in "let them fall flat on their face", but clearly that hasn't worked.
management projects
New contributor
I work for a company that has > 200 employees, and in recent years we've noticed that management hasn't consulted with relevant teams for major projects, resulting in confusion, frustration and extra money spent.
For example in 2016 the company built a new office across town. The leader of the team who would be working there was asked by management about furnishings and gave their requirements, such as longer desks (to accommodate printers or a space for clients to spread out documents). When the building was 3/4 built the team leader asked about the requirements and found many had been changed or denied, such as desk length or shelving. As a result the company had to spend money on end tables, and some people have client meetings in an unused office just to have some more desk space.
In 2017 the company moved from key-based locks to card-based locks. IT was consulted for some of the technical aspects, but only after a system had been decided upon and quotes agreed upon by management. They hadn't considered things like our copiers which would need updating to work with the new format of cards, on top of turnaround times when a visitor came on site (as a keycard would need to be printed for them). The result was a mad rush to buy a new card printer and upgrade our existing copier card scanners.
And two weeks ago we discovered that management had been talking with an external company for the last 6 months to redevelop the company's (in-house) website. Our current webmaster was only informed when someone from the external company called up asking for login details so they could switch the website over, and now there's a mild panic such as will the new site integrate with other systems we've got? Who will maintain the content on the website? questions about why the change was necessary, why wasn't anyone (except management) consulted about it, and so forth.
We've raised this issue with our supervisor a few times, who have raised it with management a few times, but nothing seems to change. Projects keep going and those who are making the decisions don't consider the finer details of the project.
Is there anything we can do to ensure management speak with people before deciding on things? I worry that at some point our customer system will be replaced on a whim by management who sat through a five minute demo at a conference and we'll be struggling to understand why, or keep up.
I'm a firm believer in "let them fall flat on their face", but clearly that hasn't worked.
management projects
management projects
New contributor
New contributor
New contributor
asked 5 mins ago
JimJim
1
1
New contributor
New contributor
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "423"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Jim is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f131656%2fwhat-to-do-when-management-doesnt-consult-relevant-teams-in-major-projects%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Jim is a new contributor. Be nice, and check out our Code of Conduct.
Jim is a new contributor. Be nice, and check out our Code of Conduct.
Jim is a new contributor. Be nice, and check out our Code of Conduct.
Jim is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to The Workplace Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f131656%2fwhat-to-do-when-management-doesnt-consult-relevant-teams-in-major-projects%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown