Notes — Christian Idiodi on Product Management

Four questions [Adler frame]

Q1 — What is it about? How to be a product manager people trust and want on their team. Two central arguments: (1) PM credibility is entirely competency-based — trust follows from knowing customers, data, and business better than anyone else; and (2) the single most powerful discovery technique is building reference customers from scratch — working with a target number of real users until they love the product enough to stake their reputation on it. Supplemented by a complete coaching framework (practice arenas, sideline vs. in-game coaching) and trust-acceleration tactics (teach-me-or-help-you).

Q2 — How is it argued? Primarily through the Snag Job case study — a complete zero-to-$32M product journey building a high-volume hourly hiring platform (McDonald’s → Starbucks → LA Airport → Macy’s), demonstrating the reference customer method live. Supplemented by Geoffrey Moore adoption curve logic (technologists and evangelists as early adopters), SVPG’s four risks taxonomy, and direct coaching anecdotes (screaming CEO, soccer team coaching, teach-me technique).

Q3 — Is it true? The reference customer approach maps directly to Jobs to Be Done (immerse yourself in the environment of the problem) and Product Positioning (Dunford’s “find the customers you can win with first”). The PMF threshold numbers (B2B 6-8, B2C 15-25) have some grounding in IBM research cited by Idiodi and align with Moore’s crossing-the-chasm dynamics. The “teach me or help you” trust-building technique is a specific instantiation of network trust transfer — well-observed in organisational psychology. The coaching claim — that corporate companies fail by not creating practice arenas — parallels Brian Chesky on Airbnb and Product (no coaching before promotion). The four risks framework is the standard SVPG model (Cagan’s Inspired).

Q4 — What of it? For PMs: competency-building is not optional — you must demonstrably know more about customers, data, and business than anyone else on the team. The reference customer technique is executable from day one without tooling: find the problem, find the people, work with them until they voluntarily put their name on it. For leaders: coaching is the daily job of management, not a one-off; if someone hasn’t been taught to do VP things before becoming VP, promoting them is setting them up to fail. For organisations: create explicit practice arenas (low-stakes environments for PMs to rehearse collaborative problem-solving) before the game.

Glossary

Competency-based trust — the only kind of trust that consistently earns a PM influence in organisations. Based on demonstrating deeper knowledge of customers, data, business, and product than anyone else in the room. Character trust (care, communication) exists but is secondary in corporate settings. You earn competency-based trust by learning publicly and relentlessly.

Reference customer — a customer who has used your product, loves it enough to put their reputation on the line by recommending it to others. Idiodi’s definition of PMF: you have achieved it when you have enough reference customers (B2B: 6-8; B2C: 15-25). The reference signal — willingness to leave a public review, testimonial, or referral — is more honest than user research because it costs the person something.

Certificate of appreciation — Idiodi’s framing of the PM’s job output: solve someone else’s problem so well that they give you something back (revenue, engagement, loyalty, referral). The return signal is the proof of value.

Four risks (SVPG) — the four categories of risk any product team must resolve: (1) value — will customers buy/choose/use this? (2) usability — can they use it? (3) feasibility — can we build it? (4) viability — does it work for our business? PM’s primary accountability is value and viability. The most commonly skipped: value.

Reference customer technique — discovery method where you identify the target customer, work directly with them to discover and iteratively deliver a solution, and don’t launch until a threshold of customers voluntarily say they would recommend it. The threshold serves as both a PMF indicator and a pre-launch marketing asset. Key constraint: all reference customers must want the same core solution — diverging requests signal you haven’t found a single market.

Technologists and evangelists — Idiodi’s (Moore-derived) labels for early adopters who make ideal reference customers. Technologists love new technology for its own sake; evangelists believe they have the problem urgently enough to queue up or pay a premium. Both will give candid feedback and honest PMF signals. [§ Reference customer technique]

Teach me or help you — trust-acceleration tactic. To build trust with the most powerful person in your environment, ask them to teach you or volunteer to help them. This forces a relationship, extends their social trust to you, and makes them accountable for your success — they cannot later undermine you without looking like a bad teacher.

Practice arena — any low-stakes environment where a PM gets reps in collaborative problem-solving: volunteer work, community events, non-profits, side projects. The absence of practice arenas in most companies is why PMs plateau: doing product management is the PM’s job; getting better at it is the manager’s job.

Promotion before title — Idiodi’s principle: the best time to learn a new role is before you hold the title. Practice the job with protection (mistakes are expected of someone not yet in the role). The worst time to learn how to be a VP is when you are one.

Sideline coaching — the coach is not in the game; the player is. The coach’s job is to observe, give feedback, and design environments for improvement. Doing product management ≠ managing product managers. The distinction breaks down when leaders “jump in to solve the problem” rather than watching and coaching.

