Just Make It Work

Since beginning a new web app project, I’ve learned a thing or two about product design. I wanted to take a few minutes to share one of the most important lessons I’ve learned: Just Make It Work.

You’ve been there. You have the best intentions to start a new project. Maybe it’s something that is a personal passion. Maybe it’s something that will make your life easier. Maybe it’s something that will get you recognition. Whatever it is, no matter your intentions, there’s always the danger of dropping the ball. I’m sad to admit this has more often than not been the case for myself.

This makes what just happened yesterday that much more exciting to me. I’ve finally finished the first working prototype of my app’s main email module. It’s great to say that. And yet, it’s certainly not what I envision for this product.

While exploring the product architecture of the app, I began to realize the full scope of what I wanted to build. I began to realize this was a much larger product than I initially predicted, and I froze. I couldn’t figure out what to work on first. Meanwhile, it was taking me fifteen minutes to put together a list I could’ve easily typed into the body of an email.

It was during my daily list-making that I got a revelation: build a prototype of the email module that just works. It would need to be something that could grab a JSON file, display it in the browser, allow me to perform CRUD operations on the data, and then save the new JSON file over the old one.

I didn’t worry about aesthetics. It’s not grotesque looking, but it certainly isn’t winning any beauty pageants. I didn’t worry about experience design. There are more rough than smooth edges in this prototype. What I focused on was the exact minimal requirements I needed. The result is a finished product that I can now use to inform the design of my final app.

If you feel like you’re stuck on a project, what’s the absolute bare minimum you need to meet your goal. Build that and use it as a starting place.

Notes from Circles 2014

What I got from the Circles conference:

Design Authenticity

  • Design should be authentic. Every piece of your design should have a purpose.
  • Start with meaning, What is this design supposed to do?; then and only then can you move on to aesthetics.
  • Whether it’s your company’s history, your portfolio, or even a design pitch, the ability to skillfully craft an authentic and compelling narrative is a crucial skill in today’s design industry.


  • If you’re looking for inspiration on a logo or design, start by researching the company’s/subject’s/message’s past. You’d be surprised what might turn up to inform the design.
  • Rephrase what’s being asked of you. Sometimes this helps get rid of self-imposed limitations.
  • Sometimes you need to forget about inspiration and just start.
  • Embrace the awkward first draft. The quicker you accept the awkwardness, the quicker you can move on to finishing and polishing it.

Good to know

  • As creatives, we all have fears and insecurities, no matter how “successful” we may be.
  • Saying no to others’ ideas of you, overcommitting and standing still can be the best thing for your creative career.
  • Three important traits of a designer: Humility, curiosity and willingness.
  • Learning is the only skill that will be relevant your entire life.
  • You have to respect the people you work with and have each other’s back.
  • I should always assume I’m dehydrated (thanks Jessica!).

Have a Purpose Bigger than Yourself

  • What you do is not as important as why you do it.
  • If you design just for the money, you will end up being sorely disappointed.
  • Look for ways to give back. Share resources and knowledge with the design community. Mentor someone. Give your services to a charity that you feel especially connected to.

If you didn’t get to go this year, you can still catch all the greatness on demand on the Circles website. And make sure you sign up for Circles 2015. It’s definitely something you have to experience live!

Lessons Learned: Tina Boone Website Redesign

I’ve written a few times about the process behind building my wife’s website, and to celebrate its official launch, I wanted to share some problems I encountered and lessons I learned throughout this project. I’ve also included a list of resources that were invaluable during this build.

Pattern Lab

I started this one-page site with Pattern Lab because I wanted to establish a style guide driven workflow. Pattern Lab helps implement that approach, but I don’t think it was very efficient for such a small project like this.

In fact, I ended up abandoning the framework about 75% in to the project, which added time and effort. This, admittedly, has more to do with my newness with Pattern Lab than any inadequacies with Pattern Lab itself. I still believe it’s a great tool for responsive design, and I will be using it extensively in the redesign of FDGB. In the end, it was still a great introduction to the workflow.


I tried to stick to the SMACSS way of styling components, and one of the things I found I found myself struggling with was separating style from structure. This is a core fundamental of SMACSS, as well as OOCSS, and following it really helps the organization and scalability of a site’s styles. I think finding these difficulties out right now will help me better structure CSS in future projects.


Going into this project, I knew what AJAX was and why it was so useful, but I really didn’t know anything more than that. I learned that AJAX involves using a JavaScript object called XMLHTTPRequest that, if supported, allows the browser to pass information to and from the server without refreshing the page. Both Treehouse’s AJAX Basics course and Mozilla’s Developer Network were great sources for learning how to evoke an AJAX call.

Plan for Performance

