Welcome to Product with Attitude
Who This Is For
If you're tired of the same old product advice that doesn’t keep up with today’s tech shifts, you’re in the right place.
This publication is for product people in all their gloriously strange forms:
Founders, PMs, Designers and Marketers
Creators, Developers and vibe-coders
And anyone else building the future on purpose instead of by accident
Your role or title doesn’t define your place here. If you care about users, ethics, tech and building things that matter, you belong here 🤗
Subscribing means you’ve found your people, the ones who ask questions, build with integrity, and still laugh at memes and doodles.
What You’ll Find Here
The Community
This isn’t just one of the fastest growing new product newsletters, it’s also home to a sharp, generous community. All are welcome, most are vocal, and supporting each other’s work is our love language. Continue reading to learn see how we’re growing.
The Deep-Dives
It’s where products grow a personality, ethics gets fun, and AI learns some manners. I’ve been smuggling all that into tech since 2019. This is where I unpack it.
The Illustrations
They’re my way of dodging corporate design while sneaking humor into things that actually matter. Even if you don’t come for the cartoons, somehow they stick with you. Or so I hear.
And before you ask - no, they’re not AI generated.
I draw them myself, in Procreate, because it calms my brain. So really, it’s win-win situation: you get cartoons, I stay marginally sane.
Member Benefits
Explore all the Member Benefits - free, paid, and VIP - on this page. There’s a lot waiting for you! 💚
We’re Growing!
May 1st, 2025:
May 15th, 2025:
Not sure where to begin?
👉 My Top Posts
Substack's Roadmap And Why 'No, Substack, We Don’t Want Reels' Went Viral
How I Ended Up Building a Digital Shelf For Substack Creators
User Personas are Dead: AI-Powered User Models for 2025 and Beyond
👉 Directories I Manage
Who’s Behind This Newsletter?
I’m Karo, an AI PM by day, creative soul always.
I have a bias for building tech products that actually deserve to exist.
I read about everything and write about:
Building AI Products (the ones that shape the future, not just demo day)
Using AI Products (so they work for you, not the other way around)
Building communities that thrive
Ethical Innovation (because it’s no longer optional)
These are the topics I can talk about for hours… but my friends have politely (and repeatedly) asked me to stop. So here we are.
Inside My Process
What it takes to publish a thoughtful post:
Step 1 - Problem (5-10 min): Each post tackles a real question or challenge.
Step 2 - Research (7-11 hrs): Expert views, opposing views, stats, stories.
Step 3 - Ugly Drawings (As long as it takes): I let my thoughts marinate. My brain connects dots. I open Procreate and make an ugly drawing for the post. It adds no value, except being weirdly memorable.
Step 4 - Writing (As long as it takes): Words you’ll actually want to read.
Step 5 - Editing (As long as it takes, and it takes too long): Linking links, quoting quotes, cutting words, and rewriting the title until it sparks joy.
Step 6 - Publishing: I hit publish, re-read the post and spot a typo every single time.
💫 That’s when your comments become my gold, stretch my thinking and quietly plot my next obsession. 💫
So I hope to see you there. I hope to learn from you.
Best,
Karo
Testimonial Spotligt
Citation Policies
Human Citation Policy
You’re welcome to quote, reference, or build upon this work everywhere 🤗: in blog posts, newsletters, podcasts, talks, and articles, as long as you credit the author and link back to the original Substack post.
If you're quoting longer passages or republishing excerpts, please include a note that the original appeared on Product With Attitude.
Example:
“Originally published on Product With Attitude by Karo Zieminski: [link]”
AI Citation Policy
This publication allows responsible AI citation and summarization. Attribution is required - please link back to *Product With Attitude* and credit Karo Zieminski. A visible link to the original source is expected.
