analytics dashboard tooling project @ hive technology

what is a product manager?

As a product manager, my role is similar to that of a strategy consultant, with a strong focus on both the technical and strategic aspects of product development. I work with cross-functional teams to deal with ambiguity, define problems, and test hypotheses, ensuring that we build the right solutions. I collaborate closely with engineers to oversee the "how," diving into technical details, system architecture, and integrations, while also managing stakeholder expectations and keeping the broader business goals in mind.

what is hive?

Hive is a project management software, similar to Asana or ClickUp, that helps companies track projects across teams, allocate resources, and manage budgets. A key factor in choosing the right project management software is the strength of its analytics capabilities. To meet this need, the product and analytics teams at Hive collaborated to revamp the platform's analytics tools, and I took on the role of a technical product manager to lead this effort.

what were the goals?

Previously, I was building out highly specific dashboards for clients who wanted analytics. The goal was to make our analytics offerings:

• Scalable, by offloading work from one individual to an entire team of product managers, designers, and engineers by moving the analytics process directly in-app.
• Cost-efficient, by removing third-party tools associated with the previous data pipeline and BI tool.
• Flexible, by allowing users to change what their dashboards consist of as their project needs develop and change.
• Time-efficient, by allowing users to create their own dashboards in a few clicks, rather than waiting 30 days for a Hive-built custom analytics dashboard.

who was the target audience?

The target audiences I had in mind while developing the prototype and main workflow of the tooling were executives, data analysts, and project managers. The goal was to create a product that was easy to navigate for executive leadership while still being robust and in-depth enough for analysts and project managers.

what did your day to day look like?

My overall work process:

• Defined essential features for the minimum viable product (MVP) based on user needs.
• Created an initial design using Figma to visualize the user interface and workflow.
• Developed an Epic product scope to outline the overall goals and objectives.
• Divided the project into smaller areas (e.g., Data Fields, Chart Types, UX/UI) and created specific user stories for each feature.
• Documented detailed user stories and product cards for features, ensuring full clarity on functionality to avoid any snags further down the line with designers and engineers.
• Provided guidance to the lead engineer during daily standups, addressing any ambiguities or concerns.
• Maintained daily notes on progress and updated stakeholders and key customers regularly.
• Engaged with customers to gather feedback and ensure the product met their needs.
• Shared updates with teams like customer success, sales, and marketing to ensure alignment.
• Helped transition from the previous analytics process to the new tooling, ensuring a smooth handover.

what did you learn?

Some key takeaways from this project:

• I found it important to advocate for users even when they are not in the meeting room.
• I found it important to consider multiple perspectives and use that insight to develop the most "win-win" solution possible.
• Clear written communication on product feature cards is crucial, and I quickly set a high standard for myself in this area. Without it, teams can end up spending unnecessary time in meetings to clarify details that should have been clear from the start. While exceptions exist, particularly in highly technical work, striving for clarity in communication is a non-negotiable workplace skill.
• I found it essential to communicate progress and any roadblocks daily to all relevant parties, especially during transition projects. In a startup, even one day's work can make a significant impact, so it's important to keep stakeholders informed—not only during daily standups but also as soon as features enter the Beta phase.

where can i read more about this?

You can read more about this project from the official website found here.

← back