6 ms·
>I didn’t fully understand this as a developer, but it become crystal clear as a product manager. 20 years, I still dont understand how most developers dont un
by ksec 6y ago
>I didn’t fully understand this as a developer, but it become crystal clear as a product manager.
20 years, I still dont understand how most developers dont understand. I guess that is the difference between a developer mindset and product manager mindset.
And hence why lots of startups failed.
- eggsnbacon1 6y agoIn my experience, its usually project managers and sales doing feature driven development while developers beg them to stop. Devs have to deal with all the bugs and messy codebase
- shard 6y agoI think this depends on the culture of the company. In sale&marketing-centric companies, it can be as you described. In engineering-centric companies, engineers sometimes create features and products that customers haven't asked for, and then it's up to sales&marketing to drive adoption, even if it is against customer protests, because the investment needs to be recouped.
- thinkharderdev 6y agoI had had the exact same reaction. My career sometimes feels like a series of meetings in which I implore product managers to keep things simple and consistent instead of adding every bell and/or whistle imaginable.
- tmpz22 6y agoDevelopers are rewarded for features, PMs are rewarded for happy customers. It’s usually that simple. Especially in companies where you are rewarded with promotions and bonuses this value proposition rules the entire product. See for example Google’s entire product portfolio. It’s promotion-driven-development.
- naavis 6y agoI think most developers already have the mindset before working in any company. Maybe the mindset propels them towards computers and software development.
- MattGaiser 6y agoIf you are developing stuff as a hobby, new features are still the reward.
- sanderjd 6y agoYou think? When I do hobby work, the reward is getting to spend as much time as I want tweaking things to be a nice as I want them to be. Which is why I've never made anything, but have had lots of fun and learned a lot.
- jcims 6y ago>Developers are rewarded for features, PMs are rewarded for happy customers. I generally feel that most things are best when they are in some kind of healthy tension. Appeasing power users happens because it appears to align with both of the above.
- MattGaiser 6y agoAs a developer, if someone does not constantly want new features, I am out of a job. Frankly I am better off with aggressive development even if it hurts customer acquisition.
- mhp 6y agoThere is always more engineering work. The questions is does the app need to add new vocabulary type features to get there, or is the work focused on making the API more flexible for 3rd parties, or the signup process less onerous, or making exports take half the time they normally take. There's definitely a balance but they have to be seen as worthwhile and valuable goals instead of adding new words to the object model or new pages to the site. Typical product creation can sometimes be "can I make this thing possible?" instead of "should I make this thing possible or accept that this is not the job of this application". Of course you can make your app do anything you could possibly want... what should it do?
- comeonseriously 6y agoDepends on the dev. I fully understand. But then I'm a minimalist by nature so maybe that has something to do with it. The more knobs and dials there are, not only the more chance for something to break, but more chance for an inconsistent user experience. The latter drives me nuts usually more than the former.
- PragmaticPulp 6y ago> 20 years, I still dont understand how most developers dont understand. Look at the tools developers use throughout their careers: Powerful version control systems that support nearly every operation you could imagine. Command line tools with pages and pages of documented switches. Server software with configuration options for every little thing you could ever want to adjust. Well documented open source software that can be changed to your liking with a simple fork. Websites full of fellow developers freely asking and answering almost any question you might have. When dealing with complexity is the story of your career and you spend 40 hours per week doing this for years on end, it's easy to forget that your customers aren't in the same boat. Most of your customers are using your products to get their job done. They want to learn it quickly, get in, get out, and get back to their work as quickly as possible. They might not even know if they're going to use the same tool at their next job, so taking time to learn it in depth isn't appealing.
- ryandrake 6y agoI've worn both product and developer hats, and honestly the way I see it is: You need to decide whether you are building tools or toys. Neither is bad, but you should decide on one and stick to it for the product. You can make money building tools and you can make money building toys. But you're going to turn away customers if you first make a tool, then turn it into a toy in the name of "simplify" and "making it sleek". As a professional user, I bought a $2,000+ workstation. I expect the applications I run on it to be powerful tools, not toys. But, there are also plenty of other people who run apps on $200 mobile devices who are fine with fewer features. Pick one market and go after it.
- Spooky23 6y agoTrello is what it is. You can pay lots of money for JIRA or something.
- sanderjd 6y agoYou took this in a slightly different direction than I expected, after I was in violent agreement with the beginning of your post. > Most of your customers are using your products to get their job done. They want to learn it quickly, get in, get out, and get back to their work as quickly as possible. This is true, but a missed opportunity. Many people could benefit from more powerful tools to do their work more quickly than currently possible. The "get back to their work" part is the dissonant part; the reason the power tools work for developers is that using those tools is our work, not something we have to leave to get back to it. This should be the case for more people than it currently is. It is not just developers though, there are really powerful tools for a bunch of high-leverage fields, for example image, video, and audio editing, and many different jobs in finance. A lot of the low hanging fruit may have been picked, but I suspect there are huge industries where this sort of thing is still ripe for picking. For instance, I still constantly interact with professionals using awful underpowered tools for their very specialized jobs, for example lawyers, accountants, and teachers.