AI Prompts for Storytelling

29 prompts available for product managers.

블로그 포스트(Blog Post)

개인 메모를 잘 다듬어진 블로그 포스트(blog post)로 바꿔주는 프롬프트입니다. 거친 아이디어를 입력하기만 하면, 고유한 보이스(voice)는 유지한 채 콘텐츠를 다듬어 블로그 글쓰기를 수월하고 진정성 있게 만

734 uses

제품 이름 제안(Product Name Suggestions)

이 프롬프트는 기존 브랜드의 정체성(identity), 가치(values), 톤앤보이스(voice)에 자연스럽게 녹아드는 제품명 또는 기능명을 만들도록 설계되었습니다. 브랜드의 성격(personality), 감정적

596 uses

릴리스 노트(Release Notes)

이 프롬프트는 프로덕트 매니저, 개발자, 마케팅 팀이 명확하고 매력적인 릴리스 노트(release notes)를 만들 수 있도록 돕습니다. 구조를 핵심 요소로 분해해 주요 업데이트, 개선사항, 버그 수정이 타깃 청중

474 uses

스티브 잡스처럼 발표하기(Announce Like Steve Jobs)

이 프롬프트는 스티브 잡스에게 영감을 받아 설득력 있고 감정을 자극하는 제품/기능 발표를 작성하도록 도와줍니다. 핵심은 단순함, 우아함, 그리고 그 기능이 사용자 경험을 어떻게 변화시키는지에 두는 강조입니다. 결과는

325 uses

슬라이드 덱을 대체할 제품 내러티브 메모(Product Narrative Memo)

제품 리뷰 미팅이 PowerPoint로 인한 죽음 — 40장의 슬라이드, 15장째에 이르면 아무도 핵심 인사이트를 기억하지 못함. 이 프롬프트는 명확한 사고와 구조화된 논증을 강제하는 Amazon 스타일의 내러티브

27 uses

투자자 및 이사회용 제품 내러티브(Investor & Board Product Narrative)

투자자 미팅, 이사회 발표, 또는 펀드레이징 덱을 위한 설득력 있는 제품 내러티브를 만드세요. 제품 지표와 로드맵을 신뢰를 쌓는 전략적 스토리로 번역해줍니다.

18 uses

Write a compelling product narrative for stakeholder alignment

Use this prompt when you need to craft a strategic product narrative that aligns executives, engineering, and cross-func

14 uses

Write a product positioning statement using the competitive wedge method

You're launching into a crowded market and your messaging sounds like every competitor's. This uses the competitive wedg

13 uses

Cross-Functional Kickoff Brief

Create a project kickoff document that aligns engineering, design, marketing, and business teams on goals, scope, timeli

12 uses

임원 요약 및 이사회 업데이트(Executive Summary & Board Update)

전략적 진행, 핵심 지표, 필요한 결정을 전달하는 임원 요약과 이사회 수준 제품 업데이트를 작성합니다 — 모두 임원들이 선호하는 간결한 형식으로.

11 uses

Product Update Email Writer

Write compelling product update emails for different audiences: customers, internal team, leadership, and investors. Eac

11 uses

Craft a stakeholder alignment brief for cross-functional buy-in

You're about to pitch a product initiative but each stakeholder cares about different things — engineering wants feasibi

10 uses

Feature Request Rejection Template

Say "no" to feature requests professionally while maintaining strong relationships with customers, sales teams, and stak

9 uses

Build a cross-functional alignment ritual for recurring conflicts

The same fight between engineering and product happens every planning cycle. This designs a standing alignment ritual —

7 uses

Give feedback using the GAIN framework (Goal, Actions, Impacts, Next actions)

Your report just missed a deliverable for the third time, or your cross-functional partner keeps rewriting your PRDs. Yo

7 uses

Write a launch announcement email for customers

Your launch email will be opened by 20% of customers, read by 5%, and acted on by <1%. This writes a launch email that r

6 uses

Conduct a product naming workshop

You are launching something and the team has been arguing over names in a Slack thread for three weeks. This runs a sing

6 uses

Draft a why-now section for an investor deck

Your investor deck has a great product and no sense of urgency. "Why now" is the slide that often decides the meeting. T

5 uses

Write a product vision statement with evidence

Your product vision statement is vague poetry and the team can't ship against it. This writes a 3-year vision statement

5 uses

Build a sales enablement one-pager for a new feature

A feature shipped and sales is asking "how do we sell this?" This builds a one-pager enablement — buyer personas, pain t

5 uses

Write a feature rejection response

You're saying no to a feature request from a major customer or a senior stakeholder. The default email sounds dismissive

5 uses

Write a changelog that converts free users

Your free users never see your paid-tier features and the upgrade path is invisible. This writes a changelog that mentio

4 uses

Build a stakeholder update cadence with tiered depth

You're writing the same update three times — short for Slack, medium for the weekly, long for the quarterly — and it's e

4 uses

Write a one-pager product narrative for the exec team

Your quarterly exec update keeps growing into a 15-slide deck that buries the point. This produces a true one-pager — th

4 uses

Craft a board update with the four key slides

Your board deck is 35 slides and the board members ask the same three questions every time. This produces a four-slide d

4 uses

Build a release notes template that drives re-engagement

Your release notes read "Bug fixes and performance improvements." Nobody opens them. This writes a release notes templat

4 uses

Write a product deprecation announcement with minimal churn

You're sunsetting a feature 12% of customers rely on and the comms team is asking you for the email draft. This writes a

4 uses

Draft a customer success handoff narrative

A customer closed and is being handed to CS, who will inherit 8 threads and no narrative. This writes a handoff narrativ

3 uses

Draft a PR/FAQ in the Amazon style

You're starting a new product and want to force clarity before anyone writes code. This drafts a working-backwards PR/FA

3 uses