How to handle new collective responsibility












2















Long story short: my team were each assigned a main focus among our daily/weekly tasks. If we completed early we’d see who else needed help, or what tasks were taking more time.



Now our new team lead has decided that there will just be collective responsibility, which means that I could choose to work on anything, or almost nothing. At least that’s how I see this change. It’s not easily traceable to see who has done what. I’m going to keep working hard but I don’t know if all of my colleagues will.



How should I flag this to the team lead? Or should I say nothing and get on? My concern is that he gets furious when work isn’t complete and now we’re all going to get it as I can’t point to my area of responsibility and show it’s done.










share|improve this question







New contributor




Smalac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • which means that I could choose to work on anything, or almost nothing..no, I don't think so. It means, the team has freedom to choose the work based on their choice, but at the end of the cycle, the work needs to be done. Any work remaining unfinished, will be treated as the teams' downside, rather than finger pointing at individuals.

    – Sourav Ghosh
    Mar 21 at 14:58











  • Don't you use any tools where tasks are assigned? It should be visible there if you completed 10 tasks and someone else 2.

    – Xander
    Mar 21 at 14:59











  • It’s not easily traceable to see who has done what. - that indicates the process has some issues, it's not the idea, but how it is implemented.

    – Sourav Ghosh
    Mar 21 at 14:59






  • 1





    @dwizum That is exactly his question, if he should or not.

    – Xander
    Mar 21 at 15:03






  • 1





    There are many many important reasons why you must know who has done what work. And this goes beyond making sure everyone pulls their weight.

    – Gregory Currie
    Mar 21 at 15:07
















2















Long story short: my team were each assigned a main focus among our daily/weekly tasks. If we completed early we’d see who else needed help, or what tasks were taking more time.



Now our new team lead has decided that there will just be collective responsibility, which means that I could choose to work on anything, or almost nothing. At least that’s how I see this change. It’s not easily traceable to see who has done what. I’m going to keep working hard but I don’t know if all of my colleagues will.



How should I flag this to the team lead? Or should I say nothing and get on? My concern is that he gets furious when work isn’t complete and now we’re all going to get it as I can’t point to my area of responsibility and show it’s done.










share|improve this question







New contributor




Smalac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • which means that I could choose to work on anything, or almost nothing..no, I don't think so. It means, the team has freedom to choose the work based on their choice, but at the end of the cycle, the work needs to be done. Any work remaining unfinished, will be treated as the teams' downside, rather than finger pointing at individuals.

    – Sourav Ghosh
    Mar 21 at 14:58











  • Don't you use any tools where tasks are assigned? It should be visible there if you completed 10 tasks and someone else 2.

    – Xander
    Mar 21 at 14:59











  • It’s not easily traceable to see who has done what. - that indicates the process has some issues, it's not the idea, but how it is implemented.

    – Sourav Ghosh
    Mar 21 at 14:59






  • 1





    @dwizum That is exactly his question, if he should or not.

    – Xander
    Mar 21 at 15:03






  • 1





    There are many many important reasons why you must know who has done what work. And this goes beyond making sure everyone pulls their weight.

    – Gregory Currie
    Mar 21 at 15:07














2












2








2








Long story short: my team were each assigned a main focus among our daily/weekly tasks. If we completed early we’d see who else needed help, or what tasks were taking more time.



Now our new team lead has decided that there will just be collective responsibility, which means that I could choose to work on anything, or almost nothing. At least that’s how I see this change. It’s not easily traceable to see who has done what. I’m going to keep working hard but I don’t know if all of my colleagues will.



How should I flag this to the team lead? Or should I say nothing and get on? My concern is that he gets furious when work isn’t complete and now we’re all going to get it as I can’t point to my area of responsibility and show it’s done.










share|improve this question







New contributor




Smalac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












Long story short: my team were each assigned a main focus among our daily/weekly tasks. If we completed early we’d see who else needed help, or what tasks were taking more time.



Now our new team lead has decided that there will just be collective responsibility, which means that I could choose to work on anything, or almost nothing. At least that’s how I see this change. It’s not easily traceable to see who has done what. I’m going to keep working hard but I don’t know if all of my colleagues will.



How should I flag this to the team lead? Or should I say nothing and get on? My concern is that he gets furious when work isn’t complete and now we’re all going to get it as I can’t point to my area of responsibility and show it’s done.







team






share|improve this question







New contributor




Smalac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question







New contributor




Smalac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question






New contributor




Smalac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked Mar 21 at 14:53









SmalacSmalac

162




162




New contributor




