Ralph Ammer
Don't think big
An Article by Ralph AmmerOne of the biggest mistakes you can make in your creative project is to pick a topic which is too big. Big topics often lead to small results, small topics foster great results.
And here is why: Your project is limited by the time and energy you have.
These are the boundaries of your project. If you pick a huge topic then there is not much room for your creative efforts. On the other hand, if you pick a small topic you have time and energy to make a great creative contribution.
Is perfection boring?
An Article by Ralph AmmerWe love to see the process, not just the result. The imperfections in your work can be beautiful if they show your struggle for perfection, not a lack of care.
Now I get it
An Article by Ralph AmmerTo design a system means to orchestrate the interplay of its elements.
Such a system is considered “interactive” if it is open, which means that there are ways to engage with the processes that are happening inside of it. There is of course a range of interactivities which spans from very basic reactive behaviour to highly complex conversational interactions.
But what do you want to say?
An Article by Ralph AmmerPablo Picasso famously said:
“The world doesn’t make sense, so why should I paint pictures that do?”
A sensible approach to something that can’t be explained is to express it.
Rather than giving you explanations or “saying something”, most artists are concerned with what I like to call “room for interpretation”. They create platforms that trigger thoughts, feelings, emotions, and ideas.
Instead of trying to explain the inexplicable artists express their view of it. They don’t want to tell you what to think, they invite you to respond.
A lightbulb is not an idea
An Article by Ralph AmmerWith conventional placeholders, such as words, we can describe patterns for a large number of situations. On the other hand it is easy to fool yourself (and others) with words, since you can avoid to be specific. Any business meeting can confirm this.
When you draw something you are forced to be specific — and honest.
Our illustration of an “idea” from above is unconventional in the sense that it conveys specific original thoughts of what an idea is. It adds value to the words.
And that is the catch: The drawing must be unconventional to support the conventional words. We have to make sure not to use “words in disguise”. Take a common illustration for “idea” for example, which haunts flip charts all over the world: the lightbulb.
The lightbulb image works on a purely symbolic level, it only replaces the word “idea”. This image of a household item contains no original thought about what an idea is. While symbols like these work well as international replacements for words or icons to indicate a light switch for instance, they convey no nutritional value as illustrations — they are empty.
The Fidelity Curve
How do we choose which level of fidelity is appropriate for a project?
I think about it like this: The purpose of making sketches and mockups before coding is to gain confidence in what we plan to do. I’m trying to remove risk from the decision to build something by somehow “previewing” it in a cheaper form. There’s a trade-off here. The higher the fidelity of the mockup, the more confidence it gives me. But the longer it takes to create that mockup, the more time I’ve wasted on an intermediate step before building the real thing.
I like to look at that trade-off economically. Each method reduces risk by letting me preview the outcome at lower fidelity, at the cost of time spent on it. The cost/benefit of each type of mockup is going to vary depending on the fidelity of the simulation and the work involved in building the real thing.
Four levels of fidelity
Suppose we have four levels of fidelity…
- Rough sketch (on paper or an iPad)
- Static mock-up (eg. Photoshop or Sketch)
- Interactive mock-up (eg. Framer, InVision)
- Working code prototype (HTML/CSS, iOS views)
Depending on the feature you’re working on, these levels of fidelity take different amounts of time to create. If you plot them in terms of time to build versus confidence gained, you could imagine something like a per-feature fidelity curve.
Time to build versus confidence gained
Take a simple CRUD web UI, where you’re just navigating between screens. It doesn’t take much more time to build the real version than it does to mock it when the design is simple. If you were to build out an interactive mock first, you would end up spending twice as much time in total without gaining much out of it.
Contrast that with a complicated Javascript interaction. Or a native iOS feature that requires programmer time to build out. If it takes substantially more time to build the real code version, then it may be smart to do an interactive mockup first.