Carl Vellotti Profile picture
Jun 5, 2024 1 tweets 1 min read Read on X
A classic PM problem:

An executive is pushing to launch a big new feature they're excited about. You have data suggesting users won't find it valuable.

How do you handle this situation with the exec while responsibly building what's best for users and the business?

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Carl Vellotti

Carl Vellotti Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @carlvellotti

Aug 11, 2024
How often should PMs communicate with stakeholders? 🤔

↳ It depends on the project.

Matching communication to project complexity is key.

Here's a 5-step process to get it right 🧵👇 Image
1️⃣ Document Stakeholders and Their Concerns

Identify all the stakeholders involved and pinpoint their specific needs and concerns within the project.

Ex: Marketing needs weekly updates on feature development for promotional planning; Sales requires monthly revenue forecasts.
2️⃣ Assess Risk and Impact

Evaluate the risk level and the impact of not communicating effectively with each stakeholder group.

Ex: Engineering is working on a high-risk, business-critical module; Marketing is focused on a seasonal campaign with high revenue potential.
Read 7 tweets
Jul 30, 2024
.@nikitabier drops an INSANE amount of product wisdom on X.

But it's all disorganized.

So I did a 40+ hour deep dive to distill his best lessons.

Today: A no bullsh*t approach to discovering viral growth hacks 🧵 Image
@nikitabier For context, Nikita is most famous for:

1. Building TBH app from 0 → 5M users in 2 months.
2. Building gas app from 0 → 10M users in 3 months.

With $0 marketing spend.

They're legendary for their ingenious viral growth optimization.

Here's what gas app looked like:
@nikitabier 1️⃣ Find viral hacks with experimentation (it's the only way)

First of all – why is experimentation so important for viral growth?

Why can't you just copy successful incumbents?
Read 20 tweets
Feb 22, 2024
1-pagers are critical for getting buy-in for your ideas.

But they're very hard to write well.

Here's:
🔹 a step-by-step guide to the 1-pager
🔹 examples of mistakes and how to fix them

(+a FREE template for rock-solid 1-pagers)

Step 1: Writing the 1-pager! Image
Step 2) Understand the purpose of the 1-pager

The goals of writing down your idea:
1. Help you make sure it's good
2. Persuade others that it's good

That second point is critical.

1-pagers aren't research projects, they're persuasive essays aimed at getting buy-in. Image
Step 3) Frame the problem & opportunity

Answer these questions:
- Why does this matter to you customers and business?
- What evidence or insights do you have to support this?
- Why is solving this problem urgent? Why now?
Read 26 tweets
Jan 22, 2024
Every PM wants to get better at strategy.

I used to love studying strategy but got lost when I tried to make my own.

Then I learned how to make product flywheels. Now I always know where to start, and how to drive alignment.

Here's a step-by-step guide to making your own 🧵 Image
Quickly, here are a few examples of excellent flywheels.

They are:
• Simple
• Customer-centric
• Adaptable

Take a moment to carefully review them before moving on. Image
Inspired? Let's get right into it

Preparation
1. Block off at least one entire hour for this process.
2. Put your phone away. Mute Slack notifications. This is DEEP WORK, baby.
3. I recommend you start this process with pen and paper.
Read 15 tweets
Jan 3, 2024
3 non-obvious requirement tips:

1. If your requirement has "and" in it, break it into two requirements.
2. Prioritize every requirement
• P0: You'd be embarrassed not to have this
• P1: People will buy your product because it does this
• P2: People will complain about missing P2s after they buy the product
• P3: Can be descoped and added to future iteration
3. Don't describe exact design

Leave your designers free to ideate without your constraints.

Focus on goals:
• usage
• user behavior
• user expectations
• why the user uses this feature
• if ease of use is more important than functionality

etc.
Read 4 tweets
Jan 2, 2024
You don't need to read every product book.

In 2024, spend more time with fewer books.

I've put together:
🔹 My 2 top recs across the product spectrum
🔹 Advice on how to choose

𝗝𝗮𝗻𝘂𝗮𝗿𝘆: 𝗟𝗲𝗮𝗱𝗲𝗿𝘀𝗵𝗶𝗽 Image
𝗙𝗲𝗯𝗿𝘂𝗮𝗿𝘆: 𝗦𝘁𝗿𝗮𝘁𝗲𝗴𝘆

1. Playing to Win: Engaging primer on business strategy packed with case studies.

2. Good Strategy Bad Strategy: Goes beyond surface-level strategy tips to examine the fundamentals of strategic thinking. Image
𝗠𝗮𝗿𝗰𝗵: 𝗦𝘁𝗼𝗿𝘆𝘁𝗲𝗹𝗹𝗶𝗻𝗴

1. Storyworthy: Practical tips for crafting sticky business narratives.

2. Tell to Win: Mastery of storytelling across fields based in science and practice. Image
Read 14 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

:(