Liftlock Studios

About the Calibre Project

Minimalistic web design by game devs | when universes collide


When Grant Padley called ...


I was on my way into the city to teach video game development. Grant and I have been professional colleagues now for a little over a decade; we first met when I was doing freelance, through a bot I had written to scan craigslist ads and send my design CV out with a single line that read, "In response to your craigslist posting". (At that time he needed some help with the Atomic Clock site which was written in php (CodeIgniter))). - Best client that little bot ever found me.

That was a long time ago. Today I'm happy to refer to Grant as good friend as well as a professional colleague. We share values and ethics, and we're both really passionate about our work. Grant is also, (hands down) the most talented producer I know. His work is just the best of the best and his portfolio is absolutely incredible.

Even though we've worked together many times over the last ten or eleven years, doing a small website contract for a company like Calibre Creative would normally have to be a pass for us at Liftlock. We're still in startup mode and really need to keep focused on the video game industry, Calibre Creative isn't directly in alignment with this industry. However, we will use their service in the future for our own marketing needs & Tariq had some availability (he was also a little excited at the idea of a website project to "recharge and re-engage on").

With a talented member of the team willing and able to put the time and care into the project that it would need, we took it on.






Tariq Ramyar

In Good Hands

Tariq Ramyar (Blue Monkey) has been designing and developing websites and video games for half a decade now. Tariq has an interesting and contagious, joyful zen "vibe" that gets woven through the fabric of everything he works on. Never one to turn down an adventure, Like most things, Tariq took this project by the horns and ran with it.

"I love building stuff when everyone on the project is on the ball; so much fun!"

Project Progression

How we got from idea to deliverible on time and budget

One Word ... Communication


Yes! A "good" client can make a difference, we've all heard stories of (or experienced first hand) clients that just frankly don't have their shit together. The same thing can be said for having good processes, or tools, or talent. But it's been my observation that what REALLY makes or breaks a project is the communication. The communication between the studio and the client AND the communication between the talent in the studio itself.

Grant is an amazing client, this is why the only thing that could have prevented us from taking on this gig was the availability of the talent 'in house' to give this project the time and attention it deserved. Grant and Tariq both understand the importance of clear communication. Even though they never needed to communicate directly to each other. That was part of my role on this project. It's important to keep the designers and developers (Tariq had both hats on) focused on their actual work and the iterations of the project (we use a loose scrum methodology), while ensuring that the client is seeing the momentum, getting the content you need and providing feedback along the way.

At Liftlock, we utilize kanban boards in a very straight forward manner. We run shorter projects (like this one) with only four columns. "Backlog" is for all the individual tasks that need to happen and this is the only column that new tasks can be added to. "Sprint" is the tasks that we want to get done in the iteration we're in (the designers or developers choose the duration they want an iteration to be), and once we start an iteration, nothing else gets added to it. "In Progress" can have only one thing per team member in it at a time and helps me (or whoever is wearing the project lead hat on a project), know whats being worked on by whom so that we can keep the conversations intelligent and to the point. And the "Done" column is for things that are ... well, done.

Ideally and in a perfect world, everything would just move forward, obviously thats not what happens and tasks sometimes get shuffled back and forth between "Sprint" and "In Progress". There are even times when something that was slated for an iteration gets bumped down on the priority list because something else thats shown up in the "Backlog" would effect it. We don't hold grudges or point fingers at this stuff, it happens. We try to remain observant of whats left (even outside the current sprint) so that we don't waste time building, designing, coding, or testing something that doesn't need to be done. (which can still happen from time to time).

We also use git, even on small projects that only have a single person working on them. (like this one). It isn't uncommon for Tariq to do 30 or so commits with 25 or so pushes to the repository in a sitting. I don't micro manage the time of the people. I do encourage everyone to try and get 12 "poms" done a day (I'll discuss the Pomodoro Technique below with the technical details), but its a target not a requirement.

Coding Practices

A peek into the technical details of our craft

We follow some pretty solid principals at Liftlock, so its hard to point to just one of them and say "that one! .... that is the one reason for x, y, or z great thing.". If I had to summarize, I would say that taking a wholistic approach to honing our craft, i.e. being pragmatic and looking for things to learn along the way is a big part of it.

Some of our practices seem so simple and obvious to us that we're sometimes taken back when someone mentions them. Like having naming conventions and coding standards documents or using Kanban boards to make all the invisible work visible and help us plan our method of attack. Other things are less obvious and only a lifetime of pain in a development pipeline makes you adopt and adhere to them as 'ideals'.

The Pomodoro Technique is one of those less obvious practices. The goal is to formally work in 25 minute time slots (a pom) and then take a 5 min break. Every fourth pom is followed by a 35 min break. Having a goal of 12 poms a day means that about 6 hours of work got done. But all poms aren't created equally. The benefit in the Pomodoro technique is in the 5 minute breaks. If you take the opportunity to reflect on the work you're doing, you will become more efficient.

Keep your eyes out for other Case Studies like this one, I'll reveal more of the internal details to the thoughts and practices we use at Liftlock Studios.

The Team

Back of House Talent


Sign Up for our Newsletter

Want to be notified when we post more case studies like this?

(We won't ever Spam you, Honest.)


Technology We Used

For all the geeks that are wondering about our tools



  • inVision
  • HTML5
  • CSS3
  • Bootstrap
  • VS Code
  • Safari
  • Firefox (Dev Edition)
  • Chrome
  • Terminal