3 ms·

Hey HelloNurse, thanks for the feedback. I understand that you think Im sensationalising, that advice is taken to heart and will not be repeated in my future wr

Hey HelloNurse, thanks for the feedback. I understand that you think Im sensationalising, that advice is taken to heart and will not be repeated in my future writing. Ill elaborate on your points. "I had to learn, out of sheer necessity, the tools to create unity and direction for teams. This is a skill that is so powerful and fascinating it eclipses all my technical skills." I say this because I'm a programmer, not a team building dude. But I was put in a project to turn it around, an important detail I did not put in the article. The project was over time and over time and over budget and most of the original team was removed and me and the team I refer to was put in. There was a total breakdown of communication and no work productive work was getting done. Nobody knew what to do. Thats why I contacted a guy I know which does business coaching and he taught me the three overarching things I mention in article 2 and the tools to build teams that I will be elaborating on in future posts. "No matter what has happened in the past, now is the time to own up to mistakes, and set new standards for going forward." I have seen plenty of unethical behaviour in my career. When your ass is on the line and your loosing money every hour, its easy to take the easy way out and take shortcuts. This is something that will permeate the project culture, and needs to stop. My sleep is more important than the project. Does this make it clearer what I meant? "In addition, passion about turning around failing projects seems intrinsically psychotic; it's a job, not a struggle for one's life." Here Im absolutely of guilty sensationalising. I was trying to get people to click and it worked, at the time of writing this comment it has almost 1k reads on medium which is way more than I was expecting. But it's a lie, Im not passionate about doomed projects, I'm passionate about highly successful projects. I just happened to learn the tools for how to create goal oriented teams from doomed projects. Thanks again for taking the time to write a comment, I'm very new at this so I need the candid feedback (everyone I showed to beforehand just said it was awesome so they were clearly just humouring me :D ). Cheers, Adam

onlydeadheroes 8y ago
> I was trying to get people to click and it worked (...) But it's a lie Can't wait for your post about how you grew out of being a liar and how being truthful is a skill "so powerful and fascinating it eclipses all my" blabla
- AdamPadam 8y ago
  OK, let me balance that. It's not a lie because Im very grateful that I went through this because it taught me something valuable. But Im obviously not passionate about failed projects because the goal is good projects. Now, if you are just going to try to catch me out and not try to understand that I am trying to communicate something real I am not going to waste my time replying. I respect your feedback, please try to respect that Im trying to learn.
  - onlydeadheroes 8y ago
    No. Don't hide behind words like "respect" and "learn". In your own words, you were not "trying to learn". What you were trying to do was: "I was trying to get people to click and it worked, at the time of writing this comment it has almost 1k reads on medium which is way more than I was expecting."
HelloNurse 8y ago
Explaining that you were in charge of a completely new team, and that the old team was kicked away, would have put your advice in a more favourable perspective. However: - Either there are reasonable targets for the replacement team, making the project a new and not failing yet one, or taking over the project is a suicide mission. It isn't at all clear what your starting situation and the attitude of your upper managers were along that spectrum. - I still have no idea of what kind of "shortcuts" and unethical behaviour you are alluding to. Lying about progress and problems? Pressuring and cheating the team to make them work overtime, unpaid for extra credits? Dirty tricks against colleagues? Theft and swindling? Envy, resentment and violence? Something beyond my imagination? In general, if you want to discuss your project management experience I think you should start from your story, telling it in detail (enough to allow readers to judge by themselves), and offer advice only as lessons learned. Exposing general advice first and tackling vague and unsettling hints of the experiences that justify it is much less effective.

onlydeadheroes 8y ago

> I was trying to get people to click and it worked (...) But it's a lie Can't wait for your post about how you grew out of being a liar and how being truthful is a skill "so powerful and fascinating it eclipses all my" blabla

AdamPadam 8y ago
OK, let me balance that. It's not a lie because Im very grateful that I went through this because it taught me something valuable. But Im obviously not passionate about failed projects because the goal is good projects. Now, if you are just going to try to catch me out and not try to understand that I am trying to communicate something real I am not going to waste my time replying. I respect your feedback, please try to respect that Im trying to learn.
- onlydeadheroes 8y ago
  No. Don't hide behind words like "respect" and "learn". In your own words, you were not "trying to learn". What you were trying to do was: "I was trying to get people to click and it worked, at the time of writing this comment it has almost 1k reads on medium which is way more than I was expecting."

HelloNurse 8y ago

Explaining that you were in charge of a completely new team, and that the old team was kicked away, would have put your advice in a more favourable perspective. However: - Either there are reasonable targets for the replacement team, making the project a new and not failing yet one, or taking over the project is a suicide mission. It isn't at all clear what your starting situation and the attitude of your upper managers were along that spectrum. - I still have no idea of what kind of "shortcuts" and unethical behaviour you are alluding to. Lying about progress and problems? Pressuring and cheating the team to make them work overtime, unpaid for extra credits? Dirty tricks against colleagues? Theft and swindling? Envy, resentment and violence? Something beyond my imagination? In general, if you want to discuss your project management experience I think you should start from your story, telling it in detail (enough to allow readers to judge by themselves), and offer advice only as lessons learned. Exposing general advice first and tackling vague and unsettling hints of the experiences that justify it is much less effective.