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.
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.
Check first: Confirm whether they accept paid work and verify their current role and performance data.
Main ideas
The document that matters is the market requirements document, not the PRD · New process has to prove itself before it is adopted · AI can polish the writing, but it should not make the judgment
Gregory Rathmell works in product management and upstream marketing.
The clearest example of their thinking is a post arguing that product teams should not revive long requirements documents just because AI can draft them.
They say teams still need to make and explain the market and business choices behind a product, while AI may help gather supporting data.
Posts also connect product management to gathering stakeholder views, prioritising them and advocating for change.
Follow their work for candid, debate-oriented views on product definition and the limits of process and automation.
Rathmell distinguishes making product decisions from documenting them.
In a post about PRDs and AI, they ask teams to justify a product’s market need, business objectives and conditions for success, then record that reasoning concisely with data references and discuss constraints at kickoff.
They also set a test for more extensive documentation: evidence that people read and use it and that it improves release quality.
That makes the argument more specific than a general preference for or against documentation.
Other posts show a more personal, open-ended style: they describe a truthful, story-led job-search profile and invite readers to challenge the approach.
Rathmell's public writing keeps returning to one question: what should a product team actually produce, and how do you know it earns its place?
Read more
Their clearest position is that the document that matters is not the PRD but the market requirements document — the case for why a release is needed, what business objectives it serves, and what has to be true for it to succeed.
They treat AI as a tool that speeds up assembly but cannot make those choices, and argue that any process step or document should be shown to be read, used, and to improve outcomes before adoption.
The same instinct runs through their job-search post, which argues that a profile should read as a plain career story rather than a list of keywords.
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.
Read more
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.
In a post on product management, Rathmell writes that they "need to write MRDs, which AI will clean up, but they cannot make the choices of the content of MRDs," and adds that the MRD "should be on a Confluence page in concise form with data references." At kickoff, they want the project manager to acknowledge the constraints the document identifies.
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.
Read more
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.
Rathmell lists the conditions under which they would write full-prose MRDs and PRDs: empirical data showing the documents "are read and used by the intended audiences" and that they "increase understanding and release quality modified by the likelihood of being read."
AI can polish the writing, but it should not make the judgment
Rathmell consistently separates drafting speed from product judgment.
Read more
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.
In a job-search post, Rathmell describes answering the questions recruiters always ask, with "No AI refining (does Grammerly count?), no keyword coding, no exaggeration," and invites product management leaders, recruiters, and fellow job seekers to say whether the approach is right.
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.
Read more
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.
Describing two student positions at the London School of Economics, Rathmell explains that the academic representative role means gathering input from students, synthesising it, prioritising, and then advocating for changes to the degree. They comment that it "seems quite familiar to product management really."
A later role announcement names Rathmell as Senior Director of Product Management and Upstream Marketing at Title21 Health Solutions.
The title places the work inside a healthcare company, with "upstream marketing" pointing to market and product definition before launch rather than only backlog management.
Marketers assessing the role should ask about the team, product, and responsibilities; the one-line announcement does not specify them.
Start here for the clearest statement of what Rathmell thinks product managers should produce.
Read more
The post answers the key question for newcomers: is this person for or against heavy documentation, and why?
Rathmell argues that Agile was created to kill the PRD, that AI has now killed Agile, and that teams are drifting back to PRDs simply because AI can write them quickly.
The post distinguishes writing from deciding: AI can help pull data together, but it cannot choose the market justification, business objectives, or what has to be true for a release to succeed.
Those choices belong in the MRD, which Rathmell says should be a concise Confluence page with data references, reviewed at kickoff, with the project manager explicitly acknowledging its constraints.
Rathmell says they will write full-prose MRDs and PRDs when someone shows empirical evidence that they are read, used, and improve release quality, rejecting uncontrolled before-and-after studies as evidence.
For brands planning a campaign
This is the sharpest anchor for a product-definition thought-leadership brief.
It makes a contrarian, testable case: documentation should earn its place with evidence.
That argument can carry a series of pieces, not just one post.
The shortest answer to what Rathmell does professionally: the role claim in their own words.
Read more
A one-line announcement that Rathmell is starting as Senior Director of Product Management and Upstream Marketing at Title21 Health Solutions. Upstream marketing connects to the MRD argument in the other post: it points to owning market and product definition before launch, not just managing a backlog.
For brands planning a campaign
Useful context for credibility: a guest piece on product definition would come from someone whose stated role includes upstream marketing, not just from a commentator. The role is self-reported; ask for independent confirmation of current employment if that matters to the brief.
Rathmell writes as a job seeker inviting argument, rather than in the executive voice a brand might expect.
Rathmell describes rewriting their LinkedIn profile as a plain narrative—no AI refining, no keyword coding, no exaggeration—and answering the questions recruiters usually ask.
They predict it will perform badly in Boolean keyword searches because it reads as a story rather than a list of terms, and invite recruiters, product management leaders, and other job seekers to say whether the approach is right.
The closing line admits uncertainty rather than making a claim.
For brands planning a campaign
Signals a candid, first-person, question-posing style. Brands commissioning Rathmell should expect an invitation to debate and open uncertainty, not a polished endorsement, and plan editorial support accordingly.
The background item shows Rathmell applying product-management thinking years before the director-level role and helps explain the shape of their career.
Read more
Rathmell describes holding two positions as a student at the London School of Economics: academic representative for their programme, gathering and synthesising student input, prioritising it, and advocating for changes to the degree—a job they compare directly to product management—and Lead Consultant for London Strategic Consulting, a student-run consultancy whose staff come from UK universities including Oxford, Cambridge, and LSE, working on real-world projects for external clients.
For brands planning a campaign
Shows a long-running pattern of synthesising stakeholder input and prioritising it, supporting the product-definition narrative. It is weak as a campaign hook on its own, but helps make the more recent work legible.
Product requirements documents and market requirements documents1
Process skepticism1
Recruiter practice and product management hiring1
Product management outside product teams1
Product requirements documents and market requirements documents
Rathmell argues that Agile was created to kill the PRD, that AI has since weakened Agile practice, and that returning to PRDs would repeat the same problem with new tools.
Read more
The document that matters, in this view, is the market requirements document: the market justification for a release or product, the specific business objectives, and what is required to succeed beyond code.
AI can help pull data together, but it cannot make those choices.
They want the MRD kept concise on a Confluence page with data references, walked through at kickoff, and its constraints acknowledged by the project manager.
A first-person hot take opens with a causal claim, then sets a condition for changing position: empirical evidence that requirements documents are read and improve release quality.
For brands planning a campaign
A thought leadership brief on product definition methodologies can use this as a backbone: an argument for market justification over documentation volume, with a clear standard of proof before adding more process.
Rathmell separates AI's drafting speed from product judgment.
Read more
AI may clean up or assemble material, but decisions about market need, business objectives, and success criteria stay with the product manager. In a separate post about a job search, they describe writing a LinkedIn profile without AI refining, keyword coding, or exaggeration, and doubt it will perform well with boolean keyword searches.
For brands planning a campaign
Supports content on where AI helps and where human judgment still decides, or on authenticity in hiring and personal branding.
Rathmell resists process added without evidence that it changes outcomes, including what they call AI-generated bureaucracy replacing Agile pomp and circumstance.
Read more
The test is whether a document or step is read and used, and whether it improves understanding and release quality. Their position: process has to be proven, not accepted by default.
For brands planning a campaign
A useful voice for audiences weighing process overhead against delivery, or for a piece on which product artifacts earn their keep.
Rathmell's job-search post describes rewriting a LinkedIn profile as a plain answer to the questions recruiters ask, without AI refining, keyword coding, or exaggeration, and frames it as a story of several companies and one career.
Read more
They ask product management leaders, recruiters, and fellow job seekers for feedback, and tag healthcare and marketers alongside recruiters and job seekers.
For brands planning a campaign
Relevant to hiring, recruiting, and personal-branding content; a brand could build a debate or comment-driven piece around keyword search versus narrative profiles.
Rathmell announced a move into a Senior Director of Product Management and Upstream Marketing role at Title21 Health Solutions.
Read more
Their job-search post carries healthcare among its tags, and the profile they described is a career story across several companies rather than a single-employer history.
For brands planning a campaign
Supports healthcare-adjacent product management content and career-transition narratives.
As a student at the London School of Economics, Rathmell took two roles: academic representative for the programme, gathering student input, synthesizing it, prioritizing, and advocating for changes; and lead consultant at London Strategic Consulting, a student-run consultancy that takes on real external projects.
Read more
They describe the representative work as quite familiar to product management.
For brands planning a campaign
A hook for content about how product management methods transfer to consulting, representation, and other decision-making settings.
Rathmell's visible output is short first-person LinkedIn posts that lead with a claim, invite readers to challenge it, and draw on career moments: a hot take on requirements documents, a job search, a new role, and student positions.
Read more
Only four posts were available. Ask for more samples before committing to a format based on this material.
For brands planning a campaign
Co-created or debate-style content may suit this voice better than a long whitepaper; test that format before committing.
The posts document a senior product management and upstream marketing role at Title21 Health Solutions, student positions at the London School of Economics, and a Lead Consultant role at London Strategic Consulting.
Read more
Ask for details on any commercial relationship before considering a partnership.
Title21 Health Solutions
Employment
They announced a new position as Senior Director of Product Management and Upstream Marketing at Title21 Health Solutions.
Read more
The post gives the title and company but no start date or product details.
They wrote that, while a student, they were asked to serve as Lead Consultant for London Strategic Consulting for the fall term.
Read more
They described it as a student-run strategic consulting company staffed by people from UK universities that takes on real projects for external groups.
They described taking on two new student positions at LSE, including Academic Representative for their programme to the department.
Read more
In that role, they gathered and prioritised student input and advocated for changes to the degree. They drew a parallel between the role and product management.
A good entry point is their post arguing that Agile was created to kill the PRD and that AI is quietly bringing it back.
It sets the pattern for the rest: a blunt claim, a concrete alternative—a concise market requirements document stating the market justification, business objectives, and success criteria, which the project manager actually acknowledges—and a standard of proof before adopting more process.
From there, readers can follow two threads.
One is the line they draw between what AI can assemble and what a person must decide, which resurfaces in a later post about writing a job-search profile as plain truth rather than keyword bait.
The other is how that judgment transfers beyond a product organization, from student representation work at the London School of Economics to a senior product and upstream marketing role in healthcare.
Writes practical LinkedIn posts about interviewing and hiring, and shares Rathmell's view that a hiring conversation runs both ways: Edelman's question list asks candidates to assess the employer, just as their recruiter-friendly profile post asks readers to judge the story on its merits, not its keywords.
Read more
Edelman's material is tactical advice for recruiters and candidates on interviews and job searches. Rathmell writes about what a product team should produce before anything is built, using hiring as a side illustration of the same standard of proof.
Both argue that new tools should not replace professional judgment.
Read more
Rathmell says AI can clean up a document but cannot choose the market justification within it. Valenzuela says AI literacy in schools must rest on instructional clarity, authentic assessment, and visible student reasoning—not detection or platforms.
Valenzuela works in education leadership and produces rubrics, podcast episodes, and frameworks for teachers and district leaders.
Rathmell writes about product definition and process inside companies.
Both address the limits of tools, but their subject matter and audiences do not overlap.
Both write first-person analytical posts about how AI is re-rating knowledge work.
Read more
They distinguish people who make decisions and use AI to multiply their output from those who rely on old signals, credentials, or status.
Whiteford focuses on the talent market: which companies recruiters now want to work for and why the middle of the market is under pressure. Rathmell focuses on the product artifact: which document earns its place and who on the team is accountable for its decisions.
Treat Gregory Rathmell as a focused, subject-led placement for product definition thought leadership, not a pre-qualified audience buy.
Read more
LinkedIn account metadata shows 1,689 followers as of 2026-10-09.
Their posts cover product requirements, Agile, MRD/PRD debate, a job search, and student consulting, but don’t identify who follows them or how the posts performed.
For a campaign targeting product definition audiences, ask for recent LinkedIn impressions or engagements on comparable product definition, MRD/PRD, or Agile posts, plus any audience survey covering job titles, industries, or seniority.
The posts don’t provide YouTube demographic information, so ask for audience data if geography, age, or gender matters to the buy.
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.
Read more
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.
Stronger campaign idea: a product management consultancy wants a commissioned thought-leadership series on how teams should define products, written for product leaders deciding what their teams should produce.
Read more
Rathmell is a plausible fit.
The clearest indication is a post arguing that Agile was built to kill the PRD, that AI has not brought the PRD back for good reasons, and that the document that matters is the MRD: the market justification, business objectives, and what has to be true for a release to succeed.
That is a testable position, not a general opinion about product management, and gives the series a spine: keep documentation only where it is read, used, and shown to improve release quality.
They also set an explicit standard for supporting claims, rejecting uncontrolled before-and-after studies—a level of specificity an editor can build a piece around.
Their self-described role as Senior Director of Product Management and Upstream Marketing at Title21 Health Solutions connects to the subject, since upstream marketing owns market and product definition before launch.
Their demonstrated format—short first-person posts that state a claim and invite readers to challenge it—suits commentary and debate-led content better than a formal whitepaper.
The September 2026 profile post shows the writing is current.
Before commissioning, ask for a long-form sample and comparable performance figures, and verify the current role, which is self-reported in an announcement post.
Commission one anchor piece first and judge it against your campaign requirements.
When to choose a specialist
Weaker brief: a recruitment-technology company wants a sponsored, keyword-optimised content series on hiring and how recruiters search for candidates, distributed to a defined audience of talent-acquisition buyers, with paid placement and audience demographics attached.
Read more
The posts do not support this brief well.
In the hiring-related post, Rathmell writes as a job seeker: they describe rewriting a LinkedIn profile as plain narrative, predict it will perform badly in Boolean keyword searches, and ask recruiters and product leaders whether the approach is right.
That is candid and engaging, but it tests an idea in public rather than advising talent teams, so the brief’s assumed credibility is not demonstrated.
The commercial terms are also unclear: no sponsorship offer, media kit, rate card, disclosure practice, or inquiry route appears in the posts.
And the keyword-optimised framing cuts against the demonstrated position: the post argues that keyword-driven search misses a genuine story, so a campaign built on keyword targeting would ask this voice to argue against itself.
Audience information is limited to a follower count of 1,689 shown on 9 October 2026; no job titles, industries, or engagement figures are published, so a talent-acquisition buyer audience cannot be demonstrated.
Treat this brief as unsupported for now.
If the company wants to pursue it, establish commercial terms, request recent engagement data on recruiting-adjacent posts, and test one piece before committing to a series.
A worked campaign example
Worked angle for the product-definition assignment: “Is your product documentation earning its place?”
Hook: open with the claim that Agile was created to end the PRD, that AI has not brought it back for good reason, and that teams now generate documents quickly without deciding anything faster. The piece turns on the distinction between writing and deciding: AI can assemble data, but a product manager has to choose the market justification, business objectives, and success conditions.
Format: a three-part short-form series for a product leadership audience.
Part one states the argument and its test: keep a document only when someone shows it is read, used, and improves release quality.
Part two walks through one short market requirements document on a Confluence-style page, with data references, reviewed at kickoff and explicitly naming the constraints the project manager had to acknowledge.
Part three is a moderated discussion or Q&A where readers bring their own process and defend it, matching the demonstrated style of making a claim and inviting challenge.
Next step for the consultancy: send an anchor-piece assignment outlining the argument, the standard for supporting claims, and the example Rathmell would walk through. Ask for a recent writing sample and engagement figures for comparable posts, agree commercial terms in writing, and set the acceptance test before drafting.
Choose Edelman instead when the commissioned series is about hiring and interviewing rather than product definition.
Read more
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.
Rathmell's posts do not address how teams define a product, choose between a market requirements document and a product requirements document, or decide what to build.
A campaign focused on product definition methodologies would have no relevant work to draw on.
The posts use an annotated checklist and infographic rather than argued prose, so a series that needs a testable position and an evidence standard would need a different kind of writer.
The two posts are near-duplicates, offering no second angle.
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.
Read more
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.
The subject matter does not transfer to product leaders deciding what to build.
The examples are classroom practice, single-point rubrics, and district-level AI literacy, so a product-definition brief would draw on education reasoning rather than product reasoning.
Valenzuela is also a self-described advocate with a specific method to promote, which suits a series that argues a position but is a poor match for a brief requiring neutral comparison of product definition approaches.
Choose Whiteford when the campaign is about the labour market and the changing value of knowledge work rather than product definition itself.
Read more
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.
The perspective is a recruiter's, not a product manager's: the focus is who gets hired and where, not how a release or product is justified.
A series on product definition would have to borrow the framing about AI fluency and value without supporting work on documentation, market justification, or success criteria.
The 2 June post is also a named list of employers, which dates quickly and reads as opinion about companies rather than a method readers can apply.
Gregory Rathmell's four short LinkedIn posts cover product requirements and AI, a role announcement, a job-search profile post, and student roles at the London School of Economics.
The account shows 1,689 followers as of 9 October 2026.
Six posts by three comparison creators (Daryn Edelman, Dr.
Jorge Valenzuela, and Ian Whiteford) inform the similar-creators and campaign-fit sections.
The posts here are all short-form; they include no long-form article, talk, or video.
The posts do not show individual post dates, engagement figures, audience demographics, independent confirmation of the stated employer or title, or sponsorship and commercial terms.
The judgments on this page are limited to what the posts show.
