Fragile foundation risk: the initial instinct was to embed TikTok links directly. Embeds are slow, off-brand, and break if the source account changes. The decision was to extract and self-host the actual media files instead, trading some extra prep work for a site that doesn't depend on a third party staying up.

Vague positioning risk: "the media guy" alone doesn't tell a hiring client what they're hiring for. The decision was to let the actual work define the specialty (photography, cinematography, on-camera talent) instead of guessing at a broader brand promise.

Overclaiming risk: early drafts described Femi as a "video editor" based on an assumption. When corrected, every instance of that claim was removed across the entire site — hero copy, meta description, section headers, role cards — not just the one place it was first flagged. A portfolio's credibility depends on the words matching the actual skill set exactly.

Rather than filler stats, the video reel cards display real TikTok Studio analytics that Femi provided — views, likes, saves, average watch time — with one weak retention metric deliberately left out. A number that would read as "nobody finished this video" doesn't help a hiring client decide anything, so it was cut even though it was technically "more transparent" to include.

The palette (moss/olive, cream, charcoal-green) deliberately avoids the black-and-neon-green combination that's become a generic default for creative portfolios. The site's signature motion device, a scroll-progress bar styled like a video scrubber, and its caption styling both borrow directly from Femi's own footage rather than a generic template motif — the goal was a site that could only belong to this client, not a reskin.

The build went through multiple real QA rounds, each one driven by the client testing the live site on his own devices and reporting specific, concrete issues: a broken CSS rule that silently hid an entire section, a positioning bug that made a caption overlap live data, a decorative element that read as a glitch instead of a feature. Every round, the fix was diagnosed at the root cause and verified against the whole file, not just patched at the one spot reported. That loop — ship, get real feedback, find the actual cause, fix it everywhere it appears, re-verify — is the same discipline that matters on any client project, not just this one.