New Notes Features

In version 2.3, notes for Scorecard object can now be added to a dashboard. Not only can the notes be viewed on the dashboard, but you can also add, edit, delete, and reply to notes without leaving the dashboard or Briefing Book slide. All updates to notes update automatically throughout the application. What a great way to communicate without having to search!

Another new version 2.3 addition is the ability to require notes when a score is too low. For example, you would require a note if you are over budget. By requiting an explanation for poor performance, you can always know what’s going on behind the red score.

New Dashboard Bubble Types

We are excited that Version 2.3 offers additional Dashboard bubble links! You can now quickly link to all kinds of things right from your dashboards, including reports, other dashboards, briefing books, strategic initiatives, documents and scorecards. We know all bubbles are not the same, therefore you can change the shape, size, font size and placement of the bubble links too.

Spider Strategies vs. Business Intelligence

One of the most commonly asked questions during our sales process is the difference between our software and Business Intelligence (BI) software. Here’s an answer I wrote up for a customer that I thought would be worth sharing. There are two main differences:

1) Data Structure.

Traditional BI software takes your data that’s in just about any format and allow you to slice and dice it in just about any way you want. It’s a lot like Excel, actually. You can put whatever data you want in different columns, and then create charts and graphs based on that data. Then, when you have the charts and graphs you like, you can add them to dashboards.

We’re Scorecard/KPI software, and we require a specific kind of data. Our software is all about choosing what you want to measure, setting goals, and then measuring it on a regular basis. You can chose to measure workplace injuries monthly and the software is going to want to know how many injuries there were every month. If you don’t have your metric values updated via automatic database feed, the software is going to annoy you with emails every month if you forget to update your metric values. When you do update the values, it’s going to give each metric a color rating and a 0-10 score based on whether you met your goals or not.

The disadvantage to our approach is that it only works with things you measure over and over at regular intervals.

The advantages, though, are huge. Once you assume the data is going to be in a specific format, you can do all kinds of things to make the software more powerful and easier to use. You can quickly view your weekly data in quarterly aggregations or go back in time to see how things looked last year. You can quickly compare the performance of different parts of your organization, even though they don’t measure the same things. You can even add Facebook-style comments to different metrics. You can ask why no products shipped last week and the shift manager can reply that there was a scheduled machine upgrade. Requiring regularly updated data means our software can be more of an interactive experience.

Both software packages create charts, graphs, etc., and then let you analyze the data in dashboards and reports. The fundamental difference between us and them, however, is we only track performance metrics and BI software is much more open ended. If you’re looking for software to track the performance of an organization, you’re not going to find something much better than our stuff. If, however, you’re looking for a tool to visualize a wide variety of data, we’re not really the best candidate for the job.

2) Web-based.

The second major difference between us and BI is that we’re 100% web based. Everything we do is through a web browser talking to a web server. We don’t require any plugins or special browsers or anything.

Most BI software is desktop software that you install on a PC. Yes, there’s a central server that can store things, but building the charts, reports, and dashboards requires that fat desktop client. Then, when you get things the way you like them, you can publish stuff to the web. This published version is an interactive online snapshot of the data on your desktop. Unfortunately, when it’s time to update your online data, you need to load the desktop client, pull in the new data, and republish everything to the web.

With our software there’s no such thing as publishing. I’m sure I don’t need to explain to you all of the advantages of web based software, but with our stuff as soon as you update a metric value online, all of your reports, dashboards, etc. throughout the system are updated right away.

CSS Sprites

We’re always exploring ways to make our software run faster, and in Scoreboard 2.3 we’ve been able to improve performance in some interesting ways. This post should give you a little peek behind the scenes into some of the tricks we’re using.

Like most websites, we use images throughout our application. Here’s an example of an up-arrow image next to some text.

In order to display this, your web browser gets all of the text on the page at once, and then asks the server for the images one at a time.  This works great for many situations, but sometimes there are thousands of icons on a single screen.  That means that your web browser has to have thousands of “conversations” with the server each time you display one of those screens!

In Scoreboard 2.3 we have a different approach, and it’s dramatically improving performance.

The idea is to combine every single icon in the application into one huge image.  Here’s an abridged example with only 10 icons included.

When you first log in, your browser downloads this big image and remembers it.  Then, every time it needs to display an icon, it shows only a little piece of the big image.  It’s like you’re looking at the big image through a tiny window and you can only see a small piece of it.

The advantages of this approach are huge.  There’s only one image to load, which means that your browser no longer needs to have all of those “conversations” with the server.  The end result is a software experience that just feels faster.