Cubyts 2.0: A Product Observability Platform

Currently, in agile development, product managers look into all aspects, from business requirements to design, development, quality, deployment, analytics as well as feedback on the deployed feature. And different tools are used during this process (Google Suite, Figma, Jira, GitHub, Freshdesk and more). While externally, they have visibility on how a feature is doing, internally its difficult to track operational/executional inefficiencies. These can be unclear requirements, low design quality, bad code and more. Today, PMs get feedback after the feature is deployed, and then have to backtrack and figure out what went wrong.

The goal is to build a centralized location for product teams to integrate all tools used in their product lifecycle. This will provide visibility into potential risks at various stages of product development, along with recommendations for workflow improvements and efficiency fixes. Risks could include unaddressed feedback, existing or potential delays, low design quality, or deployment delays. Early alerts regarding these issues will allow product managers to take corrective measures promptly.

Cubyts' product observability platform targets product managers and chief product officers in tech-focused companies who oversee the product lifecycle and rely on data for decision-making. It also caters to those involved in product development such as engineers and QA professionals, facilitating workflow, risk identification, and performance optimization. Ultimately, Cubyts is for those committed to creating market-ready products that satisfy customers and spur business growth.

The home screen shows a list of gaps identified from tools that a user has integrated with. Each gap has contextual actions that the user can take to mitigate it. Users can also search, filter and perform multi select actions on the gaps. Integration with more tools results in more gaps being unearthed.

Based on integrations, Cubyts would also auto create a repository maintaining the hierarchy from the tools. That along with an intelligent search makes it easy for users to access all their documents in a single location. Users can also configure custom folders and select specific sources from their preferred tools. For example, a Payments team might want to create a Collection with only the Payments related files from Figma, Github and GoogleDrive.

Users can integrate their product lifecycle tools with our system. Once integrated, they can configure boundary conditions for certain tools, allowing them to focus on specific scopes. For instance, leaders may not be interested in some exploratory projects running on Jira. By deselecting these projects, our system will only display gaps relevant to business-critical projects.

The design for this product involved creating components in both light and dark mode. For this we adopted Figma variables to be able to easily switch between different modes. By defining separate variables for both modes, we were able to keep design effort to a single mode. The same mechanism was adopted while defining tokens in development.