Every few weeks, another AI company announces a model that “reasons better.” The demo is polished. The benchmarks are impressive. The blog post says something like “state-of-the-art performance on complex reasoning tasks.” And every time, thousands of workplaces quietly ask the same question: Should we believe this?
The answer, based on the most rigorous independent testing we have, is: believe it cautiously — and test it against the tasks that actually matter for your job.
Here’s what the evidence says about where AI reasoning is strong, where it collapses, and what you should test before you trust a new model with anything important.
What the Independent Benchmarks Actually Show
The most important development in AI evaluation over the past year is that researchers have stopped testing models on trivia and started testing them on real work.
UC Berkeley’s Agents’ Last Exam (ALE) is the most ambitious of these. It contains more than 1,500 tasks designed by 300+ experts from 55 professional fields — finance, law, medicine, engineering, education, and more. Every task is derived from a real project that a human expert previously completed, converted into a verifiable evaluation with objective grading. No vibes. No human judges. Fully reproducible.
The results are sobering. No model exceeded a 24% success rate across the full set of tasks. On the hardest tier — tasks requiring sustained reasoning, deep domain expertise, and reliable execution over long horizons — every frontier agent tested achieved a 0% success rate .
GPT-5.5 ranked first at 24%. Other advanced models, including Anthropic’s Fable 5 and Cursor’s Composer 2.5, failed on most tasks they were given .
Harvard Business School’s BusinessCaseBench tells a similar story from a different angle. It uses business school case studies — the same method used to train MBA students — to test analytical reasoning. Models score well on partial credit: Claude Sonnet 4.6 hit 88.4%, GPT-5.4 reached 87.2%. But under stricter “complete answer” scoring, where every rubric criterion must be met, those same models scored 49.6% and 47.6% — meaning even the best model failed to fully satisfy the rubric on more than half the questions .
Mercor’s APEX-Agents benchmark tested models on real tasks from consulting, investment banking, and law. The best models struggled to get more than a quarter of the questions right. The biggest stumbling point: tracking down information across multiple domains — Slack, Google Drive, email, and other tools — which is how real knowledge work actually happens .
And WorkArena++, a benchmark of 682 realistic knowledge-worker tasks, found that current models face “several challenges” in serving as useful workplace assistants, particularly when tasks require compositional planning and contextual understanding .
What This Means: The Gap Between “Good Draft” and “Finished Work”

The pattern across all these benchmarks is consistent. AI models are excellent at generating first-pass analysis. They can summarize, draft, outline, and produce plausible-looking work product. They are not yet reliable at completing the full task — especially when the task requires:
Sustained reasoning over time. ALE’s hardest tier requires continuous reasoning, broad knowledge, and reliable execution over hours or days. Every model scored 0% .
Multi-source information synthesis. APEX-Agents found that models struggle to track down information across multiple tools and platforms — the way real professionals actually work .
Adaptation to uncertainty. The Berkeley researchers noted that the models’ main weakness is not a lack of data but a lack of “practical experience managing complex workflows that require flexibility, the ability to change strategy while working, and adaptation to specific failures” .
Judgment under incomplete information. BusinessCaseBench was designed to test exactly this: can AI “stay with a complicated business problem long enough to interpret messy evidence, weigh competing priorities, exercise judgment under uncertainty, and arrive at a recommendation that can be defended?” The answer is: partially, but not completely .
The HBS researchers put it practically: current models are best treated as “first-pass analyses whose coverage must be checked before they can be considered complete” .
So What Should You Test?
Before you believe a model’s workplace reasoning claim, test it against tasks that mirror the actual complexity of your job. Here’s a framework based on what the benchmarks reveal about where models succeed and fail.
The Five-Task Test

