Bot-It

Case study

Freelance

A bit of background information

Bot-It is a task builder and automator that allows users to create "Bots" to run tasks you assigned.

When my client first approached me with this idea he had for an automation type of product, I was instantly intrigued. He told me stories of his colleagues dreading having to clock-in for work, clock-out for lunch and so forth.

Exploration

Once this project was kicked off, I started it off by asking a list of questions.

  • What's the scope of the project?
  • What's the primary function of the product? What's the secondary?
  • Who are the primary users?
  • How do you imagine users interact with the product?

Asking the right questions early on will greatly pay off later on.

After several discussions with my client, I determined the scope of the project was small. The product focuses on three main features; creating tasks, running tasks, and returning the results.

During research, we determined the primary function most users will interact with is running tasks. We expect most accoutns will only have a single bot. This means the secondary function would be creating tasks.

My next step was to write out user stories based off of his examples and others found through research. I combined them into one universal user story that exemplified the rest.

I then defined the user journey through a rough flow diagram. I highlighted 4 key points in the user flow; onboarding, entering a URL, building a task and the user dashboard.

Getting started

I started mapping out the user journey roughly on pen and paper to get started.

Then I transfered my sketches onto a low fidelity wireframes to better describe interaction points and understand the main steps performed by the user.

I worked continuously with the client to reiterate the designs based off of feedback given after every cycle.

Design execution

Once the blueprint was solidified, I started to draft the look and feel of the final product. After several rounds of color and component testing, we eventually agreed on a decision.

Simple symbol library

Reflection

My role in this project was complete at this point. Both the client and I feel confident with the direction this is taking. I was able to include the feature needs within the scope given.

There were several nice-to-have features that were considered, such as GPS location triggers, but was ultimately decided to be put-off for a later development stage.