3 ms·
> Of course, you can achieve the same result with bureaucracy. You just change the forms and the rules. But it takes much effort. Changing software is comparati
by bob1029 5y ago
> Of course, you can achieve the same result with bureaucracy. You just change the forms and the rules. But it takes much effort. Changing software is comparatively easier. There is no need to document the change very much. There is no need to train the staff.
Herein lies the central value proposition of our B2B product stack. With enough validations and required inputs throughout, it is possible to put very complex business processes 100% on-rails.
The value to our customers come from the fact that they can basically hire people directly out of high school and have them accurately manage complex financial transactions for customers on the front line while having virtually zero domain knowledge.
If you are stuck wondering "well how far could we take this?", look to semiconductor manufacturing. I've worked in facilities that are nearly 100% automated. If we can make an entire building that keeps people from doing the wrong thing, there isn't a whole lot that is off the table.
I do see dark patterns that can emerge from this style of software, but at the same time it is impossible to argue with the standardization of outcomes you can achieve if you are willing to go to the ends of the earth in detailing your particular theme park rides.
The biggest complaint is usually from power users, but they typically get to retain some access to more powerful legacy tools anyways.
- cwillu 5y agoReminds me of the retail management system from the story https://marshallbrain.com/manna https://marshallbrain.com/manna
- morelisp 5y agoBroader ethical issues of deskilling aside, it makes no sense to do this for university professors (virtually the definition of an extensively-trained professional) creating course material (a key task they were hired to do).