Design Case Study Structure AI Prompts for Students

Transform scattered research into a cohesive academic narrative with AI as your analytical partner.

TL;DR

• AI prompts can help you structure case studies that communicate your design process clearly
• Effective prompts ask AI to challenge your assumptions, not just summarize your work
• The best prompts guide you through narrative framing before drafting begins
• Using AI early in the process yields better structural insights than using it for proofreading
• Specific, contextual prompts outperform generic requests for help

Introduction

A design case study is more than a documentation exercise—it’s the bridge between your studio work and the professional world. Yet many students find themselves staring at weeks of research, unsure how to transform it into a compelling narrative that demonstrates their thinking.

AI Unpacker tools can serve as an analytical partner throughout this process, but only if you know how to prompt them effectively. Generic requests like “help me write my case study” produce generic results. What you need are targeted prompts that force you to articulate your decisions, confront gaps in your reasoning, and structure your narrative in ways that resonate with evaluators.

This guide provides specific prompts across each phase of case study development. You’ll learn to use AI not as a writer, but as a critical friend who asks hard questions about your work.

Table of Contents

1. Defining Your Case Study’s Core Narrative
2. Structuring the Problem Statement
3. Documenting Your Research Process
4. Presenting Design Decisions
5. Showcasing Outcomes and Impact
6. Refining Your Writing and Flow
7. Preparing for Different Audiences
8. Common Pitfalls to Avoid
9. FAQ

---

Defining Your Case Study’s Core Narrative

Your case study needs a central argument, not just a project description.

Before writing a single word of your case study, you need to identify what you want the reader to take away. This isn’t the same as your project brief—it’s the specific insight, approach, or innovation that emerged from your work.

Use this prompt to crystallize your core narrative:

I'm working on a design case study for [project name]. My brief was to [original brief].
I spent [time period] researching [research areas]. My final design [brief description].

Help me identify my core narrative by asking me these questions:
1. What surprised me during this project?
2. What would I do differently if I started over?
3. What did I learn that others in my field should know?
4. What makes my approach different from similar projects?

Please challenge any narrative I propose that feels too generic or self-congratulatory.

Why this prompt works: It forces you to move beyond “what I did” into “what I discovered.” AI Unpacker’s role here is to act as a skeptical reader who won’t accept vague claims. If you say something like “I focused on user needs,” the AI should push back and ask you to be specific about which needs and how you prioritized them.

Identifying Your Unique Contribution

Many student case studies read like process logs because students are afraid to claim any special insight. Your case study needs a point of view.

Based on these notes from my project [paste notes], help me identify what makes
this case study worth reading. Ask yourself:
- Is there a methodological innovation?
- Did I discover something counterintuitive?
- Did I solve a problem that others found unsolvable?
- Did I bridge two fields or approaches that don't usually connect?

For each potential angle, tell me what evidence I have to support it. If I don't
have evidence, tell me that's not actually my angle.

---

Structuring the Problem Statement

A strong problem statement frames the challenge without giving away the solution.

The problem statement sets the stage for your entire case study. It should be specific enough to feel real, but open-ended enough to show how your design thinking led to the solution.

Crafting the Problem Frame

I need to write a problem statement for my case study about [project]. Here's what
I know:
- The client/stakeholder was [who]
- They experienced [specific problem]
- This affected [who] by [how]
- The current solutions weren't working because [why]

Help me write three different problem statement framings:
1. One that emphasizes the human impact
2. One that emphasizes the systemic issue
3. One that emphasizes the opportunity for innovation

For each framing, explain what kind of case study it would produce and what
questions it would leave unanswered.

Avoiding Problem Statement Clichés

Student case studies often open with generic problem statements that could apply to any project. AI can help you spot and fix these.

Here are three problem statements I wrote for my case study. For each one,
tell me if it could apply to ANY design project. If it could, explain why
it's too generic and suggest how to make it specific to my actual work.

[paste problem statements]

Also identify any passive voice, jargon, or vague language like "users need"
or "the problem is" that doesn't actually specify who needs what.

---

Documenting Your Research Process

Your research section should demonstrate rigor, not just activity.

