Best practices for scaling AI adoption across a large org & the trade offs you will have to make w/ Sagnik Nandy #273
The Engineering Leadership Podcast

Best practices for scaling AI adoption across a large org & the trade offs you will have to make w/ Sagnik Nandy #273

B2Upper-intermediateOctober 20, 202642 min
  • Interview
  • Technology

In this episode, Sagnik Nandy (CTO & EVP of Engineering @ Docusign) joins Jerry to discuss keys to success when it comes to peer-led AI transformation. Sagnik shares how they approached AI adoption internally @ Docusign with the use of both champions & multipliers, understanding trade offs associated with AI adoption, determining which tasks to assign to agents, frameworks for measuring the ROI of agentic tools, and how it helps bring value to your customers. He also discusses how to measure the customer productivity index (CPI) and what it takes to mitigate customer issues when scaling AI internally. ABOUT S...

Play episode

Opens the player: the full transcript, every word clickable, with translation and flashcards.

Try it: tap any word

Real sentences from the start of this episode. Every word is marked with its level.

Sentence 1 of 12 · 0:00

.

The first dimension, C, is for clarity.

Hear this sentence

Tap a word to see its meaning in your language.

Do you know these words?

8 harder words from this episode. Tap one to see what it means, then mark it.

  • C15:17
  • B27:22
  • C114:14
  • B221:36
  • B225:07
  • B232:00
  • C237:17
  • C241:18

Mark a few words and we'll tell you how this episode fits your level.

Is this episode right for you?

B2

B2 · Upper-intermediate

Comfortable if you already follow TV news

A1 26%A2 34%B1 26%B2 13%C1 2%
  • 85% of the words are B1 or easier.
  • 202 words a minute: natural, fairly fast speech.
  • 209 harder words (B2 and up) in the whole episode.

Transcript

The opening of the episode. The whole transcript is in the player.

0:00

The CAFE's framework is a definition framework for what constitutes high-quality context. The first dimension, C, is for clarity. Clarity asks whether the agent can interpret the request the way that it was intended. A request can reasonably be read more than one way.

0:23

So that is something that can feel obvious to the person, right? It can feel obvious to us because we wrote it. And we bring everything that we know into reading it. Say you ask an agent to clean up the old feature flags.

0:35

The agent is going to read old, let's say as something that has not been touched in six months across the entire repository. So it will go and remove the flags in other Teams services too. One of them might be a kill switch, which is supposed to sit there and be untouched

That was the opening. The rest of the episode (41 min) is in the player: every word clickable, with translation, saved words and flashcards.

Continue in the player

Automatically generated from the audio. May contain errors. Audio belongs to its publisher and is played from their feed. Rights holders can request removal — copyright & takedown policy