Recently, I gave a presentation to a group of 100 designers on how to get started in writing and keep it up.
In this presentation, I shared my stories – why I started writing, some tips on what to write, how to write it, where to publish, as well as how writing can help with them to become better communicators at work.
My audience was Chinese designers in North America, so I delivered the presentation in Chinese. The slides were in English though. Check out the recording.
A very interesting framework on the four methods of decision making learned from my manager Carlo based on the book Crucial Conversations.
Here’s a presentation I gave to my coworkers in a brown bag session. It’s a while ago, but still holds true. My goal was to help all of us better understand accessibility, its impact for users as well as how we could better build our software for users who have disabilities.
Behzod shared a 4-step research framework on how to decide on what/how to research: DECISION -> EVIDENCE -> DATA -> APPROACH.
As designers, our intuition and judgement take a big part when it comes to evaluating our own design ideas.
Sometimes, I kill ideas when they’re still in my head.
The problem with that is several fold.
How to expand your design explorations? How not to explore just “safe” design options?
Trained academically as a computer science student, I was used to/still sometimes evaluate feasibility too early. When a solution appears, my mind starts asking “is this feasible” very quickly. That’s the downside of having an engineering mindset: you may run “feasibility evaluations” for your design solutions your head too early, rather than putting all the solution options onto the table, and waiting for your engineering partners’ expertise. This resulted in eliminating certain solutions prematurely. When you care about “what is feasible” too much too early, you stop going an extra mile to add a level of star experience for your users.
Waiting in a line at DMV. Enjoying an exciting concert. Working on a project with a tight deadline. People perceive time differently in various situations. How would a bit front-end engineering effort make a difference in people’s perception on applications?
I have some learnings from Eli Fitch’s excellent presentation “Perceived Performance”. The quality of presentation is as amazing as the content.
Simplicity is about subtracting the obvious, and adding the meaningful. — John Maeda
“Not everything that matters can be measured, and not everything that is measured matters.”