discovery-claim-value-prop

Skill: discovery-claim-value-prop

Trigger

Use this skill when the user wants to define the value proposition during a discovery — e.g. "rédige le Claim", "écris le press release", "génère le launch tweet", "définis notre value prop", "write the press release and launch tweet".

Context

At Mayday, the Claim phase (step 3 of FOCUSED) is about defining and validating the VALUE PROPOSITION — not the solution. The goal is to have a short, compelling promise that resonates with clients.

Two deliverables are produced:

1. Press Release (Amazon-style, ~300–500 words) — Forces clarity on the positioning and user value before building anything
2. Launch Tweet (≤240 characters) — The distilled value proposition. If clients react with "wow, I want that" → strong validation signal

The Launch Tweet is shown to clients as a validation test. If it doesn't spark enthusiasm, the Claim is wrong.

What to do

Step 1 — Gather context

Ask the user for the following if not already provided:

• The FUC (First Use Case) — who has what problem?
• Key learnings from interviews (what words did clients use?)
• The persona targeted
• Any benchmark insights (Gold Nuggets) that inform the positioning

Step 2 — Write the Press Release

Use the Amazon Working Backwards format. Write as if the feature has just launched.

---

[Feature Name] — [Catchy subtitle] For immediate release

[City, Date] — [Company name] today announced [feature name], [one-sentence description of what it does and for whom].

[The problem paragraph] — [2–3 sentences describing the pain the feature solves. Use the language clients used in interviews. Make the reader recognize their own problem.]

[The solution paragraph] — [2–3 sentences explaining what the feature does and how it solves the problem. Focus on the outcome for the user, not the technical implementation.]

[Quote from a fictional client] — "[A quote that captures the value in a human, relatable way. Should sound like something a real Knowledge Manager / PM / etc. would say.]" — [Fictional client name, Title, Company]

[Quote from the PM / CPO] — "[A quote explaining why Mayday built this and what it means for the product vision.]" — [Name, Title, Mayday]

[Call to action] — [One sentence. What can users do now?]

---

Step 3 — Write the Launch Tweet

Write 3 versions of the Launch Tweet (≤240 characters each), ranked from most bold to most descriptive:

Version 1 (Bold / provocative): Leads with the pain or the transformation Version 2 (Feature-led): Leads with what the feature does Version 3 (Outcome-led): Leads with the business outcome for the user

Then recommend one version and explain why.

Step 4 — Validation signal reminder

Add a brief note on how to use the Launch Tweet for validation:

Share versions with 3–5 clients or internal stakeholders. A strong Claim produces a "I want this now" reaction. A weak one produces "interesting" or "makes sense" — those are warning signs. If multiple people ask clarifying questions, the Claim is not clear enough.

Output format

• Press Release first, then the 3 Tweet versions
• Bold the recommended tweet
• Write in the user's language
• The Press Release should feel real and client-centric — avoid technical jargon
• The tweets should be punchy, concrete, and in plain language

Example Launch Tweet (Knowledge Quality)

"Stop guessing which articles are outdated. Mayday now tells you exactly which knowledge needs fixing — and why. Your KB, always performing. 🧠"