AMA: Bluevine Senior Director of Product Management, Aaron Bloom on Product Development Process

I haven't found a universal formula for the right PM : Engineering ratio. I’ve worked with everything from one developer to much larger teams - both can be effective in the right situation.What matters more is whether the team is structured to work efficiently. Here are a few things I look at when thinking about efficiency: Priority and scope: If a feature is critical or time-sensitive, a larger team may help accelerate delivery. But if it's a smaller or more contained feature (e.g. a single new ...Read More

Engineers should have a strong voice in both sprint and strategic planning. The key is creating the right environment for structured input, not handing over decision-making.PMs must first align the team on the business and customer needs behind the roadmap.Engineers should then weigh in on feasibility, design, and alternate approaches - they often see system-level efficiencies the PM may not have perspective on.Roadmaps also carry hidden costs like tech debt and test automation. If there’s no sp ...Read More

The key levers building any product are resources, time (when the initiative needs to be delivered), and scope. If there are budget constraints driving a limitation on resources, then you can adjust the scope or timeline for the initiative. For example, if you're building an MVP and can’t get more time or people, the most practical move is to reduce scope, either by moving smaller features to later phases, or narrowing the target audience.This framework helps Product Managers make grounded trade ...Read More

A key responsibility of the Product Manager is to align cross-functional teams around the problem statement, business need, and OKRs. When everyone understands the "why" behind the roadmap, it generates alignment on decision making and accelerates meaningful outcomes.Building trust-based partnerships between product, engineering, and design is critical. When each function can confidently represent its domain, without being overly influenced by politics and second guessing, it drives strong colla ...Read More

QA testing is a minimum requirement for every story - shipping untested features leads to compounding quality issues that are harder to untangle later, which will slow down overall velocity. On small teams, it’s critical to clearly define roles, including who owns QA. This ensures coverage regardless of function or team size.PMs should be involved in QA to validate the end-to-end user experience, and that requirements have been met. In smaller or earlier stage teams, QA becomes a cross-functiona ...Read More

Representing your team to leadership is a core responsibility of a Product Manager. That starts with generating clear alignment on business goals and product requirements early, setting realistic timelines up front, and maintaining consistent communication throughout the product life cycle. This should be explicit alignment - don't assume you are on the same page from a hallway conversation. No project goes perfectly, so it’s important to share objective and proactive updates on the progress and ...Read More

Once I've gathered and documented a summary of user insights, market and competitive context, and product requirements, I focus on mapping out the key user workflows. This helps clarify what the product needs to do and frames the conversation with design around function and flow.If the product is part of an existing platform, I reference similar internal patterns or flows to maintain consistency. It also gives us a concrete starting point, rather than beginning from scratch.Before jumping into f ...Read More

If we were discussing this live, I’d first ask what exactly are you pushing back on, and why? The context matters. Like any feedback, input should be evaluated based on its quality and relevance, not just who it comes from.Start by clearly defining your target user segments. Once that's established, you can assess how closely your engineering team aligns with that profile.For example, if you're building a SaaS product for enterprise SaaS engineers, then there’s strong overlap. In that case, you’ ...Read More

Engineering needs clear context on why a problem matters - its root cause and its business impact. The timing of their involvement depends on their availability and the problem’s scope and priority.I keep engineers loosely informed as problem statements come up as they often spot technical insights early that can save time. For example, what seems like a UX issue might stem from a synchronous backend process.Deeper involvement usually comes once priorities are clear and the story / PRD for the s ...Read More