6 ms·
> You’ll lose your best developers So what? If you have paying customers and the software "works" this isn't a huge downfall. New, young and challenged develop
by mbesto 14y ago
> You’ll lose your best developers
So what? If you have paying customers and the software "works" this isn't a huge downfall. New, young and challenged developers will gladly follow in the foot steps of seasoned coders before them.
> Recruiting will get harder
This is a problem for every company with developers. As long as you have paying customers, recruiting isn't as big of a problem as people make it out to be. Is this a problem for places like Google and Facebook? Sure. For you start-up, probably not. Software challenges tend to trail off towards the latter part of the software's life cycle. If there is a new piece of functionality required then smart developers will simply find the tools, frameworks, libraries, they need to solve that problem. They don't need this dictated to them.
> Productivity won’t improve
You also are inherently decreasing their productivity by teasing them with new technologies that may never be used. You can also clearly quantify their loss in productivity when they spend time on new technologies. I'd prefer to measure the measurable and manage that, rather than half guess a "innovation debt" that I'll never be able to manage properly.
> Your software will get stale
Are your customers still paying? Good, get over this aspect then. Software that doesn't change always goes stale.
It happens when the team is too busy putting out fires and finishing up features to keep up to date with advances in languages, frameworks, libraries, tools and processes.
What about the increased costs (real actual currency HR costs) that are included in constantly taking your resources off the software maintenance and delivery for a product/service that real people are paying for. There are some serious implications with letting people's innovative brains wander too far when given a specific task to accomplish. This is why hackathons and "FedEx" days are so popular. It's a mutual agreement between employer and employee that says: "You are allowed to hack something together with new exciting technology but I cannot guarantee it will reach the production stack"
I think this idea of innovation debt is a clear non-problem for me and most web based startups in my situation.
- eitally 14y agoThis idea is not aimed at startups. It's a huge problem for large enterprises, albeit less so for product companies than for captive IT orgs creating internal systems & utilities. If you, or anyone else, would like specific examples from one company -- along with discussion of remediation attempts -- feel free to email me. When the economy went south in 2007/2008 we dismissed about 18% of our global IT org and didn't start to rebuild until late 2011. Those 3+ years of stagnation nearly killed several business critical systems.
- mbesto 14y agoFair enough -- loads of enterprise IT and IT software experience on my back... captive IT orgs creating internal systems & utilities. Again, so what? These are _costs_ centers and therefore treated as such. As long as the accounting team can add to the general ledger and the trucks ship the goods, the company doesn't go broke and people get paid. If you need innovation for your company to survive, then you do the innovator's solution - create an organisation outside the rules and realms of your existing structure to innovate. This is all too wishful and pie in the sky type thinking.
- eitally 14y agoI should have been clearer: innovation debt when combined with technical debt is the issue. When the internal systems stagnate and become a) unstable, b) un-supportable, c) un-upgradable, there is a direct impact to business operations, and escaping from the cycle is time consuming and painful. I did exactly as you suggested, btw, and created a team whose explicit charter is innovation & directed R&D.
- mbesto 14y agoAgreed. Feel free to get in touch if you wanna discuss further. (details in profile) I've seen this type of thing pretty much everywhere. c) un-upgradable, there is a direct impact to business operations I'd love to know how to measure this. Any VP of Tech/CIO would be fired if this happened.
- Retric 14y agoThinking in terms of skimping on 'cost centers' is stupid. From the development side nothing changes when managing software for internal use vs. selling that same software. What people forget is if your internal software improves in functionality you capture 100% of that value, the only problem is assigning that savings to the software vs the shipping department or whatever. What is often forgotten is time is the hardest thing to gain in software development. 1 person for 10 years can get a lot more done than 10 people for 1 year.
- pnathan 14y agoI don't want to get into an extended discussion, but in my opinion, most web based start ups don't do innovation. They build a small service people want and then 'coast' quite profitably and happily on that. The heavy duty R&D and innovation requirements start coming into play for different sorts of shops. E.g., enterprises or r&d-driven consulting shops. If you don't have R&D/innovating driving improvements to your products, you will wind up dead in the water.
- mattgreenrocks 14y agoWhich is funny, because they often bill themselves as 'changing the world.' There is a distinct dearth of R&D-to-product shops, and our industry suffers greatly for it. Intellectually, some people need more than displaying a DB on a web page, no matter how profitable it is at this time.
- setrofim_ 14y agoThis is a very short-sighted view. While losing great devs will not put your company out of business over night, it may start a death spiral that it will be very difficult, if not impossible, to recover from. Hiring may be easy for you now, but once your start up starts falling behind the curve, if will suddenly look a lot less attractive to new talent. > If there is a new piece of functionality required then smart developers will simply find the tools, frameworks, libraries, they need to solve that problem. They don't need this dictated to them. What smart developers? They have all left to work for your competitor. Besides finding the right tools, frameworks, etc takes time, which is precisely what this article is arguing for. > Are your customers still paying? Good, get over this aspect then Your customers will stop paying when something better comes along. And it will come along because, unlike your company, others are innovating. > You also are inherently decreasing their productivity by teasing them with new technologies that may never be used. Maybe, but not by as much as you'd think. Looking into new technologies may often improve productivity with the technology currently being used (by bringing in ideas from the new tech). > What about the increased costs (real actual currency HR costs) that are included in constantly taking your resources off the software maintenance You don't have to constantly take resources off. Just occasionally. A day-long hackathon a year, and a couple of lunchtime sessions a moth is really not that much. > I think this idea of innovation debt is a clear non-problem for me and most web based startups in my situation. The thing about innovation dept, like architectural debt, is that it doesn't become a problem until it is too late to do something about it.
- mbesto 14y agoThe thing about innovation dept, like architectural debt, is that it doesn't become a problem until it is too late to do something about it. And do you believe this is seriously something that is killing companies left and right? You know what kills companies? Cashflow.
- setrofim_ 14y ago> You know what kills companies? Cashflow. That, in turn, gets (eventually) impacted by innovation debt. > And do you believe this is seriously something that is killing companies left and right? No, not at all; and I don't believe the author of the post does either. There is a whole bunch of things that can kill a company (especially a startup), and a lot of them are going to be bigger and more urgent then innovation dept. You should definitely focus on dealing with those. However, innovation dept should not be dismissed entirely, especially since it doesn't take much to offset it.
- geddesign 14y agoPlease post where you work so we can steer clear.
- chadmaughan 14y agoHis profile lists "CEO/Co-Founder of competehub.com and ignitelab.net" The irony, of course, is the tagline used at ignitelab.net is: "Ignite Your Innovative Internet Business Idea Right Now"