# Your AI Isn't the Advantage. Your Judgment Is - Sid Pednekar

Sid Pednekar

[Talk page](https://ai.engineer/talks/C2-v6wkHXhY-your-ai-isnt-advantage-your-judgment-is) · [Video](https://www.youtube.com/watch?v=C2-v6wkHXhY)

## Where Should an Asset Manager Spend Its Best Judgment?

Sid Pednekar follows two hypothetical research teams from earnings transcripts to portfolio decisions to show why the choice of problem, the knowledge colleagues share, and what they learn after deployment determine the value of AI.

### An analyst can save time before the firm sees a return

[0:23](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=23s)

Dr. Sid Pednekar approaches enterprise AI from asset management. He has spent much of his career in hedge funds and in investment and academic research, building specialized teams around three objectives: improving efficiency, driving profit and loss, and reducing costs. Those objectives give him different ways to assess the same piece of engineering. A tool can help an analyst finish research sooner. Whether the firm spends less to produce that research, or makes a better investment decision because it arrived sooner, requires a different kind of evidence.

The survey figures Pednekar cites illustrate the gap. About 37% of surveyed enterprises reported a positive contribution from AI to earnings before interest and taxes (EBIT). He puts the high-performing group at about 6% and associates high performance with a roughly 5% contribution to EBIT. In other studies earlier in the year, about 66% reported productivity gains, 40% reported cost reductions, and 20% reported revenue growth. These figures come from different studies. They describe the spread of reported outcomes without establishing how often a particular productivity gain translated into profit.

![McKinsey figures on the left show 37% reporting positive enterprise EBIT impact from AI and about 6% qualifying as high performers. A Deloitte bar chart on the right shows reported outcomes for productivity (66%), cost reductions (40%) and revenue (20%).](https://ai.engineer/api/talk-essay-media/189e556a4d73fe48ab9f9e7a3bd90e0a8da05675b5a01afb20cb7a453174fb04)

Everyone has AI. Few are capturing its full value.

To examine the decisions behind those outcomes, Pednekar follows a research analyst at each of two hypothetical asset managers, Company A and Company B. Their workflows are thought experiments. He uses them to develop three practices that an individual, a function, or an entire firm can adopt: design the right problem, build shared capabilities, and compound the advantage.

### More answers increase the demands on judgment

[3:43](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=223s)

Consider the different things a firm can now produce cheaply: software, analytics, recommendations, reports. Each can answer a question or enable an action. An abundance of recommendations still leaves someone deciding which deserve attention. Pednekar defines judgment as choosing what matters and how to act when several answers are plausible. Creativity helps someone identify possibilities worth exploring. Taste helps them recognize good work in a particular context. Weighing tradeoffs lets them choose a course of action.

Those decisions happen throughout a firm. A software engineer chooses what to build, a data scientist chooses what evidence to pursue, and a portfolio manager decides how much weight to give a finding. The C-suite and AI leaders exercise judgment, too, but much of the relevant knowledge sits with the people doing the work. Pednekar’s resource-allocation question is where their best judgment is worth spending. That question applies before anyone chooses a model, a harness, or a copilot.

### Trace the late signal before choosing the tool

[5:28](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=328s)

Company B starts with a copilot and looks through the analyst’s existing work for somewhere to put it. An earnings transcript arrives, the copilot summarizes it, and the analyst receives a shorter document sooner. Once the team discovers that use, it can feed the whole stream of incoming transcripts through it. The benefit is easy to observe. The cost is harder to see. Summarization reduces information, and a detail that disappears in compression may matter to the decision the analyst has to make.

Company A starts with a problem familiar to the people responsible for investments: material signals reach them too late. That wording leaves several explanations open. Perhaps analysts lack the capacity to work through incoming research. Perhaps the underlying data is poor, arrives late, or is unreliable. Perhaps the analyst already has the evidence and the delay occurs when someone must decide what to do with it. Faster reading helps with the first explanation. If the delay occurs after the recommendation is ready, the team needs to look further downstream.

![The upper panel shows Company B’s reports squeezing through a bottleneck toward a lone analyst. The lower panel shows Company A’s reports converging into a few highlighted documents that two people examine together.](https://ai.engineer/api/talk-essay-media/414712a37098b7e2d31eca5663085c73d9e27db81f7fe12c66c134b581e5b703)

Start with right problem.

Locating the bottleneck tells Company A where to direct engineering capacity and analyst attention. It also gives the team a way to assess a proposed improvement: follow the material signal far enough to see whether it reaches the decision-maker sooner. Pednekar connects this selectivity to studies in which leaders concentrated their attention on fewer, higher-quality decisions.

### Fund the research pipeline deeply enough to change it

[8:17](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=497s)

Pednekar recognizes the appeal of experimentation and says he has felt the pull of having too many opportunities himself. Company B runs into trouble when it starts asking how many AI pilots it can launch. It builds a document summarization bot, tries a copilot elsewhere, and adds a data retrieval bot. The firm can count each completed pilot and move on to the next initiative without ever asking whether material signals now reach the portfolio manager sooner.

Company A chooses the end-to-end research pipeline as the unit of investment. Engineering, analytics, AI capacity, and the people who understand the investment decision can all work on the same delay. If the bottleneck moves from reviewing evidence to acting on it, that second step still belongs to the project. Pednekar cites research finding that leaders direct more than 80% of their investment to high-value use cases, including transforming key business functions and creating new offerings.

### Give continuous monitoring an investment thesis to test

[9:47](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=587s)

In Company B’s version, the work retains its familiar order. The analyst receives earnings transcripts and research reports, reviews them, updates a financial model, and sends a recommendation to the portfolio manager. AI can accelerate each handoff. Company A could change the analyst’s first action: ask them to define an investment thesis. Now the system has a proposition against which to evaluate incoming information, including evidence that could refute it.

With a thesis in place, monitoring and evidence gathering can run continuously. The analyst investigates exceptions, decides which developments warrant a deeper look, and weighs the evidence for and against the thesis. This gives a concrete destination to some of the time freed by automation. It also changes the analyst’s responsibility. Their judgment shapes what the research process looks for, as well as the recommendation that comes out of it.

![A linear sequence depicts Company B’s earnings-triggered research. A loop depicts Company A’s continuous thesis monitoring. Two five-step lists identify who does each task, from defining watchpoints to applying investment judgment.](https://ai.engineer/api/talk-essay-media/4e2baee5b64355efd4eb2d0f7b3a501fd807eea01d7ee4c984941e2f46d662a3)

The winners don’t just automate. They redesign.

Pednekar cites research suggesting that high performers redesign workflows more often. In his example, Company B still asks how quickly an analyst can send a recommendation to the portfolio manager. Company A gives the analyst a different job: decide what evidence would change the investment thesis and which exceptions deserve investigation.

### Bring portfolio managers into the build and share what researchers learn

[11:53](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=713s)

Redesigning the research process takes people who understand both the systems and the investment decision. Engineers are moving closer to business decisions, while business professionals are building tools and automations themselves. Alongside forward-deployed engineers and product managers, Pednekar imagines a forward-deployed portfolio manager. Working with the builders, that manager can explain which evidence could change a position. An engineer working with the analyst can see where that evidence loses context. Pednekar connects this collaboration to a broader shift: he cites studies finding that more large enterprises see their technology teams as a source of business growth.

Pednekar describes the design principle as standardizing the core and personalizing the edges. For data scientists, a shared core could include datasets and their semantic layers, which give the data meaning. It should also carry the experience of using them. Which questions has a dataset answered well? Where are its gaps? What tradeoffs did a predecessor encounter, and which approaches failed? Those findings are part of the work a new scientist would otherwise have to repeat.

![Three application columns sit above one shared core. Each has its own methods, processes or priorities, while all share trusted data and definitions, infrastructure, authentication and reusable tools.](https://ai.engineer/api/talk-essay-media/02349d8a6e72d2dcd21dd9bb6a964b12e799c3a601c91e38631b0511716388ac)

A shared core for a research assistant, document workflow and monitoring agent

Scientists can pursue different research questions using that common foundation. An analyst working with a client may need a different workflow again. The practical test for what belongs in the core is what the next person should be able to take as a starting point.

### Follow the agent from the Slack conversation to the ticket

[14:36](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=876s)

Much enterprise software was designed around one person, or a group of people, interacting with one application. An agent may need to gather context in one application, deliberate, and act in another. The quality of the data and the ability to reuse it become constraints on the whole operation. Pednekar reports that 71% of organizations in a study were modernizing core infrastructure to support AI. He also reports that 23% were investing between 6% and 10% of annual revenue in core system modernization.

He distinguishes three types of team agent, depending on what an organization is ready to support. An expert agent makes subject-matter knowledge accessible to colleagues. A workflow agent carries work across systems. His example is a Slack bot that opens and closes tickets: the conversation supplies context for a change to the state of a ticket elsewhere. A chief-of-staff agent takes a wider view, tracking the state of work across the organization and what still needs doing. Each depends on the firm making the relevant knowledge accessible at the scope of the job.

![Three side-by-side cards show an expert agent explaining a metric, a workflow agent running a recurring process and a chief-of-staff agent tracking decisions, owners and next steps.](https://ai.engineer/api/talk-essay-media/8bd33590b364e46d0f85030a82601efc4ee5a20b8a0e9210700f099f32a8409f)

4. Shared context and team agents

### Keep the evidence that prompted a correction

[16:36](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=996s)

Once the workflow is in use, an analyst may catch something it missed. Correcting a recommendation benefits its immediate recipient. Pednekar asks how the next analyst will benefit from the discovery. The correction might supply context that future investigations can draw on, or expose a need for a new tool. In either case, preserving the evidence alongside the lesson lets a colleague judge when it applies. A successful investigation offers the same opportunity to make an individual discovery reusable.

![Arrows trace +18% from an analyst note to a PM summary and then to agent reuse. The analyst’s note says the definition changed in Q2. The summary shortens that caveat, and the agent receives only the number.](https://ai.engineer/api/talk-essay-media/38052c6ba8d5afcbc544cf40a1022b8c111367ffd75fa1fcfd21b9b06e9d25b9)

The number survives. The caveat disappears.

Company A can close that loop by returning to the problem it chose. If continuous monitoring frees analyst time, how much of that capacity goes into investigating exceptions? Do material signals reach portfolio managers soon enough to inform their decisions? These are questions the hypothetical firm would need to measure after deployment. Following them connects the original investment to the next redesign and gives the team a reason to keep learning after the pilot succeeds.

## Key takeaways

- Trace a material signal from its source to the person making the decision. Locate the delay before funding a faster intermediate step.
- Use an explicit investment thesis to guide continuous monitoring, including the search for evidence that could refute it.
- Share dataset meanings, gaps, and failed approaches so the next researcher can begin with what colleagues have already established.
- Preserve the evidence behind corrections and track where freed capacity goes. Both help determine what to change after deployment.

## Slides

### Everyone has AI. Few are capturing its full value.

[1:52](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=112s) [McKinsey figures on the left show 37% reporting positive enterprise EBIT impact from AI and about 6% qualifying as high performers. A Deloitte bar chart on the right shows reported outcomes for productivity (66%), cost reductions (40%) and revenue (20%).](https://assets.ai.engineer/sites/aiecode2025/sha256/189e556a4d73fe48ab9f9e7a3bd90e0a8da05675b5a01afb20cb7a453174fb04.webp)

Everyone has AI. Few are capturing
its full value.

McKINSEY
37%
report positive enterprise
EBIT impact from AI
~6%    qualify as high
       performers

DELOITTE: REPORTED OUTCOMES
Productivity    66%
Cost reductions    40%
Revenue    20%

Access is widespread. Impact remains uneven.
Sources: McKinsey, The State of AI in 2026: On the Road to ROI (Aug. 2026; n=1,719);
Deloitte, The State of AI in the Enterprise (Jan. 2026; n=3,235).

01    Design the right problem    02    Shared capabilities    03    Compound    03
Company A    Company B    A / B

### Build the Competitive Edge

[3:19](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=199s) [Three green numbers introduce the steps in order: design the right problem, build shared capabilities and compound the advantage.](https://assets.ai.engineer/sites/aiecode2025/sha256/d19a43387d3d76bd8387f8c10eb23f20b71343f63ba6be2f7fd2e9df16d505b0.webp)

Build the Competitive Edge

01    Design the right problem
02    Build shared capabilities
03    Compound the advantage

01    Design the right problem    02    Shared capabilities    03    Compound    06
Company A    Company B    A / B

### Intelligence is becoming cheap

[3:47](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=227s) [Below a statement about AI producing more answers, a green question asks what resource is scarce in an abundant world. The answer, “Judgement,” appears to its right.](https://assets.ai.engineer/sites/aiecode2025/sha256/91425a4bf49fc1f59555adfaa655b0f38362366d228b34779e13dbb3dd463543.webp)

Intelligence is
becoming cheap

AI is creating abundance in software, analysis, recommendations, and outputs.
But more answers don’t necessarily create more value.

What is the scarce resource
in an abundant world?    Judgement

01    Design the right problem    02    Shared capabilities    03    Compound    08
Company A    Company B    A / B

### Judgement

[4:24](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=264s) [A definition of judgement sits above three columns. Creativity asks which possibilities to explore, taste asks what good looks like in context, and decisions ask which trade-offs to make.](https://assets.ai.engineer/sites/aiecode2025/sha256/127714a128625277755c94678ff7ebf2cec727200dd4125923ffa2e5467b209e.webp)

Judgement

Choosing what matters and how to act
when there is no single obvious answer.

Creativity
Which possibilities
are worth exploring?

Taste
What does good look like
in this context?

Decisions
Which trade-offs
are worth making?

01    Design the right problem    02    Shared capabilities    03    Compound    09
Company A    Company B    A / B

[10:09](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=609s) [A green box labeled “Judgement” sits between Research and Engineering. Strategy and Product appear above it, Operations and Risk below. Each surrounding box poses a decision for that function.](https://assets.ai.engineer/sites/aiecode2025/sha256/ab580621cdb661bca98b1701ef4f63fcf445f8946012aae983e504464dddaa45.webp)

PART I / Redesign workflows

Strategy
Where should we invest?

Product
What should we build next?

Research
Which evidence
can we trust?

Judgement

Engineering
Which approach
fits the problem?

Operations
Where should we add capacity?

Risk
Which risks are worth taking?

01 Design the right problem
02 Shared capabilities
03 Compound
23
Company A   Company B
B   A

### The ubiquity and scarcity of judgement

[4:49](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=289s) [Two columns pair six roles with questions about what to build, where to add capacity, which approach fits, which problems and risks to pursue, and whether evidence is good enough to use. A green question asks where to spend the best judgement.](https://assets.ai.engineer/sites/aiecode2025/sha256/fec913083afaa157ea3b298c3198e7241b147b1eb772597a5c509a7764e2c43c.webp)

The ubiquity and scarcity of judgement

Judgement runs through the work. Human attention is limited.

CTO
What should we build next?

COO
Where should we add capacity?

SOFTWARE ENGINEER
Which approach fits the problem?

AI LEADER
Which problems are worth pursuing?

PORTFOLIO MANAGER
Which risks are worth taking?

DATA SCIENTIST
Is the evidence good enough to use?

Where is our best judgement worth spending?

01    Design the right problem    02    Shared capabilities    03    Compound    10
Company A    Company B    A / B

### Start with right problem.

[6:03](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=363s) [The upper panel shows Company B’s reports squeezing through a bottleneck toward a lone analyst. The lower panel shows Company A’s reports converging into a few highlighted documents that two people examine together.](https://assets.ai.engineer/sites/aiecode2025/sha256/414712a37098b7e2d31eca5663085c73d9e27db81f7fe12c66c134b581e5b703.webp)

PART I / Target high-value business problems

Start with right problem.

COMPANY B / AI TOOLS FIRST
“Where can we add AI
to analysts’ work?”
More AI use. The research bottleneck remains.

COMPANY A / BUSINESS VALUE FIRST
“Why do material signals
reach us too late?”
Find the constraint. Measure the real payoff.

01    Design the right problem    02    Shared capabilities    03    Compound    13
Company A    Company B    B    A

### 2. Solve the Real Bottleneck

[7:32](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=452s) [Two columns list business and engineering constraints on performance. A question highlighted in green asks whether the work improves what matters.](https://assets.ai.engineer/sites/aiecode2025/sha256/f0b6ed2c5798728af5bcf6fd2d6ef9bd4a0d49684e4011aa1c7b85ce92888081.webp)

Design the right problem
2. Solve the Real Bottleneck

Find what actually constrains performance,
not necessarily what’s easiest to automate.

BUSINESS LENS
Research capacity
Decision speed
Customer conversion
Operating cost

ENGINEERING LENS
Data quality and integration
Latency and reliability
The human review process

Are we improving what actually matters?

01 Design the right problem
02 Shared capabilities
03 Compound
Company A   Company B
B   A

### Leading companies start with the right problem

[7:50](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=470s) [Large figures compare the average number of prioritized AI use cases. Leading companies average 3.5, shown in green on the left, and other companies average 6.1, shown in gray on the right.](https://assets.ai.engineer/sites/aiecode2025/sha256/3d5fa5f88cf1999f55966dd0a6d4944c6ac33f79d4390787169b32a81b27fbb7.webp)

PART I / Target high-value business problems

Leading companies start with the right problem
Average number of prioritized AI use cases

3.5
Leading companies

6.1
Other companies

Leaders are more selective about where they focus.

BCG, From Potential to Profit—Closing the AI Impact Gap (Jan. 2025)
Survey of more than 1,800 executives

01 Design the right problem
02 Shared capabilities
03 Compound
12
Company A   Company B
A / B

### Concentrate AI investment where it matters

[8:47](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=527s) [The upper illustration shows Company B’s scattered pilots as people working separately. Below, a green line connects Company A’s data sources, screens, and team in one shared workflow.](https://assets.ai.engineer/sites/aiecode2025/sha256/9906264363ce41584ccb6efd7fe613950d565d4ed840ef3d9c3b5246ef6c1aaa.webp)

PART I / Concentrate investment

Concentrate AI investment where it matters

COMPANY B / SCATTERED PILOTS
“How many AI pilots
can we launch?”
Many pilots. Limited compounding value.

COMPANY A / FOCUSED PROGRAM
“Which workflow is
worth scaling?”
One scaled capability. Reusable advantage.

01 Design the right problem
02 Shared capabilities
03 Compound
18
Company A   Company B
B   A

### Leaders concentrate AI investment In their highest value workflows

[9:29](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=569s) [A large green >80% gives the share of leaders’ AI investment directed toward transforming key business functions and creating new offerings.](https://assets.ai.engineer/sites/aiecode2025/sha256/03097df7b7b607ac4eeadcfa294adcb5015256aaa89364d68ee0a55cb6d67ccd.webp)

PART I / Concentrate investment

Leaders concentrate AI investment
In their highest value workflows

>80%
of leaders’ AI investment

Transforming key
business functions
and creating new offerings

Concentrate funding where business change matters.

BCG, From Potential to Profit—Closing the AI Impact Gap (Jan. 2025)
Survey of more than 1,800 executives

01 Design the right problem
02 Shared capabilities
03 Compound
17
Company A   Company B
B   A

### The winners don’t just automate. They redesign.

[10:18](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=618s) [A linear sequence depicts Company B’s earnings-triggered research. A loop depicts Company A’s continuous thesis monitoring. Two five-step lists identify who does each task, from defining watchpoints to applying investment judgment.](https://assets.ai.engineer/sites/aiecode2025/sha256/4e2baee5b64355efd4eb2d0f7b3a501fd807eea01d7ee4c984941e2f46d662a3.webp)

PART I / Redesign workflows

The winners don’t just automate. They redesign.

COMPANY B: REACTIVE
COMPANY B / EVENT-DRIVEN
1   Earnings trigger the work   Analyst
2   Collect and read sources   Analyst
3   Update the financial model   Analyst
4   Draft the investment note   AI assist
5   Send recommendation to PM   Analyst

COMPANY A:
CONTINUOUS THESIS MONITORING
COMPANY A / CONTINUOUS
1   Define thesis and watchpoints   Analyst
2   Monitor continuously   AI agent
3   Surface material changes   AI agent
4   Prepare decision scenarios   AI agent
5   Apply investment judgment   Human-led

01 Design the right problem
02 Shared capabilities
03 Compound
24
Company A   Company B
B   A

### Workflow redesign among AI high performers

[11:11](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=671s) [Three large figures compare reported workflow redesign. Nearly 75% of AI high performers redesigned workflows, versus 25% of other organizations, a roughly threefold difference.](https://assets.ai.engineer/sites/aiecode2025/sha256/9e9566e6c2ea3c8118e43d8ac8065a8f24a112a9f62bac37ca11d930d922485b.webp)

PART I / Redesign workflows

The winners don’t just automate. They redesign.

Organizations that fundamentally redesigned workflows because of AI

25%
Other organizations

NEARLY
75%
AI high performers

≈3×
as likely to report
workflow redesign

High performers: defined using reported enterprise financial impact.

Source: McKinsey, The State of AI, 2026.

01  Design the right problem
02  Shared capabilities
03  Compound
25
Company A    Company B
B    A

### Design the right problem — Company B and Company A

[11:25](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=685s) [Two columns contrast the companies. Company B adds AI to existing workflows and moves from project to project. Company A rethinks how work happens and redesigns processes around AI.](https://assets.ai.engineer/sites/aiecode2025/sha256/60b644e3de6fdbf271429b3052bc934bfbf054e71bf07867915afdb01ccaaad5.webp)

PART I / The two companies

Design the
right problem

Company B
Adds AI to existing workflows.
Completes individual projects.
Moves to the next initiative.

Company A
Rethinks how work happens.
Redesigns processes around AI.
Obsessing over the right problem

The difference is how the organization puts AI to work.

01  Design the right problem
02  Shared capabilities
03  Compound
26
Company A    Company B
B    A

### Technology and business are converging

[12:07](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=727s) [Paired columns show engineers moving closer to business decisions and business professionals building tools and automations. A highlighted line calls for designing the business and technology together.](https://assets.ai.engineer/sites/aiecode2025/sha256/2b76323696e02ca6e09e7c81948248c74d45b4414916b4473d3b43c8244f6bac.webp)

PART II / Technology and business

1. Technology and business
are converging

How do we move from one successful workflow
to an organization that can deliver them repeatedly?

TECHNOLOGY
Engineers move closer
to business decisions

BUSINESS
Business professionals
build tools and automations

Design the business and technology together

01  Design the right problem
02  Shared capabilities
03  Compound
28
Company A    Company B
B    A

### Technology is becoming a business growth function

[12:50](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=770s) [A large green 66% highlights the share of large enterprises that view their technology organizations as revenue generators rather than service centers.](https://assets.ai.engineer/sites/aiecode2025/sha256/14be5b5ae922b0a1df5cc91e75a178665676562497500ca2aaab2a13b50f45d9.webp)

PART II / Technology and business

Technology is becoming
a business growth function

66%
of large enterprises view their technology organizations
as revenue generators rather than service centers

Technology leadership is moving closer to enterprise strategy.

Source: Deloitte, 2025 Tech Executive Survey (Nov. 13, 2025), referenced in Tech Trends 2026.

01  Design the right problem
02  Shared capabilities
03  Compound
30
Company A    Company B
B    A

### A shared core for a research assistant, document workflow and monitoring agent

[13:03](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=783s) [Three application columns sit above one shared core. Each has its own methods, processes or priorities, while all share trusted data and definitions, infrastructure, authentication and reusable tools.](https://assets.ai.engineer/sites/aiecode2025/sha256/02349d8a6e72d2dcd21dd9bb6a964b12e799c3a601c91e38631b0511716388ac.webp)

PART II / Standardize the core

2. Standardize the core
Personalize the edges

Different applications should not require rebuilding the same foundation

Research assistant
Individual research methods

Document workflow
Different investment processes

Monitoring agent
Local questions and priorities

SHARED CORE
Trusted data and definitions
Infrastructure, authentication and reusable tools

Shared context supports independent judgment

01  Design the right problem
02  Shared capabilities
03  Compound
31
Company A    Company B
B    A

### How different roles use a shared core

[13:34](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=814s) [Three diagrams each connect a shared core to three boxes. The first branches to an analyst, a team lead and a client team. The second branches to three analysts, and the third to three data scientists.](https://assets.ai.engineer/sites/aiecode2025/sha256/f957127697fed000aec8affe910be1340b144e00c7d0c26c569e7fe7a504da52.webp)

PART II / Standardize the core

2. Standardize the core
Personalize the edges

Shared core
Analyst
Team lead
Client team

Shared core
Analyst
Analyst
Analyst

Shared core
Data Scientist
Data Scientist
Data Scientist

What should the next person not have to rebuild?

01  Design the right problem
02  Shared capabilities
03  Compound
32
Company A    Company B
B    A

### 3. Enterprise modernization and the data bottleneck

[14:34](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=874s) [Two columns contrast a replaceable model with the data access, permissions, tools, orchestration, monitoring and evaluation the organization maintains.](https://assets.ai.engineer/sites/aiecode2025/sha256/ec317297e9d44b2d5d66013084cfd8bffb4ec4cc3b7d60ebebd30ffa76b1d2ef.webp)

PART II / Enterprise systems and data

3. Enterprise modernization
and the data bottleneck

Agents need to retrieve information and act across systems
designed around people using individual applications

THE MODEL CAN CHANGE
A better model
should fit the system

THE ORGANIZATION MAINTAINS
Reliable data access and business context
Permissions and reusable tools
Orchestration and monitoring
Evaluation of what good looks like

The system around the model matters just as much

01 Design the right problem
02 Shared capabilities
03 Compound
34
Company A    Company B
B    A

### Agents need modern infrastructure and usable data

[15:13](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=913s) [A bordered panel shows infrastructure modernization figures on the left and the percentages citing difficulty finding or reusing data on the right. Source notes appear below.](https://assets.ai.engineer/sites/aiecode2025/sha256/87d5e725f17d7fda02af02d4b9ddd8f25dda4d48335b4fe36221b630dfb766c0.webp)

PART II / Enterprise systems and data

Agents need modern infrastructure
and usable data

CORE-SYSTEM MODERNIZATION
71%
of surveyed organizations are modernizing
core infrastructure to support AI

23% of organizations invest
6–10%
of annual revenue in core-system modernization

CHALLENGES TO AI AUTOMATION
48%
cite difficulty finding or discovering data
(searchability)

47%
cite difficulty reusing data
(reusability)

Sources: Deloitte, Tech Trends 2026: The Great Rebuild (71%; 23% investing 6–10%).
Deloitte, Tech Trends 2026: Agentic AI Strategy (48%; 47%, from a 2025 Deloitte survey).

01 Design the right problem
02 Shared capabilities
03 Compound
36
Company A    Company B
B    A

### 4. Shared context and team agents

[15:41](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=941s) [Three side-by-side cards show an expert agent explaining a metric, a workflow agent running a recurring process and a chief-of-staff agent tracking decisions, owners and next steps.](https://assets.ai.engineer/sites/aiecode2025/sha256/8bd33590b364e46d0f85030a82601efc4ee5a20b8a0e9210700f099f32a8409f.webp)

PART II / Shared context and team agents

4. Shared context and team agents

Make relevant knowledge accessible where needed

01
EXPERT
Make know-how accessible.
Explain a metric.

02
WORKFLOW
Execute work across people
and systems.
Run a recurring process across systems.

03
CHIEF OF STAFF
Keep decisions and
commitments on track.
Track decisions, owners, and next steps.

01 Design the right problem
02 Shared capabilities
03 Compound
40
Company A    Company B
B    A

### Build shared capabilities

[16:25](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=985s) [Paired columns compare Company B and Company A across business and technology collaboration, tool reuse, data access and shared know-how. A highlighted line describes what the next team inherits.](https://assets.ai.engineer/sites/aiecode2025/sha256/fda908948b3d59f92668917a836801a6ef9ad5d76f48f68721921e729ec20358.webp)

PART II / The two companies

Build shared
capabilities

Company B
Business and technology work apart.
Each team rebuilds its own tools.
Data access stays project-specific.
Know-how stays with individuals.

Company A
Business and technology co-design.
Teams reuse a shared core.
Data and controls serve every team.
Team agents share context and work.

The next team starts with more already built.

01 Design the right problem
02 Shared capabilities
03 Compound
41
Company A    Company B
B    A

### The individual learned. Did the system?

[16:58](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=1018s) [Company B’s gray timeline shows a single corrected report. Company A’s green timeline connects a validated comparability check to three subsequent runs.](https://assets.ai.engineer/sites/aiecode2025/sha256/8d979c17a4af0233fb99645d10dedbe5ccf4f7406660fa6e9b181ce720ec6361.webp)

PART III / Turn corrections into learning

The individual learned. Did the system?

The same correction can end with a better answer - or a better workflow.

COMPANY B
Fix the answer
The analyst corrects this report.
CORRECTED REPORT
The lesson isn't built into the next run.

COMPANY A
Improve the workflow
Validate the fix. Add a comparability test.
VALIDATED CHECK
Next run    Next run    Next run
Future work starts with the lesson built in.

A validated correction can improve every relevant run that follows.

01 Design the right problem
02 Shared capabilities
03 Compound
45
Company A    Company B
B    A

### The number survives. The caveat disappears.

[17:16](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=1036s) [Arrows trace +18% from an analyst note to a PM summary and then to agent reuse. The analyst’s note says the definition changed in Q2. The summary shortens that caveat, and the agent receives only the number.](https://assets.ai.engineer/sites/aiecode2025/sha256/38052c6ba8d5afcbc544cf40a1022b8c111367ffd75fa1fcfd21b9b06e9d25b9.webp)

PART III / Preserve and curate what you learn

The number survives.
The caveat disappears.

Each handoff can preserve the conclusion while losing its meaning.

ANALYST NOTE
+18%
Definition changed in Q2

PM SUMMARY
+18%
Definition changed...

AGENT REUSE
+18%
No caveat attached

CURATE WHAT SURVIVES
Share validated knowledge · Keep local context · Retire stale assumptions

Compounding requires curation, not just accumulation.

01 Design the right problem
02 Shared capabilities
03 Compound
46
Company A    Company B
B    A

### AI frees capacity. Where does it go?

[17:27](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=1047s) [Two columns compare how companies use freed capacity. Company B produces more reports and tasks. Company A directs attention to judgment, oversight, harder problems and new opportunities. A row below lists four measures of improvement.](https://assets.ai.engineer/sites/aiecode2025/sha256/b7a807fe55528f8979ec9cf4137d9092a8d08251ff106a25f8c7b4667e54f5b5.webp)

PART III / Measure improvement and reinvest

AI frees capacity.
Where does it go?
The critical choice comes after the workflow starts performing better.

COMPANY B
More of the same
More reports. More tasks.
The same allocation of attention.

COMPANY A
Higher-value work
Judgment. Oversight. Harder problems.
New opportunities to pursue.

MEASURE    Quality · Cycle time · Expert capacity · Costs & Outcomes

The goal is a more effective organization - not just a faster system.

01    Design the right problem
02    Shared capabilities
03    Compound
47
Company A    Company B
B    A

### Same AI. Different organizations.

[17:36](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=1056s) [Two columns show how a better model benefits both companies. Company B improves productivity, with much of the progress staying local. Company A redesigns work and builds shared capabilities. On the bottom scale, B sits under “Shared capabilities” and A reaches the end of “Compound.”](https://assets.ai.engineer/sites/aiecode2025/sha256/9693245a4bae9c0930f2ec145edc71990bc3ed28ab322ff70964f61a159f408b.webp)

CONCLUSION / One final comparison

Same AI. Different organizations.
Now a better model arrives. Both companies benefit.

COMPANY B
Productivity improves.
Much of the progress
stays local.
Tools layered on. Projects completed.

COMPANY A
Work redesigned
The organization's
capability compounds.
Shared capabilities built

The advantage is being built to turn better AI into more value.

01    Design the right problem
02    Shared capabilities
03    Compound
48
Company A    Company B
B    A

## Full transcript

[0:12](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=12s) Good afternoon, um, everyone present here. It's, um, it's been a, it's been a great day and, um, an absolute pleasure to be here.

[0:23](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=23s) The topic of my talk today is Everyone Has AI: Who Has the Advantage? I'll be talking about what the orgs that are doing, that are leading in AI with their implementation and adoption, what are they doing differently? Um, and so before that, who am I and what's my POV? So I'm Dr. Sid Pednekar. I am an AI

[0:53](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=53s) technology and data exec in asset management. I've spent most of my tenure in hedge funds and, um, investment and academic research. Uh, what I've done and focused on is lead strategy and build specialized teams towards three main verticals: optimizing efficiency, driving P&L, and reducing costs. So, um, I'll be following the discussion

[1:22](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=82s) ala- a- along with, uh, two hypothetical companies, company A and company B, right in the slider below. Uh, these are hypothetical, um, you know, with, um, with made up workflows, but we'll be following their journey along, um, the rest of this presentation. So everyone has AI. Who has the advantage? Um, before we get started there, first, let's see what the lay of the land is. And

[1:53](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=113s) recent studies have shown that only about thirty-seven percent of enterprises that were surveyed are showing a positive contribution to their EBIT. And only about six percent of those would be qualified as high performers, so that's about five percent contribution to their EBIT. Other studies earlier in the year have shown that about sixty-six percent are saying they're having a productivity

[2:23](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=143s) increase, but only about forty and twenty percent are actually seeing cost reductions and, uh, revenue growth. So as we know, access of AI is widespread, yet the impact remains uneven.

[2:40](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=160s) So

[2:43](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=163s) the question I would ask or how I think about this is really in terms of three verticals. And the way I think about these three verticals should apply to organizations and individuals alike, and it should apply to functions regardless of where you are in that organization. Um, so the three main vertical pillars that I think of are, number one,

[3:13](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=193s) design the right problem. Number two, build shared capabilities. And number three, compound the advantage. Now, before we dive into each of these pillars, there is an idea that I think goes through all these verticals, and I think the best leading firms are taking advantage of that and capitalizing on it. As we know, throughout time, the only constant in this world has been

[3:43](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=223s) change. What's different in the AI and super intelligence era is that intelligence has become cheap. Regardless of what your unit of intelligence is, whether it be software, analytics, recommendations, reports, AI is creating an abundance in all of it. And, um, as we know, more answers don't necessarily create more value. So what is scarce? What is the scarce

[4:13](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=253s) resource in an abundant world?

[4:17](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=257s) What, what are companies taking advantage of, the leaders at least? It's judgment. What is judgment? Judgment is choosing what matters and how to act when there's no single obvious answer. It's the creativity that lets you explore what possibilities are worth exploring. It's the taste that tells you what good looks like in a given context. It's the decisions where you can weigh what trade-offs are

[4:47](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=287s) worth making. Judgment is ubiquitous. It exists throughout your organization on a daily basis. Your C-suite... The C-suite is asking questions, taking advantage of judgme- judgment all the time. So are the software engineers, the AI leaders, the portfolio managers, and the data scientists. So the question that they're focused on is, given judgment is a finite asset,

[5:18](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=318s) a limited capacity, the main question becomes: where is our best judgment worth spending? I'd like for you to hold on to that thought. With that, we'll dive into our first pillar, design the right problem. So questions, uh, a question that, um, the leading organizations are asking all the time is they're obsessed over what is the right problem to solve, right? It's tempting to start with a tool. Today, we're

[5:47](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=347s) surrounded with better models, harnesses. We're surrounded with all these AI tools. We're surrounded with co-pilots, but that isn't the way about, is it? At least that's not the way the leaders are approaching it. Now let's go back to our hypothetical, um, two companies. Let's say they're from asset management. Let's say, uh, we're tracking the workflow of two research analysts in these hypothetical, um, organizations. Well, let's say organization

[6:18](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=378s) B starts with the tool, the co-pilot. They're asking, "Where can we add AI to the analysts' work?" They're looking at the current existing process to say, "Earning transcript comes in, I discover the summarization workflow, let me pass all of this in through my fire hose, analysts get earning summaries faster." Win-win, right? Well, not so much, at least not compared to the guys who are leading.

[6:48](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=408s) And such a workflow of, of being a faster horse introduces one key, um, nuance. That is, you are losing context as you have information, um, I guess reduction as part of your summarization. So what, what is a hypothetical organization A doing in this? Well, they're obsessed on the right problem to ask. They could be asking, "Why are our material signals reaching us too late? Where do we focus the attention, the AI, the bandwidth,

[7:18](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=438s) the capability on? Where is our bottleneck?" Right? And so it becomes this redesigning of the workflow, or at least a reevaluation on what to focus on. That's what they're doing different. Now, this consideration isn't particular to finance. It's across the, the realm and function. You know, you're asking the same question on what to focus on, whether it be research capacity, decision speed, quality of your data, latency, reliability. It,

[7:47](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=467s) it, it traverses all of that. And studies show this. They show leading studies, um, on average, spend their attention on fewer higher quality decisions than the other cohort. So leaders are being more selective in where they focus their attention and what they focus their attention. So it's great. The leading companies, uh, have, um, an idea of what the right problems are. Where do they go from there?

[8:17](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=497s) Well, they also concentrate their investments in the highest value workflows. I get it, and I've been, uh, I've been culpable of, of something similar where, you know, is... AI is almost creating too many opportunities. And experimentation can be a good thing. Um, but one needs to separate experimentation and the resulting innovation theater, or worse, the productivity theater, with actual value generation.

[8:48](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=528s) Going back to our two, um, hypothetical companies, what does this mean? Company B is looking at, "How do we launch the most number of AI pilots?" And what that ends up looking like is a, a document summarization bot here, a co-pilot there, um, a, a data retrieval bot here. It's scattered all over the place. Whereas what company A is focused on in their investments is potentially use cases like end-to-end workflows on the

[9:17](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=557s) research, um, on the research pipeline. They're focused on aligning engineering, analytics, AI capacity, and judgment towards a singular focus. And research has shown that the leaders spend more than eighty percent of their investments on these high-value use cases, transforming key business functions and creating new offerings. Perfect. We, we

[9:47](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=587s) know they're focusing on, um, finding the right problem, and they're also spending deep investment in select workflows. Well, they're also doing something different. They're reimagining how work is done.

[10:03](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=603s) I think this is, this is key, and it goes back to what we discussed previously, which is judgment. They're redefining and reorganizing functions, roles, capacities around this key element of judgment.

[10:19](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=619s) What does that mean for our hypothetical company? Well, company B might be focused on, as we discussed, "I'm getting my earnings transcript, I'm getting my research su- my research reports. How do I summarize it? Maybe I make that faster. Maybe I update my financial models faster. Maybe I send my recommendation to my PM faster." Company E-- A is focused on an entirely different ball game. Hypothetically, they could be asking the analyst to define the investment thesis, and they're watching

[10:49](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=649s) and gathering evidence that could refute that thesis or support it. They'd be monitoring continuously, they'd be investigating exceptions, and they could be deep diving on, you know, select examples that could lead to actual generation of value. So the winners just don't just automate, they redesign. And studies show that the cohort of high performers are seventy-five percent more likely, or in

[11:19](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=679s) practice, they actually do redesign their workflow versus the twenty-five percent of the cohort that doesn't.

[11:26](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=686s) So where does this leave us with our two hypothetical companies, um, and designing the right problem? Company B adds AI to existing workflows. They're completing individual projects, and they're moving to the next initiative. Whereas company A is rethinking how work is done. They're redesigning processes around AI, and they're obsessing over the, the, the right problem. That's, that's the difference in how organizations put AI to work.

[11:53](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=713s) Great, so they've picked the right problem. Uh, what, what happens next? Um, well, we all know in order to actually enable that capacity, you need to build shared capabilities across the org. And what's, what's a trend that's seemingly emerging for, for some time now is that the lines between technology and business are converging. And we're seeing this everywhere. We're seeing engineers that are moving closer to business outcomes. We're seeing business professionals that are

[12:23](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=743s) building tools and automations. And as you can see and imagine, you can have forward deployed engineers, you can have forward deployed product managers, but you could also have the inverse, which is f- forward deployed, uh, portfolio managers. And it's really this combination of getting the right people in the room by breaking down organization silos that the leaders are really leaning on. Studies have shown that, uh, more and more

[12:53](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=773s) of the large enterprises are viewing their technology arm as a business growth function. Um, and that's creating an edge for these, for these companies.

[13:04](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=784s) So the other sort of vertical inside building shared capabilities that, um, is probably a per- personal favorite of mine, it's, um, standardizing the core and personalizing the edges. And this is something that isn't new, uh, to the technology world. We've, we've built infrastructure, we've built, you know, shared modules and system design. But what's interesting here today is that's taking a very different shape with the capabilities out there and with the org and the breaking down of silos.

[13:34](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=814s) And this could look very different depending on where you sit. You could be building shared cores for a h- you know, a team that looks very different with analysts and, and clients. You could be doing that with, you know, a bunch of analysts, or you can do- be doing that for software engineers or, or data scientists. With the data scientist example in particular, that could look very interesting where instead of having one-off workflows that,

[14:04](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=844s) that is really common in the industry, you could build a shared core of the data sets, their semantic layers, the trade-offs of what worked, what didn't, what, you know, what, what some data sets do good of, where are the gaps and, and so on and so forth, such that each new personnel becomes almost a plug-and-play module in the system where they can then stand on the shoulder of their predecessors. So what should the next person not have to rebuild?

[14:36](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=876s) Now, what's also interesting is, um, you know, the enterprise wasn't really built for agents. Um, agents, they, they work across workflows and applications. They, they take context, they, uh, deliberate, they take actions, whereas really the enterprises are focused, um, uh, previously on a single human or a collection of them interacting with a single application. So the leaders are cognizant that something needs to change and that they need to

[15:06](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=906s) modernize, um, their infrastructure, and they're very self-aware of where they are in their journey. And so studies show that, you know, seventy-fi- seventy-one percent of the orgs are modernizing their core infrastructure to support AI. And, um, you know, six to ten percent, um, or twenty-three percent of them are investing six to ten percent of their annual revenue in, in core system modernization, um, to take advantage of this. And a common complaint here or a common

[15:36](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=936s) challenge here is, um, you know, data quality and, and the ability to reuse data. Um, so great. We, you know, we, we have the right people in the room. We, um, have, uh, you know, we have the right knowledge there. What does-- what do we do next? And then comes the concept of, "Hey, how do we make this knowledge reusable and accessible?" And that's where we have, you know, depending on, on the adoption and where, where they are, you can have different types of team agents, where you

[16:06](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=966s) can have expert agents being subject matter experts. You can have workflow agents that work across streams like Slack bots that are creating and opening tickets, they're closing them and what have you. And then you can have really chief of staff kind of agents that keep a tab on what the state of the organization is and what needs to be done. So, um, you know, going back to our workflows, A, again, is looking at this very differently in terms of shared capabilities.  Now, the last pillar here that I want to

[16:36](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=996s) draw, uh, your attention to is, well, when does this system really compound? What happens when it's deployed? Well, leading companies, what they're doing is they're actually thinking about it slightly differently. What are failures that can give us an edge that we can learn from? If, if there's a success, how do we make it part of the system? And the way they think about this is, you know, the individual learned, but did the system. Is there a

[17:06](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=1026s) way perhaps when they've encountered something where they need to make a correction that that knowledge is fed back into the org either through a new tool or context or, or, or what have you? And, um, what's, what's key here is preserving the evidence along with those learnings. So, um, really the last vertical here is AI frees capacity. Where does it go? Being cognizant that you need to redesign your system

[17:36](https://www.youtube.com/watch?v=C2-v6wkHXhY&t=1056s) and really focus it on key metrics that you're evaluating, you're monitoring, and you're creating a fry- flywheel off. So where does this leave us for companies A and B? You know, company A has their entire work redesigned. They're building capabilities that compound, and they have shared capabilities built. So I want to leave you off with one final question. Everyone has AI. Who has the advantage? Thank you.
