We’re excited to announce the general availability of dashboard variables in SquaredUp. With this new feature, dashboards you create are flexible and reusable. Instead of hardcoding specific objects within the tiles on a dashboard, you can use variables to create just one dashboard to be reused across all your objects of the same type – be it your pipelines, apps, or microservices. Viewers of the dashboard can then select which objects they are interested in on the fly.

In this blog, I wanted to take a deep-dive into our Notifications feature and explain some of the product design decisions we made. Notifications is one of the most frequently used features of SquaredUp. We designed this feature to be quick and easy to set up, with a primary focus on delivering timely notifications to the appropriate audience.

We're excited to share a small but mighty new feature. Our Text tile now supports Markdown! This allows you to include rich content on your dashboards such as headings, links, lists, images and more. At SquaredUp we know that a useful dashboard is more than just a few charts. With this update you can now provide key context to the data on a dashboard to help tell the right story. For example you might want to: You can easily do all that now, and more.

As a Senior Product Manager here at SquaredUp, I’d like to tell you more about how easy it is to share dashboards with anyone, as well as share some design decisions and explain the feature in more detail.

I first started my career in IT support back in 2003 when VMs where something that was “coming” rather than mainstream, so I had the privilege of witnessing the birth of VMs first hand when my company made the switch from bare metal to VMware GSX running on top of Windows Server 2003.

In previous roles I have been both an Engineering Manager responsible for a team, and a Program Manager responsible for branching strategy and process around CICD pipelines. In both of those roles (but for very different reasons), my product's build quality has been critical to product success. The obvious "why" to this is no builds, no product, but the real why is much more nuanced.

In discussions across the tech and data communities in recent years, a provocative idea has been gaining traction: the notion that dashboards are dead. The first time I came across this was in the article by Taylor Brownlow of the same name, "Dashboards are Dead". A worthwhile read. The article suggests that dashboards, as we known them, no longer serve the needs of modern data-driven organizations. Not through their own fault as such, more through misuse or over-asking.