First 30 Days: 11 High-Impact Experiment Ideas to Impress Your New Product Team
Starting a new product role is like being dropped into the middle of a movie. Everyone else knows the plot, characters, and backstory—while you're just trying to figure out what's happening.
But here's the thing: your first 30 days aren't just about learning the ropes. They're a unique opportunity to demonstrate your value quickly and set the tone for your tenure as a product manager.
Having consulted dozens of Product Teams, this blog is my attempt to document my learnings and observations. In this blog, I will try to share my learnings and observations on how to make a strong impression in your first 30 days.
Focus on Quick Insights, Not Perfect Solutions
As a new PM, you don't need to solve every problem immediately. You just need to show you can identify important issues and approach them systematically.
Experiment #1: The 5-Minute User Test
Choose one critical user flow in your product (signup, checkout, core feature). Watch 5 users interact with it for 5 minutes each. Record three pain points and share your findings.
This simple activity demonstrates that you:
- Care about user experience
- Can identify issues quickly
- Know how to communicate findings effectively
Pro tip: Schedule these sessions within your first week. Create a simple slide with before/after screenshots highlighting the issues. Most teams rarely do enough user testing, so this creates a good first impression.
Leverage Existing Data in Unexpected Ways
Your new team has mountains of data they've been staring at for months. Your advantage? Fresh eyes to spot patterns they might have missed.
Experiment #2: The Customer Support Mining Expedition
Ask for access to customer support tickets from the last 30 days. Sort them by topic and identify the top 3 issues. Then—and this is key—quantify the potential impact of fixing each issue.
For example: "Password reset issues affect approximately 120 users per week, taking an average of 8 minutes of support time per incident. That's 16 hours of support time weekly we could reclaim."
Pro tip: Present findings as "opportunities" rather than "problems." This approach positions you as solution-oriented rather than critical of current practices.
Find the Metrics That Matter to Your Boss
Every product leader has metrics they care about most. Identifying these quickly allows you to target experiments for maximum visibility.
Experiment #3: The Metrics Alignment Sprint
Schedule 15-minute meetings with key stakeholders and ask one question: "What's the one metric you wish would improve in the next quarter?" Cross-reference answers to find patterns.
Then, design a small experiment specifically targeting that metric.
Pro tip: Create a simple 2×2 matrix showing potential experiments mapped by effort (low to high) and potential impact on the priority metric. This demonstrates both analytical thinking and strategic prioritization.
Optimize Existing Features Before Proposing New Ones
It's tempting to suggest new features immediately, but optimizing what already exists is often more valuable—and less risky.
Experiment #4: The Abandoned Action Recovery
Identify one user flow with high abandonment rates. Design an A/B test with a modified version focused on simplifying the experience or clarifying user benefits.
Even a 5% improvement in completion rates for a core flow can significantly impact overall metrics—and shows you can extract more value from existing assets.
Pro tip: Focus on reducing steps, clarifying language, or adding progress indicators. These changes are typically easy to implement but can show measurable results quickly.
Connect Product Decisions to Business Outcomes
The fastest way to impress leadership is to connect your product thinking directly to business results.
Experiment #5: The Revenue Impact Calculator
Create a simple model showing how specific product improvements could affect revenue. For example, calculate how a 10% reduction in checkout abandonment translates to additional monthly revenue.
This experiment shows you understand that product improvements must ultimately drive business results.
Pro tip: Present this as a hypothesis rather than a promise. "If we can improve X by Y%, our model suggests we could see Z additional revenue, which we can validate with a controlled experiment."
Make the Invisible Visible
Often, the most valuable insights come from exposing information that was always there but never highlighted.
Experiment #6: The Daily User Journey Map
Create a visualization showing how users interact with your product throughout the day. Identify peak usage times, common sequences of actions, and potential moments of delight or frustration.
This visualization often reveals opportunities for better sequencing, notifications, or feature placement.
Pro tip: Use existing analytics data to create this visualization. The key is presentation—turn complex behavior patterns into a simple visual story that everyone can understand instantly.
Simplify One Thing Ruthlessly
Most products suffer from feature bloat and complexity. Showing you can simplify effectively demonstrates both courage and user empathy.
Experiment #7: The Ruthless Simplification Test
Choose one complex feature or flow. Create a radically simplified version that focuses solely on the core user need. Test both versions with a small percentage of users to compare completion rates and satisfaction.
Pro tip: If a full A/B test isn't feasible in your first month, create a clickable prototype of the simplified version and test it with 5-10 users. The qualitative feedback alone can be compelling.
Surface Competitive Insights
Your fresh perspective makes you ideal for reassessing the competitive landscape with new eyes.
Experiment #8: The Competitor Experience Audit
Sign up for 3-5 competitor products and document your experience with screenshots and notes. Create a feature comparison highlighting where your product leads and lags.
Importantly, focus on experience quality, not just feature presence. A competitor might have the same feature but implement it more intuitively.
Pro tip: Present findings as opportunities rather than criticisms. "Company X does Y particularly well. Here's what we might learn from their approach..."
Find the Hidden Power Users
Every product has unexpected power users leveraging the product in ways the team never imagined.
Experiment #9: The Power User Interview Series
Identify 3-5 users with unusual usage patterns—extremely high engagement, unique feature combinations, or unexpected use cases. Conduct 30-minute interviews to understand how and why they use the product.
These conversations often reveal untapped opportunities or positioning advantages.
Pro tip: Record these sessions for your own reference and create a presentation of the most interesting insights. These authentic user voices can be incredibly persuasive in product discussions.
Create One Perfect Onboarding Moment
First impressions matter for users too. Improving onboarding shows immediate impact and signals your understanding of the growth funnel.
Experiment #10: The Aha Moment Accelerator
Identify your product's "aha moment"—that instant when users truly understand its value. Design an experiment to help users reach this moment faster through better onboarding, tooltips, or guidance.
Pro tip: Keep it small and measurable. For example, test adding a single, well-timed tooltip that highlights a valuable feature many users miss initially.
Bridge Departmental Divides
Product success often hinges on cross-functional collaboration. Demonstrating you can bridge divides sets you apart immediately.
Experiment #11: The Cross-Functional Insight Exchange
Schedule separate 30-minute sessions with leads from sales, support, and engineering. Ask each team: "What's one thing you wish product understood better about your challenges?"
Synthesize these insights into specific product improvement ideas that address cross-functional pain points.
Pro tip: Focus on quick wins that make other departments' lives easier. For example, a small dashboard giving customer support visibility into user actions can dramatically improve their effectiveness while requiring minimal development effort.
Ending Notes
Your first month in a new product role is less about having all the answers and more about demonstrating how you approach problems. These 11 experiments provide a framework for making an impact quickly while building the relationships and knowledge you'll need for long-term success.
Remember, the goal isn't to implement all 11—it's to choose the 2-3 most relevant to your specific situation. The best experiments align with your strengths, address your organization's priorities, and can be executed quickly with minimal dependencies.
Remember, "First impressions matter a lot."