How a "ReadMe" doc can improve collaboration for Product Managers

Hey friends,

As product managers, we’re often stepping into new teams, navigating complex workflows, and making decisions that will shape the product’s future. But there’s one thing I’ve learned over the years: the better people understand how you work, the easier it is to collaborate and make things happen. 

That’s why I’m sharing my ReadMe, a guide to how I work, make decisions, and collaborate. Whether you’re a PM, engineer, designer, or just want to get a sense of how I approach projects, this doc can give you insight into what to expect when working with me.

Why a "ReadMe" Doc?

It’s simple: transparency leads to better collaboration.

By giving everyone a glimpse into how I think, how I prioritize, and how I make decisions, we can avoid confusion, unnecessary back-and-forth, and streamline the process of getting things done. If you’re new to a team (or a new team member on a project), I highly recommend creating one of your own.

How I Think About Product

1. User-Centered:
I focus on solving real user problems. I always start by understanding customer pain points and using their feedback to guide my decisions.

Example: If we’re working on a new feature, I’ll dive into customer interviews and feedback to understand if the problem we’re solving is significant enough to warrant development.

2. Data-Driven:
I combine quantitative data (like metrics and trends) with qualitative insights (user interviews, support feedback) to make informed decisions.

Example: If a feature is getting high usage but low adoption, I’ll look into the metrics and compare that to user feedback to figure out where the disconnect is.

3. Collaboration-First:
I believe the best solutions come from cross-functional teamwork. That means working closely with engineering, design, and product teams to ensure we’re all aligned on goals.

Example: Before we dive into building something new, I’ll make sure we align on the "why" and the problem space—this helps us stay focused and ensures everyone is on the same page.

4. Iterate & Optimize:
I believe in shipping incrementally and constantly iterating based on user feedback.

Example: If we roll out a new feature, I’ll be monitoring feedback closely and push for updates or improvements based on early usage data.

How I Work

Making Decisions:

• Prioritization Frameworks: I use a mix of impact vs. effort, customer urgency, and alignment with our product vision to prioritize what to work on next.

• Customer Signals: I rely on customer interviews and usage data to validate what’s most important to tackle.

• Trade-offs & Alignment: I communicate why a decision was made, what’s in scope, and what’s not, so everyone knows where we’re heading.

Communication Style:

• Async-friendly: I love structured updates in Slack, Notion, and Loom—this way, everyone knows what’s going on without having to wait for live meetings.

• Direct but Collaborative: I value transparency and constructive feedback.

• Frequent Check-ins: I’ll regularly update the team on progress and keep stakeholders in the loop.

How to Work with Me

• If You’re an Engineer:
  I’ll ensure we’re aligned on the problem space and the “why” before jumping into execution. I’m happy to dive deep into technical trade-offs and feasibility.

• If You’re a Designer:
  Expect deep conversations about discoverability, information hierarchy, and UX patterns. I’ll advocate for a customer-first approach and share real user feedback to guide design decisions.

• If You’re a Fellow PM:
  I love collaborating and brainstorming. If our work overlaps, let’s sync early to align on goals and avoid duplication of efforts.

How I Gather Feedback

• User Research & Customer Calls: I regularly join customer interviews and listen in on support calls to gather feedback directly from users.

• Analytics & Adoption Data: I track key usage metrics to understand how users are interacting with our product and where friction may exist.

• Internal Feedback Loops: I connect with Sales, Customer Success, and Support teams to get a pulse on what users are saying.

What I’m Currently Focused On

• Improving Discoverability in Analytics: Making sure users can easily find the reports they need in the analytics suite.

• Enhancing Personalization: Tailoring dashboards to better fit user workflows and increase engagement.

• Refining Onboarding: Simplifying the onboarding process to help users get up and running faster.

If you want to take a deeper dive into how I work, feel free to check out my full ReadMe doc. And hey, if you’re a PM or on a team and haven’t created one of these yet, I highly recommend it, it’ll save you so much time and confusion in the long run.