How to Use AI for Better Communication
BLOG 5: One Product Update, Different Audiences
A Product Manager often has to deliver the same piece of information multiple times. The development team needs technical context. Management wants business impact. Customer Support wants to know what changed.
What matters most to the user is: “What’s in it for me?”
The information is the same. But the communication isn’t.
And that’s where AI can be very practical.
Don’t just change the tone
If you tell AI “Make this sound more professional.” you’ll get a more professional version.
But that’s not where the real value is. It’s better to say:
“This is for management. The goal is for them to understand the business impact. Technical details aren’t important unless they support that message.”
Then you aren’t just changing the style. You’re changing the focus.
Proposed prompt to get started
Role: You are an experienced Product Manager who knows how to tailor the same information to different audiences and channels. Do not change the facts, meaning, or results from the original input.
Raw notes: [enter what was done]
Audience: [development team / management / customer support / end users]
Goal: [inform / get a decision / request action / explain a change]
Channel: [Slack / email / release notes / presentation / in-app]
What matters most to this audience: [enter here]
Tone: [professional / simple / formal / friendly]
What to leave out: [enter here]
Create communication tailored to this audience. Do not invent business or customer value that is not contained in the input. If important context is missing, state what is missing.
At the end, explain in one sentence what you changed and why it is more relevant to this audience.
Same fact, different focus
Let’s say the information is:
“Fixed an issue with charts loading on mobile devices and sped up data synchronization.”
What might matter to the development team: what was changed and what needs to be checked.
To management: what kind of problem was solved and what the impact is.
To Customer Support: what users can expect now.
To the user: what is better for them. No version should invent a result.
But not every version has to talk about the same thing in the same way. That’s an important difference.
AI shouldn’t be a “copywriter” here. It should be a tool for the translation of context.
Same input. Different audience. Different relevance. Still the same facts.
Try it today
Take the last sprint update you sent out. Give AI the same input.
Ask for four versions:
- for the development team;
- for management;
- for Customer Support;
- for the end user.
Then compare the results.
Ask yourself: Did AI just change the tone – or did it change what matters most to the audience?
If it’s the latter, you used AI the right way.
BLOG 4: How to use AI for RICE and Assumption Testing
Clarifying Acceptance Criteria ensures you build the feature right. Next, you need to make sure you are building the right feature first. And find out how AI can help.
THE FINAL WORDS
Once you make a product decision, the job isn’t done. You have to explain it to different people. The development team needs one context. Management needs another. The user needs a third.
Yet the core information remains the same.