4 ms·
I think many of these issues are caused by a "silo" mentality. Decisions often flow from the business end through product before finally ending up as a story in
by qw 8y ago
I think many of these issues are caused by a "silo" mentality. Decisions often flow from the business end through product before finally ending up as a story in the developers backlog.
How can the devs understand the business decisions and learn to make less academic slides if they are not exposed to the business?
I worked at a medium sized business where devs had lunch with sales/product/marketing and was treated as more than just coders. That has helped me a lot when it comes to the business side of work.
If you have problems with the developers in your company, it may be that the real problem is with the company culture.
- sonnyblarney 8y agoI agree with your points about exposure - however - these problems generally do not exist in other parts of organizations. Devs are unique in their peculiar aspect disdain for 'management and business'. And unfortunately it's very rare that devs get such exposure but we agree it'd be great if they could.
- UK-Al05 8y agoHave you considered that the disdain comes from not being treated with respect? I don't know what comes first. But the places where engineers get on well with management are the ones where their opinions matter. Otherwise resentment comes in.
- tixocloud 8y agoDevs are unique but I would argue it's less of the dev mentality and more about how management and business can incorporate them as part of the decision-making process. Granted technical folk are a special breed but being technical myself and having moved over to the business side of things, it's still equally important to think about motivation for devs. To maintain engagement, I bring my technical guys with me to meetings where they can add value. And I always press about the value of meetings and what we're trying to get out of it.