The B2B Podcast Index
Index
All categories
MarketingSalesSaaSFinanceHROpsLeadershipCustomer SuccessAI & DataProductStartups & FoundersRevOpsEngineering & DevTools
MethodologySubmit
Best of:MarketingSalesSaaSFinanceHROpsLeadershipCustomer SuccessAI & DataProductStartups & FoundersRevOpsEngineering & DevTools
An independent project byFame
SearchBest episodesGuestsInsightsMethodologySubmit a podcast
Index/AI & Data/The Effective Data Scientist
The Effective Data Scientist artwork

Using Frameworks for Prompts for Better Outcomes

The Effective Data Scientist · 2026-06-12 · 21 min

0:00--:--

Key moments - from our scoring

Substance score

23 / 100

Five dimensions, 20 points each

Insight Density5 / 20
Originality4 / 20
Guest Caliber4 / 20
Specificity & Evidence6 / 20
Conversational Craft4 / 20

Prompting isn't simply asking questions - it mirrors writing a rigorous analytical brief with explicit assumptions, constraints, and success criteria. Paolo and the host discuss why starting with a well-structured prompt beats iterative refinement of poorly-formed ones. They introduce multiple prompting frameworks: ROSE (Role-Objective-Scenario-Expected Solution-Steps) for complex tasks requiring structured reasoning; CRISP (Context-Role-Instruction-Style-Parameters) when format and structure matter; APE (Action-Purpose-Expectation) for simpler tasks; and TRACE (Task-Requirements-Context-Example) for technical outputs. The conversation anchors on a real pharmaceutical data scenario: transforming messy Excel files into analysis-ready tabular formats without corrupting expensive experimental data. The host shares a detailed prompt incorporating role-based instructions, explicit constraints (no data modification, no assumptions without clarification), and verification requirements. Key principles include treating prompts as technical specifications, avoiding assumptions that compound errors, and knowing when to restart rather than endlessly iterate. The episode targets data scientists and technical professionals who interact with LLMs regularly and need reliable, reproducible outputs.

Key takeaways

  • →Treat prompting like writing an analytical brief with explicit assumptions, constraints, and success criteria rather than casual questioning.
  • →Start with a well-structured prompt using a framework (ROSE, CRISP, TRACE, or APE) matched to your task complexity, rather than refining poorly-formed initial prompts.
  • →Include technical specifications in prompts: expected output format, verification steps, style requirements, and explicit constraints (e.g., 'do not modify or infer data values').
  • →When prompt iterations plateau, restart with a clean context rather than accumulating refinements, and use AI itself to help improve your prompting.
  • →Different prompting frameworks suit different scenarios - choose based on whether context, structure, complexity, or simplicity matters most for your task.

Guests

Paolo

Topics in this episode

Prompt engineeringLarge Language Models (LLMs)Data transformationPrompting frameworksCRISP framework (Context-Role-Instruction-Style-Parameters)TRACE framework (Task-Requirements-Context-Example)APE framework (Action-Purpose-Expectation)CARE framework (Context-Action-Result-Example)Tabular data formattingPharmaceutical data analysis

Questions this episode answers

What is a prompting framework and why should I use one instead of just asking questions?

A prompting framework is a structured template that reduces ambiguity by answering key questions about role, objective, context, expected output, and reasoning approach. Starting with a well-structured framework produces better results than iteratively refining a poorly-formed initial prompt, because unclear assumptions compound errors early on.

Which prompting framework should I use for transforming messy data into a clean tabular format?

TRACE (Task-Requirements-Context-Example) or ROSE (Role-Objective-Scenario-Expected Solution-Steps) work well for data transformation. Include explicit constraints like 'do not modify, infer, or delete any values unless explicitly instructed' and define verification steps (row/column counts before and after).

How do I prevent AI tools from corrupting expensive data during transformation?

Build constraints and verification steps directly into your prompt: define what 'no modification' means, require the AI to list every transformation step before executing, ask for confirmation, and request before/after comparisons to verify nothing changed unexpectedly.

Should I use the same prompt across different AI tools to compare results?

Yes, comparing the same prompt across different AI tools can reveal whether results vary by tool and which performs better for your specific task, though practical constraints like company laptop access may limit this exploration.

When should I stop refining a prompt and start over instead?

If you've iterated several times without improvement and feel lost in accumulated context, restart with a clean slate rather than continuing to refine - this is a heuristic approach that can help clarify the core requirements.

What our scoring noted

Our reviewer’s read on each dimension, with quotes from the episode.

Insight Density

5 / 20

The episode is almost entirely surface-level: framework acronyms are listed with only their letter expansions and almost no functional explanation of how or when to deploy them. The one substantive moment is a single concrete prompt shared verbatim; the rest is platitudes and repetition with very low insight per minute.

