Interview
Brand Design Tips From Linear Founder Karri Saarinen
- Early-stage websites should be built rapidly (within one day) to prioritize product development over polished aesthetics, avoiding the risk of setting user expectations for a product that "isn't there yet."
- Brand messaging must be specific (e.g., identifying the product as a "chat app") to filter for ideal users and prevent vague narratives, while allowing founders to speak ambitiously to investors.
- As companies scale to include enterprise clients, brands must balance fitting current customers without evolving into a generic "enterprise oracle" style, while adapting content to include security details, customer stories, and text-heavy materials for corporate buyers.
- Landing page design should provide sufficient information to engage strangers without overwhelming them, utilizing grouped workflows by user type (e.g., YouTubers, business people) and avoiding distracting elements like looping movements or floating bottom elements that users ignore.
- For non-technical audiences, homepages should be simple at the top rather than information-dense, using clear navigation targeted to specific roles and prioritizing customer-based stories over feature-based explanations.
- Conversion challenges for enterprise products may stem from users not evaluating tools randomly; strategies to improve this include offering self-service trials, using industry-specific language, and providing prompts that demonstrate specific use cases rather than requiring immediate demo bookings.
- Memorable branding relies on unique fonts for headlines paired with standard typefaces for readability, along with organic visual elements, while ensuring claims about safety or methodology effectively mitigate audience uneasiness.
- To clarify a company's nature for technical versus non-technical audiences, websites should explicitly state affiliations (e.g., "built by creators of deep eval") and identify specific early adopter groups.
- Trust-building remains critical for products handling sensitive assets, requiring design choices that convey stability and reliability, similar to the focus on trust concerns during early-stage fintech development.
- Potential risks in website design include creating "chaos" through excessive automatic movement, failing to guide users on product location or explanation, and overloading navigation with unverified assumptions about customer support needs.