Making products worth making

In a badly designed book, the letters mill and stand like starving horses in a field… In a well-made book… the letters are alive. They dance in their seats. Sometimes they rise and dance in the margins and aisles. (Robert Bringhurst, The Elements of Style)

I’ve been enjoying a slow crawl through Robert Bringhurst’s The Elements of Typographic Style. The book has both the poet’s charming ability to turn a phrase and an engaging continuous theme of what Brian Zmijewski terms progressive design.  In Elements, Bringhurst states the goal of typographic design is to represent written content accessibly and accurately1.  The principal tactic to achieve this goal is by designing from the “content out”:

Read the text before designing it… Discover the outer logic of the typography in the inner logic of the text.

In other words, Bringhurst argues that to make something well, you must first understand its core meaning, purpose and character (aka. “the text”). Only after this first step is taken should considerations like fonts, margins, and layout, come into consideration.

This is sage advice for any typographer; I think it applies to business too. Thousands of people make millions of new products every year. Staff are hired, plans drafted, monies spent and then most of these products fail.

So how does a company avoid making products that are not worth making at all? Budget excuses aside, a common element of unsuccessful products (and startups) is that they fail to deliver significant value to customers.  This is a good place to start! To illustrate the point of value, let me replace a few of Bringhurst’s wise words with my own:

Understand the customer before designing a solution… Discover the outer logic of the product in the inner logic of the customer.

“Reading the text” when creating a product, then, is the process by which we can better understand the inner logic of the customer,2 that is, to anticipate their wants and needs. Here are a few questions I’ve found useful:

  • What are some important motivations for the person(s) involved?
  • What job is the product being hired to do by each person involved?
  • What actions allow us to validate that the product/idea is significant3 in addressing those motivations with a minimum of effort?

In my experience if an entrepreneur addresses each of these questions, the processes of drafting a new product, a pitch, a startup company strategy, or a marketing campaign becomes much less challenging.

Ultimately we make products for other people. When we work directly, honestly and sympathetically to help others achieve their motivations, we’re more likely to create a product that, like a well-designed book, feels meaningful and alive.  These are the products that are worth making.  As Jason Fried of 37 Signals has put it:

“Here’s what our product can do” and “Here’s what you can do with our product” sound similar, but they are completely different approaches.

1. Bringhurst’s Elements tells us that the purpose of typography is “to honour and elucidate the character of the text”.

2. By “customer” I mean anyone who decides on an investment of time, effort or money.

3. A good way to measure the significance (value) of a product to a customer is by determining how much they will pay (to make it, to buy it, to rent it, to keep it, etc.)

The photo is of Jitterbug dancers in NYC by Alan Fisher in 1938. The dance was controversial in multiple contexts. Events featuring the Jitterbug filled seats and dance floors (and sometimes the aisles too). The coloration is anachronistic and entirely my fault.

Strategy, tactics and diversity

I’ve started off 2015 thinking about the interplay of strategy, tactics and diversity in new business efforts. This quotation from Sun Tzu’s The Art of War has been stuck in my head:

Strategy without tactics is the slowest route to victory. Tactics without strategy is the noise before defeat.

Breaking this passage down, I’ll define tactics here as “doing things right” (management) and strategy as “doing the right things” (leadership).

In my experience new companies prioritize questions of strategy (what will we do?) and not tactical execution (how will we do it well?).  I think the focus on strategy over execution is a mistake and I agree with Mike Roach’s sentiment:

Strategy without execution is hallucination.

In my experience:

  • Planning to do things is easy
  • Doing things well is difficult
  • Doing new things well is more difficult
  • Groups of people doing new things well is even more difficult
  • New groups of people doing new things well is almost impossible

So the question remains: How does a new team (a startup) doing something new (an innovation) learn to execute well?  Here are a few informal principles I’ve identified:

1. Plan to learn from failure

We all make mistakes when trying something new, we should keep in mind that failure can be an invaluable instructor.  The privilege to make mistakes, learn and improve should inform (not detract from) timelines, product schedules and project leadership.

This means giving people the opportunity to fail at achieving a goal and allowing them to try again (but differently!). I’ve come to prefer this approach of “fail, learn and re-try” over one of the popular alternatives: hire ambitious recent MBA from established company internship and/or well-branded school with a specialization in X.

2. Encourage critical team reviews

I’ve witnessed (and delivered) some truly terrible investment pitches, product launches and marketing efforts.  Usually the story goes something like this:

  1. A person or team ignores or does not engage with diverse critical feedback
  2. Wider examination reveals an important flaw and a pitch / product / company fails

When we ignore critical examination by others it becomes more likely that what we don’t know, in fact, will hurt us.  Giving priority to early, constructive and critical reviews from different people with different skills and viewpoints helps us to:

  • Identify risks early (when we are best able to change things)
  • Reduce overconfidence and over-planning
  • Better prepare to deal with dissenting viewpoints
  • Distinguish strategic errors from tactical problems when they do occur (“was our product wrong for the market or did we market it wrong?”)

We don’t know what we don’t know but we can ask. So how do we ensure that we’re asking the right people?  This brings me to the third principle:

3.  Encourage significant diversity

A significant number of business studies have concluded that groups that look more alike, act more alike, and think more alike are less likely to succeed in innovative contexts.  Why?  In the words of Scientific American editor Fred Guterl (summarizing the research findings of Katherine W. Phillips, Vice Dean of Columbia Business School):

