They are suggesting that just as a unit test is an important aspect of determining functionality, it may be helpful to have a metric of how much excitement a certain feature may engender.
I'm not going to judge the quality of that advice; I just offer the possibility that it was a well-intentioned attempt to add a view from a different professional perspective.
perhaps we can be forgiving to someone who is perhaps acting in a socially awkward manner?
Signed, an insecure developer with bad marketing skills
This can lead to the "if you build it, they will come" mentality.
Or worse, "we'll build it and we don't care if they come (and if they do come, they'd better RTFM!)" mentality.
A huge amount of developers just want to be shielded from any kind of customer interaction, and I'm not talking about call center support.
Very true. I build for the sake of building in my free time.
> Or worse, "we'll build it and we don't care if they come...
True as well. If I am working on a personal project is because I believe it's the best project ever conceived (obviously I know I'm wrong, but there is always "what if I'm not?!").
> A huge amount of developers just want to be shielded from any kind of customer interaction, and I'm not talking about call center support.
But if we are talking in the context of developers working for companies (not developers working on their personal projects) then the only responsible person of working on features no one will use is the project manager (or product owner): they own the product, they decide what comes next (with the help of devs).
Or work on behind the scenes stuff with little oversight and unclear actual benefits.
Some developers are actually good at promoting their initiatives.
I fully agree.
I've worked with an incredible b2b salesman before. He wasn't very technical, but he was always curious about what was possible and how difficult it would be to accomplish. Going to a conference with him as the technical expert was amazing. Customers were a gold mine for information. We always looked deeper to find the problems to solve, not the features to create. Learned a lot from him.
Sadly, I haven't had this dynamic since.
Since then, I've run into marketing departments. My issue with them is they constantly switch tools, want immediate results, and destroy site performance without any concern for the path of destruction they leave behind. And marketing is good at selling stuff internally as they are externally. As a result, few people in management care about how marketing impacts anything else in the company.
On the flip side, marketing is the first department to be stabbed in the back when numbers come up badly. It's not really a surprise to me they treat other departments as scapegoats pass blame to.
Things don't have to be this way. :(
When in reality, as you discovered, the best salespeople are the ones who are able to really, truly understand the problems of their customer base and help them find solutions. That is an incredibly special skill, and one that should never be underrated.
The essence of what Xerox taught was: to sell, find out what problems your customer has, and figure out how your product/service can help him/her solve the problem. That's it.
Xerox was very good at sales.
Oh, cool! That's the SPIN model[1], implemented by Neil Rackham at Xerox in the 70s.
https://books.google.com/books/about/SPIN_Selling.html?id=0n...
You're right, all you have to do to eliminate it is get rid of all of the ridiculous metrics that people try to apply to human interaction, ban billion dollar "platforms" like the social media companies, and reduce everything back down to face to face scale.
We would be better off, I'm not being facetious.
Somewhat off topic, and speaking of unicorns: http://widgetsandshit.com/teddziuba/2011/07/the-craigslist-r...
"I want what I write to matter to someone" is the fundamental calling of many founders.
This requires delivering a high-impact product.
> earn some reasonable money
These two are in opposition
The end result is that you feel like a tiny part of some weird, random, extremely expensive process to (rarely) create successful new businesses. Like part of a living pachinko machine that burns cash. But you can get paid plenty for it!
For example, here in Latvia we don't quite have such a large tech scene, outside of WITCH companies.
Thus, it feels like that argument isn't entirely valid in all that many circumstances.
> Adobe
22 000 employees.
Revenue of $12.86 billion.
They're a literal Fortune 500 company (and not that far off from Fortune 200): https://fortune.com/company/adobe-systems/fortune500/
We’ve forgotten about general tech/companies, consulting, fossil/energy, etc etc that are also very very mega.
If someone has tips on how to weed out pretenders (who themselves do not realize they are pretending) - I would love to learn about it. Unfortunately, my budget typically is too small to keep hiring until i hit the gold.
Marketing also covers a very wide spectrum. For a small operation, the person you might hire to create content and/or messaging for a product is probably different from the one you would hire to create a digital demand generation program.
I think this entirely depends on what kind of people you hire, and what type of environment you put them in. I've worked with developers who's sole focus was on just building whatever they were told, they focused on the technical aspects, and didn't care whether it would be deployed, or if the user would even use it.
I've also worked in teams, where everyone was a product engineer, which essentially just means that we focused on building products, and while the tech side was important, it was more important to make sure the product got build, and eventually used. We often worked side by side with our business teams, marketing and design people, and it was honestly the most fun I've ever had. Knowing that I was building something that people were actually going to use, just motivated and excited me.
I found what you said really interesting, and am sharing it with my SO who is a marketing and business contractor. Thank you for sharing!
Up until a couple months ago, I thought Marketing teams/organizations were a bit hand wavy. But recently, I took a digital marketing course at Georgia Tech, which changed my perspective completely: marketers (can/do/should) apply data driven techniques.
As an engineer, I now (at least try) to think about how the feature I'm building will impact the end-user; it's easy to fall into a trap where you are writing code without thinking about your end users.
I strongly agree with this! If you're working towards a product (and not just a hobby project) then these are crucial requirements. If they can be found out before writing any code, then they should be, since it will save time in the long run.
For me it's also the kind of thing that can lead to costly changes after the fact, which is prone to rub developers up the wrong way. It seems like the principle of phase containment might apply - if you found it early in the development cycle, then it would have been easier to fix.
As a marketer, improving my understanding of the development process and technology in general has been one of the best skills I continue to learn. I have built a personal project iOS app but have no desire to be an engineer. (Know what you're good at and all that!)
I see it as a forever loop that continues to build on itself, going back and forth between marketing and engineering. Understanding users/behaviours/needs can greatly inform the product scoping and add clarity to the development process with the “why” that makes a product or feature more useful - which in turn then becomes easier to market and solve user use cases.
This is such a user-facing mindset. I’d say most of the development work I do isn’t even something the user will know about and definitely not get excited about. Also, I do not care about what happens after a feature gets built, my job is not to make sure the right things are being built, it’s to make sure things are being built right. Do your job and I’ll do mine.
If you build the right things the wrong way, then you have technical debt. If you build the wrong things the right way, then you have nothing (except maybe an aesthetically pleasant code base that won't get used?). Every developer should try to have some part in making sure the right thing is being built.
Bingo. For as much as developers hate technical debt, it seems many miss the obvious way to avoid it is to not build something at all.
"User" doesn't mean the person clicking around a website. Someone is using your software, I hope?
There can be communication challenges between our disciplines though.
Frequent changes in direction can leave software in a bit of a shambles. This is probably the thing that creates the feeling that development is "a sacred space for creation". It takes time to both make the change, and end up with code that is pleasant to work with. On teams I've been on, this has sometimes led resistance to the marketing perspective.
I, personally, am often uncomfortable with the language of marketing (both on the analysis side, and on the promotion side). On the promotion side, marketing teams like to make claims that are aspirational or appeal to emotional needs, rather than actually true from a technologists perspective. On the analysis side, marketing often looks like it's working from incomplete information, and extrapolating trends that I don't feel confident exist. It feels like guessing, and I don't like to gamble.
These can be difficult gaps to bridge, but ultimately, I feel like we have the same goal: building the right thing for the right audience.
"If you build it they will come" is a sure fire way to have your hopes and dreams dashed on the rocks of reality. Marketing is as important as the dev skills to make a product happen. They are two sides of the same coin of success.
the vast majority of folks in software engineering should not be thinking in terms of user exitement, or market value or brand positioning etc.
if I were a solo indie entrepreneur/engineer who had to wear all the hats I couldnt delegate to others? heck yes I should follow your advice.
marketing, product design and UX are all incredibly important. but they are not the responsibility, or anywhere in the top concerns, of a software engineer. for the business overall? heck yes
But just to provide some insight (which you probably already have) into the mind of a different kind of person: I can both recognize the truth that marketing is critically and synergistically important, and also have just a deep seated allergy to it. I have concluded that being a freelance / independent developer or even a very early stage startup developer is not a great fit for me for this reason. I thrive more when there is lots of work to do that is not deeply attached to marketing a new product.
As a dev I had to learn marketing inversely, to allow me to better understand the process of ensuring clients a smooth and trust-worthy process... In running my business I have to daily be involved in absolutely every aspect of it (without being too controlling of course) because managing delivery and client experience is a key to gaining and retaining new and follow-up work.
The best method of self-marketing/promoting I've found is to build my own products/portfolios that represent what would be useful and engaging to new potential clients. Working product demos also help marketers to better be acquainted with what they are ultimately selling, and make intuitive screen shots and presentations of the products in support of their efforts. That way I also have a template I can build quicker from, but I also demonstrate to clients that I can actually do the work.
IT is far too complex in presentation these days; many clients are not focused on tech stacks, methods, tools, services, or things developers are usually focused on. Modern clients are usually most concerned about their requirements and business needs, a marketer should focus on being a translator in a way when it comes to marketing development work, linking that work to productivity, progress, and things that satisfy requirements and provide benefits in a clear and usually less-technically inclined manner than a developer would detail a solution...
E.G.... We keep selling "the cloud" to everyone, but if you ask a client what "cloud" is they simply don't know/don't really care what it really is, as long as it fulfills their business goals.
In a world where people are using imagery alone to market their capability, the real working examples of what we do as a company are often what wins us new work.... Even if we don't win new work, the products we build usually end up being valuable and highly useful to us ultimately in real life.
What do you mean by this? I don't disagree in anyway, just looking for your insights.
Marketing and sales has very different incentives from developers. Marketers are often trigger happy with features because they "sell" despite the fact that these feature may have a short shelf life and may take resources away from developing of more essential product features. Developers are similarly allergic to additional development because it's (1) work (2) often results in technical debt.
You need to have an intermediary to think about what features actually matter and how they fit into a broader development roadmap otherwise you risk building a product with lots of bells and whistles no one really cares about that's a beast to maintain.
Similarly not all marketers are “trigger happy with features” a lot of marketers understand how feature work impacts developers and actually take time to figure out the most important features to build and market and don’t have short shelf life.
In my experience you’ve basically just described people bad at their jobs all around.
Following your advice would just be adding potentially unnecessary headcount and creating an unnecessary communication gap between two critical teams, again with a focus on small business or startups. I do think larger companies could do well with less compartmentalization as well though.
When a potential customer has a problem, they go through several hoops before they have any hope of finding a solution. First, they have to recognize and identify a problem. Second, they have to motivate themselves to solve that particular problem over all others.
Once a potential customer has made those leaps, they are potentially your potential customer. That’s when the language leap comes into play. My favourite example is “I built a scraper but it turns out the market wants an automated tool to crawl their entire website and return some data.” Catch what happened there?? I built a scraper but the paying market doesn’t know what a scraper is.
If your language matches up with a potential customer’s language, there is a chance they will see you, pay attention and decide that you could solve their problem. That’s around the time when marketing campaigns will make you question Darwin but try to act surprised…:)
Once you catch that stuff, it’s easier to push back on shitty bloatware marketing feature requests. What’s the real problem here? Does that new feature solve a problem or does it just increase the chances that a potential customer will find you??
If it increases the chance a customer will find you, it might be a good feature. In my experience, it usually means you should do some tech support calls so you can figure out what words your customers use…
Marketing is a dialogue between the producer and the user/prospective user. If the first response to someone trying to be helpful is "No." then that dialogue has been essentially shut down immediately and neither side is going to learn anything.
No one who wants to understand the other side's needs is going to respond that way. So they're showing that they have no interest in marketing what they're working on.
All employee incentives should be aligned around selling more product and lowering cost of delivering said product. The closer that marketing and software work together the more they can empathize with each groups challenges.
Using your example, what makes a product feature essential if it does not in fact sell?
This is just a single data point, but for a view "from the other side", my honest and immediate answer to this question is: "I don't care".
When writing programs, my concern has never been "to deliver a high-impact product". In fact, I find this language very annoying; and saying that my program is a "product" feels like a very offensive insult. The goal is never to deliver a product, much less a high impact product. The goal is always to solve a problem that I have, regardless of whether any other person on earth has the same problem. Now, I may have been given that problem because it was deemed useful to other people, but during the actual act of programming I prefer to make an abstraction of that and focus only on the problem itself.
EDIT: I appreciate that there are managers and such that keep proposing meaningful problems. I also like to find problems myself, and sometimes I appreciate when (rarely) they turn out to be shared with others, who in turn are happy that I solved them. But this is always a happy secondary effect, never the main goal.
For hobby projects, I agree with you whole-heartedly.
The thing is, things are products. But the answer isn’t “all hackers are wrong, you’re dumb for not involving me early on.” Rather, the answer is ‘chill, you’ve got this.’
We don’t need a product placement meeting before we type git -m commit “First commit” and if we did, the bast majority of cool things would never have been built. Sometimes we just build because that’s what builders do.
When I am working for someone who is paying me, though, I am only building for one reason; to deliver value to my employer. That is the entire reason I am being paid. I build for other reasons at other times.
I really hate working with other developers who think like you do. It is so hard to work with people who care more about the code itself than what it is for. We aren’t working for the same goal, and sometimes the beautiful code actually makes it harder to accomplish our actual goal.
First, this doesn’t do anyone any favours. Second, if marketing types would stop being such know it alls, you would have an easier time interacting with developers while they’re building something. Third, marketing isn’t special. And finally, you don’t even understand how or why developers build things.
Be nice and build developers up, especially on a thread with a bunch of people sharing their innermost fears. This whole “you’ve been wrong since the beginning; the cure is me” is terrible marketing. Not to mention that it’s cruel.
Be decent to hackers.
You are not exactly making developers look good here.
I think marketers and developers need a stronger culture between ourselves. The tools of marketers (data mining, consumer behavior analysis, surveys, market testing, etc) aren't just a veneer to be applied at the completion of a development project. Marketing, when done correctly, informs UX. Marketing can provide developers with insights into the problems they should try to solve.
From what I can tell, many developers view the development process as a sacred protected space for creation. This is not the optimal means to delivering a high-impact product. Developers should be asking themselves during the development process: "Is this feature going to excite a group of users, and do we have some statistical mechanism to predict that excitement?"
When you create something that you already know will excite people, the product launch becomes much simpler.