What Doing Makeup at Weddings Taught Me About Product
What Doing Makeup at Weddings Taught Me About Product
For most of the last decade I have had two jobs. One is product manager — IPSY, LexMeet, Accentra. The other is professional makeup artist, mostly bridal and editorial. They sound unrelated. They are not. The makeup work has shaped how I think about product more than most "product books" I've read.
Here are the three things it has taught me.
Lesson 1: The customer's stress is the actual product
Nobody books a bridal makeup artist for makeup. They book a bridal makeup artist because they are about to have the most photographed day of their life and they need someone who will not let it go wrong. The makeup is a deliverable. Confidence is the product.
I watch new artists optimise the wrong thing. They obsess over palette, over technique, over the perfect blend. The brides remember none of those things. What they remember is whether the artist was calm, on time, and kind under pressure. The technical work is the cost of admission. The emotional work is the value.
Product is the same. Users do not care about the elegance of your data model. They care about whether your app is the calm, on-time, kind thing in their day. The technical work is necessary. The emotional work is what they're actually buying.
Lesson 2: Constraints make you better, not worse
A bridal job is the most constrained product environment I know. You have one chance. There is no v1.1. The bride doesn't get a re-do. The lighting is whatever the venue is. The clock is the wedding photographer's schedule. You ship live, in front of the customer, every time.
Working under those constraints permanently rewired how I scope work. When you only have one shot, you stop adding things. You ship the smallest version that survives the conditions. You build for the worst case and pray for the best case. You over-prepare on durability and under-prepare on novelty.
Most software gets the opposite treatment. We assume infinite revision, infinite tolerance, infinite undo. So we add things. The discipline of "you only ship once" is a useful one to import — even into a context where you can ship again next sprint.
Lesson 3: Customer empathy is built, not declared
Every PM job description says "customer empathy." It is the most performed skill in the industry. Half the time it means "I have read about empathy" and half the time it means "I sat in a user interview once."
Real empathy is built by sitting in the customer's chair, repeatedly, in conditions you cannot control. By being the one who has to absorb the customer's anxiety, fix the thing they didn't tell you was broken, and not visibly panic when the timeline collapses.
I learned more about real customer empathy from one stressful bridal job than from a quarter of user research at any of my product roles. Not because user research is wrong — it isn't. But because the consequences are abstract. The bride is not abstract. She is right there, and she is two hours from walking down an aisle.
The PMs I admire most have something analogous in their backgrounds. A stint in customer support. A side hustle with real customers. A role where they were the one absorbing the customer's stress. It is the closest training there is for what product actually demands.
The shorter version
Two careers, one common thread: people don't buy what you make. They buy what they feel when you give it to them. Get the feeling right, and the rest of the work — the makeup, the app, the roadmap — has a much easier job.
I keep both jobs because they keep teaching me each other.

Teena skipped presentations and built real AI products.
Teena Azmi was part of the June 2026 cohort at Curious PM, alongside 20 other talented participants.
