All Prompts
#33

Build Your Cross-Team Reputation in Every Update

(The Visibility Loop)

Opening

You're shipping a feature that touches three teams. You send a quick Slack update to your manager. She knows what you did. The other teams? They have no idea you exist.

You're building influence across teams. You send a structured update to four channels with context each team cares about. Engineering sees your technical decisions. Product sees your user impact. Leadership sees your strategic thinking. Two teams reach out to collaborate on their next projects.

The difference? You turned one update into four targeted moments of visibility. Each team saw how your work connected to theirs.

Peter Drucker wrote that effective knowledge workers manage across organizational boundaries, not just up and down. Your impact multiplies when other teams see your work. AI adapts one update for multiple audiences without rewriting from scratch.

This used to take an hour of rewriting. AI can now adapt your core update for different audiences in 90 seconds, giving you cross-team presence without the overhead.

The Principle

Cross-team visibility isn't about broadcasting everywhere. It's about showing up in the right conversations with the right context.

Most people write one generic update and copy-paste it. It lands flat because engineering doesn't care about business metrics, and leadership doesn't care about implementation details.

The pattern that builds reputation: same achievement, different lens. Engineering hears about architecture decisions. Product hears about user outcomes. Leadership hears about strategic alignment.

You're not changing what you did. You're translating your impact into what each audience values. That's how you become known beyond your immediate team.

The Prompt

Loading...

Why It Works

Visibility isn't about volume, it's about relevance. When you show people how your work connects to their goals, they remember you as someone who understands the bigger picture.

Different teams track different metrics. Engineering values technical decisions. Product values user outcomes. Leadership values strategic alignment. Speaking their language shows you can operate at multiple levels.

This compounds. When someone needs a technical lead who understands business impact, your name comes up. When they need someone who can work across teams, they remember you. You're building a reputation for seeing connections others miss.

Try This

Do this right now:

1. **Find your last shipped project or completed task** - Pull up the Slack message, email, or doc where you announced it. Copy the text.

2. **Paste it into ChatGPT with this prompt** - "Turn this into 3 versions: one for engineering (technical depth), one for product (user impact with metrics), one for leadership (strategic value). Keep each to 3-4 sentences."

3. **Post each version in the next 24 hours** - Engineering version in your tech channel, product version in your project channel, leadership version in your weekly update or all-hands doc. Add one sentence inviting collaboration.

Takes 8 minutes. You'll get at least one response from a team that didn't know about your work before.

Want all 50 prompts?

Get the Book — $27

Early pricing. Regular price $197