4 ms·
But this is a double-edged sword, is it not? I mean, "the site the developers want to build" will invariably be a site with no ads whatsoever. It loads so fast!
by smacktoward 11y ago
But this is a double-edged sword, is it not? I mean, "the site the developers want to build" will invariably be a site with no ads whatsoever. It loads so fast! Look at how clean the code is! Then everybody loses their job because there's no actual revenue.
In theory, reconciling these opposing forces should be what top management does. In reality, top management is usually too terrified to do so, because they're subject to the same pressures the sales people are: they have corporate masters of their own, demanding a revenue chart that always drives up and to the right, who will cheerfully throw them overboard the moment they appear to not be 100% behind that goal. So it's ads ahoy and UX take the hindmost.
- notjustanymike 11y agoAgreed - and there have to be ads on the site. The problem is that user experience is always sacrificed for short term profit. The same people who sold a 6 month 300x600 scabies home page takeover (seriously...) wanted to know why our returning user rate was so low. Developers want to build and experience people will return to, while Sales and Product will sacrifice anything for short term gain.
- emodendroket 11y agoWell it'd be a pretty unusual graph if it did not go to the right.
- Chinjut 11y agoStop drawing revenue, and the graph _will_ eventually stop going to the right...
- morgante 11y ago> I mean, "the site the developers want to build" will invariably be a site with no ads whatsoever. I think that's shortchanging developers. They know where the money is coming from and if the company has good incentive structures (ie. equity) want to make sure revenue grows as well. Fortunately, developers are also aware of the cost which is associated with every third-party tool included on the page. That's why it's really important to include someone technical in any deal conversation as early as possible, and they need to have the ability to block a deal which would substantially degrade the user experience. They can also weigh different providers by their implementation cost to users, which is crucially important: a sales guy loves to hear "just one line of JS" but I'd much rather use a REST API. The key to getting this sort of control and buy-in is demonstrating to management the fact that page load time has a direct effect on traffic (and thus revenue).