Perhaps I simply don't understand what you mean, but it sounds like the first point could be rephrased in some way. To me, workflow integration and data privacy sound very much like technical blockers.

▲

barrenko 3 days ago | parent | next [-]

But if you define them as non-technical related blockers agents are just swell.

▲

advikipedia 3 days ago | parent | prev | next [-]

More than the "actual" problem, the "perception" of the problem is worse. Workflow integration is more to do with users having to rethink their workflows, their roles, and how they work with AI. As for data privacy concerns, even where startups have taken measures to overcome the problems, very often enterprises still remain concerned (making this more of a perception problem than an actual problem). That's why I focused on the non-technical aspect of it!

	▲	DrScientist 3 days ago \| parent [-]
		When I see vendors complain about workflow and integration issues, it's because the vendors software is written around an expectation of a certain workflow and integration points and they find out in reality every customer does it slightly differently. Some key challenges around workflow are that while the fundamental white-board task flow is the same, different companies may distribute those tasks between people and over time in different ways. Workflow is about flowing the task and associated information between people - not just doing the tasks. Same goes for integration - the timing of when certain necessary information might be available again not uniform and timing concerns are often missed on the high level whiteboard. Here's a classic example of ignoring timing issues. https://www.harrowell.org.uk/blog/2017/03/19/universal-credi...

▲

refactor_master 3 days ago | parent | prev | next [-]

Consider this simple example: Storing all your sensitive user data in one centralized location (e.g. a US server) would be great for any kind of analytics and modeling to tap into, and is technically very easy to do, but it also violates virtually every country's data privacy laws. So then you have to set up siloed servers around the world, deal with data governance, legal stuff, etc.

Sure, it then becomes a technical challenge to work around those limits, but that may be cost/time prohibitive.

▲

1718627440 3 days ago | parent [-]

That sounds more like, that you can solve the problem, when it would have other requirements.

	▲	refactor_master 3 days ago \| parent [-]
		If you ask Silicon Valley, any organizational problem can be a technical problem if you try hard enough.

▲

IanCal 3 days ago | parent | prev [-]

There are two sides to workflow integration.

One is technical (it’s a hassle to connect things to a specific system because you’d need to deal with the api or there is no api)

The other isn’t, because it’s figuring out how and where to use these new tools in an existing workflow. Maybe you could design something from scratch but you have lots of business processes right now, how do you smoothly modify that? Where does it make sense?

Frankly understanding what the systems can and can’t do takes at least some time even if only because the field is moving so fast (I worked with a small local firm who I was able to help by showing them the dramatic improvements in transcription quality vs cost recently - people here are more used to whisper and the like but it’s not as common knowledge how and where you can use these things).