Hacker News new | past | comments | ask | show | jobs | submit login

Personally, I would treat the GP's mindset of "inventing workflows" differently than your mindset of redesigning at "poorly designed processes".

Yes, a poorly designed process sucks but it works at some level. That means the rough flow of it is figured out. Yes, there are exceptions and complications and all kinds of odd things but it's fundamentally different. It's not "from scratch" as you're taking an existing working-but-broken process where you know the input, know the output, and rethinking everything in between.

In an "inventing" scenario, you have what you think should be the input, a notion of what the output should be, and you're trying to build towards that notion.. without the validation that you're thinking of it correctly.

The first is a harder social problem (aka getting people to change) while the second is a harder technical problem.




Ultimately you have to build within your sphere of competence. If you have a well-established but inefficient manual process, it may sometimes be the case that burning it down and replacing it with a tech-driven approach might be the best way forward.

But if you are trying to solve a novel problem, and the proposed solution involves "ML will magically predict the future", you'd better have a very good idea of exactly how the problems will be solved, or else you're probably better off starting with good old-fashioned human intelligence.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: