“The workshop sold out” sounds impressive until someone asks how many seats were available. A useful case study gives readers enough to make sense of the result: what changed, when it changed, and what happened afterward. A cardmaker, for instance, might replace a general workshop description with photos of the finished light-up card and a materials list, then fill 10 of 12 seats over three weeks. That is a concrete result, though it does not prove which part of the new description led to the bookings.
For a cardmaking shop, teacher, or craft blogger, a case study connects a real starting point to an action and an observed result. A testimonial tells you what someone thought; a case study shows what happened. And the result need not be higher sales. Fewer supply questions, less assembly time, or more beginners finishing their cards may matter just as much.
Choose one question the case study can answer
Keep the project contained. “How did we grow the business?” is hard to support with a few photos and records. “Did adding a step-by-step supply photo help beginners prepare for a stamping workshop?” gives you something you can check.
Look for a visible starting point, a documented change, and an outcome you can examine. A maker selling custom birthday cards could look at a revised proof-approval process. A tutor could compare classes before and after introducing a pre-cut paper kit for a stencil workshop. A blogger could examine how readers used a printable marker-coloring guide after its instructions were clarified. Stay with the process you studied rather than drifting into a general guide to service pages or tutorials.
Be clear about whose result you mean. If an event organizer found setup easier, you need their perspective and permission to share it. If you packed kits faster, your own records can support that claim. They are different results, even if they came from the same project.
Find a result that matters to a real person
Measure the problem you were trying to solve. If customers kept asking which markers worked with a stamped design, count those supply questions rather than unrelated page views. If a workshop ran late, note how many participants finished their cards during the session. Numbers are useful, but a teacher’s observation can be useful too: perhaps beginners assembled a battery-and-LED card without repeatedly needing help with the same connection. Call that an observation, not a measured rate.
- Before: What was the difficulty, and how was it recorded?
- Change: What did you alter, and when?
- After: What happened over a stated period or number of projects?
- Limits: What else might have affected the outcome?
Mixed results are still worth sharing. If a brighter photo attracted interest but did not reduce questions about card size, say both. That boundary may be more helpful to another maker than a claim that every adjustment worked.
Collect the evidence before drafting the story
Start with what you already have: dated instructions, workshop plans, order logs, customer messages, production notes, and photos of finished cards. Remove private details from working copies. Put dates and definitions beside your totals. “Eight orders” means little unless readers know whether they came in over a weekend or two months, and whether repeat orders count.
A simple evidence sheet makes it easier to check the story as you write:
| Item | What to record | Why it helps |
|---|---|---|
| Starting point | Previous process, time period, and relevant count | Shows the point of comparison |
| Intervention | Exact revision and the date it began | Keeps “improvements” from becoming a vague catch-all |
| Outcome | Same measure over a comparable period | Makes the comparison understandable |
| Context | Season, group size, promotion, or supply changes | Shows other plausible influences |
| Permission | Approval for names, quotes, and identifiable images | Protects participants and clients |
Suppose you want to describe a change in completion time for a stamping class. Compare sessions of similar length and size if you can. If one had four experienced makers and the other had twelve first-timers, tell readers; it is not a clean comparison. And if the only record is the teacher’s estimate, write “the instructor estimated” rather than presenting the time as a measurement.
Keep the original records long enough to check the finished account. A spreadsheet total helps, but dated booking entries show where it came from. Do not collect extra customer information just because it might make the story sound persuasive later; keep only what you need and have permission to use.
Build the case around a decision, not a victory lap
Start with the constraint behind the decision. Say a small cardmaking studio wanted participants to make an interactive card, but wiring a tiny LED behind the paper panel took too long for the scheduled workshop. That tells readers why the studio needed to change something. “We created an innovative experience” does not.
Then say what changed. Did the studio pre-cut the circuit layers, add a diagram of battery polarity, or choose a thicker card base to hide the wiring? Those details explain the intervention without turning the case into a full interactive-card tutorial. If the studio made several changes at once, name them all. The diagram cannot take sole credit if pre-cutting and extra teaching time were part of the session too.
End with what you saw, not what you hoped the change would do. A clearer materials list may coincide with fewer pre-workshop emails. It cannot tell you whether every attendee read the list, or whether the list caused the whole drop.
A compact example, with the evidence made visible
This is an illustrative example, not a report of an actual business. A cardmaker running beginner stencil-and-marker sessions keeps getting messages about whether participants need to bring coloring tools. They update the booking confirmation with a photo of the supplied kit and a sentence saying markers are provided. Across the four sessions before the change, they logged 11 tool-related messages from 38 booked participants. Across the next four, they logged four from 36 participants.
What can they say? Fewer tool-related messages were logged in the second set of sessions, and the revised confirmation may have helped clarify what was provided. They cannot claim the photo “cut customer confusion by a proven percentage.” The groups were small, participants may have differed, and the wording changed along with the photo. The remaining questions are worth mentioning, especially if they prompted another edit to the confirmation.
Make the numbers legible without overstating them
Give the count and its denominator when you have both. “Nine participants completed a card” means something different in a class of ten than in a class of twenty. Include the time window, too. Compare the same workshop format, similar booking periods, or comparable order types. If the samples differ too much, describe them separately instead of forcing a neat before-and-after figure.
Keep output and outcome distinct. Publishing six product photos is an output; receiving fewer requests for size clarification is an outcome. Selling more handmade cards is a business outcome, but a holiday, a market event, or extra stock could also have played a part. Put that context beside the result, where readers will see it.
Take the same care with money. Revenue is not profit: paper, envelopes, LEDs, packaging, fees, and the maker’s time all affect what remains. If you discuss costs, say which you counted. Any budgeting example is a general planning illustration, not individual financial advice. When records are incomplete, describe the time saved or orders handled rather than inventing a return-on-investment figure.
Use quotes and photos as evidence, not decoration
A quote can tell you something a count cannot. “I knew which markers to bring” identifies what the participant found clear. Get permission to publish their words, name, role, and project image. Permission to read or keep a private message is not permission to publish it. If you shorten a quote, keep its meaning; never stitch several people’s comments into one attributed statement.
Choose photos that show the detail at issue. A close view of the revised supply kit helps document a change to workshop preparation. A beautiful finished card, on its own, does not. For a light-up-card case, a photo might show the switch position and finished panel while the text explains what happened in class. Write alt text that describes the image, and check the frame for addresses, order numbers, or handwritten personal messages before publishing.
Give mixed feedback its place as well. If someone liked the stencil design but struggled with ink smudging, that tells you where the project fell short. For the separate task of replying to public feedback, see the guide to handling customer reviews for a cardmaking shop. Keep this case study on the project and its evidence.
Give readers enough detail to judge whether the result transfers
A result depends on the setting. A pre-packed kit may suit a twelve-person local class but take too much time or money to prepare for a larger event. A revised custom-card approval form may be clear to repeat customers yet leave first-time buyers with questions. Include the audience, scale, skill level, and any unusual materials so readers can judge what applies to their own work.
Before publishing, go through the draft with the records open. Can you trace each figure to a dated source? Are the client’s words separate from your interpretation? Have you mentioned other changes made at the same time? Check the title against the evidence, too. “How a Kit Photo Clarified Supplies for Beginner Card Workshops” is more defensible than “The Photo That Eliminated Workshop Questions” if questions remained.
Keep a short working note with the intervention date, records used, and permissions granted. If a participant later withdraws permission to display their card, you can find the exact photo and caption to remove without having to guess.