Admissions committees and employers want to see that you conducted meaningful research, not just that you went through the motions. Your case study needs to show how your research informed specific design decisions.

Structuring Research Documentation

I'm documenting research for [project name]. Here's what I did:
[paste research methods and findings]

Help me structure this into a narrative that:
1. Explains WHY I chose each research method
2. Shows how findings connected to each other
3. Identifies which findings directly influenced key design decisions
4. Acknowledges limitations or gaps in my research

For each major finding, I want to be able to trace a direct line to a design
decision. If I can't trace it, tell me whether that finding should be
included or cut.

Synthesizing Research into Insights

Raw research data doesn’t make compelling case study content. You need to synthesize it into insights that inform design.

I conducted [research methods] with [participants/sources]. Here are my raw
findings:
[paste findings]

Help me synthesize these into 3-5 key insights by:
1. Identifying patterns across multiple data points
2. Surfacing unexpected findings that changed my assumptions
3. Connecting findings to design principles or theories
4. Prioritizing insights based on their impact on my design direction

For each insight, tell me what design decision it influenced and what I would
have done differently if I'd had this insight earlier.

---

Presenting Design Decisions

Every design decision is an argument—make it explicit.

The body of your case study is where you demonstrate your design thinking. Each decision should be presented as a considered response to research findings or project constraints.

Writing Decision Narratives

I need to explain why I made [specific design decision] in my project.
Here's my thinking:

[paste your reasoning]

Challenge this reasoning by asking:
1. Is this based on research evidence, or just my assumption?
2. What alternatives did I consider and why did I reject them?
3. Does this decision align with my stated design principles?
4. What would I say to someone who disagreed with this choice?

If my reasoning isn't solid, tell me honestly—this is easier to fix now
than after I've written the full case study.

Using Visuals to Support Decisions

Design case studies need visual evidence of your process, but visuals without explanation are meaningless.

For my case study section on [design area], I have these images/visuals:
[describe available visuals]

Help me write captions and annotations that:
1. Explain what each visual shows in context
2. Connect the visual to my stated research findings or design decisions
3. Highlight specific details the viewer should notice
4. Show the evolution or iteration of ideas, not just final outputs

Tell me if I have too many visuals that just show "the answer" without
showing the process that led there.

---

Showcasing Outcomes and Impact

Results matter, but so does context—don’t let numbers speak for themselves.

If your project had measurable outcomes, present them. But always include the context that helps readers understand what those numbers mean.

Framing Qualitative Outcomes

My design was implemented and here are the outcomes:
[paste outcomes]

Help me present these in a way that:
1. Shows the before/after contrast clearly
2. Acknowledges what external factors might have influenced results
3. Connects specific design features to specific outcomes
4. Includes honest limitations or unexpected results

I want to avoid both false modesty (pretending nothing worked) and
unfounded claims (attributing all success to my design).

Presenting Qualitative Feedback

I received this feedback on my design:
[paste quotes]

Help me use these quotes effectively by:
1. Selecting the most specific, detailed quotes (not vague praise)
2. Providing context for who gave the feedback and when
3. Connecting the feedback to specific design features
4. Acknowledging criticism alongside praise

Tell me if the feedback is too generic to be useful, or if I'm
cherry-picking only positive responses.

---

Refining Your Writing and Flow

Good structure makes your case study readable; good writing makes it memorable.

Once you’ve drafted your case study, AI can help you refine the writing and ensure coherent flow between sections.

Checking Narrative Flow

Here's my case study draft:
[paste draft]

Read it as a skeptical evaluator and tell me:
1. Does the introduction hook you and set clear expectations?
2. Does each section build on the previous one, or do I jump around?
3. Are there places where I've buried the key insight in too much detail?
4. Does the conclusion add something new, or just repeat what I've already said?
5. Where do you feel bored or confused?

I want to know where the case study loses momentum so I can fix those spots.

Tightening Your Prose

Here are three paragraphs from my case study that I'm worried about:
[paste paragraphs]

For each one, tell me:
1. What's the single point this paragraph is making?
2. Am I making that point clearly, or obscuring it with extra words?
3. Are there sentences that could be cut without losing meaning?
4. Is my tone appropriate for an academic/professional audience?

