Ask HN: Going to lead a struggling dev team in a different culture, now what?
41–50 of 79 posts
Re: Ask HN: Going to lead a struggling dev team in a different culture, now what?
#42"no test, a single staging dev server (no local dev env), no doc, inconsistent function and variable naming" --> none of these things prevent code from shipping, per se. I know it's convenient, as a first time leader, to focus on the technical aspects, but from your description, it seems there's underlying non-technical issues you might want to get familiar with first. On the technical side, I recommend _listening_ a…
You almost certainly will find some people who already long for what you're going to advocate.
Re: Ask HN: Going to lead a struggling dev team in a different culture, now what?
#43I'd go about it like so. 1. Start on a high note, take the team out to lunch / dinner and start to get to know them. 2. Don't force any changes, they will likely resist and you'll lose any budding support. Forcing a code review workflow is likely to demoralize them, and will be perceived to be slowing down dev that's already behind. 3. Work longer hours than anyone. You need to earn their respect, being seen to work…
#8 - you need to find a balance between crediting your team and making it absolutely clear to management that your contribution was critical. Obviously you do want to avoid the latter in front of "your team"; but in closed doors or in management-only meetings, you should not sell yourself short... which means sometimes you need to just boldly say, "I recognized X and chose to guide the team to do Y, and that resulted in Z (a good outcome)".
Re: Ask HN: Going to lead a struggling dev team in a different culture, now what?
#44Re: Ask HN: Going to lead a struggling dev team in a different culture, now what?
#45Earlier quoted context omitted.
This is an outstanding list and should be required learning on every software manager's todo. I can't tell you how important 3. is.
My personal feeling is actually quite different. I tend to respect a leader much more as a professional and as a person if they are able to deliver really great work within sensible working hours, leading by example with effective and sustainable work habits.
Things are certainly different if you are an established leader building your own team in a stable company.
Re: Ask HN: Going to lead a struggling dev team in a different culture, now what?
#46I've been in similar situations in the past a few times and did a talk on how I did it. Video : https://www.youtube.com/watch?v=eYzk2BKeG9s Blog Post : https://www.hibri.net/2016/06/18/continuous-delivery-rags-to... There is no one way, every team has been different (for me), it what technique you use depends on context. They key themes that stand out for me are 1. Limiting Work in Progress (focus on delivering one t…
Also, don’t be surprised if the team was given a project which was really hard to deliver with the team’s capabilities, and the CEO or his team leader, should have recognised that in the first place, and they (CEO etc) will be hard to convince that they are part of the issue. Also your list of things look like something that would take a rather long time to implement (many months), especially if you have a late proje…
Limiting work in progress, forces the issue upstream. Managers are forced to realise how much of a precious resource the team is, and why they are struggling. Throwing more work at a struggling team makes it even worse.
Re: Ask HN: Going to lead a struggling dev team in a different culture, now what?
#47Re: Ask HN: Going to lead a struggling dev team in a different culture, now what?
#48Excerpt:
> It’s very tempting, if you’re a software engineering manager, to propose broad, sweeping solutions to problems that affect large areas. ... > > So what can you do as a manager...? Well, the trick is to get the data from the individual contributors and then work with them to help them resolve the issues.
Re: Ask HN: Going to lead a struggling dev team in a different culture, now what?
#49If hierarchy is important in that culture and you're not introduced as the new boss, you're pretty much dead in the water from day one.
As other posters have said, until you figure out why the project is late (bad project management, unrealistic deadlines from the start, not the right people, trying to hit a moving target), going in an prescribing a cure without understanding the nature of the problem isn't going to get you anywhere.
Re: Ask HN: Going to lead a struggling dev team in a different culture, now what?
#50- don't worry about the usual western alpha-coder crap or any defiance. You'll be respected because the boss says so. They won't give you any of the shit that a western dev team would do while they work out the pecking order - the hierarchy is the pecking order. BUT... no-one will tell you the truth, they will always tell you what they think you want to hear. Only ask open questions (if they can say yes they will), don't ask for opinions (you'll get whatever they think you want to hear). If you tell them to do something stupid, they will never tell you they think it's stupid. They might not go and do it, and hope you don't notice, or if you do notice that you will realise that what you told them to do was stupid and you're not going to lose face by mentioning it.
- Authority and hierarchy are massively more important and more rigid than in the west. I can't overstate this enough.
- you will constantly run into communication problems. They won't tell you when they don't understand you, but will nod and say yes boss and then go do their best to guess what they think you said. Ask if they understand often, and do that by the patronising-sounding "what did I just say?" or "what did I just tell you to do?". It's difficult, because we only do this with children in western culture, but it's necessary.
- Use email and written comms waaaay more than you would with a western team. It's easier for them to understand written english, and they can take their time over puzzling it out. And you have a audit trail of what you said (yes, they'll happily do the "you told me to do this" if they think they can get away with it).
- You will get automatic respect for being western (assuming you're white that is - racism is real here). So I wouldn't worry so much about demonstrating that the practices you want to introduce have actual value. That will be taken for granted because they're western practices. Instead make sure they're understood. That will be hard.
- If your boss is not western, they will expect total and complete obedience to their authority. Don't ever question them, contradict them, suggest alternative ideas, or tell them what they just told you won't work, at least in public and probably in private too. You will have to learn how to allow your boss to keep face while getting the right result.
- listen a lot more than you think you will have to. If something's not working, there's probably a cultural reason for the fail that you're not seeing. Listen harder and you'll discover it. Often it's easier to let them do things their way even if it's slower and less efficient, because trying to get them to do things the western way is too alien to their way of thinking. It's surprising how often this is the case.
that'll do... you'll learn the rest as you go. Good luck :)