3 ms·
This is addressed to organizations with large internal IT organizations, where software is not an external product. That's a classic problem. Thinking of in-ho
by Animats 4y ago
This is addressed to organizations with large internal IT organizations, where software is not an external product. That's a classic problem.
Thinking of in-house software as a product is not all that useful. It's not a product. It does not have real pricing. You can't sell more of it and increase the customer base. You can't drop money-losing products. Cost centers do not have the same incentive structure as profit centers.
Here's a classic memo on that subject.[1]
[1] https://www.fourmilab.ch/autofile/www/section2_40_3.html https://www.fourmilab.ch/autofile/www/section2_40_3.html
- disgruntledphd2 4y agoAs an aside, that document is fantastic, I'd never seen it before, went to the start, and now I'm finding it very difficult to stop reading.
- jdougan 4y agoThe Autodesk File is fabulous. Timeless advice in many places, alternating with interesting glimpses of the early software industry. For that matter there is a bunch of interesting stuff at the fourmilab site.
- AyyWS 4y agoSo this is like the opposite of Amazon, who rents out their previously internal only systems?
- quadrifoliate 4y agoI couldn't disagree with your points more, so I'll address them in detail. Thinking of in-house software as a product is useful at modern, flexible companies; and here's why: > It does not have real pricing. It absolutely does have real cost pricing, in terms of the number of engineers working on it! This is why internal tools or developer productivity teams at the typical Dunder Mifflin Paper Company style orgs are chronically underfunded, and generally seens as a joke by the business people — which naturally leads to bad hires and a generally weak effort in that direction. It's self-fulfilling downward spiral. A bunch of modern companies counteract that by treating internal tools and developer productivity as a product, which communicates not just the cost, but also the effective advantage that the company gains, and improves it over time just like the company's external-facing products would. > You can't sell more of it and increase the customer base. There are innumerable exceptions, but a single 27 billion dollar one is Slack, which started off as an internal tool [1] for Stewart Butterfield's company Tiny Speck. > You can't drop money-losing products. Wrong! In fact, you can absolutely drop "money-losing" products that don't have enough internal customers, and do a much better job than a tired team without a product mindset complaining that "no one uses this tool anyway" as they try to fix a ticket that was filed 7 years ago. > Here's a classic memo on that subject I don't know about "classic", it seems to be the experience of one company selling proprietary software that was founded 40 years ago, and very likely has a captive market due to a first mover advantage. I strongly counsel anyone starting out today against having over-applying this narrow "What business is the company in" mindset. In my experience, it encourages frat-house "I am working on the real product" attitudes, and destroys internal productivity, because zero people are incentivized to think positively about that. ---------------------------------------- [1] https://en.wikipedia.org/wiki/Slack_(software)#History https://en.wikipedia.org/wiki/Slack_(software)#History