A senior candidate walked us through a photo book editor redesign, and the research move that mattered didn't involve a single user. It involved prints, scissors, and her kitchen table.
Midway through a panel interview, a senior candidate told us where the defining insight of a long redesign came from, and it wasn’t the research program. She’d been hired to unify several fragmented editing experiences in a photo book product where a meaningful share of users rated creation “not easy”. She ran the responsible playbook: a survey targeted at the lowest scores, follow-up calls, screen-share sessions, a competitive teardown of every rival product. All of it very useful, but none of it explained the friction.
So she printed a stack of photos from a family birthday and built the book by hand at her kitchen table.
She printed the photos, sorted them, started building the book, and noticed she kept adding and removing images. That step was missing from the product.
The digital flow assumes you pick your photos, arrange them, and finish. The physical act surfaced a whole step the product had no room for: refinement, the constant adding and removing in the middle of making.
That one observation became the redesign’s spine, an image tray built for mid-creation refinement, and the results followed: print rates ran well past projection, the not easy complaints fell, and support tickets fell with them. The orthodox research de-risked the project. One afternoon of making told her what to build.
The shelf
For ICs, the practice travels. Whatever your product helps people make, make one yourself with real materials and real stakes: your own photos, your own claim, your own note. Flowcharts hold the steps you planned. Hands find the steps you missed. The candidate didn’t call it a methodology, which might be the most senior thing about it. She had a question her data couldn’t answer, so she went and made the thing.
The teachable part
When research stalls, make the thing your users make, with real materials and real stakes. Direct contact surfaces the steps your flowcharts skip. One afternoon of making can tell you what a quarter of studying can’t.