As of this writing, Tina’s site doesn’t perform very well in terms of speed. I will be optimizing images and CSS as I get time, but I would’ve definitely save time and effort if I had simply planned a performance budget from the very beginning. I have to admit, I’m not very experienced in this area, and any attempts at setting a budget would’ve been merely guesswork on my part. I definitely look forward to growing in this area.

Browser Bugs

I knew that no two browsers were quite the same, but I was fascinated by the odd bugs I found in very modern browsers. As of this writing, the latest stable build of Safari has trouble applying a transition to the fill of an SVG anchor element once that link has been visited. The handling of color profiles as well seems to be all over the map, making it a headache to achieve consistent color between browsers. Note the differences in the color between Safari and Chrome:


Comparison of Safari 7 (left) with Chrome 37 (right). There’s a slight difference in the CSS defined background color. It’s much more pronounced on my personal monitor with a custom color profile.

At the end of the day, I realize that it’s not the job of a web developer to achieve total consistency between all browser, but to achieve an acceptable compromise.


I think overall I’m happy with the final results. There are a few tweaks that need to happen, probably the biggest being PNG fallbacks for the SVG elements, as well as a full CSS audit, but I believe the end product is very close to what was designed in the beginning. It’s functional, usable and has a very friendly aesthetic. The lessons learned here have helped me grow as a front end developer and as a designer.

Now, on to the next project!


Pattern Lab
AJAX on Mozilla Developer Network
Brad Frost on Atomic Design
Responsive Design Workflow by Stephen Hay
Google PageSpeed Insights

Where I Falter

“Uses promptos facit.” — Latin, loosely translated, “Practice makes perfect.”

Earlier last week, I read an article about how a scientific study on practice as it relates to talent, conducted by Dr. Gary McPherson and Dr. James Renwick from the University of New South Wales, Australia, debunked the “10,000-Hour” rule. In summary, the study hypothesizes that talent is something that emerges from practice, but only when certain conditions are met. The most interesting condition to me was the final one in the article:

Strong, Direct, Immediate Feedback. Can you sense when you’re making mistakes and when you’re not? Can you use those mistakes to guide you to better performance?

This is one of the hardest things for me to do relating to practice. It’s very easy for me to gloss over my own mistakes, mostly because I don’t realize when I make them.

Recognizing Mistakes

One of my most favorite songs ever is John Mayer’s Why Georgia. Say what you want about John Mayer, he is a guitar acrobat, and this song really shows off his unique finger-picking style. In my admiration for this song, I decided I was going to learn it. That was about three years ago, and I still have yet to master it. It’s not for lack of time spent practicing, either. It’s because I don’t recognize my mistakes.

Essentially, I focus on certain things like chord structure and voicing, then overlook others like fingering trouble spots and incorrect rhythm. I want to understand the music, but I stop just short of mastering it.

The funny thing is I can correct this pretty easily. All I have to do is start recording myself, and all of my mistakes magically come into view. Pretty easy fix, right? My next thought is, How does this relate to me growing in the field of web design and programming?

Showing My Work

I have no idea at the end of the day how I’m making mistakes. I’m not sure I have a holistic enough understanding of the field to help me grow the way I want to. I think this may be where mentors and forums like Stack Overflow can come in real handy. Maybe the code version of recording a practice is to just post your code for experts to see.

To be honest, I’m a bit scared to do that. I have a tendency to keep myself happy by keeping everything I do to myself. Of course, that’s not a way to grow by any means.

When I can get up the courage to have others show me where I falter, I can begin to grow to the level I desire.

And Now for Something Different

It’s been a few months since I began pushing further into the world of designing for the screen, and I have thoroughly enjoyed the change of pace. One of the things I find the most fascinating is the ability to make my own tools. To clarify, building tools isn’t always necessary, but the experience gained in making them is priceless.

Currently, I’m working on an app for my day job. It’s basically a to-do list, but with a few modifications that tailor it specifically to my work environment. When it’s done, it will hopefully streamline the creation of my daily job progress report, nicknamed the Hotsheet. Basically, the Hotsheet is just an HTML email of work project tasks, when they’re due, as well as other bits of information that are important to the progress of a particular job.

The idea to build an app was born out of a persistent problem that bugged me. One day I was entering in project information and realized how much I was repeating myself. The project managers I work with print out production sheets that contain due dates for all major milestones of each project, and I found myself hand-keying each item into an email, finding the due date, and then manually updating the status (e.g., late, need item, etc.).

I’m a fairly careful person, but nobody’s perfect; I would forget to update tasks, projects were missed because they had been added after the latest production sheet, dates changed, etc. Coupled with an outdated and very WET system for tracking each individual project, this presented a great opportunity to simplify and automate.

I read this great 24 Ways article that inspired me to learn Ruby on Rails by digging deep into the trenches. So, that’s what I’m doing. When I’m done, I’ll hopefully have something of value that could possibly help out my print design compadres. Or, at the very least, I will have gained invaluable experience. I’ll keep this blog posted on my progress.