Visual content system
05 / 08Teamind Visual Content System
A cross-channel visual system for explaining Teamind collaboration scenarios consistently and giving Operations reusable formats
At a glance
BriefOperations needed to publish recurring content without rebuilding every asset, while the product lead wanted a recognizable Teamind identity across channels.
My contributionI defined the color direction, layout rules, content templates, channel adaptations, and ongoing visual support. Operations owned the content categories, copy, and scenarios.
Evidence boundaryThe archive confirms the visual output and repeated formats. It does not preserve production-time, reach, engagement, or conversion data.
Brief & ownership
Solve a production bottleneck without turning content into feature lists
Operations needed to publish recurring product content more efficiently, while the product lead wanted users to recognize Teamind across channels.
Operations owned the categories, copy, and scenarios. I translated those inputs into color direction, layout rules, reusable templates, and channel-specific formats. Because online whiteboards were still unfamiliar to many people, each piece also had to explain a collaboration scenario without becoming a feature list.
Visual system
Create a template family, not one fixed layout
Operations organized the work into scenario inspiration, product education, and feature releases. I designed a template family for those content types instead of forcing every topic into one composition.
The palette, typography hierarchy, layout rules, and screenshot treatment fixed the decisions that should stay consistent while leaving room for different copy, scenarios, and product images. Within those boundaries, I adjusted scale, composition, and supporting graphics for each piece.
Channel adaptation
Adapt information density without losing recognition
I used each platform’s requirements to define canvas size, text scale, and information density. Short social posts focused on one idea, while video and community covers needed a stronger title and more context.
The composition changed by channel, but the color direction, typography hierarchy, and visual tone continued to identify the work as Teamind.
Working model
Use real content to set the system, then review before release
Operations brought the copy, scenario, and publishing need. I selected the appropriate template, adapted the information hierarchy, and provided ongoing visual support for new topics.
Each format went through internal review before release. The review aligned the content need with the visual execution; it was not audience testing.
Delivery & evidence boundary
A reusable visual system, with its evidence boundary stated clearly
The delivered templates supported scenario inspiration, product education, feature releases, community content, and video promotion across Xiaohongshu, WeChat, and Bilibili.
The system was intended to reduce repeated layout decisions and help Operations produce recurring content more efficiently. The archive confirms that formats were reused, but it does not contain production-time or channel-performance data.
I therefore present this project as evidence of visual-system thinking, cross-channel adaptation, and ongoing operational support—not as proof of marketing impact.
Next Project