PM credibility: the competency-based trust problem

Why PMs are disliked: engineers, designers, and executives feel they know more about customers, data, or the business than the PM does. When that’s true, the PM cannot earn the trust required to influence decisions. The solution is not political — it is epistemic.

Idiodi’s “Bob” test: think of the person in your company that everyone trusts to make decisions on strategy and markets. Why do they trust Bob? Because Bob has been here the longest, knows everybody, understands the business deeply. That’s the competency level a PM must reach. Imagine every team having a Bob — that’s the ambition.

PM role definition (SVPG framing): a team sport. The PM works alongside a designer and engineer to uncover a solution to a problem. The four risks. PM’s primary ownership: value and viability. Result: if it works, it was a team effort; if it fails, the PM is blamed — because they are accountable for answering “should we build this at all?”

Reference customer technique (full method)

The insight: PMF is not a survey score, a retention rate, or a Net Promoter Score. PMF is reached when a threshold of target customers are willing to publicly stake their reputation on your product by recommending it.

Why the threshold matters: one or two enthusiastic customers could be flukes, personal relationships, or bad fits for the market. Six to eight in B2B represents the social proof threshold at which a comparable buyer’s objection (“am I the first?”) is neutralised. Twenty-five in B2C represents the App Store signal threshold.

Practical implementation (derived from Snag Job case study):

1. Identify the problem and hypothesis customer. Drive around, talk to people, don’t leave the building until you find someone with the problem (Starbucks call → McDonald’s construction site).
2. Agree on a minimal value proposition. Don’t write requirements; don’t design in a vacuum. Get agreement that if you solve it, they’ll tell someone.
3. Do it manually first. Excel spreadsheets, phones, emails, Craigslist flyers. Learn what works and what doesn’t at the smallest scale before building anything.
4. Expand to the next customer. Use what you learned from one to pitch the next. The second customer benefits from the first’s constraints and insights.
5. Iterate on the solution in parallel with discovery. The designer and engineer are present from step one — not brought in at requirements-handoff time.
6. Know when to disqualify. If reference customers want diverging features, it is not one product. If you can’t find 25, maybe there is no market.
7. Launch with reviews ready. On day one, the threshold of reference customers provide the first reviews/testimonials.

Product marketing integration: the language reference customers use to describe the product is the marketing copy. Idiodi never invents a description. Whatever Lenny said about the steakhouse goes on the box. This directly parallels Product Positioning (Dunford) and Brian Chesky on Airbnb and Product (story first).

Disqualifying customers: the LA Airport episode shows this cleanly. Airport hiring required demographic matching, complex logistics, minimum wage + union negotiations. Outcome: “that is not our customer, never again.” The reference customer method provides a natural kill switch.

Coaching framework

Core distinction: doing product management is the PM’s job. Getting better at product management is the manager’s job. Most corporate environments collapse these — the manager is also in the game, not on the sideline.

Root cause of poor coaching: people can only give to others what has been given to them. The screaming CEO anecdote: he was screaming because his boss screamed at him and he got to CEO, so it must work. He had no model of an alternative. The fix: show the alternative in context, get candid feedback from the team.

Practice arena principle: product management is a game-time role. When do people practice? If they don’t, every high-stakes meeting is the first time. The fix: create low-barrier practice environments (volunteer work, community events, side projects) where mistakes are expected and feedback is safe.

Promotion-before-title: teach someone to be a VP before promoting them. When they hold the title, they’ve already done the job — so they’re not faking it, not Googling “how to do an interview,” not replicating their boss’s habits because they have no alternatives. Group PM roles are meant for exactly this: practice managing before managing.

Trust-acceleration (teach me or help you): [§ Glossary — Teach me or help you]. Works because: (1) forces a direct relationship with influence; (2) extends existing social trust to the new person; (3) makes the influential person accountable for outcomes — they won’t undermine someone they’ve publicly taught.

Africa / Innovate Africa Foundation

Idiodi’s observation: he falsely assumed problems solved in North America were also solved globally. Visited Nigeria, found jobs were found via newspaper — a problem he had personally worked on in 1998.

Two patterns in Africa:

1. Technology available but poorly deployed to solve real problems.
2. A “walk around the problem” culture: buy generators instead of fixing power, buy bigger cars instead of fixing roads — a whole society of workarounds, not solutions.

Positive framing: fastest-growing young population, 7 unicorns created despite <30% internet penetration, enormous latent opportunity.

Idiodi’s response: Innovate Africa Foundation (innovateafricafoundation.org) — education and enablement. Inspire Africa Conference (1,000 attendees from 31 countries). Paid Africa Fund (angel fund for startups not yet ready for institutional investment). WorkNigeria (job board).