Loading video...

Video Failed to Load

Go Home

Databricks Chief AI Scientist Jonathan Frankle (Jonathan Frankle) says the bottleneck to enterprise AI adoption is evals, not models. "The models are good enough at a lot of really complex enterprise tasks and knowledge tasks" "the real challenge is describing what you want AI to do and knowing whether...

28,166 views • 9 days ago •via X (Twitter)

23 Comments

Calvin Luttrell's profile picture
Calvin Luttrell9 days ago

@jefrankle @mercor @BrendanFoody Corporate politics is the biggest bottleneck. The solution to adoption is mayhem.

Mike Fishbein's profile picture
Mike Fishbein9 days ago

@jefrankle @mercor @BrendanFoody haha true

Jay's profile picture
Jay9 days ago

Agree. The 'describe what you want' half is mostly a modelling problem. If the business entities, states and rules aren't written down anywhere (an ontology, basically), you can't write evals that mean anything to the business. Do you see clients who focus on modelling business logic rather than dumping more text into the agent?

Augusto Marietti | API father's profile picture
Augusto Marietti | API father8 days ago

@thinkshiv @jefrankle @mercor @BrendanFoody Somewhat. More that the execution path is blocked or not discoverable (different apis, mcp, data lakes, tools, systems, clouds).

Counterparty's profile picture
Counterparty8 days ago

@jefrankle @mercor @BrendanFoody The models aren't good enough yet. They still hallucinate on enterprise data and fail at multi-step reasoning under pressure. Both model quality and evals need work, not one or the other 🤷‍♂️

Earnest Pen's profile picture
Earnest Pen8 days ago

@jefrankle @mercor @BrendanFoody Describing what you want is basically writing a spec, and most teams never wrote one for knowledge work because a person quietly filled the gaps. The eval ends up being the first honest job description.

lonny's profile picture
lonny9 days ago

@jefrankle @mercor @BrendanFoody Welcome to me TED talk

Jayesh Jawandhia's profile picture
Jayesh Jawandhia9 days ago

@jefrankle @mercor @BrendanFoody Agree. Once models are good enough, the hard part is defining 'correct' for your own tasks and checking it every time. Evals built on your own data are what turn a demo into something a team can trust

Web制作出身のAI・Webアプリ開発者's profile picture
Web制作出身のAI・Webアプリ開発者8 days ago

@jefrankle @mercor @BrendanFoody モデルの精度だけ上げても、現場の依頼をどう評価するかが曖昧だと導入判断できないんですよね。まず「何をもって完了か」と例外時の扱いを決めて、小さく実データで確かめるのが結局近道だと思います。

Mike Fishbein's profile picture
Mike Fishbein9 days ago

full pod

Caliber's profile picture
Caliber8 days ago

@jefrankle @mercor @BrendanFoody i'd give the 'knowing whether ai did it' half to the people who did the task by hand, not a central ai team. the person who ran the month-end reconciliation for years can spot a wrong agent output in a minute.

Wayne Sutton's profile picture
Wayne Sutton8 days ago

@jefrankle @mercor @BrendanFoody @mikeysee 👀

Dhruv Jain's profile picture
Dhruv Jain9 days ago

@jefrankle @mercor @BrendanFoody describing what you want is the part nobody budgets time for most teams can't say what a good output looks like until they've seen a bad one lol

Mike Fishbein's profile picture
Mike Fishbein8 days ago

@jefrankle @mercor @BrendanFoody Yep common for small biz getting at to do new things

Dhruv Jain's profile picture
Dhruv Jain8 days ago

@jefrankle @mercor @BrendanFoody yeah and small biz has it worse because the owner is usually the only one who knows what good looks like do they get clearer after the first bad batch or just more annoyed

Deus Machina's profile picture
Deus Machina8 days ago

@jefrankle @mercor @BrendanFoody He wanted to say "verification" I guess.

Nick P.'s profile picture
Nick P.8 days ago

@jefrankle @mercor @BrendanFoody So much institutional knowledge is muscle memory for tenured employees. Things they’d never think to put in a prompt. So the ai literally has a partial script to follow and 0 experience. Results won’t follow this.

Abhi | FabMeet's profile picture
Abhi | FabMeet9 days ago

@jefrankle @mercor @BrendanFoody same thing in outbound. the writing is fine, nobody wrote down who the buyer actually is. describing the target is most of the job

ClientPulse's profile picture
ClientPulse9 days ago

@jefrankle @mercor @BrendanFoody describing what you want is the hard part for people too tbh. half the briefs i've seen handed to a new hire would fail an eval

Prem Balwani 🚀's profile picture
Prem Balwani 🚀9 days ago

Describing the work is the hard part. Rethink it from first principles with AI at the center, or you end up with a pilot that never makes it to production. Then put the exceptions and ground truth in place as evals, so you can measure whether it works. This is where forward deployed engineers earn their place. They're curious, and they surface the deep organizational truth that ops teams never have time to write down.

🤠Fren's profile picture
🤠Fren8 days ago

@jefrankle @mercor @BrendanFoody That’s weird take… if you give smartest person goal he will find a way and define all things… What a nonesense these people say

The Logic Atelier's profile picture
The Logic Atelier9 days ago

@jefrankle @mercor @BrendanFoody On the "knowing whether AI did it" half: run each case more than once. IBM Research's ALTK-Evolve write-up had a retail agent averaging 78.1%, but 57.5% when a task only counts if all 4 runs succeed. Enterprises live with the second number.

Supply Chain 10X's profile picture
Supply Chain 10X9 days ago

@jefrankle @mercor @BrendanFoody Models are often good enough. What’s scarce is knowing exactly what “good” looks like and being able to measure it. Like having a skilled cook but no one who can taste the food. Judgment is the current bottleneck.

Related Videos