A HUB obsession: Simplicity

I wanted to take a quick break from development (yes I still write a good deal of the Shugo code) and share something we’re completely obsessed with in building HUB: Simplicity!

In everything we do in HUB, we keep asking ourselves: Is this simple enough for someone to use?  Is there a better and more intuitive way to lead a user down a specific path? Sometimes our search for simplicity takes a bit longer, but in the end it will pay off. The product will be able to support more users with less support — since it’s easy to use!

An example — the Mulligan process

I though providing an example of something we’ve incorporated into HUB would prove our point on simplicity. We all know that sometimes employees will forget to clock in or out on a given day. What happens then?  Typically communication needs to occur between the employee and their manager that they forgot to clock and the manager needs to resolve it manually.

We thought — isn’t there a simpler way to do this? Why not have the employee request a “mulligan“, kind-of of “oops, I messed up but this is what it should’ve been”?

Let’s see this in an scenario: Employee Paul comes into the office at 9 am and goes to HUB to clock in.  Paul notices that he forgot to clock out last night when he left!

What’s he to do? Well, just ask for a mulligan!

Clock Out Mulligan


Once Paul asks for the mulligan, he fills out information to help his manager quickly resolve his mistake.

Clock Out Mulligan - Callout

He simply identifies when he should’ve been clocked out, can add a message that will be sent to his manager and even choose to clock in now when he submits his mulligan request!  We even provide some example messages Paul can use to fill in #2, again trying to make it simple and easy (if you can think of some more example messages, send them our way).

Clock Out Mulligan - Callout Examples


So what happens once the request is submitted?

  1. Paul’s manager is emailed that a mulligan request was made by Paul
  2. The manager clicks on the link within the email and is directed to either approve the request as is or modify it (see below for how that screen will look)
  3. Once approved, Paul is notified via email that his request is complete

Clock Out Mulligan - Approval

So what do you think? Is that simple or can it be simplified even more?



Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s