Certificate of Appreciation
"I try to explain to people that the real essence of this job is that you wake up on behalf of someone else to solve a problem for them, and you have to do it well enough that they give you something back in return. That's kind of the real essence of it, and that's what I always call a certificate of appreciation." - Christian Idiodi
What It Is
The Certificate of Appreciation is a mindset framework that reframes product success around what customers give back in return. Rather than measuring success by features shipped or milestones hit, you measure it by the tangible appreciation customers demonstrate through their actions.
This framework captures the essence of product management: solving problems on behalf of others so well that they reciprocate with value. It's not about what you build—it's about what you receive back as proof that you truly solved their problem.
How It Works
Forms of the Certificate
The "certificate" customers give back can take many forms:
- Revenue - They pay money for your solution
- Engagement - They use your product regularly
- Loyalty - They stick with you over time
- Reference - They tell others about you (the ultimate form)
- Time - They invest their attention
- Data - They trust you with their information
The Virtuous Cycle
When you solve problems well:
- Customers give something back (certificate)
- That proves value creation
- Which justifies continued investment
- Which enables solving more problems
- Which generates more certificates
The Warning Signs
If you're not receiving certificates of appreciation:
- "If it's not fun, you're probably not doing it right"
- "If it's not hard, you're probably also not doing it right"
No certificates = no real value creation, regardless of how much you built.
How to Apply It
Reframe your success metrics - Instead of "we shipped X features," ask "what certificates did we receive?"
Define your certificates clearly - Know what form of appreciation matters most for your product (revenue? engagement? referrals?)
Track certificates, not outputs - Measure customer reciprocation, not just your own activity
Use certificates for prioritization - Features that generate certificates get priority over features that don't
Let certificates guide discovery - The strongest certificate (someone staking their reputation) indicates product-market fit
When to Use It
- Evaluating product success - Did customers give something back?
- Prioritizing roadmap - Which work generates the most certificates?
- Assessing product-market fit - Are customers giving the ultimate certificate (references)?
- Motivating teams - Connect work to tangible customer appreciation
- Avoiding vanity metrics - Focus on reciprocation, not just usage
Source
- Guest: Christian Idiodi
- Episode: "The essence of product management | Christian Idiodi (SVPG)"
- Key Discussion: (00:00:00) and (00:12:49) - Christian explains the certificate of appreciation concept
- YouTube: Watch on YouTube
Related Frameworks
- Reference Customer Development - The ultimate certificate is a reference
- Jobs to Be Done - Understanding what progress deserves a certificate