Growth experiments live somewhere between a structured A/B test and a product investigation. They usually start from a clear hypothesis like 'shorter onboarding will lift day-7 activation,' run three or four variants instead of two, and document both the quantitative result and the qualitative learnings. The recap reads more like a story than a data dump, which means the share image has to set up the narrative rather than just surface a number.

The setup uses three custom fields: hypothesis_number for the corner mark (G14 for growth experiment 14), variant_count for an optional subhead detail like '3 onboarding variants,' and result_lift for the headline lift on the primary metric. The accent is a green tuned for growth-team posts, slightly more saturated than the experiment recap preset to distinguish the two categories in the same feed.

The post body carries the full narrative: the hypothesis, the variants tested, the data, the qualitative interviews if any, and the change shipped to the product. The card carries the hypothesis number and the headline result so readers can place the experiment in the team's broader research stream. Over time, the series of cards documents the growth team's thinking in a way that single posts cannot.

Growth teams that share experiment writeups publicly are doing more than marketing. They are building a documented research record that future hires, partners, and observers can browse. The value of that record compounds: each new hypothesis adds to the stream, each result confirms or contradicts earlier work, and over time the team develops a public reputation for thinking carefully about growth questions.

The share image is the surface that makes the record visible. Without a consistent card on every writeup, the stream reads as scattered posts. With a consistent card, the same accent, same corner-mark style, same two-line subhead structure across dozens of experiments, the stream reads as a research program.

SleekPixel makes the consistency almost free because the template is the source of truth and the post fields drive the layout. Six months after a hypothesis is published, the card on the post still carries the hypothesis number and the result lift because the fields are still in the post. Two years later, when a new growth analyst joins the team and browses the company blog, they see a continuous research stream that documents the team's thinking on growth.

That continuity is the real reason to share experiments publicly, and SleekPixel makes the visual half of the continuity essentially automatic. The team focuses on the experiments themselves, the templates focus on the visual presentation, and the resulting record looks like a deliberate research program even when each individual post is written by a different teammate.