Smalac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Smalac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Smalac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.













  • which means that I could choose to work on anything, or almost nothing..no, I don't think so. It means, the team has freedom to choose the work based on their choice, but at the end of the cycle, the work needs to be done. Any work remaining unfinished, will be treated as the teams' downside, rather than finger pointing at individuals.

    – Sourav Ghosh
    Mar 21 at 14:58











  • Don't you use any tools where tasks are assigned? It should be visible there if you completed 10 tasks and someone else 2.

    – Xander
    Mar 21 at 14:59











  • It’s not easily traceable to see who has done what. - that indicates the process has some issues, it's not the idea, but how it is implemented.

    – Sourav Ghosh
    Mar 21 at 14:59






  • 1





    @dwizum That is exactly his question, if he should or not.

    – Xander
    Mar 21 at 15:03






  • 1





    There are many many important reasons why you must know who has done what work. And this goes beyond making sure everyone pulls their weight.

    – Gregory Currie
    Mar 21 at 15:07



















  • which means that I could choose to work on anything, or almost nothing..no, I don't think so. It means, the team has freedom to choose the work based on their choice, but at the end of the cycle, the work needs to be done. Any work remaining unfinished, will be treated as the teams' downside, rather than finger pointing at individuals.

    – Sourav Ghosh
    Mar 21 at 14:58











  • Don't you use any tools where tasks are assigned? It should be visible there if you completed 10 tasks and someone else 2.

    – Xander
    Mar 21 at 14:59











  • It’s not easily traceable to see who has done what. - that indicates the process has some issues, it's not the idea, but how it is implemented.

    – Sourav Ghosh
    Mar 21 at 14:59






  • 1





    @dwizum That is exactly his question, if he should or not.

    – Xander
    Mar 21 at 15:03






  • 1





    There are many many important reasons why you must know who has done what work. And this goes beyond making sure everyone pulls their weight.

    – Gregory Currie
    Mar 21 at 15:07

















which means that I could choose to work on anything, or almost nothing..no, I don't think so. It means, the team has freedom to choose the work based on their choice, but at the end of the cycle, the work needs to be done. Any work remaining unfinished, will be treated as the teams' downside, rather than finger pointing at individuals.

– Sourav Ghosh
Mar 21 at 14:58





which means that I could choose to work on anything, or almost nothing..no, I don't think so. It means, the team has freedom to choose the work based on their choice, but at the end of the cycle, the work needs to be done. Any work remaining unfinished, will be treated as the teams' downside, rather than finger pointing at individuals.

– Sourav Ghosh
Mar 21 at 14:58













Don't you use any tools where tasks are assigned? It should be visible there if you completed 10 tasks and someone else 2.

– Xander
Mar 21 at 14:59





Don't you use any tools where tasks are assigned? It should be visible there if you completed 10 tasks and someone else 2.

– Xander
Mar 21 at 14:59













It’s not easily traceable to see who has done what. - that indicates the process has some issues, it's not the idea, but how it is implemented.

– Sourav Ghosh
Mar 21 at 14:59





It’s not easily traceable to see who has done what. - that indicates the process has some issues, it's not the idea, but how it is implemented.

– Sourav Ghosh
Mar 21 at 14:59




1




1





@dwizum That is exactly his question, if he should or not.

– Xander
Mar 21 at 15:03





@dwizum That is exactly his question, if he should or not.

– Xander
Mar 21 at 15:03




1




1





There are many many important reasons why you must know who has done what work. And this goes beyond making sure everyone pulls their weight.

– Gregory Currie
Mar 21 at 15:07





There are many many important reasons why you must know who has done what work. And this goes beyond making sure everyone pulls their weight.

– Gregory Currie
Mar 21 at 15:07










2 Answers
2






active

oldest

votes


















2














Flagging problems is better received when accompanied by solutions. You should definitely bring your concerns to your boss, as at the end of the day it's in his best interest that the team performs.



I would avoid mentioning laziness though, perhaps use the word impediments instead. Ie: John is on Facebook all day is bad because it's accusatory, but John is on this task for several days, so he must face a blocker allows John to save face, smarten up, and put the phone down. Win-win for everyone.



With that in mind, I present you:



Quick Feedback Cycles



Have a morning stand-up meeting to see what the progress and impediments are. I'm going to highlight a few things from the Wikipedia entry, just substitute scrum for daily/weekly focus (emphasis mine):






  1. What did I do yesterday that helped the development team meet the sprint goal?


  2. What will I do today to help the development team meet the sprint goal?


  3. Do I see any impediment that prevents me or the development team from meeting the sprint goal?




This way everyone can pick their own tasks but no one can hide their laziness for long.



Additionally (and perhaps, crucially) if someone is stuck on a tasks for days at a time, someone else should notice and jump in to help them. Or, if it looks like a task won't be ready by the week's end, the team member should flag it for attention. It works wonders for self-diagnosing problems within the team, and fixing them.






