Melissa Perri

Melissa's writing style

Melissa Perri writes in short, declarative bursts: expect a one-line thesis followed by two- or three-sentence paragraphs that quickly move from idea to implication. She peppers posts with role-signalling and credentials, often showing a title line like "Board Member | CEO | CEO Advisor | Author | Product Management Expert | Instructor | Designing product organizations for ..." and anchors arguments with analogies such as "Product Ops: the unsung hero turning chaos into alignment and guesswork into strategy. It's like the backstage crew of a Broadway ..." She uses plain, direct vocabulary rather than jargon; sentences average 10–18 words, and paragraphs are compact so readers can skim. Melissa favors occasional clipped lists or enumerations inside the post (short numbered or line-broken points) but rarely long-winded paragraphs. When she wants emphasis she starts with a bold thesis sentence—"AI is reshaping product management."—then follows with concrete examples or a call for debate. Visual formatting is minimal: line breaks to create rhythm, occasional ellipses for trailing thought, and a signature-style role or link at the end to signal provenance and next steps.

Who Melissa writes for

Melissa Perri is addressing product leaders who design how products get built and the people who scale those systems: product managers from senior IC to Group/Head/VP of Product, product ops managers and directors, startup CEOs and CEO advisors who own product strategy, board members who oversee product org design, and instructors building curricula for product organizations. The profile line in her posts—"Board Member | CEO | CEO Advisor | Author | Product Management Expert | Instructor"—is itself a cue to reach folks who are making hiring, org-design and strategy decisions rather than entry-level practitioners only. Her examples—about Product Ops and how AI reshapes product management—are aimed at people responsible for organizational processes and cross-functional alignment, not solely feature-level execution. Melissa’s tone assumes readers are influencing roadmaps, defining OKRs, hiring product talent, or standing up product operations, and she writes to help them move from tactical chaos to strategic structure.

Melissa's signature hooks

Melissa returns to a small set of opening moves. First: the bold thesis hook. She will begin with a single declarative line that names the trend or problem, for example "AI is reshaping product management." That line frames the rest of the post and invites immediate judgement. Second: the debate invite. She opens with a provocation that names another prominent practitioner and calls for public conversation—"I think we need a podcast debate between Melissa Perri and Marty Cagan." That pattern turns followers into participants and signals Melissa is staging an argument, not just opining. Third: the analogy hook. She will open or quickly pivot to a vivid metaphor to make organizational mechanics tangible—"Product Ops: the unsung hero turning chaos into alignment and guesswork into strategy. It's like the backstage crew of a Broadway ..." Each hook either stakes a position, recruits interlocutors, or translates abstraction into an everyday image.

Posting cadence and format mix

Melissa posts regularly on LinkedIn, multiple times per week, with a mix that favors short text posts and practical essays over long personal narratives or visual gimmicks. The snippets show repeated posts with comment counts, indicating a steady cadence of commentary and episode-level reactions rather than once-a-month longform pieces. She posts more short-format, opinionated posts and operational primers (hooks, metaphors, and actionable recommendations) and less often posts purely promotional content or lifestyle updates. Formats she uses most are single-text posts with compact paragraphs and occasional inline enumerations; she uses links to her work or Produx Labs at the end, and sometimes references podcast episodes or peers to spark discussion. Video and carousel content appear less frequently than written posts; the emphasis is on creating a readable public argument that can be scanned and replied to quickly.

What to steal from Melissa

Open with a one-line thesis that names the change or problem. Example: "AI is reshaping product management." Keep that sentence alone on line one and let it frame the rest. Follow the thesis with two short paragraphs: the first lays out one concrete consequence for how the organization works, the second names who must act and how. Signpost your authority by adding one compact role line under your post or at the end: e.g., "Product Manager | Head of Product | Instructor" separated by vertical bars. Use a single vivid analogy inside the first or second paragraph to make an abstract system feel concrete — start a sentence with "It's like..." and finish in 10–12 words. Finish by inviting a public exchange: name a peer or pose a binary debate challenge — "We should debate X vs Y on a podcast — who's in?" — to convert readers into responders.