Task 1: The Multi-Step Judgment Call. Give the model a scenario with incomplete information and competing priorities. Ask it to make a recommendation and explain its reasoning. Then check: Does it acknowledge what it doesn’t know? Does it weigh trade-offs, or just pick one? Can it defend the recommendation against a counterargument?
Why this matters: BusinessCaseBench shows that models can produce plausible recommendations but often fail to satisfy all the criteria of a complete answer . The gap between “sounds good” and “is actually correct” is where workplace decisions get made.
Task 2: The Cross-Domain Synthesis. Give the model information from multiple sources — a document, a spreadsheet, an email thread, a policy — and ask it to answer a question that requires integrating all of them. Then check: Does it find all the relevant information? Does it cite its sources? Does it miss something that’s buried in one of the inputs?
Why this matters: APEX-Agents found that multi-domain reasoning is the models’ biggest stumbling point . If your job requires pulling information from multiple systems, test that explicitly.
Task 3: The Long-Horizon Task. Give the model a task that would take you hours — not minutes — to complete. Break it into steps. Ask the model to complete the whole thing. Then check: Does it maintain coherence across steps? Does it adapt when something unexpected comes up? Does it finish, or does it stall?
Why this matters: ALE’s hardest tier requires sustained reasoning over hours to weeks. Every model scored 0% .
Task 4: The Ambiguity Test. Give the model a request that’s vague, contradictory, or underspecified. Ask it to proceed without asking clarifying questions. Then check: Does it make reasonable assumptions? Does it flag the ambiguity? Does it hallucinate details that weren’t provided?
Why this matters: The Berkeley researchers specifically noted that models struggle with tasks that require “flexibility, the ability to change strategy while working, and adaptation to specific failures” .
Task 5: The Error Recovery Test. Give the model a task where you know the correct answer — but introduce a deliberate error in the inputs. Then check: Does it catch the error? Does it proceed as if the error isn’t there? Does it flag the inconsistency?
Why this matters: This is the single most important test for workplace trust. If the model can’t catch a known error, it won’t catch an unknown one. And if you can’t trust it to catch errors, you can’t trust it with anything that matters.
The Evidence Grading Framework
Before you accept a model’s output on any task, ask these questions:
Question | What to look for | Red flag |
|---|---|---|
Did it show its work? | A reasoning trace you can follow and verify | Only a final answer, no intermediate steps |
Did it cite sources? | Links or references to the inputs it used | Claims without attribution |
Did it acknowledge uncertainty? | “I’m not sure about X” or “This depends on Y” | Confident answers to ambiguous questions |
Did it catch the error? | Flagged the inconsistency you introduced | Proceeded as if the input was correct |
Did it finish the task? | Completed all steps | Stalled, looped, or gave up |
Did it adapt? | Changed approach when something went wrong | Repeated the same failed approach |
Was the cost reasonable? | Time and tokens spent vs. value delivered | High cost for low-quality output |
One additional consideration: cost per task varies dramatically across models. ALE found that Fable 5 delivered similar performance to GPT-5.5 while costing roughly 4–12× more per completed task . If you’re evaluating models for workplace use, measure not just accuracy but cost-effectiveness.
A Note on Benchmark Limitations
There’s an important caveat to all this: benchmarks measure what they measure. BusinessCaseBench, for example, gives models one turn, no tools, no retrieval, no clarification. It isolates analytical reasoning, but it doesn’t measure “interactive investigation, negotiation, implementation, or accountability inside real organizations” .
That means benchmark scores are a lower bound on what models can do in a real workflow — where they can use tools, ask questions, and iterate. But they’re also an upper bound on what you should trust without verification. The gap between “can reason” and “can be relied upon” is exactly what these benchmarks are designed to expose.
The HBS researchers also found something interesting: a “cross-model oracle” that selected the highest score achieved by any of three frontier models on each question reached 93% — well above any single model alone . What one model misses, another often captures. For organizations, this suggests that using multiple models to audit each other may be more reliable than betting on a single provider .
What I’m Going to Do With This
I’m going to build a personal evaluation protocol. Every time a new model claims “better workplace reasoning,” I’ll run the same five tasks against it: multi-step judgment, cross-domain synthesis, long-horizon completion, ambiguity handling, and error recovery. I’ll keep a log of the results — not just pass/fail, but where it failed and how it failed.
I’m also going to test models on my actual work, not synthetic tasks. The benchmarks are useful for comparison, but the only task that matters for my job is my job. If a model can pass the Berkeley exam but can’t handle a real client email thread, that’s the failure mode I need to know about.
And I’m going to share the results here. Not as a formal benchmark — I don’t have the resources for that — but as a running log of what actually works and what doesn’t, from someone who has to use these tools to get paid.
No feedback yet — submit the first.