Related Posts
New to Fishbowl?
Download the Fishbowl app to
unlock all discussions on Fishbowl.
unlock all discussions on Fishbowl.
That was just a preview…
Sign Up to see all discussions
Sign Up to see all discussions
- Discover what it’s like to work at companies from real professionals
- Get candid advice from people in your field in a safe space
- Chat and network with other professionals in your field
Sign up in seconds to unlock all discussions on Fishbowl.
"" is an unusual email domain. If correct, please proceed to the next step
Messaging rates may apply
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
New to Fishbowl?
Download the Fishbowl app to unlock all discussions on Fishbowl.
Share
Embed this post
Copy and paste embed code on your site
Preview
Download the
Fishbowl app
Scan your QR code to download
Fishbowl app on your mobile
Sign up for free to view this conversation on Fishbowl
Sign up for free to continue using Fishbowl
Messaging rates may apply
Communicate. Communicate before you think you even need to communicate because chances are when you think you need to you could/should have already.
Bowl Leader
Celebrate wins within the group and also across stakeholders via product updates, slack etc. make sure they are in the loop for planning.
As a PM, there are various ways to show appreciation to your devs, such as recognizing their accomplishments publicly, providing opportunities for growth and development, offering flexible work arrangements, and simply saying "thank you" or giving positive feedback regularly. Personally I like calling them out in the group/slack to make sure they see that I see them!
Appreciate experience and their opinions. Include product developers in this process because they are skilled at finding solutions to business issues.
Let them to be inventive. This isn't to say that you should let engineers spend unlimited resources on ten separate tech stacks, but giving them time to improve things makes them happy, improves the system's effectiveness, and may even make it easier to manage in the long run.
Save no expense while purchasing equipment and laptops. Even the most costly laptop has a ROI in months for an engineer who is 10% more efficient.
Transparency in growth and compensation including a clearly defined growth path, equivalent base pay for everyone at the same level, promotion velocity data, clearly specified goals for promotion to the next level, and updating existing developers' pay so it is comparable to newly hired workers.
Celebrate success, praise them and be vocal about the good things they do. Not just within the team but outside in the team, for example give them a shoutout when you give demos, or mention them when they have good ideas.
Always ask for their opinion, include them as early as you can in refinement process. I tend to leave them lots of freedom when we refine features and they sometimes have ideas I didn’t think of and make the whole feature much better.
I also try to protect them as much as I can. I push and say no when it is too much and it helps building trust with them. Sometimes they are thrown work to meet mad deadlines and it’s not nice. I also make sure to remind them to take time off if they did overtime.
Simple things like saying thank you is very important. I am surprised to see how often people are not thankful….
One more thing, suggest support and ask for feedback to improve things.