4 ms·
> If engineering is acting like a disorganized, isolated group in the company, it's often (in my experience) because management has created structures that keep
by thrwwyngnr 8y ago
> If engineering is acting like a disorganized, isolated group in the company, it's often (in my experience) because management has created structures that keep them feeling isolated and without a sense of ownership/belonging.
OP here.
This is an extremely interesting insight.
Now that I think about it, engineers were indeed isolated for a long time, because PO and UX people were the ones doing all the talking with stakeholders and users "because this is the way it is supposed to be done".
This is probably both the reason they're actively isolating themselves and the reason the morale is low.
Thank you.
- DanielBMarkham 8y agoI've been brought in several times to situations like this. Worst-case was the team that not only moved to their own building, but they set up a gated security system where the other folks couldn't get in. The technical checklist above is awesome, but no amount of technical chops is going to fix that. Your company should be an engineering team, some of which can't code very well, that also kicks ass in whatever field you're in. That's probably a big mental leap! But it's where you have to go. Tear down the barriers and integrate engineering as tightly as possible with the "real" work. Hint: whatever you do, you can do more. Put coders on the customer support phones. Rotate people through the teams as SMEs. Physically put them in places where they rub elbows with other groups. Got a bug in a CSR app? Bring in the folks affected and have them personally explain the impact to the team. I could go on, but I'm just winging it. Whatever you do will depend on what your company does and what the people are like -- how willing they are to change. Finally, and the people that do the work I do are going to hate this, be ready to fire people. Bad cultures grow employees with horrible attitudes that many times cannot be fixed. Not every bad culture situation can be fixed with magic sauce. Experience shows it only takes one person with a bad attitude in a group as large as 50 to destroy positive momentum. In general, if you want to rock, the people that code should live inside the heads of the people who find and grow value for the org. Once you get the social walls down, work on the technical stuff. Otherwise you'll just make more arrogant tech teams.
- thrwwyngnr 8y agoFunny, the previous manager actually wanted a gate with a keycode to avoid anyone from ever coming. > Your company should be an engineering team, some of which can't code very well, that also kicks ass in whatever field you're in. That's probably a big mental leap! But it's where you have to go. > Tear down the barriers and integrate engineering as tightly as possible with the "real" work. Hint: whatever you do, you can do more. Put coders on the customer support phones. Rotate people through the teams as SMEs. Physically put them in places where they rub elbows with other groups. Got a bug in a CSR app? Bring in the folks affected and have them personally explain the impact to the team. This is kind of amazing to read, and a great idea to reorganize the team. Would surely solve our cultural problems, and would actually free time from the programmers. Makes a lot of sense. > Once you get the social walls down, work on the technical stuff. Otherwise you'll just make more arrogant tech teams. That's interesting to read and makes a lot of sense. Thank you.
- Aeolun 8y agoThis sounds like people coming from an enterprise instead of startup background to me.