share|improve this answer

































    1














    Your setup is similar to agile development and as such you can borrow some functions from that development method.



    As @rath mentioned, it's a good idea to do daily standups where people can say what they did yesterday, what they will be doing today and if they are blocked from anything.



    To answer your questions, you can raise the issue with your manager but you need to be able to provide solutions. One solution would be the daily standups, other would be to communicate with your team members to have a meeting every week perhaps and see where you stand regarding a project. What remains to be done and where you need to focus and divide tasks accordingly.



    Lastly, if you want accountability, you can push for implementing a tool like JIRA where tasks are added and assigned to specific people. This way both your team lead and you as team members can go back and see who's done what.



    In the end of the day, your team leads want you to police each other. You already know who's slacking and at some point you'll have to confront them as a team to avoid getting heat from your lead.






    share|improve this answer























      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
      });


      }
      });






      Smalac is a new contributor. Be nice, and check out our Code of Conduct.










      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f132190%2fhow-to-handle-new-collective-responsibility%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      2














      Flagging problems is better received when accompanied by solutions. You should definitely bring your concerns to your boss, as at the end of the day it's in his best interest that the team performs.



      I would avoid mentioning laziness though, perhaps use the word impediments instead. Ie: John is on Facebook all day is bad because it's accusatory, but John is on this task for several days, so he must face a blocker allows John to save face, smarten up, and put the phone down. Win-win for everyone.



      With that in mind, I present you:



      Quick Feedback Cycles



      Have a morning stand-up meeting to see what the progress and impediments are. I'm going to highlight a few things from the Wikipedia entry, just substitute scrum for daily/weekly focus (emphasis mine):






      1. What did I do yesterday that helped the development team meet the sprint goal?


      2. What will I do today to help the development team meet the sprint goal?


      3. Do I see any impediment that prevents me or the development team from meeting the sprint goal?




      This way everyone can pick their own tasks but no one can hide their laziness for long.



      Additionally (and perhaps, crucially) if someone is stuck on a tasks for days at a time, someone else should notice and jump in to help them. Or, if it looks like a task won't be ready by the week's end, the team member should flag it for attention. It works wonders for self-diagnosing problems within the team, and fixing them.






      share|improve this answer






























        2














        Flagging problems is better received when accompanied by solutions. You should definitely bring your concerns to your boss, as at the end of the day it's in his best interest that the team performs.



        I would avoid mentioning laziness though, perhaps use the word impediments instead. Ie: John is on Facebook all day is bad because it's accusatory, but John is on this task for several days, so he must face a blocker allows John to save face, smarten up, and put the phone down. Win-win for everyone.



        With that in mind, I present you:



        Quick Feedback Cycles



        Have a morning stand-up meeting to see what the progress and impediments are. I'm going to highlight a few things from the Wikipedia entry, just substitute scrum for daily/weekly focus (emphasis mine):






        1. What did I do yesterday that helped the development team meet the sprint goal?


        2. What will I do today to help the development team meet the sprint goal?


        3. Do I see any impediment that prevents me or the development team from meeting the sprint goal?




        This way everyone can pick their own tasks but no one can hide their laziness for long.



        Additionally (and perhaps, crucially) if someone is stuck on a tasks for days at a time, someone else should notice and jump in to help them. Or, if it looks like a task won't be ready by the week's end, the team member should flag it for attention. It works wonders for self-diagnosing problems within the team, and fixing them.






        share|improve this answer




























          2












          2








          2







          Flagging problems is better received when accompanied by solutions. You should definitely bring your concerns to your boss, as at the end of the day it's in his best interest that the team performs.



          I would avoid mentioning laziness though, perhaps use the word impediments instead. Ie: John is on Facebook all day is bad because it's accusatory, but John is on this task for several days, so he must face a blocker allows John to save face, smarten up, and put the phone down. Win-win for everyone.



          With that in mind, I present you:



          Quick Feedback Cycles



          Have a morning stand-up meeting to see what the progress and impediments are. I'm going to highlight a few things from the Wikipedia entry, just substitute scrum for daily/weekly focus (emphasis mine):






          1. What did I do yesterday that helped the development team meet the sprint goal?


          2. What will I do today to help the development team meet the sprint goal?


          3. Do I see any impediment that prevents me or the development team from meeting the sprint goal?




          This way everyone can pick their own tasks but no one can hide their laziness for long.



          Additionally (and perhaps, crucially) if someone is stuck on a tasks for days at a time, someone else should notice and jump in to help them. Or, if it looks like a task won't be ready by the week's end, the team member should flag it for attention. It works wonders for self-diagnosing problems within the team, and fixing them.






          share|improve this answer















          Flagging problems is better received when accompanied by solutions. You should definitely bring your concerns to your boss, as at the end of the day it's in his best interest that the team performs.



          I would avoid mentioning laziness though, perhaps use the word impediments instead. Ie: John is on Facebook all day is bad because it's accusatory, but John is on this task for several days, so he must face a blocker allows John to save face, smarten up, and put the phone down. Win-win for everyone.



          With that in mind, I present you:



          Quick Feedback Cycles



          Have a morning stand-up meeting to see what the progress and impediments are. I'm going to highlight a few things from the Wikipedia entry, just substitute scrum for daily/weekly focus (emphasis mine):






          1. What did I do yesterday that helped the development team meet the sprint goal?


          2. What will I do today to help the development team meet the sprint goal?


          3. Do I see any impediment that prevents me or the development team from meeting the sprint goal?




          This way everyone can pick their own tasks but no one can hide their laziness for long.



          Additionally (and perhaps, crucially) if someone is stuck on a tasks for days at a time, someone else should notice and jump in to help them. Or, if it looks like a task won't be ready by the week's end, the team member should flag it for attention. It works wonders for self-diagnosing problems within the team, and fixing them.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Mar 21 at 15:26

























          answered Mar 21 at 15:12









          rathrath

          20.9k1462103




          20.9k1462103

























              1














              Your setup is similar to agile development and as such you can borrow some functions from that development method.



              As @rath mentioned, it's a good idea to do daily standups where people can say what they did yesterday, what they will be doing today and if they are blocked from anything.



              To answer your questions, you can raise the issue with your manager but you need to be able to provide solutions. One solution would be the daily standups, other would be to communicate with your team members to have a meeting every week perhaps and see where you stand regarding a project. What remains to be done and where you need to focus and divide tasks accordingly.



              Lastly, if you want accountability, you can push for implementing a tool like JIRA where tasks are added and assigned to specific people. This way both your team lead and you as team members can go back and see who's done what.



              In the end of the day, your team leads want you to police each other. You already know who's slacking and at some point you'll have to confront them as a team to avoid getting heat from your lead.






              share|improve this answer




























                1














                Your setup is similar to agile development and as such you can borrow some functions from that development method.



                As @rath mentioned, it's a good idea to do daily standups where people can say what they did yesterday, what they will be doing today and if they are blocked from anything.



                To answer your questions, you can raise the issue with your manager but you need to be able to provide solutions. One solution would be the daily standups, other would be to communicate with your team members to have a meeting every week perhaps and see where you stand regarding a project. What remains to be done and where you need to focus and divide tasks accordingly.



                Lastly, if you want accountability, you can push for implementing a tool like JIRA where tasks are added and assigned to specific people. This way both your team lead and you as team members can go back and see who's done what.



                In the end of the day, your team leads want you to police each other. You already know who's slacking and at some point you'll have to confront them as a team to avoid getting heat from your lead.






                share|improve this answer


























                  1












                  1








                  1







                  Your setup is similar to agile development and as such you can borrow some functions from that development method.



                  As @rath mentioned, it's a good idea to do daily standups where people can say what they did yesterday, what they will be doing today and if they are blocked from anything.



                  To answer your questions, you can raise the issue with your manager but you need to be able to provide solutions. One solution would be the daily standups, other would be to communicate with your team members to have a meeting every week perhaps and see where you stand regarding a project. What remains to be done and where you need to focus and divide tasks accordingly.



                  Lastly, if you want accountability, you can push for implementing a tool like JIRA where tasks are added and assigned to specific people. This way both your team lead and you as team members can go back and see who's done what.



                  In the end of the day, your team leads want you to police each other. You already know who's slacking and at some point you'll have to confront them as a team to avoid getting heat from your lead.






                  share|improve this answer













                  Your setup is similar to agile development and as such you can borrow some functions from that development method.



                  As @rath mentioned, it's a good idea to do daily standups where people can say what they did yesterday, what they will be doing today and if they are blocked from anything.



                  To answer your questions, you can raise the issue with your manager but you need to be able to provide solutions. One solution would be the daily standups, other would be to communicate with your team members to have a meeting every week perhaps and see where you stand regarding a project. What remains to be done and where you need to focus and divide tasks accordingly.



                  Lastly, if you want accountability, you can push for implementing a tool like JIRA where tasks are added and assigned to specific people. This way both your team lead and you as team members can go back and see who's done what.



                  In the end of the day, your team leads want you to police each other. You already know who's slacking and at some point you'll have to confront them as a team to avoid getting heat from your lead.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Mar 21 at 15:36









                  XanderXander

                  728215




                  728215






















                      Smalac is a new contributor. Be nice, and check out our Code of Conduct.










                      draft saved

                      draft discarded


















                      Smalac is a new contributor. Be nice, and check out our Code of Conduct.













                      Smalac is a new contributor. Be nice, and check out our Code of Conduct.












                      Smalac 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.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f132190%2fhow-to-handle-new-collective-responsibility%23new-answer', 'question_page');
                      }
                      );

                      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







                      Popular posts from this blog

                      Plaza Victoria

                      Puebla de Zaragoza

                      Musa