Imagine this scenario: you want to build a new house, so you hire two people: an architect to design the structure and all the plumbing and wiring and the like, and an interior designer to come up with the various features of the rooms, the lighting, the colors, the decor. Six months later, they each hand over their plans...but they haven’t actually spoken to each other the entire time. If you hand those two sets of plans over to a contractor, how likely do you think your house is to be built effectively and efficiently?
Victoria Blake's Blog
I’m used to thinking of ergonomics in terms of chairs, desks, physical plant, tennis rackets, etc., but this week our expert UX designer, Cami, blew my mind when she shared a “natural thumb extension” image that she uses to help design for mobile.
“What’s this?” I asked
“The green zone is where the controls should be,” she replied.
“Ohhhh,” I said. “Ahhhh….”
Once we get past POC and MVP, we need to start thinking about the entirety of the product we’re building. Here are four features that our clients commonly overlook, but, like the parts of an iceberg supporting the surface, are needed to support the whole.
We just completed a huge, deep, complex, and super sexy Discovery for a client I can’t name. But I can say that the timing was tight, the expectations were high, the info going in was murky, and the result at the end was, as our VP of Engineering likes to say, “baller level ten.”
My kid is a year and a half old. She is accumulating language at a startling rate. A few weeks ago, she started saying “no.” No has quickly become her favorite word. She uses it to mean everything from “I’d prefer to have sugar, please,” to “get that toothbrush away from me.” Sometimes she really means no, but when she really really means it, she doesn’t say the word. She behaves no by turning her head, or, worse, swatting the offending thing away.
My husband and I are involved in a never-ending construction project that takes us to wonderful Portland businesses solely in search of odd things. A few months ago, we went to the stone yard. At one end of the stone yard were the boulders. They were big. Big enough that it was hard for me to conceive of anybody buying a boulder, because where would they put it? Other stones were arranged in progressively smaller sizes, from boulder down to dust. Which got me thinking about sizing, and about software.