# Gregory Rathmell

Gregory Rathmell works in product management and upstream marketing. In a LinkedIn post, Rathmell announced starting a Senior Director of Product Management and Upstream Marketing role at Title21 Health Solutions. His posts also discuss product requirements, Agile, and product management careers.

- Profile: https://b2binfluencer.marketing/creators/gregory-rathmell/
- LinkedIn: https://www.linkedin.com/in/gregrathmell
- Topics: artificial-intelligence, leadership, recruiting, healthcare, product-management, career-transitions
- Based on 10 dated posts, latest 2026-10-08

## Summary

Useful for product definition thought leadership on why teams should keep market reasoning, not long PRDs.

- Best for: A product management consultancy commissioning debate-led thought leadership for product leaders.
- Not for: Recruitment technology brands seeking keyword-optimised hiring content for talent acquisition buyers.
- Check first: Confirm whether they accept paid work and verify their current role and performance data.

### Takeaways

- Rathmell argues Agile was built to kill the PRD, and AI has not brought it back.
- They say the document that matters is the MRD, not the PRD.
- They set a test: documentation must be read, used, and improve release quality.

## Main ideas

- **The document that matters is the market requirements document, not the PRD**: Rathmell argues that Agile was created to kill the product requirements document, that AI has since weakened Agile practice, and that teams are drifting back to PRDs mainly because AI can write them quickly — repeating the original problem with a new tool. The distinction they draw is between writing and deciding. AI can help pull data together, but it cannot choose the market justification for a release, its specific business objectives, or what is required to succeed beyond shipping code. Those decisions belong in the MRD, which they want kept concise on a Confluence page with data references and reviewed at kickoff, with the project manager explicitly acknowledging its constraints. Only then should engineering work out how to build the solution.
- **New process has to prove itself before it is adopted**: Rathmell sets a clear bar for adding documentation or ceremony: evidence that it is read and used by the intended audience, and that it improves understanding and release quality. The post rules out uncontrolled before-and-after studies as evidence and closes with the line "I have to prove my decisions; you prove your process." They also warn against replacing "Agile pomp and circumstance with AI-generated bureaucracy." Documentation should earn its place through its effect, not convention or ease of production.
- **AI can polish the writing, but it should not make the judgment**: Rathmell consistently separates drafting speed from product judgment. AI may clean up or assemble material; decisions about market need, business objectives, and success criteria stay with the person accountable for them. Applying the same logic to self-presentation, they write a LinkedIn profile with no AI refining, no keyword coding, and no exaggeration — and predict that it will perform badly in Boolean keyword searches because it reads as a story rather than a term list. They are not anti-AI in either context, but draw a line at handing over the choices.
- **Product judgment is a general skill, not a job title**: Rathmell frames core product management work — gathering broad input, synthesising it, prioritising, and advocating for change — as something that applies well outside a product organisation. Their experience spans student representation, consulting, and a product leadership role. They treat prioritisation and advocacy as the transferable skills, not the tooling or artifacts.

## Work to read

- [Why AI did not bring back the PRD](https://www.linkedin.com/posts/gregrathmell_product-management-hot-take-why-are-we-talking-activity-7473407552538607616-bK9j)
- [Announcing a Senior Director role in product management and upstream marketing](https://www.linkedin.com/posts/gregrathmell_im-happy-to-share-that-im-starting-a-new-activity-7164379827280560128-zwWx)
- [Rewriting a LinkedIn profile as plain truth instead of keywords](https://www.linkedin.com/posts/gregrathmell_recruiters-jobseekers-productmangement-activity-7509342967879561216-nHKv)
- [Student roles at LSE: academic representative and consulting lead](https://www.linkedin.com/posts/gregrathmell_london-strategic-consulting-lsc-linkedin-activity-6856885811707686912-1T-q)

## Brand relationships

- **Title21 Health Solutions** (employment)
- **London Strategic Consulting** (employment)
- **London School of Economics** (mention)

## Partnerships

Gregory Rathmell’s posts discuss product management practice, a job search, and a student consulting role, but include no sponsorship offer, sponsored-content example, media kit, partnership terms, paid collaborations, brand partnerships, or route for companies to commission work. They give no rates, deliverables, disclosure practices, or partnership contact. A brand considering a thought-leadership engagement should ask whether they accept paid work and request those details.

## Alternatives

- Daryn Edelman, M.A., C.P.R.W: Choose Edelman instead when the commissioned series is about hiring and interviewing rather than product definition. The same consultancy could use this voice for a product-leader audience on how to hire and assess product managers. Edelman's two available posts both focus on the last five minutes of an interview, argue that top performers interview the company as much as they are interviewed, and supply a grouped question bank covering recruiter questions, the role, team insight, manager perspective, and company direction, with an instruction to pick the three most relevant to the interviewer. That structure could anchor a practical piece on what a product leader should ask before accepting a role or sitting on the other side of the table.
- Dr. Jorge Valenzuela: Choose Valenzuela when the buyer shifts from a product organisation to a school, district, or education-technology audience, and the topic shifts from product definition to how institutions should adopt AI and assess learning. Valenzuela's posts argue that instructional design matters more than tools, that project-based learning and strong assessment make student thinking visible, and that technology should be used only when it adds value to learning. The 8 October 2026 post also uses an interview format: a podcast conversation about trust and psychological safety in innovation culture. It offers a workable template for commissioned thought leadership with a named guest.
- Ian Whiteford: Choose Whiteford when the campaign is about the labour market and the changing value of knowledge work rather than product definition itself. The 21 May 2026 post contrasts people who combine domain expertise, execution, and AI fluency, who are in high demand, with a squeezed middle of detached managers and juniors without shipped work. The 2 June 2026 post argues that prestige tech employers have lost their pull for recruiters and names the London companies drawing talent instead, giving a reason for each. For a consultancy whose clients also buy employer-brand or talent content, Whiteford offers a stronger argument and more specific examples on that terrain than Rathmell does.

---
AI-assisted summary of public posts. Audience demographics are not available. Engagement appears only where we checked recent posts. Method: https://b2binfluencer.marketing/methodology/