4D Framework Quick Reference
FreshQuick guide to the AI Fluency 4D Framework for effective AI collaboration.
The 4 Ds at a Glance
D1: Delegation Cheat Sheet
Give to AI
| Task Type | Example |
|---|---|
| First drafts | "Write a first draft of..." |
| Summaries | "Summarize this article..." |
| Research | "Find information about..." |
| Brainstorming | "Generate 10 ideas for..." |
| Reformatting | "Convert this to a table..." |
| Code | "Write a function that..." |
Keep for Humans
| Task Type | Why |
|---|---|
| Final decisions | Accountability |
| Ethical judgments | Values require human context |
| Sensitive communications | Relationships matter |
| Strategic direction | Vision requires human insight |
D2: Description Template
I need you to [TASK].
Context: [BACKGROUND INFO]
Audience: [WHO WILL READ THIS]
Format: [BULLETS/ESSAY/CODE/TABLE]
Length: [WORD COUNT OR SCOPE]
Tone: [PROFESSIONAL/CASUAL/TECHNICAL]
Include: [MUST HAVES]
Avoid: [DON'T DO THIS]
Example of what I want:
[SAMPLE OR REFERENCE]Quick Prompting Tips
| Element | Weak | Strong |
|---|---|---|
| Task | "Write about X" | "Write a 500-word blog post about X" |
| Audience | (missing) | "for software engineers" |
| Format | (missing) | "as bullet points" |
| Tone | (missing) | "using a friendly, accessible tone" |
D3: Discernment Checklist
Quick Evaluation
□ Is it accurate? → Fact-check key claims
□ Is it complete? → All requirements met?
□ Is it appropriate? → Right tone/format?
□ Is it useful? → Does it solve the problem?
□ Would I sign it? → Quality I'd claim as mine?Iteration Phrases
| Goal | Say This |
|---|---|
| Shorter | "Make this more concise" |
| More detail | "Expand on [section]" |
| Different tone | "Make this more [formal/casual]" |
| Restructure | "Lead with the conclusion" |
| Add examples | "Include 3 specific examples" |
| Simplify | "Explain this for a beginner" |
D4: Diligence Reminders
Before You Prompt
□ No sensitive personal data
□ No proprietary secrets
□ No passwords/credentials
□ Consider who might see thisAfter You Receive Output
□ Verify important facts
□ Check code before running
□ Review for bias
□ Consider who created thisTransparency Guidelines
| Situation | Action |
|---|---|
| Work deliverable | Note AI assistance if required |
| Published content | Disclose per organization policy |
| Academic work | Follow institution guidelines |
| Personal use | Your judgment |
Common Use Cases
Email Writing
D1: Draft → AI
D2: "Write a professional email to [person] about [topic].
Keep it under 200 words. Use a [warm/formal] tone."
D3: Check accuracy, adjust tone, personalize
D4: Verify no sensitive info, add personal touchResearch Summary
D1: Initial research → AI
D2: "Summarize the key findings from [topic].
Include pros/cons. Format as bullet points."
D3: Verify sources, check for missing perspectives
D4: Fact-check before sharingCode Generation
D1: First implementation → AI
D2: "Write a [language] function that [does X].
Include error handling. Add comments."
D3: Review logic, test edge cases, check security
D4: Test before deploying, understand the codeQuick Decision Tree
See Also
- Workflow-007: AI Fluency 4D - Full details
- SOP-007: Claude 101 - Getting started