Why this persona fits the audience
Works in a 3-person design/product pod at a seed-stage SaaS company in Chicago. He regularly receives PNG marks from partners and event sponsors and needs them in SVG for landing pages, in-app empty states, and docs; he already has an Adobe CC subscription.
- Age: 32
- Location: Chicago, Illinois, US
- Occupation: Product designer
- Income: $140k/year
- Education: MS in human-computer interaction
- Company size: Seed-stage (8-12 employees)
- Years in role: 6
“A good design system isn't about having pretty components; it's about making sure the next person doesn't have to reinvent the wheel just to make a button look right.”
Alan Schiller, 32, is a Senior Product Designer operating out of a bustling seed-stage SaaS company in Chicago. Holding a Master's in Human-Computer Interaction, he navigates the intersection of aesthetic rigor and functional utility with the precision of a watchmaker. His career trajectory has been marked by a shift from pure visual design to systems thinking, driven by a frustration with fragmented digital experiences. Currently, he operates within a lean three-person pod, where he wears multiple hats ranging from UX research to frontend prototyping. A defining characteristic of his recent work life is the persistent bottleneck caused by external dependencies: partners and sponsors frequently deliver low-quality PNG assets that require labor-intensive vectorization for use in high-fidelity contexts. While he possesses a comprehensive Adobe Creative Cloud suite, the weight of those applications often feels disproportionate to the task of cleaning up simple logos, leading him to seek lighter, more specialized workflows. Financially stable with a six-figure income, Alan values time efficiency above all else, viewing every minute spent on manual asset cleanup as a lost opportunity for innovation. He is deeply embedded in the Chicago tech and design community, known for his contributions to local meetups and his insistence on maintaining high standards of usability despite the chaotic nature of early-stage product development. His personal life mirrors his professional ethos: structured, active, and focused on sustainable growth.
Background & daily life
A day in their life
Alan wakes at 5:30 AM for a run along the Lakefront Trail, returning just as the sun breaks over the skyline. After a quick breakfast and shower, he joins his virtual stand-up at 9:00 AM, where he defends the current sprint's progress against a tight deadline. By 10:30 AM, he is deep in Figma, refining a new onboarding flow, but gets interrupted by a request from Marketing to convert five partner logos into SVGs for a webinar landing page. He spends an hour wrestling with an auto-trace tool that fails to preserve the brand's specific kerning, forcing him to manually redraw paths in Illustrator. Lunch is a sandwich eaten at his desk while reviewing analytics dashboards. The afternoon is split between code reviews with engineers and a workshop on design tokens. He leaves the office by 6:00 PM, heading to a community garden project or a client call before ending his day with reading or editing photos from his weekend hike.
Lifestyle
Alan lives in a converted industrial loft in Logan Square, filled with mid-century modern furniture and a dedicated home office that doubles as a studio. His mornings are non-negotiable: 5:30 AM wake-up, a 7-mile run along the lakefront before the city fully wakes, followed by a precise coffee ritual using a Chemex. He is financially disciplined, maxing out his 401(k) while saving aggressively for a down payment on a condo. Socially, he prefers small, deep conversations over large networking events, often gathering with his partner and two other couples for dinner or board game nights. He maintains his physical fitness through running and occasional rock climbing, viewing health as a long-term investment rather than a vanity project.
Work life
At his seed-stage SaaS startup, Alan is one of three designers supporting a product team of twelve. The environment is chaotic but high-autonomy; there is no dedicated engineer for design handoff, so he often writes basic code snippets to prototype interactions. His primary friction point is the constant influx of marketing assets—partner logos and sponsor graphics—that arrive as low-resolution PNGs. He spends hours weekly manually tracing these in Illustrator or wrestling with auto-trace algorithms to create clean SVGs for documentation and web headers. Despite having a full Adobe Creative Cloud license, he frequently feels the software is too heavy for simple vector tasks, leading him to juggle between Figma, Illustrator, and various online utilities just to get files ready for engineering.
Relationships
Alan is married to Elena, a civil engineer, whose pragmatic approach balances his creative tendencies. They have a close-knit circle of four other couples from their graduate program days, meeting monthly for potlucks. Professionally, he relies heavily on his two co-designers, treating them as intellectual sparring partners rather than just colleagues. He maintains loose ties with his former professors at the HCI program, occasionally consulting them on research methodologies. His community is largely defined by the Chicago running scene, where he bonds with peers over early morning miles rather than office politics.
How they decide
Alan is a methodical researcher who gathers data before acting. He rarely makes impulsive purchases, preferring to test free versions, read technical documentation, and consult peer reviews. When evaluating solutions, he prioritizes workflow integration and long-term reliability over immediate cost savings. He is skeptical of 'magic button' promises and looks for transparent technical specifications. His decisions are influenced by how well a tool fits into his existing ecosystem and whether it reduces cognitive load, often spending significant time prototyping a solution internally before committing to any new software stack.
How they sound
Alan speaks with a calm, Midwestern cadence, avoiding hyperbole. He uses precise terminology like 'vectorization,' 'path smoothing,' and 'accessibility compliance' without hesitation. In conversation, he tends to pause before answering, thinking through the logic of his statements. He avoids emotional language when discussing work, preferring to frame issues as structural or process-based problems. He rarely says 'I think' or 'maybe'; instead, he offers 'Based on the data...' or 'The constraint here is...'. He is polite but direct, cutting off circular arguments quickly if they lack a logical conclusion.
Personality traits
- methodical
- visually critical
- pragmatic
- quietly competitive
- systematic
- detail-oriented
- resourceful
- stoic under pressure
- collaborative but independent
- adaptable
Goals
- Build a scalable design system that reduces component creation time by 40%
- Publish a case study on optimizing user onboarding flows for B2B SaaS
- Run a sub-3-hour marathon within the next 18 months
- Achieve financial independence markers by age 40
- Transition into a Staff Designer role with broader strategic influence
- Mentor junior designers through local university workshops
Problems & frictions
- Inconsistent file formats from external partners delay launch timelines
- Lack of clear ownership on design system maintenance across the engineering team
- Time spent on manual asset cleanup detracts from core product feature work
- Balancing rapid iteration needs with long-term technical debt reduction
- Difficulty finding reliable third-party vendors who understand accessibility standards
- Limited budget for specialized training or conference attendance
Values
- usability
- design consistency
- cross-functional clarity
- technical precision
- efficiency
Interests
- design systems
- product analytics
- running
- minimalist interfaces
- urban planning
- analog photography
Media habits
- Lobsters newsletter
- Raycast community forums
- Local running group Slack
- Design Systems Weekly
- NPR All Things Considered
- GitHub repositories for open-source tools