Sharebird
Anton Kravchenko

AMA: Carta Sr. Director of Product Management, Anton Kravchenko on Product Roadmap & Prioritization


April 11, 2024 @ 11:00AM PT

View AMA Answers

  1. Where do ideas for new features come from? How do you decide which ones to build?

    Anton Kravchenko
    Anton Kravchenko

    Carta Sr. Director of Product Management | Formerly Salesforce, MuleSoft, Apple • 2y

    Ideas for new features come from various sources, including customer feedback, market research, internal brainstorming sessions, competitor analysis, and emerging technologies. To decide which ideas to invest in, product teams evaluate them against business goals, user impact, and technical feasibility. Personally, I find a lot of joy during the ideation phase. The biggest challenge I see teams face is bringing these ideas together into a cohesive narrative that generates virality before the pro ...Read More

    592 Views
    1 request
  2. How do you get autonomy for prioritizing your roadmap when your sales process is very sales heavy, and sales leadership wants to dictate priorities?

    Anton Kravchenko
    Anton Kravchenko

    Carta Sr. Director of Product Management | Formerly Salesforce, MuleSoft, Apple • 2y

    Let me begin by emphasizing the problem. It's important to prioritize sales yet balance growth with sustainable practices that prioritize customer satisfaction and ongoing innovation within your product teams. How to gain autonomy in shaping your roadmap heavily depends on your organization's culture. Understanding whether sales, product, or engineering primarily influences the company's direction is key. In a product-driven culture, for instance, your product leadership (CPO) can often support ...Read More

    444 Views
    1 request
  3. How do you handle exec input in the roadmap, and convey a point of view while also accommodating?

    Anton Kravchenko
    Anton Kravchenko

    Carta Sr. Director of Product Management | Formerly Salesforce, MuleSoft, Apple • 2y

    I usually focus on deeply understanding the "why" behind an ask or input. One time, I heard "We should build a new product A" directly from a CEO. Asking the question "why" helped me understand that the broader delivery organization was undergoing a transformation, and building a new product would support the business while creating customer delight. In return, when conveying a point of view, I often refer to data or customer anecdotes. Offering customer-centric insights helps executives underst ...Read More

    406 Views
    1 request
  4. Which stakeholders have input into your roadmap, and how to balance giving them influence vs control?

    Anton Kravchenko
    Anton Kravchenko

    Carta Sr. Director of Product Management | Formerly Salesforce, MuleSoft, Apple • 2y

    Your key stakeholders to shape a roadmap are: Customers/Users: Capture direct feedback and use data to gain insights into user needs, pain points, and feature requests. Sales & Marketing: This group will provide insights on market demand, competitive landscape, and feedback from prospects and customers. Support & Customer Success: These teams are an excellent source for understanding common issues, pain points, and feature requests from existing customers. Executive team: Seek guidance f ...Read More

    459 Views
    1 request
  5. What is your end to end process for prioritizing features on your roadmap?

    Anton Kravchenko
    Anton Kravchenko

    Carta Sr. Director of Product Management | Formerly Salesforce, MuleSoft, Apple • 2y

    At Carta, our end-to-end process for prioritizing features is rooted in strategic alignment, user-centricity, collaboration, and data-driven decision-making. For simplicity, you can think of the process in the following way: Align: Our process begins by aligning the team's product strategy with the overarching business objectives, ensuring that every feature we prioritize contributes directly to the company's strategic goals. During this process, we gather valuable insights from various sources, ...Read More

    800 Views
    4 requests
  6. We’re pivoting our product, and it’s difficult to plan the roadmap too far out. How do we reset expectations on what product communicates?

    Anton Kravchenko
    Anton Kravchenko

    Carta Sr. Director of Product Management | Formerly Salesforce, MuleSoft, Apple • 2y

    Navigating a product pivot involves recalibrating communication with stakeholders, including customers, investors, and internal teams. The primary goal is to build trust. I recommend transparently communicating the rationale behind the pivot and framing it as an opportunity for innovation and growth. At this phase, shifting your team's focus from long-term planning to short-term goals is crucial. Your ability to demonstrate tangible progress toward these short-term goals will deepen trust and re ...Read More

    409 Views
    1 request
  7. How does your product team usually work with your product marketing team with building the roadmap?

    Anton Kravchenko
    Anton Kravchenko

    Carta Sr. Director of Product Management | Formerly Salesforce, MuleSoft, Apple • 2y

    At Carta, our product teams collaborate closely with product marketing when building the roadmap to offer context into upcoming features and product enhancements. Product marketing leverages this information to develop compelling messaging, positioning, and go-to-market strategies aligned with the product roadmap. Once we get close to an upcoming release, we usually work together more often to shape the value proposition and share it with customers and prospects via webinars, blogs, and updates ...Read More

    417 Views
    1 request
  8. What framework should I use to prioritize either dedicating engineering resources to build out product functionality or just using a 3rd party service?

    Anton Kravchenko
    Anton Kravchenko

    Carta Sr. Director of Product Management | Formerly Salesforce, MuleSoft, Apple • 2y

    My two go-to frameworks are MoSCoW and RICE. The first focuses more on prioritization based on the importance of features, while the latter emphasizes prioritization based on the Reach, Impact, Confidence, and Effort involved in each option.

    In your specific situation, I'd start by outlining a list of user stories and then using one of the frameworks above to compare build vs. buy solutions.

    433 Views
    1 request