Also check for: passive voice, jargon, clichés, and places where
I've told instead of shown.

---

Preparing for Different Audiences

The same project can support multiple case studies for different purposes.

You might need a version for portfolio submission, another for academic evaluation, and potentially a third for grant or scholarship applications.

Adapting for Portfolio Format

I have an academic case study draft of [project name]. I want to adapt it
for a design portfolio that will be viewed by potential employers.

Help me restructure it for this purpose by:
1. Front-loading the most impressive/visual elements
2. Reducing process documentation in favor of outcomes
3. Making the "what I learned" section more honest and specific
4. Adding details that show collaboration or real-world constraints
5. Including any limitations I overcame through clever design

Tell me what to cut if I'm over the typical portfolio length, and
what to add if I'm under.

---

Common Pitfalls to Avoid

Knowing what to avoid is as important as knowing what to do.

The Process Dump

Many student case studies read like detailed process logs—every step taken, every method used, every meeting attended. This isn’t compelling.

I tend to document everything I did in my case studies. Here's a section
where I've done this:
[paste section]

Tell me what's actually interesting in this section and what can be cut.
I'm probably including things that are only relevant to me, not to the reader.

The Solution Reveal

Starting with a beautiful final design and working backward is tempting, but it hides your actual design thinking process.

My case study currently opens with my final design and then explains how I
got there. Here's my opening:
[paste opening]

Tell me how to restructure this to show my design thinking from the start,
not just in retrospect.

---

FAQ

How long should a design case study be for a student portfolio?

Most design programs recommend 1,500-2,500 words for a portfolio case study, with additional space for visuals. Academic case studies may be longer depending on requirements. The goal is to be thorough without being repetitive—every section should earn its place.

Should I include failed experiments in my case study?

Yes, strategically. Brief acknowledgment of what didn’t work adds credibility and shows honest self-reflection. The key is to connect failures to learning: what did they teach you that changed your approach? Don’t dwell on failures, but don’t pretend they didn’t happen either.

How do I protect confidential client information in my case study?

Use generalized descriptions instead of specific details: “a Fortune 500 retailer” rather than “Walmart,” or “an enterprise SaaS platform” rather than naming the specific company. For student projects, this is less of a concern, but good practice for professional work.

Can I use AI to write parts of my case study?

You can use AI to help structure, refine, and proofread your case study, but the insights, analysis, and design decisions should be your own. Transparency matters—if you’re asked whether you used AI tools, be honest about it. Your voice and critical thinking are what evaluators are assessing.

My project didn’t have dramatic results. Is it still worth writing about?

Absolutely. Not every project leads to breakthrough findings or stunning visuals. Sometimes the most compelling case studies are about thoughtful process, careful research, or elegant solutions to modest problems. Focus on what you learned and how you think, not just on measurable outcomes.

How do I make my case study stand out from other students’ work?

Specificity and honesty. The most memorable case studies are those where the writer takes a clear position, acknowledges complexity, and shows genuine learning. Avoid generic claims about “human-centered design” and instead show exactly how you applied design thinking to your specific problem.

Should I include sketches and process work, or only polished final designs?

Include process work, but strategically. Show the evolution of ideas through key iterations—not every sketch you’ve ever made. The goal is to demonstrate your thinking, not to document every moment of your process. Label process images to explain what they show and why they’re included.

---

Conclusion

AI Unpacker tools work best as a thinking partner, not a writing tool.

The prompts in this guide are designed to help you develop clearer thinking about your design work, which then becomes a clearer case study. The key principles to remember:

1. Start with your narrative, not your process. Identify what makes your project worth reading about before you begin writing.

2. Use prompts that challenge you. Generic requests get generic results. Ask AI to push back on your assumptions.

3. Include research that informs decisions. Every major finding should connect to a design choice you made.

4. Be honest about limitations. Acknowledging what didn’t work adds credibility and shows growth mindset.

5. Tailor your case study to your audience. The same project can be framed differently for academic, professional, or portfolio contexts.

Your case study is your opportunity to show how you think, not just what you produced. Use these prompts to develop that narrative, and your work will speak for itself.