The 4D framework: a learner's map for working with AI

Two learners in the same cohort gave Claude the same assignment: “write a function that groups a list of transactions by month and returns the totals.” One pasted the prompt, copied the first answer into their project, and moved on. It ran. The other typed roughly the same prompt, read the result, noticed it silently dropped transactions with no date, asked for the edge case to be handled, then checked the totals against three rows by hand before keeping it. Same model, same starting prompt, different value, and a month later, different learners. The difference was not the AI. It was the set of habits wrapped around it.

Those habits have a name. Prof. Rick Dakan of Ringling College of Art and Design and Prof. Joseph Feller of University College Cork built a framework called AI Fluency in 2023-2024, now taught as the free Anthropic Academy course “AI Fluency: Framework & Foundations”: about seventy minutes of video across twelve modules, released under a Creative Commons licence. They define AI fluency as the ability to work with AI effectively, efficiently, ethically, and safely, and they organise it into four competencies nicknamed the 4Ds: Delegation, Description, Discernment, and Diligence. This is a walk through what each one means and why a learner who builds these four habits gets more out of AI without handing over the understanding that was supposed to be theirs.

Four habits, not four tricks

The 4Ds are not four prompt tricks to memorise. They are four kinds of thinking you bring to any AI collaboration, in roughly the order they come up: decide what to hand off, ask for it well, judge what comes back, and take responsibility for the result. Each one is a competency with sub-skills under it, and none of them depend on a particular product. The same four habits apply whether you are working with Claude, a coding assistant, an image tool, or whatever ships next year, which is the point of teaching habits instead of features.

Read left to right, the diagram looks like a pipeline, but the dashed arrow is the real story: Description and Discernment cycle. You rarely get a useful result in one shot, and the learners who improve quickest are the ones who treat the first answer as a draft rather than a verdict.

Deciding, then asking

Delegation is deciding whether, when, and how to involve AI at all, and how to split the work between you and the model. It breaks into three sub-skills. Goal and task awareness is knowing what you are actually trying to achieve: a learner who wants to understand recursion has a different goal than one who just needs a working function, and the right amount of AI differs accordingly. Platform awareness is knowing what today’s tools can and cannot do, so you neither ask for something they will fabricate nor hand-roll something they would do reliably. Task delegation is the act of dividing a project: you take the parts where your judgement matters or your learning lives, and pass the parts that are mechanical or already mastered.

A concrete case: a student building their first app has to lay out a screen and write a date formatter. Good delegation keeps the layout, the thing they are there to learn, in their own hands, and hands the formatter, a solved problem they will reuse without thinking, to the AI.

Description is communicating with AI so it does something useful, and it also has three sub-skills. Product description is prompting that defines the output you want: the format, the constraints, the example of “good.” Process description is the dialogic, iterative side: shaping the collaboration as you go (“explain your reasoning first,” “ask me before you assume the schema”). Performance description is directive prompting that sets how the AI should behave over time, the kind of thing you put in a system prompt or custom instructions (“you are reviewing my code; point out bugs, do not rewrite it”).

The learner version of this is small but real: “fix my code” gets a guess; “this sorts ascending but I need descending, and I cannot change the function signature, what is the smallest change?” gets a usable answer, because the description carried the constraints. Description is deep enough to be its own subject: the companion piece prompting for general tasks goes into it on its own.

Judging, then owning it

Discernment is judging what the AI gives back instead of accepting it. Product discernment is evaluating the output itself: is this correct, is it good, how would I improve it? Process discernment is judging whether the back-and-forth is actually productive, or whether you are three follow-ups deep and going in circles (often the signal to start the prompt over rather than patch it again). Performance discernment is judging whether an AI running on its own (an agent, an automation, a standing instruction) is giving good results over time, not just on the one example you checked.

For a learner this is the habit that separates the two students from the opening. Product discernment is reading the grouped-transactions function and noticing it drops the dateless rows. You cannot discern what you do not understand, which is why discernment keeps a learner in the work rather than beside it.

Diligence is taking responsibility for the collaboration, the ethical and accountable side. Creation diligence is applying your principles while you work: not asking for content you should not, not building something you would not put your name to. Transparency diligence is being honest about AI’s role when you share the result: telling a teammate which parts were AI-assisted, citing it where that matters. Deployment diligence is verifying and vouching for an AI-assisted output before it goes out the door: you checked it, and you stand behind it.

The learner case is mundane and important: before pasting AI-written code into a shared repo, you read it, you test it, and you can answer “why does this work?” if asked. If you cannot, it is not ready, regardless of whether it runs.

How the four fit together

The four are not equal in shape. Delegation happens once at the start; it frames the task. Diligence happens at the end; it guards what leaves your hands. The two in the middle, Description and Discernment, are a loop: you describe, the AI produces, you discern, and then you describe again with what you learned. Dakan and Feller call this the Description-Discernment loop, and it is the engine of nearly all day-to-day work with AI.

Here is the same framework as a quick reference: what each D answers, the question a learner should be asking, and what tends to go wrong when the habit is missing.

The benefit, concretely

For a student, the 4Ds do one thing that copy-paste never does: they keep you in the loop. Discernment and diligence are exactly the thinking that pasting an answer skips: reading the output, judging it, understanding it well enough to vouch for it. That is not overhead on top of learning; for a learner it often is the learning. The student who discerned their way through the transactions function had to understand grouping, totals, and edge cases to spot the bug. The one who pasted understood none of it, and the gap compounds with every assignment.

It helps to see where this framework sits next to the others on this site. The AI Access Ladder answers how much AI to use on a given task: which rung, from no-AI fundamentals to full delegation. The 4Ds answer how well you work with AI at whatever rung you are on. They are complementary: the ladder picks the amount, the 4Ds set the quality. A learner at Level 2 (write your own draft, then ask AI to review) is doing the Description-Discernment loop with the dial turned low. And if you want the practical, build-the-habit version, drills and routines rather than definitions, the companion becoming AI-fluent: a learner’s playbook is the how-to that follows this map.

Go back to the two learners. Same model, same prompt, same starting point, and a month apart in what they could actually do. The model was never the variable. Delegation, Description, Discernment, and Diligence were. Build those four habits and AI becomes a tool that develops your thinking. Skip them and it quietly does your thinking for you, which feels the same right up until the moment you need to think on your own.