Small, Clean Datasets & Persona LLM Visibility | Madison Weekly
Komal reviews a completed 136-image hand-annotated loon dataset, explains why extreme scale variance in the bounding boxes creates two distinct detection problems, and previews a new persona-based LLM brand visibility study.
Komal gives the weekly Madison update on two parallel workstreams: finishing a hand-annotated bird dataset for a conservation computer vision project, and designing a new way to measure how visible a brand is to specific customer personas rather than to a generic average user.
Closing the annotation set
The team closed out an annotation set of 136 quality-checked loon images this week, with every bounding box drawn by hand. The images come from a mix of sources, frames pulled from the web, shore-based shots, and drone footage over water, all labeled under a single class: common loon. Nothing in the set was labeled and then discarded; quality control ran before the boxes were finalized, not after.
Why the scale range is really two problems
Looking across the 136 images reveals a wide range in how much of the frame the bird actually occupies. In close-up shots, the bird fills a large portion of the picture and details like the collar, the beak, and the red eye are clearly visible. In distant shots over open water, the same bird is reduced to a dark smudge only a few pixels wide, and the water's motion and glare add noise on top of that. Komal's point is that these aren't the same detection problem with different difficulty levels, they're two distinct problems being trained under one label.
Why the team is training now instead of waiting
With only 136 images, there's a natural pull to keep annotating until the dataset is larger before running any model. The team's call is to run a first YOLO model now anyway, not because 136 images is enough to produce a strong detector, but because the first run is a test of the pipeline itself: label formatting, parsing, class mapping, whether loss actually moves during training. Catching a plumbing problem now, while the dataset is still small and clean, is far cheaper than catching it after a thousand more boxes have been added on top of a broken pipeline.
The persona visibility study
Alongside the imaging work, the team opened a second research thread: a persona-based LLM visibility study. The question isn't only which brands an AI model recommends, but who it recommends them to. A brand can score well in a general visibility measure and still be effectively invisible to a specific segment that matters to it, such as students, developers, creative professionals, or enterprise buyers. This week's work was research design; prompt sets and an evaluation prototype come next.
A rigor-first brand archetype tool
The team also sketched a plan for a brand archetype diagnostic based on Jungian archetype theory. Most existing tools in this space ask a founder for a handful of adjectives and return a label, which Komal flags as the core gap: there's no rigor behind the output. The plan instead is to score a brand's actual language, return both a primary and secondary archetype with the tension between them named explicitly, and finish with practical guidance on voice pillars and the common trap associated with that archetype. Before building anything further, the plan calls for validating the approach by hand against a few real brands first.
Key takeaways
- The team completed a 136-image hand-annotated loon dataset with quality control applied before finalizing the boxes, not after.
- Extreme scale variance between close-up and distant frames means the dataset is really training two distinct detection problems under one class label.
- Running a first YOLO model on a small, clean dataset is a deliberate test of the labeling and training pipeline, not an attempt to produce a strong detector yet.
- A new persona-based LLM visibility study aims to measure whether a brand is visible to specific customer segments, not just in a general average score.
- The planned brand archetype diagnostic scores actual brand language rather than adjectives, and will be validated by hand before any further build.
Who this is for
This is for people following the Madison project's computer vision and brand research work, and for anyone building a small labeled dataset or a brand visibility evaluation who wants a concrete example of testing infrastructure before scaling up.
Chapters
- 0:00Weekly Overview: From Hand-Drawn Boxes to Active Testing
- 0:35The Scale Paradox: Distinguishing Close-Up Birds from Open Water Smudges
- 1:10Testing the Plumbing: Why You Should Run YOLO on Small Datasets Early
- 1:45Persona LLM Visibility: Auditing Segment-Specific Recommendations
- 2:20Beyond Adjectives: Designing a Rigorous Brand Archetype Diagnostic
Full transcript(auto-generated, with timestamps)
Weekly Overview: From Hand-Drawn Boxes to Active Testing
[0:00]Hedge. This is Leum in for KML Madison's weekly update. This week, the team closed the annotation set about 136 quality checked LON images, every box drawn by hand. They designed a Persona LLM visibility study, and they wrote the plan for a Yian brand archetype detector. Here's the week in one breath. The quality check ran first, then the boxes. Small, clean, ready for a first YOLO run. Nothing trained yet. Overall, brand visibility scores hide who the model is talking to. And most archetype tools guess from a brief. The team wants evidence, a hybrid read, and a brief you can actually use. Last week, the boxes
The Scale Paradox: Distinguishing Close-Up Birds from Open Water Smudges
[0:35]Were a promise. This week, the promise closed. About 136 images that already passed quality control, frames from the web, Nikon shots from shore, drone over water, one class common loon, every box by hand. Nothing got labeled that was going to be thrown away. Look at the range. In some frames, the bird fills half the picture. In others, the box is a dark smudge a few pixels across on open water. Close in you get the collar, the beak, the red eye. Far out, all of that is gone, and the water moves and glints. That is not one detection problem. It is two wearing one name. So train now or keep annotating. 136 is
Testing the Plumbing: Why You Should Run YOLO on Small Datasets Early
[1:10]Small, and the pull is to wait until the set can win. The call, the first run, is not a test of the detector. It is a test of the plumbing, labels, pars, classes, map, loss moves before there are a thousand more boxes to redo. Small and clean is the version you can still fix cheaply. Next week, the first YOLO run. The team also opened a Persona LLM visibility study. Not only which brands an AI recommends, but who it recommends them to. A brand can look loud in a general score and stay invisible to a segment that matters. For laptop personas, student developer, creative, enterprise buyer. This week was the research design. Next, the prompt data
Persona LLM Visibility: Auditing Segment-Specific Recommendations
[1:45]Set and an evaluation prototype and a strategic plan for a Yian brand archetype detector. Most tools ask a founder for adjectives and hand back a label. The gap is rigor. Score the brand's actual language. Return a primary and a secondary with the tension named and finish an application. Voice pillars and the trap of that archetype. Validation first. Run it by hand on a few real brands. Then decide whether to build. Let's recap with Claude. About 136 hand boxes. One class quality first. Nothing trained. First yolo next week. Persona visibility. Four personas controlled prompts design this week. Archetype detector as a diagnostic, not
Beyond Adjectives: Designing a Rigorous Brand Archetype Diagnostic
[2:21]A quiz. Design judgment. A small clean set in a score that names who it is for. Beat a big average that hides the miss. Your turn. Paste this into Claude. I have a labeled set of about 136 images, one class with huge scale range. Sort every box by area. Compare the smallest tenth to the largest. If they do not look like the same problem, write two evaluation splits before I train. Then for a brand visibility study, name four user personas and the one metric and overall score would hide. Madison weekly step four.
More from Madison
5:48Ground Truth & Lovable Prototypes: Loon Conservation AI Progress | Weekly Update by Komal
2:28Transitioning from Raw Images to Structured Labeled Data in Loon Conservation
2:26Build vs. Borrow: Locking Scope & Integrating CVAT in Loon Conservation AI
2:08Every Box Checked: Closing the Promise on Ground-Truth Data | Nikhil
1:55Build the Door First: Centralizing and Ingesting Clean Training Data by Nikhil
1:45