Mixing
How to convince superior/boss to use software tool, so we can avoid constant status updates?
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
4
down vote
favorite
I have a boss in charge of Product and Marketing who seems reluctant to learn about a product management tool we use, called Pivotal Tracker. My boss started working with us long after we began using the tool.
The main issue is our boss asks us for ETAs on when projects will be started, how long they will take, and a notification for when they are deployed. He also wants to keep track of what is being worked on at a given time. Pivotal Tracker is made to be able to do all those things automatically. Instead of using the tool, during one instance, he made a Word Doc with bug fixes listed out manually. That made us have to update our progress in two locations. All these extra steps, I believe, is a waste of time and gradually slows our workflow.
I am part of a small team of developers, and we have casually told (but not really pushed) him to use this, but I find it difficult, considering I am lower ranked, and I cannot boss him around.
What can I do to ensure he regularly uses this tool, so we don't need to resort to using manual notifications, such as via email?
management communication project-management
asked Oct 9 '15 at 22:49
StanMarsh
9116
suggest improvements |Â
up vote
4
down vote
favorite
I have a boss in charge of Product and Marketing who seems reluctant to learn about a product management tool we use, called Pivotal Tracker. My boss started working with us long after we began using the tool.
The main issue is our boss asks us for ETAs on when projects will be started, how long they will take, and a notification for when they are deployed. He also wants to keep track of what is being worked on at a given time. Pivotal Tracker is made to be able to do all those things automatically. Instead of using the tool, during one instance, he made a Word Doc with bug fixes listed out manually. That made us have to update our progress in two locations. All these extra steps, I believe, is a waste of time and gradually slows our workflow.
I am part of a small team of developers, and we have casually told (but not really pushed) him to use this, but I find it difficult, considering I am lower ranked, and I cannot boss him around.
What can I do to ensure he regularly uses this tool, so we don't need to resort to using manual notifications, such as via email?
management communication project-management
asked Oct 9 '15 at 22:49
StanMarsh
9116
1
One of those managers? Facilitate their wish to be told everything. Point the most verbose email outputs of your build, source control and work tracking systems at their email. :D
– Nathan Cooper
Oct 10 '15 at 8:49
suggest improvements |Â
up vote
4
down vote
favorite
up vote
4
down vote
favorite
I have a boss in charge of Product and Marketing who seems reluctant to learn about a product management tool we use, called Pivotal Tracker. My boss started working with us long after we began using the tool.
The main issue is our boss asks us for ETAs on when projects will be started, how long they will take, and a notification for when they are deployed. He also wants to keep track of what is being worked on at a given time. Pivotal Tracker is made to be able to do all those things automatically. Instead of using the tool, during one instance, he made a Word Doc with bug fixes listed out manually. That made us have to update our progress in two locations. All these extra steps, I believe, is a waste of time and gradually slows our workflow.
I am part of a small team of developers, and we have casually told (but not really pushed) him to use this, but I find it difficult, considering I am lower ranked, and I cannot boss him around.
What can I do to ensure he regularly uses this tool, so we don't need to resort to using manual notifications, such as via email?
management communication project-management
asked Oct 9 '15 at 22:49
StanMarsh
9116
I have a boss in charge of Product and Marketing who seems reluctant to learn about a product management tool we use, called Pivotal Tracker. My boss started working with us long after we began using the tool.
The main issue is our boss asks us for ETAs on when projects will be started, how long they will take, and a notification for when they are deployed. He also wants to keep track of what is being worked on at a given time. Pivotal Tracker is made to be able to do all those things automatically. Instead of using the tool, during one instance, he made a Word Doc with bug fixes listed out manually. That made us have to update our progress in two locations. All these extra steps, I believe, is a waste of time and gradually slows our workflow.
I am part of a small team of developers, and we have casually told (but not really pushed) him to use this, but I find it difficult, considering I am lower ranked, and I cannot boss him around.
What can I do to ensure he regularly uses this tool, so we don't need to resort to using manual notifications, such as via email?
management communication project-management
asked Oct 9 '15 at 22:49
StanMarsh
9116
edited Oct 10 '15 at 2:46
asked Oct 9 '15 at 22:49
StanMarsh
9116
asked Oct 9 '15 at 22:49
StanMarsh
9116
asked Oct 9 '15 at 22:49
StanMarsh
9116
9116
1
One of those managers? Facilitate their wish to be told everything. Point the most verbose email outputs of your build, source control and work tracking systems at their email. :D
– Nathan Cooper
Oct 10 '15 at 8:49
suggest improvements |Â
1
One of those managers? Facilitate their wish to be told everything. Point the most verbose email outputs of your build, source control and work tracking systems at their email. :D
– Nathan Cooper
Oct 10 '15 at 8:49
1
1
One of those managers? Facilitate their wish to be told everything. Point the most verbose email outputs of your build, source control and work tracking systems at their email. :D
– Nathan Cooper
Oct 10 '15 at 8:49
One of those managers? Facilitate their wish to be told everything. Point the most verbose email outputs of your build, source control and work tracking systems at their email. :D
– Nathan Cooper
Oct 10 '15 at 8:49
suggest improvements |Â
3 Answers
3
active
oldest
votes
up vote
3
down vote
You said your boss is reluctant to use this tool, however you didnt say unwilling. Since you say this tool can do all the things he wants, perhaps you should take some time and teach him how it works. If you show him how to get all the information he needs, then he might stop interrupting you. A good reporting tool should make reports easy to make and use.
If he still does not want to use the tool, then you are in a quandary. You could go to his boss and explain this situation. Obviously, there are drawbacks and advantages to this situation, but if it is the right thing to do, then you should do it.
In the end, he is the boss. If no one above him forces him to use the tool, then that is that. Adapt and survive.
answered Oct 9 '15 at 23:58
Keltari
1,83621218
1
+1, roughly what I would say. I might add, show him how it pays off in the long run. I would assume the software tool requires budget or, best case, front-end resources to set it up. Rather than focusing on "ensuring he regularly uses the tool," show him the positive impact the tool has on the business, and how it's worth the investment to make it work.
– S. Grey
Oct 10 '15 at 5:13
suggest improvements |Â
up vote
1
down vote
Your boss is reluctant, because using your tool is really not his job. It's your job to update him on your status.
That said, there is no need to do double tracking of tasks. All your boss needs is status updates. If your tool is any good, sending status updates at the time and in the format needed and should be trivial.
There is no need to fill out your bosses Word Document if he gets a daily report from your tool. The important part here is "gets". He should not need to learn the tool to pull himself a report. A report should be pushed to him by the tool without any extra work by him. And it's your job to make that happen.
answered Oct 10 '15 at 8:37
nvoigt
42.6k18105147
suggest improvements |Â
up vote
0
down vote
A lot of managers are reluctant to use software/practices which they have never been used, for obvious reasons. What if adopting it is just a tiny value addition, and takes a significant time/resources for learning it?
But, if you think it would really provide significant value addition to the company and the project, then you have to build a nice POC(Proof of concept), and take it's snapshots, or better make your manager look at it and use it.
When I presented the idea of an automated data workflow pipeline(in place of separate cron jobs for each), my manager was obviously reluctant to adopt it, as he didn't want to make such a drastic change in the architecture and convention unless the proposed idea have a significant value addition.
So, I went ahead and made a basic POC, and made my manager execute the entire flow and he loved it. Thus, I got a green signal to adopt and re-design the architecture.
So, PROVE the value addition. Make him use it, or make him see when the team is using it for a quick POC session.
answered Oct 10 '15 at 7:55
Dawny33
12.2k34563
suggest improvements |Â
StackExchange.ready(function ()
$("#show-editor-button input, #show-editor-button button").click(function ()
var showEditor = function()
$("#show-editor-button").hide();
$("#post-form").removeClass("dno");
StackExchange.editor.finallyInit();
;
var useFancy = $(this).data('confirm-use-fancy');
if(useFancy == 'True')
var popupTitle = $(this).data('confirm-fancy-title');
var popupBody = $(this).data('confirm-fancy-body');
var popupAccept = $(this).data('confirm-fancy-accept-button');
$(this).loadPopup(
url: '/post/self-answer-popup',
loaded: function(popup)
var pTitle = $(popup).find('h2');
var pBody = $(popup).find('.popup-body');
var pSubmit = $(popup).find('.popup-submit');
pTitle.text(popupTitle);
pBody.html(popupBody);
pSubmit.val(popupAccept).click(showEditor);
)
else
var confirmText = $(this).data('confirm-text');
if (confirmText ? confirm(confirmText) : true)
showEditor();
);
);
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
You said your boss is reluctant to use this tool, however you didnt say unwilling. Since you say this tool can do all the things he wants, perhaps you should take some time and teach him how it works. If you show him how to get all the information he needs, then he might stop interrupting you. A good reporting tool should make reports easy to make and use.
If he still does not want to use the tool, then you are in a quandary. You could go to his boss and explain this situation. Obviously, there are drawbacks and advantages to this situation, but if it is the right thing to do, then you should do it.
In the end, he is the boss. If no one above him forces him to use the tool, then that is that. Adapt and survive.
answered Oct 9 '15 at 23:58
Keltari
1,83621218
1
+1, roughly what I would say. I might add, show him how it pays off in the long run. I would assume the software tool requires budget or, best case, front-end resources to set it up. Rather than focusing on "ensuring he regularly uses the tool," show him the positive impact the tool has on the business, and how it's worth the investment to make it work.
– S. Grey
Oct 10 '15 at 5:13
suggest improvements |Â
up vote
3
down vote
You said your boss is reluctant to use this tool, however you didnt say unwilling. Since you say this tool can do all the things he wants, perhaps you should take some time and teach him how it works. If you show him how to get all the information he needs, then he might stop interrupting you. A good reporting tool should make reports easy to make and use.
If he still does not want to use the tool, then you are in a quandary. You could go to his boss and explain this situation. Obviously, there are drawbacks and advantages to this situation, but if it is the right thing to do, then you should do it.
In the end, he is the boss. If no one above him forces him to use the tool, then that is that. Adapt and survive.
answered Oct 9 '15 at 23:58
Keltari
1,83621218
1
+1, roughly what I would say. I might add, show him how it pays off in the long run. I would assume the software tool requires budget or, best case, front-end resources to set it up. Rather than focusing on "ensuring he regularly uses the tool," show him the positive impact the tool has on the business, and how it's worth the investment to make it work.
– S. Grey
Oct 10 '15 at 5:13
suggest improvements |Â
up vote
3
down vote
up vote
3
down vote
You said your boss is reluctant to use this tool, however you didnt say unwilling. Since you say this tool can do all the things he wants, perhaps you should take some time and teach him how it works. If you show him how to get all the information he needs, then he might stop interrupting you. A good reporting tool should make reports easy to make and use.
If he still does not want to use the tool, then you are in a quandary. You could go to his boss and explain this situation. Obviously, there are drawbacks and advantages to this situation, but if it is the right thing to do, then you should do it.
In the end, he is the boss. If no one above him forces him to use the tool, then that is that. Adapt and survive.
answered Oct 9 '15 at 23:58
Keltari
1,83621218
You said your boss is reluctant to use this tool, however you didnt say unwilling. Since you say this tool can do all the things he wants, perhaps you should take some time and teach him how it works. If you show him how to get all the information he needs, then he might stop interrupting you. A good reporting tool should make reports easy to make and use.
If he still does not want to use the tool, then you are in a quandary. You could go to his boss and explain this situation. Obviously, there are drawbacks and advantages to this situation, but if it is the right thing to do, then you should do it.
In the end, he is the boss. If no one above him forces him to use the tool, then that is that. Adapt and survive.
answered Oct 9 '15 at 23:58
Keltari
1,83621218
answered Oct 9 '15 at 23:58
Keltari
1,83621218
answered Oct 9 '15 at 23:58
Keltari
1,83621218
answered Oct 9 '15 at 23:58
Keltari
1,83621218
1,83621218
1
+1, roughly what I would say. I might add, show him how it pays off in the long run. I would assume the software tool requires budget or, best case, front-end resources to set it up. Rather than focusing on "ensuring he regularly uses the tool," show him the positive impact the tool has on the business, and how it's worth the investment to make it work.
– S. Grey
Oct 10 '15 at 5:13
suggest improvements |Â
1
+1, roughly what I would say. I might add, show him how it pays off in the long run. I would assume the software tool requires budget or, best case, front-end resources to set it up. Rather than focusing on "ensuring he regularly uses the tool," show him the positive impact the tool has on the business, and how it's worth the investment to make it work.
– S. Grey
Oct 10 '15 at 5:13
1
1
+1, roughly what I would say. I might add, show him how it pays off in the long run. I would assume the software tool requires budget or, best case, front-end resources to set it up. Rather than focusing on "ensuring he regularly uses the tool," show him the positive impact the tool has on the business, and how it's worth the investment to make it work.
– S. Grey
Oct 10 '15 at 5:13
+1, roughly what I would say. I might add, show him how it pays off in the long run. I would assume the software tool requires budget or, best case, front-end resources to set it up. Rather than focusing on "ensuring he regularly uses the tool," show him the positive impact the tool has on the business, and how it's worth the investment to make it work.
– S. Grey
Oct 10 '15 at 5:13
suggest improvements |Â
up vote
1
down vote
Your boss is reluctant, because using your tool is really not his job. It's your job to update him on your status.
That said, there is no need to do double tracking of tasks. All your boss needs is status updates. If your tool is any good, sending status updates at the time and in the format needed and should be trivial.
There is no need to fill out your bosses Word Document if he gets a daily report from your tool. The important part here is "gets". He should not need to learn the tool to pull himself a report. A report should be pushed to him by the tool without any extra work by him. And it's your job to make that happen.
answered Oct 10 '15 at 8:37
nvoigt
42.6k18105147
suggest improvements |Â
up vote
1
down vote
Your boss is reluctant, because using your tool is really not his job. It's your job to update him on your status.
That said, there is no need to do double tracking of tasks. All your boss needs is status updates. If your tool is any good, sending status updates at the time and in the format needed and should be trivial.
There is no need to fill out your bosses Word Document if he gets a daily report from your tool. The important part here is "gets". He should not need to learn the tool to pull himself a report. A report should be pushed to him by the tool without any extra work by him. And it's your job to make that happen.
answered Oct 10 '15 at 8:37
nvoigt
42.6k18105147
suggest improvements |Â
up vote
1
down vote
up vote
1
down vote
Your boss is reluctant, because using your tool is really not his job. It's your job to update him on your status.
That said, there is no need to do double tracking of tasks. All your boss needs is status updates. If your tool is any good, sending status updates at the time and in the format needed and should be trivial.
There is no need to fill out your bosses Word Document if he gets a daily report from your tool. The important part here is "gets". He should not need to learn the tool to pull himself a report. A report should be pushed to him by the tool without any extra work by him. And it's your job to make that happen.
answered Oct 10 '15 at 8:37
nvoigt
42.6k18105147
Your boss is reluctant, because using your tool is really not his job. It's your job to update him on your status.
That said, there is no need to do double tracking of tasks. All your boss needs is status updates. If your tool is any good, sending status updates at the time and in the format needed and should be trivial.
There is no need to fill out your bosses Word Document if he gets a daily report from your tool. The important part here is "gets". He should not need to learn the tool to pull himself a report. A report should be pushed to him by the tool without any extra work by him. And it's your job to make that happen.
answered Oct 10 '15 at 8:37
nvoigt
42.6k18105147
answered Oct 10 '15 at 8:37
nvoigt
42.6k18105147
answered Oct 10 '15 at 8:37
nvoigt
42.6k18105147
answered Oct 10 '15 at 8:37
nvoigt
42.6k18105147
42.6k18105147
suggest improvements |Â
suggest improvements |Â
up vote
0
down vote
A lot of managers are reluctant to use software/practices which they have never been used, for obvious reasons. What if adopting it is just a tiny value addition, and takes a significant time/resources for learning it?
But, if you think it would really provide significant value addition to the company and the project, then you have to build a nice POC(Proof of concept), and take it's snapshots, or better make your manager look at it and use it.
When I presented the idea of an automated data workflow pipeline(in place of separate cron jobs for each), my manager was obviously reluctant to adopt it, as he didn't want to make such a drastic change in the architecture and convention unless the proposed idea have a significant value addition.
So, I went ahead and made a basic POC, and made my manager execute the entire flow and he loved it. Thus, I got a green signal to adopt and re-design the architecture.
So, PROVE the value addition. Make him use it, or make him see when the team is using it for a quick POC session.
answered Oct 10 '15 at 7:55
Dawny33
12.2k34563
suggest improvements |Â
up vote
0
down vote
A lot of managers are reluctant to use software/practices which they have never been used, for obvious reasons. What if adopting it is just a tiny value addition, and takes a significant time/resources for learning it?
But, if you think it would really provide significant value addition to the company and the project, then you have to build a nice POC(Proof of concept), and take it's snapshots, or better make your manager look at it and use it.
When I presented the idea of an automated data workflow pipeline(in place of separate cron jobs for each), my manager was obviously reluctant to adopt it, as he didn't want to make such a drastic change in the architecture and convention unless the proposed idea have a significant value addition.
So, I went ahead and made a basic POC, and made my manager execute the entire flow and he loved it. Thus, I got a green signal to adopt and re-design the architecture.
So, PROVE the value addition. Make him use it, or make him see when the team is using it for a quick POC session.
answered Oct 10 '15 at 7:55
Dawny33
12.2k34563
suggest improvements |Â
up vote
0
down vote
up vote
0
down vote
A lot of managers are reluctant to use software/practices which they have never been used, for obvious reasons. What if adopting it is just a tiny value addition, and takes a significant time/resources for learning it?
But, if you think it would really provide significant value addition to the company and the project, then you have to build a nice POC(Proof of concept), and take it's snapshots, or better make your manager look at it and use it.
When I presented the idea of an automated data workflow pipeline(in place of separate cron jobs for each), my manager was obviously reluctant to adopt it, as he didn't want to make such a drastic change in the architecture and convention unless the proposed idea have a significant value addition.
So, I went ahead and made a basic POC, and made my manager execute the entire flow and he loved it. Thus, I got a green signal to adopt and re-design the architecture.
So, PROVE the value addition. Make him use it, or make him see when the team is using it for a quick POC session.
answered Oct 10 '15 at 7:55
Dawny33
12.2k34563
A lot of managers are reluctant to use software/practices which they have never been used, for obvious reasons. What if adopting it is just a tiny value addition, and takes a significant time/resources for learning it?
But, if you think it would really provide significant value addition to the company and the project, then you have to build a nice POC(Proof of concept), and take it's snapshots, or better make your manager look at it and use it.
When I presented the idea of an automated data workflow pipeline(in place of separate cron jobs for each), my manager was obviously reluctant to adopt it, as he didn't want to make such a drastic change in the architecture and convention unless the proposed idea have a significant value addition.
So, I went ahead and made a basic POC, and made my manager execute the entire flow and he loved it. Thus, I got a green signal to adopt and re-design the architecture.
So, PROVE the value addition. Make him use it, or make him see when the team is using it for a quick POC session.
answered Oct 10 '15 at 7:55
Dawny33
12.2k34563
answered Oct 10 '15 at 7:55
Dawny33
12.2k34563
answered Oct 10 '15 at 7:55
Dawny33
12.2k34563
answered Oct 10 '15 at 7:55
Dawny33
12.2k34563
12.2k34563
suggest improvements |Â
suggest improvements |Â
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f55720%2fhow-to-convince-superior-boss-to-use-software-tool-so-we-can-avoid-constant-sta%23new-answer', 'question_page');
);
Post as a guest
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
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
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
1
One of those managers? Facilitate their wish to be told everything. Point the most verbose email outputs of your build, source control and work tracking systems at their email. :D
– Nathan Cooper
Oct 10 '15 at 8:49