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.
Software that nobody wants
Finding value is the result of enabling individual and group-level discovery attempts. It's not the result of everyone following one leader's gut.
What just happened is a new software product/feature was created that no customer wanted. This happens way too often. In fact, most hyper important software projects that must be done by date certain or else, have deep flaws that cause some variation of this phenomenon, flaws that include:
- Not wanted - Company specified a solution to a problem that customers don't actually have
- No Rarity - Company is pursuing an iKnockoff of existing products. The market already has two scaled competitors with working solutions, customers naturally spend budget on products that are already successful to avoid risk
- Incorrect Packaging - Customers need a website, but the company created an iOS app instead
- Incorrect Pricing - Customers need SaaS pricing, but the company created a shrink wrapped, on-premise solution with CapEx and maintenance agreements instead
The 'date scrum' anti-pattern
Date Scrum is an R&D pattern where developers are asked to estimate software project requirements upfront for the entirety of the project. After the project is green lighted and the budget is set based on the final estimates, the team then holds daily scrums to status and manage risk as they “iterate” the solution toward the release date. To some, this approach is described as doing Waterfall in sprints.
The fundamental problem with Date Scrum is that the team is de-focused from discovering the best solution. Instead they are heavily focused on delivering Something™ by the Date™. Engineers are problem solvers, and if the primary problem becomes delivering Something™ that will pass QA by the Date™, they will, with enough pressure, solve that exact problem.