From Error Analysis to Better Prompts: The Missing Step Most Teams Skip

Now tell me, I've identified all these problems. I have these evals that give me data. How do I write a good prompt? Like, are there, are there some techniques or, you know, what do I, what do I do? Are there things that you found consistently in the next step of improving your system instructions, improving your tools, um, where you actually have to go solve these problems are, are effective?

When you get to like the errors that you have, you're gonna use these evals and you're going to deploy it at scale. You're not looking at all your data, you're looking at a sample of data and you're going to deploy that at scale and you're going to like look at where are there errors. You have to make a judgment call. How do you improve your system based on the errors you're finding?