TL;DR
We held a small launch event in February 2026 with about 47 readers, journalists, and dermatology professionals. Three editorial assumptions came apart in the room. We thought readers wanted longer pieces. They wanted clearer entry points. We thought the FAQ was sufficient. It wasn’t. We thought our category structure was clear. It was not. Here is what we changed.
I have done a lot of launch events. Most are theater. You hand out the product, people are polite, everyone leaves with a tote bag, and the substantive feedback is missing. Our event was different. We deliberately made it small, kept the lights up, and put real chairs in real circles. About 47 people, including 12 long-time readers, 9 journalists, 4 dermatologists, and the rest from formulation and operations. Three hours, no deck. By the time the chairs were stacked, I had three pages of notes. Three of them mattered enough to change what we publish.
Lesson one: readers wanted entry points, not longer pieces
I had assumed, based on analytics and the response to our 2,500-word manifestos, that our reader liked long form. Some did. Most were doing something different. A reader would Google a specific question (“is squalane comedogenic,” “how long until tretinoin starts working,” “is azelaic acid pregnancy safe”) and land on a long piece that buried the answer under context. They would scroll, give up, sometimes find the answer in paragraph eleven, and remember the experience as “that brand has good info but you have to dig.” That is not a compliment. That is friction.
Tool: pregnancy-safe skincare planner — ingredients to avoid + safer alternatives by trimester.
The correction: every piece now opens with a TL;DR in a styled box. Thirty-five to sixty words. The qualifying detail moved into the body for readers who want it. We retrofitted the back catalog over six weeks. Reader satisfaction shifted from “useful but dense” to “useful and direct.” Time-on-page dropped for some pieces; the reader getting the answer in 20 seconds is better than scrolling for two minutes.
Lesson two: the FAQ was an afterthought, and readers were starting there
Most pieces ended with a four-to-six question FAQ. I had designed those as a courtesy, almost an SEO move, expecting the reader to skim them after the body. The data and the room told a different story. Many readers were scrolling directly to the FAQ, reading those answers first, then deciding whether to read the body. If readers were starting in the FAQ, the FAQ had to be doing real work, not parroting the body.
The correction: FAQ questions are now generated from actual reader queries, not from a generic template. Our content team pulls search-console data and email questions for each piece’s topic and uses the most-asked specific questions. The redundancy with the body shrank. I am still not sure we have this right, but the directional change (treat the FAQ as a primary surface, not a footnote) was correct.
Lesson three: the category branding was confusing readers
This one stung. We had built five editorial categories: The Elelaf Edit, Routines, Concerns, Ingredients, and Science. In the room, multiple readers told me they could not find what they were looking for. A reader Googling “can I use retinol if I’m pregnant” did not know whether to look in Routines, Concerns, or Ingredients. The cross-category nature of real reader questions was bigger than our taxonomy could handle.
The correction is still in progress. We added a search bar to every page and built tag-based hubs that cut across categories (pregnancy, microbiome, beginner, sensitive) as primary entry points. Browse the skinimalism archive or the botanical skincare archive as live examples. Information architecture is harder than it looks.
The contrarian section: small launch events outperform big ones
The instinct in beauty is to throw a 200-person launch with a step-and-repeat, a celebrity, and a tote-bag list. The press coverage is bigger, the photographs are better. The substantive feedback from a 200-person event is, in my experience, close to zero. People do not speak openly in those rooms. The format pushes you into small talk. The serious questions never surface because nobody wants to be the person asking a hard question in front of 200 strangers.
What we did instead, 47 people in small circles for three hours, was the most useful three hours we have spent in the brand’s first year. The press coverage you imagine from a 200-person event is mostly already determined by your pre-launch outreach. The real value of being in the same room with readers is the substantive feedback. You do not get that at scale.
What did not change
The core editorial position did not move. Skinimalism, slow skincare, fewer products consistently used. Microbiome and regenerative biotech as the science territories. The corrections were structural, not philosophical. The thinking still traces back to our founder note, the slow skincare manifesto, and the logic in why we won’t bottle skin cycling.
FAQ
How big was the launch event, exactly? 47 confirmed attendees plus four staff. Three hours. Small enough that conversation was real, big enough to surface patterns.
Did the editorial changes hurt your traffic? Time-on-page dropped on some pieces. Overall reader satisfaction (measured in surveys and email feedback) improved. Net, we count the change as positive.
Are the category names going to change? Possibly. We still use The Elelaf Edit, Routines, Concerns, Ingredients, and Science, but supplement them with tag hubs that may eventually become more primary.
How do I send feedback? Email, the Reddit thread we run, or in person at the next event. The Journal exists for readers, and we read everything that comes back.
What’s the most important thing the event taught you? That the reader’s behavior on the site is not the behavior we designed for. Designing for actual behavior is a continuous job, not a launch task.
Sources
Elelaf launch event, February 2026, transcripts and notes. Internal reader survey, March 2026. Search Console query data, January-February 2026.