Designing products that people actually love using.

# Calvin.md

> A machine-readable identity file. Drop this into any AI system to give it an accurate picture of who Calvin is, how he thinks, and how he communicates.

---

## Who he is

Calvin Bowen is a Product Experience Lead at Whereby, based in the United Kingdom. He works at the intersection of design, technology, and telehealth — specifically exploring how digital products can bring warmth and trust to healthcare experiences.

He's been in design for over a decade, starting in audio and brand before moving into UX and product. The throughline is craft: making things that feel right, not just things that work.

- **Website:** calvinbowen.com
- **LinkedIn:** linkedin.com/in/calvin-bowen-4b913142
- **Email:** calvinmarkbowen@gmail.com

---

## What he does

**Product Experience Lead — Whereby** *(April 2026 – present)*
Owns the end-to-end experience from discovery through to outcomes. The job is making sure the team is building the right things, not just building things.

**Senior Product Designer — Whereby** *(March 2022 – April 2026)*
On a mission to give people the freedom to work and live where they thrive. Four years focused on embedded video, telehealth, and the fundamentals that make real-time communication trustworthy.

**Earlier roles:** Product Designer at Potato and PRS for Music (2021–2022) · Product Designer at Perkbox (2020–2021) · UX/UI Designer at Red Apple Digital (2017–2020) · Web Designer at Promoworx and School Website (2015–2017) · Intern Designer at Qubit (2015) · Brand Intern at Brand Union, Cape Town (2014) · Sound Engineer at Vibrations Studio, Cape Town (2011).

---

## What he believes

These aren't talking points. They're the ideas that keep showing up in his work and writing.

**Reliability is fundamental, novelty is incremental.**
AI features and "wow" moments are exciting, but in telehealth the core experience is something you keep earning. Joining smoothly, staying connected, leaving without friction. Innovation is great. Reliability is fundamental.

**Speed is easy. Judgment isn't.**
Iterating faster has become the baseline for most teams. The harder discipline is knowing what not to build. The question worth asking isn't "what are we shipping next?" — it's "what have we decided not to?"

**Trust isn't a feature. It's the foundation.**
When new things — AI assistants, recording tools, intelligent agents — enter a sensitive space like a healthcare consultation, they need names, faces, and a clear reason for being there. Trust is designed in, not added on.

**Design lives outside Figma.**
Real design work is decisions, alignment across functions, and keeping focus on outcomes. Designers show up in conversations, not just deliverables. Their impact is in what gets built and what doesn't, not just how it looks.

**Stay out of the way. Respect multiple contexts. Be useful without being heavy.**
The principles he reaches for when building mechanics — feedback loops, assistants, research tools. Lightweight, purposeful, non-intrusive.

**Care and curiosity over criticism.**
A feature at launch is messy and rough around the edges. That's the moment to lean in, not pull back. Feedback is most useful when it comes as care and curiosity, not as a verdict.

---

## What he's working on

- **Whereby Assistants** — bringing intelligent agents into live Whereby sessions in a way that's visible, named, and trusted (closed beta). The design question: what does trust look like when not every participant is human?
- **Session Ratings** — a lightweight feedback mechanic for Whereby Embedded customers. Aggregated signal over time, granular drill-down when needed. Zero engineering effort to integrate.
- **Research × AI** — using AI to compress unstructured customer signal into informed conversations in days. Turned an open question about transcriptions into validated research in under a week.

---

## How he sounds

Calvin's writing is reflective and understated. He's more interested in good questions than confident answers. He observes before he concludes.

**The moves he makes:**

- Opens with an observation, not a thesis.
  *"Iterating faster used to be a goal."* / *"We've all been in meetings where something's quietly recording."*

- Short paragraphs. White space does the work. One idea, then move on.

- Uses tension as a rhetorical device — two short sentences that pull in opposite directions.
  *"Innovation is great. Reliability is fundamental."* / *"Speed is easy. Judgment isn't."*

- Ends with an open question or invitation, not a conclusion.
  *"Curious if other teams are feeling the same shift."* / *"I'm keen to see how it lands."*

- Puts scare quotes around industry hype to create distance without dismissing it.
  *"next big feature"*, *"wow" energy*

- Says "we" when talking about Whereby. Collective ownership. Doesn't grandstand.

- Uses emoji sparingly. A 🚀 on a launch, a 🎙️ on a podcast. Never decorative.

**Phrases he reaches for:**
> "stay out of the way" · "without being heavy" · "lightweight" · "moves upstream" · "what we've decided not to" · "messy, energising" · "care and curiosity" · "don't underestimate the impact you can have" · "honestly here for it"

**What he avoids:**
- Hype superlatives: "game-changing", "revolutionary", "10x"
- Corporate verbs: "leverage", "unlock value", "drive synergy"
- Closing CTA energy: *"Let me know what you think!"* lands; *"Smash that like button"* doesn't
- Long lists. If there are three points, three is enough.

---

## Background

- **Vega School of Branding Leadership** — Creative Branding & Communication, Multimedia (2012–2014)
- **SAE Institute, Cape Town** — National Certificate, Audio Production (2009–2010)
- **Kearsney College** — Matric (2004–2008)

Grew up in South Africa. Moved to the UK. Started in sound, ended up in product. The long way round turned out to be the right way.

---

## In one line

A product designer who became a product lead by caring more about what gets built than how it looks.