it's really important to explore The framework that applies best for your situation And then experiment and find tool for your day-to-day work.
it's also important to follow development with large language models and understand how do they work?

Originality

4 / 20

Every claim here is drawn from widely circulated prompting articles - list the acronyms, 'start structured,' 'iterate carefully,' 'ask the AI to improve your prompt.' There is zero contrarian, first-principles, or counterintuitive framing; the episode reads like a shallow blog summary of existing content.

It's really nice to read about them, I was impressed by the number and quality of the acronyms.
Be a bit cautious but some exploration. you can pick up one of these frameworks improve it and start in better way with your prompting.

Guest Caliber

4 / 20

There is no external guest - two co-hosts converse with each other, and both explicitly describe themselves as beginners who stumbled onto these frameworks through internal company learning sessions. No demonstrated depth of expertise or seniority is evidenced in the transcript.

I just accidentally learned about prompting in one our learning sessions at my company
Of course I'm currently only experimenting.

Specificity & Evidence

6 / 20

The episode earns marginal credit for one verbatim prompt example with concrete constraints for pharmaceutical data transformation, including specific rules like 'do not modify infer impute correct or delete any data values.' All other references to frameworks are name-only with no worked examples, metrics, or case data.

Your objective is transform raw experimental data into an analysis ready tabular format without changing the underlying data. And a critical constraints are do not modify infer impute correct or delete any data values
provide the before and after row and column counts

Conversational Craft

4 / 20

The hosts consistently agree with each other, producing no pushback, no probing follow-ups, and no productive disagreement. Questions are either absent or extremely generic, and the conversation frequently meanders without the host redirecting toward substance.

Yeah, that's really great strategy.
I agree with you.

Conversation analysis

Computed from the transcript - who did the talking, and the words that came up most.

Most-used words

data21framework15example14different14prompting12frameworks11better11prompt10tool9important8task7examples7context7general7start6scenario6

Episode notes

Episode Summary How can you get better, more reliable results from AI? In this episode, Paolo and Aziza explore why effective prompting is about much more than asking good questions. We discuss how structured prompting frameworks such as ROSES, CRISP, CARE, TRACE, and APE can help data scientists provide clearer instructions, reduce ambiguity, and improve the quality of AI-generated outputs. We also share practical examples of applying these frameworks to real-world data challenges and discuss why designing how AI should think is often more important than the answer itself. Episode Highlights Why prompting is closer to writing an analytical brief than asking a question An overview of popular prompting frameworks including ROSES, CRISP, CARE, TRACE, and APE How structured prompts improve reliability and reduce ambiguity Practical considerations when using AI for data transformation and analysis-ready datasets Why data scientists should focus on defining assumptions, constraints, and expected outputs How AI can help refine and improve prompts over time Key Takeaway Don't just ask AI for answers. Design how it should think.

Full transcript

21 min

Transcribed and scored by The B2B Podcast Index.

Welcome to the Effective Data Scientist Podcast. This podcast is designed to help include your skills, save focus manage successful projects and have fun at work. Be part of our community. this is an independent podcast and the views expressed are all over.

Hello everyone! And welcome back to the effective data scientist. Hi Paolo how I drink? I have this.

uh I'm doing well. what about you? I'm doing fine, hoping for the sun to come back. Same here it seems that winter is back once again but let's hope an improved weather in coming days.

Stay positive! So i am super excited today Paolo because you and me will be discussing prompting. what really means why matters how frameworks can improve quality reliability of AI inputs. So today's episode is about using frameworks for prompts, for better outcomes.

And let me start with a situation many of us have experienced. maybe you too. so ask an AI tool question and the answer sounds confident it well written yet you hesitate to actually use it. does that sound familiar to you Paolo?

Yes family scenario, because sometimes it seems easy to get in front of the generative AI tool and askively. And the outcome is not what you were expecting. now Because although things are always changing In a sense that LLMs are improving I think its really important To apply The best principles and start very focused, and tailored to the question because it's difficult to get better answers refining an initial prompt which is not very well structured. or It's better to start with a well-structured prompt instead of starting in simple and trying to refine later.

Which is possible but it's suboptimal. I agree with you. So for our listeners who are not familiar with the word prompting, I assume there some of us that aren't familiar with terminology we're using. But just going back one step...

When you talk about prompting it simply means how to instruct an AI system what-to do? A prompt is input given It's a question, task description and instruction. And it's not just asking a question, It is much closer to writing a good analytical brief. Defining assumptions and setting constraints being explicit about what correct means.

So I learned this myself as data scientist. we already know that the less assumptions are confusing The more questions can generate. Missing assumptions lead to wrong conclusions, for example. Or a small misunderstanding can have very big consequences The more detailed you explain the background I think assumptions and constraints And what is exactly expected.

