7 ms·
Weirdly, almost exactly 20 years ago, I sat next to somebody at a wedding who had an almost-identical story about cleaning up after an SAP rollout, but all of t
by wpietri 7y ago
Weirdly, almost exactly 20 years ago, I sat next to somebody at a wedding who had an almost-identical story about cleaning up after an SAP rollout, but all of the numbers had an extra zero or two. It amazes me that what the SaaS shift appears to have achieved is that now much smaller companies can get stuck in the same "solve everything" money pit.
But I guess the fundamental problem hasn't changed: executives want to believe in magic solutions that give them all the feelings of control with none of the actual work. With no regard for actual operational efficiency, and no need to hold themselves to the ROI standards they'd demand of others.
- zbentley 7y ago> executives want to believe in magic solutions that give them all the feelings of control with none of the actual work Corollary: R&D wants to believe they can build magical solutions that solve all the problems--solutions that will scale better and cost less to keep up than off-the-shelf ones made by people with extensive domain expertise--in a week or two, promise. As with most things, the problem is complicated, deeply human, and answers lie somewhere in the middle.
- abakker 7y agoI agree with this wholly. I very much doubt that many people are building tools in bad faith to consume money. It’s just that in the end, “solve everything” means implementing 10:1 weird hacks for edge cases vs actual features that companies all have in common.
- com 7y agoThat works both ways. 70% of features are common with other businesses, but the feature set is pretty diverse. My experience is that internal folk with a good understanding of the business hit 90-95% of the requirements without implementing the 200% of non-relevant broader industry requirements. YMMV.
- CuriouslyC 7y agoThe off the shelf solutions are designed to fit everyone, while bespoke solutions are designed just for you. A lot of the complexity in off the shelf software is that generality that might never be needed.
- frankzinger 7y agoSo true but very rarely expressed. And often the features you need are much easier to implement than you might have expected and, due to the generalisation complexity, hacking on the off-the-shelf product often much more difficult.
- chriscappuccio 7y ago20+ years ago, same for Seibel
- saber6 7y agoDid you ever consider there are actual benefits to SAP, Salesforce, and Netsuite? Step out of the tech mindset for 2 minutes.
- specialist 7y agoMaybe we'd all do better de-digitizing our processes. Return to paper. -- I've been struggling to articulate a thesis, for way too long. But here it goes. Complexity catastrophe occurs when cost of change outweighs benefit. Or simply can't be done in time to make a difference. Whereas databasization makes processes inflexible, humans are relatively more flexible. Like being able to make notes on forms, or quickly modify a form and make more copies to use. -- I'm heavily influenced by process and methodology ideas. Deming, Drucker, TPS, etc. As well as their critics. Postman, Norman, etc, and most recently David Graeber. Graeber's notions about bullshit jobs and bureaucracy have articulated many of my misgivings as well as made me feel stupid for my hubris. -- Both database and paper mediated systems have pros and cons. In defense of younger self, we were not fully aware of the costs and limitations of databases, so couldn't properly weigh the options. Worse, my entire career, I tried to mitigate, engineer workarounds to databases, not willing to accept the problems are intrinsic and not just artifacts of suboptimal implementations. Basically, clap louder and Tinkerbell will fly. Embarrassing. -- My notion of "complexity catastrophe" comes from Design Rules: The Power of Modularity. I may have just coined "databasization". I've long accepted the difference between digitization and automation. Moving processes from paper to computer mediated vs removing judgement (aka process reengineering). But have never found a succinct way to explain it. Maybe "databasizition" makes the distinction more clear. -- Thanks for listening.
- gmueckl 7y agoOne of the first things I got told about databases is that you may build the most beautiful database schema for the domain, but it will never be able to be complete. For the applications that I designed so far, that meant that I always made room for intentional loopholes like free-form comments or ways to override hardcoded processes. It is not 100% perfect and foolproof, but it made using these applications a lot less painful in practice. A wholesale return to paper is like trying to put the genie back into the bottle. It is really about how rigid a process can become without becoming a barrier or burden.
- specialist 7y agoSuperior strategies like this are like hidden lore. Why is that? I'm certain there are dozens or hundreds of these hard won lessons. I had to rediscover the "INSERT only, no UPDATEs" trick on my own. Changed from separate truth and historical tables to a single table which is groomed over time. Major simplification. A few extra benefits: like scaling, testing and auditing. And my peers absolutely lost their minds. A senior VP rolled back my architecture the moment he could. (We were acquihired, so this meant major upheaval of systems which had be in use for over 3 years.) My solution was just too weird looking, too unorthodox. So while there's lots of things we can do to mitigate databasization and buy ourselves some head room, we don't. Square peg, round hole? My radical (unoriginal) thought is the problem is the people, not the tools.
- o-__-o 7y agoIt’s vendor lock-in pure and simple. In my org, I make sure there is data portability. Even if we have to write the plumbing between services, we understand and own the data and an interface to access it is available. This argument applies to open and close sourced software alike (ever try to migrate from MantisBT to Jira?)
- cosmodisk 7y agoSome years ago, shortly before my manager asked me to join the company he was working for, they embarked on a mission to find an implementation partner to get their Salesforce system off th ground into a new level. So the business owners and him discussing how they'll pick the right consultancy. My manager says: we'll take those who will tell us that we talk nonsense instead of nodding head after every single word we say. I then joined the company and ended up in the meeting,where initial plans were discussed. My manager says: we want x,y,z,etc. The consultant says: OK, let's be realistic first: let's learn how to walk and then we may discuss whether you should be launching rockets to space. All these SAP, NetSuite and other corporate software get bad name because of poor implementations and not because the software itself is bad.
- Aeolun 7y agoI dunno, every time I interact with anything SAP or Oracle I am reminded of the fact that the software itself is bad.