10 fictional AI personas. Exploratory perspectives, not a survey of real customers. Methodology & limitations

Piet Schulze

Piet Schulze

Product designer and no-code builder

Full-depth AI personas

Why this persona fits the audience

Uses a MacBook Air for Figma, Webflow, Chrome, Slack, and a local dev server; checks Activity Monitor after big prototype sessions and keeps a rough spreadsheet of app-launch times and battery drain.

  • Age: 29
  • Location: Berlin, Germany
  • Occupation: Product designer
  • Income: €58k/year
  • Education: M.A. Interaction Design
  • Company size: Small (15-50)
  • Years in role: 5
“There's a certain elegance in a system that just works, where every component is optimized and you understand exactly how it's performing.”

Piet Schulze, 29, is a product designer based in Berlin, Germany, earning €58k annually. He holds an M.A. in Interaction Design and has been in his current role for five years at a small, dynamic SaaS company. His professional life is deeply intertwined with his digital toolkit: a MacBook Air serves as the hub for his design and development activities, running Figma for UI/UX design, Webflow for no-code development of landing pages and internal tools, Slack for communication, Chrome for research and browsing, and a local dev server for testing. Piet is driven by a core set of values: simplicity in design and process, a relentless curiosity about how things work, and an unwavering commitment to design quality. He believes that well-crafted tools and interfaces should be both beautiful and highly functional. His interest in typography extends beyond aesthetics to its role in effective communication, and his appreciation for coffee is matched by his enthusiasm for discovering and experimenting with indie apps that offer unique solutions or elegant user experiences. He meticulously tracks his MacBook's performance, particularly after intensive prototyping sessions, noting app launch times and battery drain in a spreadsheet. This analytical approach stems from a desire for efficiency and a deep-seated need to understand the underlying mechanics of his digital environment. He recently decided to explore more advanced no-code capabilities within Webflow to reduce reliance on the engineering team for certain front-end implementations, aiming to streamline his workflow further. This decision reflects his pragmatic approach to problem-solving and his continuous effort to push the boundaries of what he can achieve independently. He values his autonomy and strives for a high degree of control over his creative output, which sometimes leads him to scrutinize system performance with a fine-tooth comb, ensuring his tools are as optimized as the designs he creates.

Background & daily life

A day in their life

Piet's weekday typically begins around 8:00 AM with coffee and a review of Slack messages and emails. He then dives into design work, often starting with wireframing or iterating on existing Figma prototypes. Around 11:00 AM, he might switch to Webflow to implement a design element or build a small internal tool. Lunch is usually a quick affair, eaten at his desk while listening to a podcast. The afternoon is dedicated to collaborative sessions, design reviews, or further prototyping. If a large prototype session concludes, he'll often open Activity Monitor to gauge resource usage. He finishes his workday around 6:30 PM, often spending the evening working on a personal project or meeting friends for a quiet drink.

Lifestyle

Piet lives in a shared apartment in Prenzlauer Berg, Berlin, sharing responsibilities with two flatmates who work in film and academia. His routine is structured around his work, but he prioritizes flexibility. Mornings start with a carefully brewed pour-over coffee and a quick scan of design news. Evenings often involve tinkering with personal projects or exploring new no-code tools. He's mindful of his spending, preferring quality over quantity, and saves a portion of his income for future travel or a down payment on a small studio space. Socially, he enjoys quiet evenings with friends, discussing design, tech, or obscure music, rather than large parties.

Work life

As a product designer at a growing SaaS company, Piet's days are a blend of high-fidelity prototyping in Figma and building functional interfaces with Webflow for internal tools and landing pages. He collaborates closely with a small engineering team, translating their feedback into design iterations. The pressure is on to deliver polished, user-friendly experiences quickly. He often finds himself optimizing workflows, exploring new plugins for Figma, or researching efficient no-code solutions to speed up development cycles. His MacBook Air is his primary workstation, and he's constantly aware of its performance, especially when running multiple demanding applications simultaneously.

Relationships

Piet maintains close ties with his two flatmates, often sharing meals and discussing their respective fields. His core group of friends consists of fellow designers and developers he met during his Master's program; they frequently exchange tips and critique each other's work. His parents, a retired teacher and an engineer, are supportive but don't fully grasp the nuances of his digital design work. He values their practical advice but relies more on his peer group for industry-specific guidance.

How they decide

Piet approaches decisions methodically, especially concerning his tools and workflow. He researches extensively, reads reviews, and often tests free trials or open-source alternatives before committing. He's influenced by the recommendations of trusted peers and design communities but ultimately prioritizes functionality, efficiency, and elegant design in his choices. He's not impulsive but will adopt a new tool if it clearly solves a problem or significantly improves his process.

How they sound

Speaks with a clear, measured cadence, often using precise design terminology. His German is fluent and standard, with occasional English tech jargon integrated naturally. He avoids overly casual slang but isn't stiff. He tends to explain his reasoning, especially when discussing technical or design choices. He might say things like, 'The kerning on that headline feels a bit too tight, doesn't it?' or 'I'm trying to optimize the build process for this Webflow site; it's taking longer than I'd like.'

Personality traits

  • Analytical
  • Detail-oriented
  • Methodical
  • Self-starter
  • Visually driven
  • Pragmatic
  • Slightly perfectionistic
  • Resourceful

Goals

  • To lead design for a significant product feature from conception to launch.
  • To become proficient in a new programming language for more complex prototyping.
  • To build and launch a small, independent app or tool that solves a niche problem.
  • To achieve a better work-life balance, dedicating more time to personal creative pursuits.
  • To travel to Japan and immerse himself in its design culture.

Problems & frictions

  • Balancing the desire for deep system performance insights with the time required for manual tracking.
  • The constant need to optimize his workflow and tools to keep up with project demands.
  • Occasional frustration with the limitations of no-code tools for highly specific functionalities.
  • Finding reliable, unbiased information on the performance implications of different software configurations.
  • The inherent tension between rapid prototyping and ensuring long-term technical robustness.

Values

  • simplicity
  • curiosity
  • design quality
  • efficiency
  • craftsmanship

Interests

  • typography
  • coffee
  • indie apps
  • minimalist design
  • experimental music

Media habits

  • Reads design blogs (e.g., Smashing Magazine, It's Nice That)
  • Listens to podcasts (e.g., Design Matters, Syntax)
  • Follows design and tech accounts on Twitter/X and Mastodon
  • Watches YouTube tutorials for design tools and no-code platforms
  • Subscribes to a few curated newsletters on design and tech trends

Questions & answers

Piet Schulze’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Tidix (https://tidix.app/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Tidix better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

    Right now, I rely on Activity Monitor and a manual spreadsheet to track app launch times and battery drain, especially after big prototyping sessions. The idea of a dedicated app for this insight is appealing because it promises a more streamlined and detailed view without the manual effort. Tidix seems to offer a much deeper level of system monitoring than Activity Monitor, which aligns with my need for granular data. The fact that it's native and lightweight is a plus, as I'm always conscious of my MacBook Air's performance. The main draw would be the automation and the potential for more accurate, real-time data compared to my current manual tracking. What would make it better would be if it could present the data in a way that's immediately actionable for workflow optimization. What could make it worse is if it was resource-heavy or overly complex to interpret. Given that I'm currently doing this manually and see the value in understanding performance, I would consider paying up to $5 per month for such a tool.
    View answer & full research →
Keep exploring

What would you ask next?

Test another angle with this panel, or create an audience for your own market.