When I joined the project, Apolitical had already gone through several attempts on LinkedIn social posts and visual identity, none of which had worked. The problem wasn't lack of effort. It was lack of alignment. Each attempt tried to fix the surface (style, colors, templates) without first answering the right question about what the system actually needed to solve.

Before proposing any visual direction, I ran a structured discovery process. I looked through the content history on LinkedIn and the client's other social channels, and put together a discovery brief around the criteria I felt were essential to get to a result that actually matched the business need, not just another aesthetic. The decision was to prioritize function before form: figure out how the system needed to behave first, and let that shape the visual standard, instead of the other way around, which is what had been tried up to that point.

A concrete example of this: the client came in with a long, fragmented list of content categories. Instead of trying to account for all of them visually, I restructured it, grouping and absorbing subcategories into the content types the team actually used regularly: Events, News, Courses, Article, Newsletter, Hiring, Announcements. That simplification became the foundation the visual components were built on, so each category had a clear, recognizable pattern instead of a one-off visual exception for every variation.

That shift in approach is what broke the cycle of fragmented attempts and got the project to a system with real consistency in style, components, patterns, and objectives.

Instead of delivering a set of static templates, I built the system around a proper component library: a foundations layer covering Logo, Colors, Typography, Iconography, Badge, Signature Tile, and LinkedIn Tile, with master components reused as instances across 934 individual placements throughout the templates. Updating a master component propagates that change across the whole system.

Since the people actually using this day to day were non-designers, the library ships with governance built directly into the file. There's a dedicated Foundations page documenting how components and instances relate, why deleting a master component breaks every instance built on it, when to use "Detach Instance" for one-off exceptions, and naming conventions to keep the library organized as it grows. That's what turns the library into a real single source of truth the marketing team can rely on without needing a designer to step in.

The system also includes an onboarding layer, a "Get Started" page explaining what the file is for and how to use it, which doubled as a bridge between the agency and the client's marketing team, keeping both sides working off the same assets and process.

On top of the foundations, the library covers 10 content categories the marketing team actually publishes regularly: News, Courses, Keywords, 100 Lists, Article, Newsletter, Event, Hiring, Announcements, and Communities of Practice, each with several validated template variations. Contextual guidance sits right next to each variation (text/image contrast rules, when to use a background image versus a solid color, how to swap logos or images), and multi-frame carousel posts follow a defined pattern: the logo shows up only on the first and last frame, with an arrow motif signaling continuity through the middle frames.

That combination, governed components, embedded documentation, and an onboarding layer for non-designers, is what made the system genuinely self-service.