skills/managing-up/SKILL.md
Help users work effectively with their manager and executives. Use when someone is struggling with their manager relationship, needs to influence leadership, wants to get better at executive communication, or is trying to build trust with their boss.
npx skillsauth add cvillamarp-lgtm/skillspodcast managing-upInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Help the user work effectively with their manager and executives using strategies from 35 product leaders.
When the user asks for help managing up:
Boz: "The advice I give more frequently than any other is for people to more directly leverage their leaders." Your primary job is to achieve results. Your manager has tools and authority to clear paths. Ask for help to bulldoze blockers rather than trying to solve everything yourself.
Casey Winters: "People just way under communicate upward. Then they complain that executives are out of touch when they aren't telling executives what they need to know." Send weekly "state of" emails with priorities, blockers, and thoughts. Frame updates as "no response required" to keep leaders informed without creating burden.
Fareed Mosavat: "You should understand your boss's priorities and your boss's boss's priorities. Eventually, that means you have to know what the board is thinking." Build a mental model of how your work creates leverage in the larger system. Tailor communication to address senior leadership's specific concerns.
Wes Kao: "When you ask 'Hey manager, what should we do?' you're putting a lot of cognitive load on them. Instead say 'Hey manager, here's what I think we should do.'" Present a point of view even if it's just an initial hunch. Provide insights and takeaways, not just raw data.
Boz: "We used HPM - Highlight, People, Me. Every manager at Facebook would send this to their manager." Use consistent formats. Ask your manager: "How do you like to get information about me?" Consider weekly emails with priorities, blockers, and general thoughts.
Ethan Evans: "Management can be a lonely job. Having an ally is a huge weight off people's shoulders." Recognize managers are overwhelmed. Move from asking "How can I help?" to suggesting specific solutions. Keep them in the loop by proactively fixing problems before they ask.
Casey Winters: "You have to start with chapter one, which is what part of the company strategy are you working on? What metrics are you trying to improve? What assumptions are you making?" Find the last point that's obvious to the audience and build from there. Don't dive into "Chapter 6" details without the strategic context.
Dylan Field: "The more concrete an artifact is or the more you can debate something, the better. I ask for examples a lot." Present designs and docs rather than abstract ideas. If you lack data for a follow-up question, pause to find the answer rather than guessing.
Itamar Gilad: "If you run a secret experiment and come back with data, either they get extremely mad at you... or more commonly, they're pleasantly surprised." Use evidence to flip a leader's perspective rather than engaging in a battle of opinions.
Jiaona Zhang: "It's understanding the spirit of what they're trying to achieve. Being able to go back with 'I understand the spirit, but here's a better way to achieve it.'" Align on the underlying goal first. Present automated or scalable alternatives rather than just saying no.
Noah Weiss: "High involvement at the start for strategy and at the end for quality, with autonomy in the middle." Involve founders early for strategic buy-in on goals. Bring them back at the end to ensure the product meets quality standards.
Peter Deng: "Say you're going to do the thing, say that you're doing the thing, and then say that you did it." This repetitive communication ensures alignment and provides opportunities for course correction.
For all 50 insights from 35 guests, see references/guest-insights.md
testing
Help users communicate more effectively in writing. Use when someone is drafting memos, emails, strategy docs, announcements, or any written communication that needs to be clear, concise, and persuasive.
documentation
Help users write effective specs and design documents. Use when someone is creating technical specs, feature specs, design docs, or trying to communicate product requirements to engineering and design teams.
development
Help users write effective PRDs. Use when someone is documenting product requirements, preparing specs for engineering, writing feature briefs, or defining what to build for their team.
tools
Help users define their North Star metric. Use when someone is choosing their primary success metric, trying to align the team around a key measure, struggling with metric proliferation, or setting up their measurement strategy.