Becoming More Strategic and Navigating Difficult Colleagues with Anika Gupta

Executive overview

Being strategic means articulating a clear, compelling "why" behind decisions and championing difficult changes that serve the company's long-term interests. At its core, strategic leadership requires balancing a positive mindset with deep operational clarity—understanding the business deeply enough to know when to shift direction, then making decisions quickly with imperfect information and learning from the results.

Core insight: Strategy is a mindset (abundance, fun, gratitude) combined with the discipline to decide with 70% certainty, then iterate.

How to become strategic: The two-part formula

• Articulate a compelling and simple "why" behind your decisions and company direction.
• Champion hard ideas that serve long-term interests, even when execution is difficult.
• Both elements matter equally—strong communication alone or ambitious ideas alone won't register as strategic.
• Start by listening, summarizing, and synthesizing what others are saying in meetings; people perceive summarization as strategy.
• Make ideas "one click better" rather than radically different—refine outside-in (customer problems, market dynamics) rather than inside-out (technical constraints).

Decision-making with imperfect information

• Always operate with incomplete information; waiting for perfect clarity is analysis paralysis.
• Commit to decisions at 70% confidence and iterate post-launch to learn what actually works.
• Frame decisions as hypotheses with explicit assumptions (e.g., "We believe this customer segment will pay because X").
• Reward learning over outcomes—if a decision fails, celebrate what was learned to use elsewhere.
• Being a "historian" of your organization helps: study past decisions, why they were made, and what baggage people carry about similar attempts.

Managing energy and mindset

• Strategic leaders bring their full selves to difficult situations—manage energy, not just time.
• Simple tactics: eat lunch (don't skip for a protein bar), avoid scheduling hard meetings during your worst hours (e.g., 5–6 PM).
• Reframe difficult moments: ask "What can I learn?" and "How can I have fun with this?"
• Journaling uncovers irrational triggers and clarifies what's within your control.
• One post-it on every monitor: "Have fun."

Working with founders in Founder Mode

• Recognize a founder's power to shift direction or innovate; activate them as allies when major momentum is needed.
• If a founder pushes an idea you disagree with, ask yourself: What's the underlying objective? Is this mechanism the right path?
• Discuss the objective, not just the mechanism—e.g., "I know you want to move the needle here. Let's explore options beyond just option A."
• Pick your battles: Decide which hills are non-negotiable for company success, and let the rest go.

Operating in Founder Mode as a product leader

• Get into the details: understand the business deeply (financials, metrics, decisions), even if you don't act on everything immediately.
• Ask your team to present their strategies; ask probing questions and share hypotheses rather than dictating.
• Seed assumptions (e.g., "I heard X feedback from customers; what does that mean for our strategy?") to keep the discussion open.
• Focus on a few strategic areas: what could kill the business if wrong, and what are the biggest opportunities?
• This approach builds clarity for teams while preventing the perception that you're "stomping" on their work.

Navigating difficult personalities

• Believe you can work with anyone; curiosity beats judgment.
• Understand what drives them: career ambition, company success, ego, or something else.
• Connect their motivation to what you need from them—like product discovery, but for people.
• Replace frustration with gratitude: study what they do well (communication, vision, influence) and learn from them.
• Talk to people who've worked for them successfully to understand what makes them tick.

Giving hard feedback effectively

• Set up the conversation: explicitly say "I care deeply about you and want you to succeed," backed by body language and tone.
• Be direct: passive-aggressive feedback doesn't work; name the behavior or perception clearly.
• Frame as perception, not character: "This is how you're being perceived" gives people room to course-correct without defensiveness.
• Provide 2–3 concrete steps to change the outcome, then brainstorm together.
• Ask what they want in their career first—tailor feedback to their goals, not generic advice.

Receiving hard feedback

• Let yourself feel the emotion first (hours, days, whatever it takes); don't suppress or rationalize immediately.
• After the emotional wave passes, come back curious: Why is this feedback emerging? From whom? What's the context?
• Talk to others for additional context; don't just react to the single source.
• Decide what to act on by anchoring to company needs: What must we fix? What's nice-to-have?
• Not all feedback is actionable, but all feedback reveals valid feelings—separate the two.

Breaking into product management

• Easiest path: Join a product-adjacent role (support, sales, engineering) at the same company, build credibility, then transition internally.
• Each function brings value: support teams know customer pain, sales teams know what sells, engineers know the technical landscape.
• For startups: say you want product in your interview if it's a 20-person company; for large companies, build the relationship first, then ask.
• Once inside, work on product projects, present to product leaders, and make the transition formal.
• Most successful paths: product-adjacent role in a company, or first PM at a small startup.

New PMs often misunderstand the role

• The job isn't learning tools (Figma, whatever)—it's learning to take ambiguous situations and drive clarity iteratively.
• Teaching this class revealed that the frameworks (discovery, ideation) are flexible; what matters is the mindset and problem-solving skill.

AI tools for product teams

• Dovetail (or similar): Automatically summarize user research calls, tag insights, and make them searchable across projects.
• Early days of AI impact on PM work, but summarization and insight retrieval are already powerful unlocks.

Building the mindset: Practical techniques

• Journaling: Write down all your negative thoughts, then explore why. Question whether the emotion is rational or grounded in something real.
• Cognitive-behavioral therapy on yourself: Once written, you can separate fact from feeling and decide what to act on.
• Reframe threats as fun challenges; bring humor into meetings to shift your own mood and the room's energy.
• Connect with gratitude even for difficult people; name what you learned or admired about them.

Books, media, and influences

• The Hard Thing About Hard Things by Ben Horowitz—mindset for approaching hard problems.
• Brandon Sanderson (sci-fi/fantasy): Elite craftsperson; writes extensively on writing and craft.
• Fallout (TV series): Quirky, unexpected, dystopian—fun escape.
• Foundation series by Asimov: Complex, rich; worth the initial effort to get into.