

        <h3>&zwj;<strong>What is data product management</strong>?</h3>
        <p>In our experience at Secoda working with many data teams, we've seen most data teams do not have the tools they need
            to succeed. For growing organizations, the data function is usually an afterthought. The first data hire is brought
            on before raising a Series A and is expected to manage the workload that comes afterward with little to no support.
            This means that this first data hire usually spends all of their time answering other people&rsquo;s questions.
            These teams tend to be overworked and are likely to remain a reactive function for the foreseeable future.</p>
        <p>This is because most data teams are understaffed and misunderstood. Instead of reacting to employee data requests,
            working with data requires the data team to treat employees as their customers and their data as the product.</p>
        <p>An organization's data product is its collection of all of its data knowledge, along with the resources used for
            accessing, creating, and analyzing that data. Making the data product more self comprehensive, accessible,
            trustworthy, accurate, and secure should be the goal of the data team and the data team.&nbsp;</p>
        <p>Additionally, the data PM should help direct resources towards the highest leverage areas of the business. When
            products are built with everyone in mind, they usually don&rsquo;t accomplish what they need to for any specific
            subset of users. Data PMs should think about their data products the same way. Building data products for specific
            levels of technical capabilities and specific&nbsp;<em>persona&rsquo;s&nbsp;</em>of data consumers should be the
            goal of the data PM.&nbsp;</p>
        <h3>What makes a good data product manager</h3>
        <p>A good data product manager understands the company ecosystem of people and data. It is crucial to understand the
            different segments of the organization and document the requirements and knowledge from both data producers and
            consumers to generate and manage clean, reliable, and meaningful data. A good data product manager will apply
            product management practices to guide the roadmap for the data team by displaying some of the competencies below:
        </p>
        <ul role="list">
            <li>Conducting employees interviews to understand how they want to use data</li>
            <li>Running data-design sprints (How do we get a minimum version of this product to the employees in the shortest
                amount of time)&nbsp;</li>
            <li>Data product prioritization and road map planning.</li>
            <li>Communicating with the product team and updating the data team on changes that may affect their work.</li>
            <li>Performing vendor assessments.</li>
            <li>Translating business-to-data requirements, and vice versa.</li>
            <li>Defining and tracking key metrics for each stakeholder.</li>
            <li>Sharing knowledge and tracking data product usage metrics.</li>
        </ul>
        <p>We think about data PMs as the bridge between the data team and the rest of the organization. It takes time, tooling,
            and measurement to make sure that all stakeholders can access the right data, but when it&rsquo;s achieved,
            organizations can increase enterprise value by up to 5%.</p>
        <h3>Role requirements</h3>
        <ul role="list">
            <li><strong>Create Data Requirements</strong>&nbsp;&mdash; Data PMs should create clear data product requirements
                that satisfy the preferences of the end-users and data developers they work with. Even though data product
                requirements are still being defined, we like the development, release, and measurement model for building
                useful data products and determining how they are used.&nbsp;</li>
        </ul>
        <ul role="list">
            <li><strong>Employee feedback</strong>&nbsp;&mdash; Data PMs should bring together basic employee insights through
                interviews, understanding department OKR&rsquo;s, taking inbound questions, etc. Based on an explicit set of
                requests from the employees for whom the data product is being developed, they meet their baseline expectations
                (e.g. the employee says a part of the data is broken).</li>
        </ul>
        <ul role="list">
            <li><strong>Data insights</strong>- Data PMs should have a data proficiency where they can look at the data related
                to their data product (very meta) and use that data to make decisions about which products are performing well
                and which should be depreciated. They should have a working knowledge of data languages like SQL and know how to
                use popular tools like dbt, Looker, Metabase, Snowflake, Fivetran, and so on.</li>
        </ul>
        <ul role="list">
            <li><strong>Run Meetings</strong>&nbsp;&mdash; Data PMs should also run effective meetings with the data team and
                advocate for the team's resources to leadership. That includes setting the agenda and tracking action items as
                well as making sure the data team is well staffed and able to contribute to the data product the way that
                employees require.&nbsp;</li>
        </ul>
        <ul role="list">
            <li><strong>Vendor evaluation</strong>&nbsp;&mdash; The data PM should work closely with the engineering, sales, and
                operations teams to understand which products can give their team the best visibility and transparency into the
                data. By evaluating the right tools with other department leads, the data PM can help accelerate their team's
                data literacy and data maturity.&nbsp;</li>
        </ul>
        <h3>Data analytics</h3>
        <p>Think about how difficult it would be for a product manager to manage features without critical information about how
            people are using the product. Today, many data teams are operating in this same way. It&rsquo;s very unclear which
            tables, dashboards, metrics, and charts are used frequently and which should be depreciated. PMs can empower
            themselves and their teams with the information they need to make decisions to improve data products by adopting a
            tool that enables them to measure the most used data knowledge.&nbsp;</p>
        <p>It should be possible for data PMs to see how often teams use data, whether they are using the right data, and
            whether they aren't using any data. By understanding how people use analytics', data PMs can focus on the most
            important tasks that drive data literacy across their company.&nbsp;</p>
        <h3>The future of the Data PM</h3>
        <p>Over the next three to five years, we see the product-management role continuing to evolve toward a deeper focus on
            data as a product. Data product managers of the future will work with the data team to produce high-quality data
            products that can help drive self-service across the organization.&nbsp;</p>
        <p>To communicate data with the rest of the organization, data PM's might choose to implement tools like dbt, Looker,
            and Secoda. As we continue to help data PMs for the organization share their knowledge, we hope to be able to offer
            a greater depth of assistance and support to all employees trying to use data to make decisions. Data interactions
            are becoming increasingly complex, and Secoda hopes to simplify the interaction with data for every employee.</p>

Data Product

Data Product Manager: The role and best practices for beginners

Tags

Top contributor