Product Owner - Dynamics 365

Product Owner - Dynamics 365

Primary Purpose The Dynamics 365 Product Owner is responsible for the overall health, effectiveness, and continuous improvement of ChemPoint's customer engagement platform. Working within product strategy established by the Product Manager, this role partners with sales, customer service, operations, and technology teams to optimize account management, lead/opportunity management, customer support, and other core business processes supported by Dynamics 365. The Product Owner translates business objectives into scalable product capabilities, manages the product backlog, and drives enhancements from concept through adoption. This role balances new functionality with platform stability, usability, data quality, and long-term sustainability to ensure technology investments improve business performance, user productivity, and customer experience.

What You'll Do

• Maintain understanding of product capabilities, dependencies, risks, limitations, and improvement opportunities.
• Analyze product usage, user feedback, and vendor roadmaps to inform recommendations.
• Recommend technical debt remediation and product sustainability improvements.
• Balance enhancement opportunities with platform stability, maintainability, and supportability.
• Partner with stakeholders to understand business needs, challenges, constraints, and desired outcomes.
• Develop and evaluate solution options, including tradeoffs, risks, dependencies, and expected business impact.
• Define workflows, capabilities, features, and requirements that support approved product objectives.
• Align on recommended solutions and translate them into delivery-ready work.
• Maintain a prioritized product backlog aligned to approved priorities and business objectives.
• Create user stories and acceptance criteria sufficient for development, testing, business validation, and efficient delivery.
• Ensure upcoming work is appropriately scoped, understood, and ready for execution.
• Manage dependencies, risks, assumptions, and decisions impacting delivery.
• Guide initiatives through the softw