3 ms·
I’m starting to be of the opinion that large companies are impossible to ‘rescue’. Unless you count sustained change over 20 years as a rescue. I swear, there
by Aeolun 7y ago
I’m starting to be of the opinion that large companies are impossible to ‘rescue’. Unless you count sustained change over 20 years as a rescue.
I swear, there are so many exceptions and special cases embedded in a large company that it’s impossible to replace any one product without also overhauling the rest, oh and overhauling customer expectations, because if they’re used to a static website that takes 10s for each page load, then whatever replaces it better takes at least 10s to load.
- julienreszka 7y agoWhat do you mean, why would they not want faster reload time?
- EdwardDiego 7y agoMaybe they wrote an Excel spreadsheet that imports data by scraping the webpage using VBA (don't laugh, it can happen) and they relied on that 10 seconds as part of their VBA code?
- Aeolun 7y agoMy question exactly. Unfortunately getting the actual requirements after the 10 layers of indirection in the enterprise means you just hear the Product Owner say that the requirement is the page load should take 10 seconds. By that point any justification has been long lost.
- rakoo 7y agoI've already had the case of clients complaining when the load time was greatly reduced, because they felt the only way it could have been so fast is that the system didn't do as much as before. Which was true in a way (the best way to be fast is to do as little as possible) but the results were correct so nothing was wrong.
- Shivetya 7y agothe fun I find is there are so many touch points that fixing or replacing gets bogged down in just identifying them. then you are up against each touch points budget and hours availability to adjust to changes you have set forth. one solution I have seem similar to the story's problem was to adapt an edi like solution, there was one group whose entire job was to transform data from group to group and each group in turn had to meet the interchange formats. that can be a political fire storm in itself because the other truth of big companies is that there are many fiefdoms within it and some have a lot of pull.
- C1sc0cat 7y agoI think maybe that problem is that external sites are owned by old school marketing types - who do not have the knowledge and skills required for the 21st century. For example the botched SEO changes ASOS made recently - that actually made the front pages of the financial press in the UK This is my persona opinion and does not imply any connection with my employer.
- dharmab 7y agoYou don't need to fix the whole org. Just the pieces that are currently bottlenecking the org's mission. Part of working with large systems is accepting that it's okay if some of the components suck as long as the objective is still being achieved.
- Aeolun 7y ago> Just the pieces that are currently bottlenecking the org's mission. The problem is that all pieces are interdependent. So you cannot just replace only a single part (of course that’s not always true, but often enough that it might as well be the rule).
- SamuelAdams 7y agoYou're right. But then everyone who wants their systems worked on starts attributing "business value" to each change request. So now you have a huge backlog of changes with made-up points, and each manager says their change is more important than the other's. The only way to get any traction is to get VP level people involved to prioritize which systems to work on. But some VP level people might see you reaching out to them as incompetence - "you can't prioritize your own work?! What did I hire you for!", etc. At the end of the day it's really about the people in the org and how altruistic they are when considering the constraints of the IT dept.