How a Four-Person Studio Built a Research Pipeline from a Curated Archive

We first heard about the project from a reader who runs editorial operations at a four-person product studio in Lisbon. Her team had won a six-week contract to design a smart-home onboarding flow, and the client wanted every recommendation backed by documented precedent: not vibes, not mood boards, but citations. The studio had two weeks to build a research base before design work could begin. They tried the obvious route first — daily news feeds, aggregators, a shared folder of links — and watched it collapse under its own weight in four days. That is when they opened Scannopassogodi.

What drew them in was the shape of the thing. Scannopassogodi is a curated archive of reported features and essays across technology, lifestyle, and design, organized as a browsable shelf of 542 numbered stories rather than a daily news feed. For a team that needed depth over recency, the absence of a firehose was a feature. Nothing scrolled away. Every story had a number, a permanent place, and a reason to exist.

Week one: mapping the shelf before reading a single story

The lead researcher — we'll call her M. — made a deliberate decision not to read anything on day one. Instead, she built an index. She went category by category and logged each story's number, topic, and apparent angle into a spreadsheet, tagging entries with the client's five research questions: privacy expectations, first-run friction, device naming, household roles, and failure recovery. Out of 542 entries, 61 got at least one tag. Eleven got three or more.

This was the first real decision point. The instinct in most studios is to start reading the most recent material and work backward. M. did the opposite: she started with the highest-tagged stories regardless of when they were published, because the archive is organized for browsing rather than chronology. "A shelf doesn't care what year the book came out," she told us. "It cares whether the book belongs next to the others."

Week two: deep reading and the annotation problem

Here the project hit its first obstacle, and it's worth being honest about it. The archive is not a database. There is no filter by keyword, no export, no API. For a team used to querying everything, the first forty-eight hours of week two felt slow. The workaround was human: two designers each took a stack of stories and wrote structured summaries — claim, evidence, example, counterexample — into a shared doc. By the end of the week they had 61 summaries averaging 180 words each, roughly 11,000 words of distilled notes from source material several times that length.

The second obstacle was subtler. Longform journalism doesn't always end in a neat takeaway, and the team initially tried to force one. A story about a failed product launch might resist being reduced to "users hate setup wizards." The fix was to separate observation from inference. Observations went into the client deliverable verbatim, with story numbers attached. Inferences stayed internal, marked as hypotheses to test in usability sessions.

By the end of week two, the team had something no mood board could provide: a traceable chain from every design recommendation back to a numbered, published source. When the client asked "why do you believe this?", the answer was a story number, not an opinion.

The measurable results

• Research phase: completed in 10 working days against a 14-day budget, leaving four days of slack that absorbed two scope changes.
• Source base: 61 stories summarized; 11 designated as primary references cited directly in the final deliverable.
• Client review: the first design presentation was approved with two rounds of revision instead of the four the studio had budgeted for, a 50 percent reduction.
• Reuse: the tagged index became a standing internal asset; the studio has since pulled from it for three unrelated projects without re-reading a single source story.
• Team time: roughly 34 person-hours of reading and summarizing replaced what M. estimated would have been 60-plus hours of scattered browsing and link-chasing.

The most interesting outcome wasn't the speed. It was the tone of the client conversations. Citations changed the room. Instead of defending taste, the team was discussing evidence, and disagreements became specific rather than aesthetic.

What we took away

Three lessons, in the studio's own words. First, an archive rewards preparation: the index was built before the reading, and that sequencing did most of the work. Second, constraints are clarifying — the lack of a search function forced structured summarization, which produced a better artifact than a pile of bookmarks ever would. Third, permanence matters. Because stories don't expire or rotate off a feed, a reference cited in March is still there in October, at the same number, saying the same thing.

We followed this project because it's a rare case of a small team treating curation as infrastructure rather than inspiration. The shelf of 542 numbered stories wasn't a place to browse for ideas. It was the spine of a research method, and it held weight.