News for hackers. Stuff that matters.
Re:The Case for Why Marketing Should Have Its Own Engineers by smacktoward on Tuesday July 15, 2014 @02:02PM (#8037982)
This seems more like a description of management failure than of a need for marketing to have its own engineers.

If the problem is that marketing and engineering can't talk to each other, the solution is for management to be able to talk to both of them, not for people whose skills would put them in one group to be embedded in the other. Going that way just creates "B teams": the good engineers (the "A team") are in Engineering; the ones Engineering doesn't want get shunted over to Marketing to get them out of the way. Which doesn't do Marketing any favors, since those are the ones least likely to be able to understand what Engineering is doing in the first place.

Re:The Case for Why Marketing Should Have Its Own Engineers by kyllo on Tuesday July 15, 2014 @04:04PM (#8038651)
Usually in this case the Marketing folks are no dummies and will spring for an outside hire rather than take the rejects from the IT/Engineering Department. They are often forced to do this because IT cannot grow fast enough to support the business side, and the business stakeholder cannot get an IT "resource" allocated to their project. So they just go hire their own.

But, if the company is actually big enough that Marketing and Engineering have serious problems communicating with each other, perhaps it's time to reorganize into product divisions, so that all the people whose cooperation is needed to perform the daily work to support a given product, are under the same reporting structure, and so that the product team that needs another developer can just hire another developer, rather than having to plead with the IT department to allocate them one.

Re:The Case for Why Marketing Should Have Its Own Engineers by dwd on Wednesday July 16, 2014 @04:37AM (#8041112)
Currently in the early stage of such a reorganisation.

About a year ago the development team was on a separate floor and communication breakdowns with business were endemic. Treating marketing like a customer didn't work and worse, they would come up with the ideas and we would implement them.

Relocating to the same floor helped and development was more involved with planning and ideas.

We have now gone a step further and organised along product lines with each team consisting of a mix of devs and business (account and project managers). There is still a marketing team who are primarily involved with PR, advertising and social media and sit alongside the database/analytics team.

Devs still report to the Development Manager while Marketing, Business and Accounts report to their respective managers.

Seems to be working so far.

Re:The Case for Why Marketing Should Have Its Own Engineers by hyperliner on Tuesday July 15, 2014 @08:47PM (#8040009)
One tweak: sometimes you can solve the problem through establishing the process of decision making and accountability and progress tracking without having to reorg.
Re:The Case for Why Marketing Should Have Its Own Engineers by joshdance on Tuesday July 15, 2014 @05:02PM (#8038973)
The problem is not that just management needs to be able to talk to both of them, everyone needs to be able to talk to the other group. Having small teams of cross disciplinary skill can work very well, especially with projects of limited scope like marketing automation etc.
Re:The Case for Why Marketing Should Have Its Own Engineers by jontas on Tuesday July 15, 2014 @02:05PM (#8038006)
That isn't how it works at all. As per TFA, marketing interviews and hires their own talent, and there isn't any crossover between the engineering and marketing team staffing.
Re:The Case for Why Marketing Should Have Its Own Engineers by enraged_camel on Tuesday July 15, 2014 @02:16PM (#8038067)
Right, that's how it should work in theory. In practice though, marketing doesn't have the capability to interview and hire their own engineering talent. How can they, when they are marketers? How is a marketing manager supposed to do, say, a code review?

So what happens in practice is exactly what smacktoward described: the B-level engineers are sent to the marketing department because Engineering doesn't want them around.

Re:The Case for Why Marketing Should Have Its Own Engineers by apalmer on Tuesday July 15, 2014 @02:25PM (#8038118)
Thats making a lot of assumptions here. Honestly the opposite is just as likely to happen. If marketing has a better 'manager'/'lead'/'architect' and is offering better pay and more interesting work, I have seen where the 'B' team becomes more effective than the 'A' team.

What it does always do is bifurcate your technical staff...

Re:The Case for Why Marketing Should Have Its Own Engineers by drumdance on Tuesday July 15, 2014 @02:54PM (#8038284)
It doesn't necessarily have to be "b" talent. A more common case is probably young talent. When I first started coding a lot of my projects were marketing oriented: landing pages, email signup forms and the like. After a few years of doing that I had developed the skills to do more core engineering tasks.

Edit to add: not necessarily at the same company. Creating marketing automation applications is a great entry level job that makes your resume more attractive to future employers.

Re:The Case for Why Marketing Should Have Its Own Engineers by jontas on Tuesday July 15, 2014 @02:39PM (#8038205)
I don't understand how you can say that is what happens in practice when the article (and me, personally) is proof of the exact opposite. As I mentioned in a different comment, I am the developer working for the marketing team described in this article. My boss, the director of marketing, knows when to reach out for assistance and wouldn't presume to make technical decisions that are outside of his area of expertise. He happens to be one of the more technically proficient marketers I've worked with, but even if he wasn't that doesn't mean he is doomed to make poor decisions in isolation.

At Knewton, someone who was not up to standards wouldn't be shifted out of the way to another department, they would be let go. That is a pretty rare occurance because the hiring standards are strict (in my opinion, maybe too strict, I think we get a lot of false negatives, but that is another topic). Any company that had a policy of sticking another department with an employee they disliked would not last long because you'd end up with a lot of poor talent being shuffled all over the place.

Re:The Case for Why Marketing Should Have Its Own Engineers by nmcfarl on Tuesday July 15, 2014 @09:30PM (#8040141)
I don't know – I once was a marketing Dev. And I like to think that I'm good.

In that case how they found a dev team for marketing was to go trolling for the best Devs from their previous companies (the marketing team being very deep in start up experience). That's how they found me, that's how they found my coworkers and I like to think that we were the best engineers in that company. Or at least the most pragmatic, and profitable.

Anyhow - every single company that isn't founder by a coder has this problem, and many of them make it past it somehow.

---

I would say that there were political problems in this company, and if wouldn't do it this way myself. For unclear reasons, engineering a policy was to hire only c coders in 2003. And there was a need for full fledge ecommerce site - for which they were quoting multiyear lead times. Which is why marketing just built it. And a bunch of other stuff.