How do you explain to leaders who do not have a good understanding of software based systems (or honestly may not care to learn) that software development is not one and done? I need to advocate to keep my software development staff - maybe not the full level but they want to eliminate them. Any ideas? I can use analogies but looking for any insights in plain language.
Sort By:
Oldest
Chief Technology Officer in Software8 months ago
This is always a difficult one. The main thing to convey is what they have is a custom product(s)? that needs at the very least, some degree of maintenance. Show hard data that about what systems are in place, what requests are made by the business and who does what when things go wrong. Explaining that the IP of what is there is with the engineers that built it and cannot easily be transferred down the track is probably also a good call. Ultimately it is a business decision about what is needed, but I would show options - keep the lights on only, basic BAU and then what is needed for larger initiatives. If any of your systems are business critical, firing all the engineers with no plan is a bit like that scene in the original ghostbusters where the guy from the city comes in and turns off the power...IT Manager in Construction8 months ago
It may be challenging, but using analogies (like comparing software development to gardening), adopting KPIs and metrics, showcasing the paradigm and needs of CI/CD, among other strategies, and using language that's not too technical yet encompasses necessary technical concepts and expected business outcomes, can be effective.Founder & COO in Services (non-Government)8 months ago
Use the metaphor of building a high performance car. Everyone can understand that. Chief of DevOps and Partner in Healthcare and Biotech8 months ago
Think of software not as a one-time project like building a house, but as a continuously evolving product like maintaining a home. Just as a home needs regular upkeep, improvements, and repairs, software requires ongoing maintenance, updates, and enhancements to remain functional, secure, and valuable. Eliminating the software development team after initial creation is like abandoning a house after construction; continuous investment in the software is essential for its long-term success and usefulness.CTO in Healthcare and Biotech8 months ago
Use Price and Value to let them know the importance of sw development. If the price you pay is high, and the value you receive is greater for the sw dev staff.
Then you might receive a lesser price for downsizing the team, but then you’ll have no value at all for what’s important to the business needs.