Is there way to go? I would say Yeah...I think you introduced me To the word of Brahms frameworks because I wasn't aware of different prompting frameworks that exist and they span from the easier to more structured. Do you have some examples?

Yeah, sure! I was not aware about it too... I just accidentally learned about prompting in one our learning sessions at my company And so I learned that the prompting framework is simply a structured way to reduce ambiguity by answering few key questions up from, for example. What should they AI be?

what Is The goal and what is the context? and what kind of output do i expect? and how Should the AI reason or proceed? So this was something I learned and apparently there are varieties Of examples of prompting frameworks That we can use And I was introduced to ROSE's framework, which stands for R-Role O-Objective S Scenario and E for Expected Solution and Steps.

This is one framework that we can use better explaining what do you expect? To better formulate the problem statement? This was one example that I learned from the learning sessions and i was curious about use. And this is something, do you have any examples?

and you can use certain sources like data, literature guidelines. And also set up the expectations in terms of the length or the plan T level of analytical details and some basic layers of assumptions .And then they You Can Also Set Up. The Style In The Tone Like For Example Could Be less formal since we are writing a psychometric analysis plan and maybe statisticians in the pharmaceutical industry, I'm not familiar with the language.

And the science behind the analytical plan then may be. you can include that in the prompt in terms of the styling expectations also to include more context for the methods being used on it improves a lot The first examples and the very first drafts. And then it becomes easier to iterate quickly, get a solution faster. Of course I'm currently only experimenting.

It's important because when i was learning these frameworks one thing is that you can use them also as an inspiration each framework for your specific case. The narrative doesn't make sense to you? I agree with you, there are varieties and then... For example this Roses case, the Roses Framework is it seems that its used when the task is complex When the context really matters And you want a structured reasoning.

So also mentioned about style like which I can correspond or I can resonate with another type of framework, which is known as CRISP stands for context role instruction style parameters. And this is particularly useful when format and structure are critical. so different prompting frameworks were different tasks. As you mentioned it could be used depending on what your working and you can make a use of different prompting frameworks.

It's really nice to read about them, I was impressed by the number and quality of the acronyms. You can start very simple for example with the APE framework which stands for action purpose expectation Which is very basic. So what do we want? to do, the purpose required.

The expectation is the formal style requirements and there are many examples I've found for example for creative work in marketing. but you can also find examples in a science And You Can Also Reuse Some Of The Case Study You Find In Other Fields For Your Specific Career Expertise Your Area of Work. Another thing I want to explore is the principle of front-end in general, because frameworks just have a first approach that can work for you. But it's also important to follow development with large language models and understand how do they work?

And what was best way to interact with them. That would be really great if we knew like learning your language a foreign language and really be able to understand what is meant, so it will help you communicate better. Learning what's behind the program. Starting from the framework...

It's important make your own research and pick up from beginning the best framework that applies for work and fine-tune elements of the framework. I think that would be great. And while we were talking, I was switching to different ideas like what can ask you and the idea is thinking where could apply? What are challenges facing at work or which kind of problems have in mind for this scenario?

maybe i can ask about your input on how do approach it The scenario when you have data, which is not in the right format. Like with statistician we need that data in the correct format and do we have to have it in a tabular form? And NOT IN THE EXCELFORM with merged cells... and A LOT OF INCONSISTENCY in the cells & labelling.

So which framework would you use for creating a prompt that will help you to transform this data into the format that you will be using. So, it was something I was struggling and in my company... In my role i get data from many different formats. It comes from PDF reports, Excel records with not proper formatting for statistical analysis because I was afraid that if it changes one data or value, this will have a drastic impact.

Because every data we generate is very expensive. and how to make sure i get the correct values back from what I provided in the AI tool? I think its important to discuss the ideal framework to stop. For example, I think that trace framework or trace framework are great examples because in trace defect on the element is requirements which add the technical specifications for the final output.

but i think it's very important setup of your data and then the expectations for how they should look like at the end of the transformation. For example, in general LLMs are now very capable of doing an at-the-end tabular data is a very simple example language. so it's chain of symbols which have numbers with separators. So if you are able to set up the requirements, the context and also the expected outputs in the best way then You can get a lot from your prompt.

There is an evolving field for example how to generate the prompt automatically From LLMMs To deal with specific situations. This is quite frontier topic For now But for sure, we have to be careful with the technical requirements of this scenario and expectation. Yeah thank you for the input that maybe I can share. how i dealt in this scenario?

I did use AI itself for helping me create a better prompt! So what I did is enroll...I took role And said You are senior data scientist With strong experience in pharmaceutical development. Your objective is transform raw experimental data into an analysis ready tabular format without changing the underlying data.