When we have to work with people who are not like ourselves, we tend to prepare more thoroughly and work harder to marshal our arguments, and we do better work as a result.

Significant diversity prevents the assumption that team members, investors or customers will perceive things the same way you do.  It is important to remember:

  • When we make assumptions, we guess
  • When we examine our ideas, products, and methods, we still guess but we make better, more educated guesses

In this way, diversity* better prepares “new people doing new things” for the unorthodox, always-changing and impermanent world, which, in our corner, is the business market.

Final thoughts

So “how does a team without much experience in a given area learn to execute well?” My short answer:

  • By planning to learn from failure
  • By encouraging critical team reviews
  • By encouraging significant diversity

* I define diversity broadly here as a condition in which any person will not assume that another person shares their perspective.  

The painting in the header of this post is by the artist Au Ho-Nien. His work acknowledges arts from many periods of historic China including the ink wash styles of the Song Dynasty. Sun Tzu has been required reading for military strategists since at least the Song, so a match with the topic of this article felt appropriate. The subject of the painting reminds me a popular idiom about birds which isn’t entirely true.

Three UX Lessons: What I learned by making mistakes

While there may be some technical accuracy to the claim that “all the startup advice you read is wrong” my personal experience is that the mistakes I’ve made are pretty common in startup land.

I created this slide deck for Startup Drinks Hamilton. The event encourages speakers with “validated experience” (a history of making mistakes and learning from them) and that’s why I’d encourage anyone considering a new venture to attend.

LICEcap: The GIF screen recorder with a terrible name

As HTML5 and responsive patterns mature the relevance of motion in user interface design increases as well. However, when an application uses motion to communicate, static screenshots may fail to demonstrate how an interface works to clients or team members.

To that end I’ve been using LICEcap, a simple and lightweight screen recorder that renders a GIF “video” on save.  The program is cross platform, free, and made by a company with a trend toward inexplicable naming choices.

One more use: bug reports.

The LiON’S Lair: Startup trial and error

Weever Apps won the inaugural “LiON’S LAIR” competition in 2011!  The Hamilton competition offers $160,000+ in prizes and is inspired by “Dragon’s Den” (known better as “Shark Tank” in the U.S.).  I had the opportunity to provide a guest post  on the Lion’s Lair site and I’ve republished it here as it may be useful to other startup ventures.


At the LiON’S LAIR awards gala, audience focus is understandably on the entrepreneurial “elevator pitch”—those precious minutes where a visionary outlines how their product will solve a problem and become the basis of a successful new business in Hamilton (and beyond). The stakes for the competing entrepreneurs are significant: the $160,000+ in cash and in-kind services for winners guarantee a chance at making it big.

Not seen in the excitement and pageantry of the award night, however, are the weeks (and months!) of hard work put in by each competing team as they adjust their business plan, product, and pitch in response to the critical reviews by volunteer LiON’S LAIR mentors. Each mentor is a successful, experienced business person in their own right. And this is where the competition really shines—it provides contestants the opportunity to learn from the mistakes of those entrepreneurs who have gone before them. LiON’S LAIR uniquely provides contestants the opportunity to make business errors on paper instead of in practice.

The process of trial and error is so critical to new business development in Hamilton because, as a startup, you will get it wrong.

Don’t feel bad though! Almost every startup “gets it wrong” on some level… and we did too. Early in Weever Apps history, we thought we had it all figured out—an optimistic opinion that was corrected early and often as we prepared our pitch for the inaugural LiON’S LAIR competition of 2011. After weeks of intensive practicing, we had one critical breakthrough, and, to our surprise, it was a rather simple one: focus less on what we were excited about (our product) and more on our team’s ability to cope with mistakes successfully (because there will be tough times that need to be overcome through strategy and solid organization).

So while Weever Apps brought all of our (necessary) enthusiasm to LiON’S LAIR, we also brought in a honed pitch (from all those mentoring sessions) to emphasize the diversity and commitment of our team as a whole. Our new pitch won LiON’S LAIR but, just as importantly, it helped us to survive in those first two years as we inevitably “got it wrong” and had to quickly refocus our business on providing companies with actionable mobile data from the field.

Today, Weever Apps is a thriving company and we’re thrilled to be a sponsor of this year’s LiON’S LAIR. Our journey from being a few entrepreneurs with a “big idea” to part of a growing workplace that strives to offer real benefits to the city demonstrates anything is possible in Hamilton. LiON’S LAIR is not just about the money—it’s about learning how to fail…and how to get back up stronger than before. We wish the contestants the best of luck and look forward to seeing you on October 2nd.

Full-width images inside a padded container

Sometimes the most simple CSS layout rules are the most challenging.

I recently needed to make an image inside a padded container full-width.  Easy enough, right?  Just wrap the image in a div with negative margins equal to the padding.  Gawker sites like Jezebel do a lovely job of this by adding a “fullwidth-for-small” CSS class which triggers on smaller screens.

See the Pen emzQoM by Andrew J. Holden (@holdencreative) on CodePen.

But what if you don’t have access to modify the HTML? After some trial and error I created a solution using CSS3’s calc and vw properties.

See the Pen raLoyQ by Andrew J. Holden (@holdencreative) on CodePen.

The CSS calc() and viewport properties certainly present some interesting opportunities for cases where hacks using position:absolute would have been the only recourse in the past.   This method isn’t exactly elegant, but it works, and I’m sure it could be improved.