Everyone nodded. Nobody agreed
I've spent 10+ years figuring out why that keeps happening — and what to do before it costs you months building the wrong thing.
Here’s what actually happens in product teams.
Your users want one thing. Your stakeholders want another. Engineering has constraints nobody mentioned in the kickoff. And everyone walks out of the alignment meeting with a different interpretation of what you’re building.
You ship three months later. The product misses. And the post-mortem reveals what nobody said out loud at the start.
That’s not a process problem. It’s a clarity problem. And it almost always starts before the first line of code.
A bit about me
I’m Rafael — a product manager, builder, and writer based in Madrid.
I’ve spent 10+ years shipping products across IoT, edtech, and SaaS. Home security systems that reduced churn by 50%. Language learning tools that changed how people work. A social app that failed, and taught me more than anything that shipped.
That pattern — the gap between what teams think they’re building and what actually ships — kept showing up everywhere. So I built CRISP to address it.
CRISP Framework
Clear thinking for product builders
CRISP is a five-stage product discovery framework I developed after watching smart teams repeatedly build the wrong things — not from lack of talent, but from skipping the uncomfortable questions at the start.
Figure out what problem you're actually solving. Not meeting-room agreement. Real agreement.
Understand reality before you form opinions.
Generate options before locking into one solution.
Build a plan you can actually execute.
Ship what you meant to ship, not a watered-down version of it.
Let’s talk
If something here resonated, if you're working through a product problem, or if you just want to think out loud — reach out!