And a critical constraints are do not modify infer impute correct or delete any data values, Do not assume units meanings relationships unless explicitly stated and do not rename variables unless explicitly unstructured. If ambiguity exists, stop and ask clarification questions. In the task I said describe how you interpret the current data structure a target tabular structure And explicitly list every transformation You plan to apply. Wait for my confirmation before performing any transformation.

Last but not least there are some verification requirements and also style verification requirements, I said provide the before and after row and column counts. And some more details in style a brief precise cautious an explicit and treat these as regulated development data. so this is very important! i think it was okay for me but should apply several times to see if get results that are promising.

Sometimes when I refine the prompt after a few iterations, I prefer to restart another chapter. To clean up context because i see that After a few iteration things are not improving as expected and you find yourself in forest of big data trying process all outcomes right? Just in the middle of exploration, I mean it's a bit heuristic. i don't have any data or source to support that.

It is also good to ask the A-Tool To provide you with an Aswerra Or once You Have Something Good With Your Front Then You Can Also Directly Ask The A-tool To Improve Directly The Front So you can make a better use of the GenAI tool also asking to improve your content. Yeah, that's really great strategy. and do you also use different AI tools? Like I used the same prompt using different Ai tools and see if you get two different results.

I typically don't do it but just for practical reasons because usually working with my company laptop for example or my personal one more on frequency then we are a bit bounded in terms of the pulse you can use. but, In general I tend to pre-one AI tool For specific task and i don't switch across tools for same tasks. And...for example..

in terms of coding I prefer work with cloud while for tasks like writing or you know searching and fine with chat gpt also. so it depends more on the type of task. but i'm not always curious about what could be the result if I ask different general tools. yeah well that's a good advice, to explore.

Yeah, I do share your limitations with respect to the work environment. We are using our own validated AI tool for that and sometimes i really wish that i could just have more options To see if i get the same results Using different AI tools like the same question Just different AI Tools And See What Happens. But I'd Share The Limitation That You Mentioned. And yeah, so for general tasks maybe it would be a good idea to see like not work related task or general task.

It could be nice to see what are the outcomes that we get and if they differ... If one answer is better or not? So this will be something maybe someone can try. Yeah I agree.

We talked about different frameworks for prompting. Maybe we can recap. We talked about roses, we named a few like trace aid. And there are other prompts too Like care context action result an example.

and yeah A lot of options one can use. I think if you browse in internet You find a lot Of options and a lot of articles that Are available with some applications shown. It's really nice to see how Use them in which kind of situations to use them and what would be your final take away or message? To the listeners.

I think it's really important to explore The framework that applies best for your situation And then experiment and find tool for your day-to-day work. Stay tuned with the update, be careful because they use new ways of prompting or updates for large language models are overwhelming at this day. Be a bit cautious but some exploration. you can pick up one of these frameworks improve it and start in better way with your prompting.

I agree with you. thank you Paolo for this fantastic discussion. I think the general takeaway would be from my side, don't ask AI for answers. Design how it should think better description and explaining what exactly do you expect that could be useful to get what you want?

So thank you Paolo! It was a good start into this topic. Let's continue with different topics regarding AI and data science in future episodes and thank you for the listeners, for tuning into the effective beta science.

Related episodes across the Index

Other episodes covering the same guests and topics, from across The B2B Podcast Index.

  • How Organizations Can Thrive in the Human + AI Era with David ChestnutThe Edge of Work · on Large Language Models (LLMs)85 / 100
  • Why B2B Brands Are Using AI to Write Sales ProposalsThe Growth Operator with Fexingo · on Prompt engineering85 / 100
  • Episode 018: Season 2, the $75 Consult and the Frankenstein StackAI Tools for Practicing Lawyers · on Prompt engineering84 / 100
  • Episode 111: Building Your Defences Against AI MisinformationValue Driven Data Science · on Prompt engineering83 / 100
  • #194 Brian Donohue: Intercom threw their playbook out the window when AI got good - A case study on questioning your mental models.The Way of Product with Caden Damiano · on Large Language Models (LLMs)82 / 100
  • How B2B Marketers Use AI to Personalize at Scale for EnterpriseB2B Marketing with Fexingo · on Prompt engineering82 / 100

More from The Effective Data Scientist

All episodes →
  • Alexander and Team on What Leadership Means in Data Science
  • Relaunching The Effective Data Scientist: Beyond Code to Influence, Impact & Career Growth
  • As a Statistician - Do You Take the Back Seat or Do You Drive Yourself? (Episode 24)
  • On Building Your Own Company (Episode 23)
  • Cluster Analysis (Episode 22)
Explore the best B2B AI & Data podcasts →
All The Effective Data Scientist episodes →