Introducing Saved Views: Tailored Data for Every Role

One of the things we’ve learned in working with hundreds of Beam users is that each stakeholder within an organization often requires their own dedicated view of the data. While individual stakeholders may all need to work with assets, reservations and tickets, the data that each stakeholder and role needs to complete their job is often different.  An operations executive needs to understand data about utilization, uptime, and performance metrics about the assets they own, while an IT executive needs to ensure that all of those same assets adhere to compliance and security standards. Traditionally, these two roles will maintain their own sheets, systems and communication channels to track information about the same exact thing, in this case an asset. Over time this leads to entropy, disconnected data, and ultimately difficulty in creating meaningful insights from the data that teams are generating.

‍

At Beam, we saw the long term inefficiencies that this approach was causing to enterprise organizations and how it reduced the ROI these organizations were gaining from their fixed assets and other critical resources. We first built a fully customizable platform that allowed for unlimited custom fields for every entity type, so that the right data could be associated with the right entities. This allowed each stakeholder to define the data they needed to know about the respective entity so that all the right information lived in one place, connected to the right thing. To further this initiative, we also developed configurable table, calendar and grouped views so that individual stakeholders could set up their own data views and modify them without affecting other users. We then furthered this initiative by allowing data across entities to be displayed within a single view. This flexibility was quickly adopted by organizations to solve many different problems and complete hundreds of various jobs across various roles within their organization. 

‍

As the use cases and applications of Beam grew across these organizations we started to see that even within a single role configurable views alone was not enough. Individual roles are very often tasked with completing many jobs that each require their own view of a mixed set of data. While we could have created many fixed views as most platforms do, we instead saw that to deliver the most value to our users we would need to do the extra work to provide a high-level of flexibility. 

‍

The result of this discovery has been the development and now the launch of Saved Views. Each user in Beam will now have the opportunity to save their custom column configurations, filters and data across multiple entities into one or multiple saved views, providing greater control over the data they need to see to complete the job at hand. We are thankful for the many Beam users who helped drive this feature forward and we look forward to the new problems this will help solve for all Beam users.

‍