All projects

Service design · Frog Design workshop, MAS SUPSI · 2019

Wanted.Buy

A social commerce service for a design blog: a place where young designers sell the objects the blog writes about. The research told us the readers wouldn't buy there — which became the actual design problem.

Type

Workshop, Designing advanced services

Company

Frog Design

Client

Design Wanted

Team

Michela Burzio, Shiran Hirshberg, Giorgio Ratti

Output

Service blueprint, architecture, hi-fi concept

My role

User interviews, mobile prototype

Wanted.Buy shown on a laptop and a phone: the seller showcase on web and the buyer feed on mobile
Two platforms, two roles: sellers manage a showcase on the web, buyers browse a feed on mobile.

The brief

Design Wanted is a design blog. It writes about objects made by young, mostly unknown designers — and the obvious question is why you can't buy them there.

The brief came as four questions, and they're worth quoting because they set the shape of the whole project:

How can designers turn a project into a brand, and a brand into a business? How is a social commerce different from a website that just redirects you to an online store? Which social features make a sales platform worth visiting? And how do you fold an existing editorial blog into a commerce service without breaking either one?

The four questions of the brief, from the project presentation
The brief, as we received it.

What the research actually said

We ran two studies: ten designers through an online survey, and eight end users in face-to-face interviews. Small samples, and worth reading as directional rather than conclusive.

The supply side was easy. 80% of designers said a new platform to sell through would be welcome. On money they were more careful: 50% would pay a fee only per sale, 30% said it depends, 20% weren't willing at all.

The demand side said no. Asked whether they'd buy inside the blog, 90% said they wouldn't. They used words like risky and not reliable; they said they needed time to compare prices, they needed to trust the seller, they wanted more information before spending.

But the same people said something that pointed the way out: 70% do buy after reading an article that interested them. They trusted the content. What they didn't trust was the transaction.

Research findings on designer habits: promotional channels, selling channels, willingness to pay a fee
Ten designers: how they promote and sell today.
Research findings on end users: where they buy, what motivates them, willingness to buy in the blog
Eight buyers: 90% wouldn't buy in a blog, 70% buy after reading one.

Where those numbers came from

The survey and the interviews were the visible part. Most of the work was contextual: meeting people where they actually shop and read, sitting with them at a table, and getting them to sort and rank things rather than describe them.

I ran the interviews with end users. [DA COMPLETARE: conferma — e aggiungi qui l'altra parte che ti ricordi, i prototipi mobile, precisando se erano i wireframe, le schermate hi-fi o il prototipo navigabile.]

The team during fieldwork: interviews in cafés, contextual sessions, card sorting on paper
Fieldwork: interviews, contextual analysis, and the card sorting board.

What already existed

We benchmarked two sets of products against each other: commerce platforms designers already sell on — Archiproduct, Yanko Design, Society6, Faberin, SquareSpace — and the social platforms they already promote on.

Two columns of the commerce matrix are empty for every single platform: credit points and visual scanner. On the social side the pattern is reversed — the social mechanics are all covered, but only Facebook does direct payment well.

That gap is where the concept went. It's also the honest reason to be careful: a feature nobody has built is either an opportunity or a thing that doesn't work, and a benchmark can't tell you which.

Feature matrix for commerce platforms: exploration, personalised, portfolio, credit points, visual scanner, tracking
Commerce platforms. Credit points and visual scanner: nobody.
Feature matrix for social platforms: pay direct, follow, live stream, suggestions, launch
Social platforms. Everything social, almost no commerce.

Two archetypes out of five

The research produced five archetypes: shop owner, startup owner, creative producer, non-designer shopper, social and design eager. We kept two and dropped three.

The two we kept — Creative Producer on the selling side and Social & Design Eager on the buying side — are the ones for whom the social part of a social commerce isn't decoration. The creative producer needs an audience before she needs a checkout. The buyer wants to talk about design as much as own it.

The three we dropped were the more conventionally commercial ones. That choice narrowed the market and made the product sharper, which is the trade-off worth naming: a service designed for people who want to talk is a harder sell to people who just want to buy fast.

Five archetypes with two highlighted: Creative Producer and Social and Design Eager
Five archetypes, two kept.
Persona: Alessandra, 32, graphic designer, buys design objects with conceptual value
Alessandra, the buyer.
Persona: Anna, 25, product designer, wants to promote and sell her projects
Anna, the seller.

Two journeys, told as storyboards

Rather than writing requirements, we drew both sides end to end: Alessandra from seeing a product on Instagram to unpacking it on video, and Anna from registering as a seller to managing her first shipment.

Drawing them is what surfaced the features. The chat with the seller appears in Alessandra's story because she wants to know whether a chair is made of real wood — not because a competitor had a chat feature.

Buyer storyboard: seeing products on Instagram, scanning the room, chatting with the seller, bidding, unboxing
The buyer's journey.
Seller storyboard: registering, uploading a product, receiving an order, shipping, getting reviewed
The seller's journey.

The answer to the trust problem

If buyers don't trust the transaction but do trust the content, then the service has to make the people visible rather than the catalogue. Three features carry that:

Talk to the person who made it. Direct chat between buyer and seller. The seller stops being an anonymous storefront and becomes the designer you read about.

Ask the community before you buy. Post what you're considering, collect opinions, see how others rated it. It replaces the price comparison people said they needed with something a blog can actually offer.

Find products from your own room. Capture a video of your living room, kitchen or office, and the service surfaces products that fit it. This one is the most speculative of the three — in 2019 it was a concept, not something we built.

These three weren't picked from a list. We printed twenty feature cards — images, reviews, wallet, wish list, seller profile, voice recognition, virtual reality and the rest — put a real product at the centre of three concentric rings, and asked people to place each card by how much it mattered: very important, interesting, not useful. Then we changed the product at the centre, from a smart speaker to a chair to an event ticket, and watched the cards move.

[DA COMPLETARE: quali card finivano stabilmente al centro e quali venivano scartate sempre — se te lo ricordi, o se lo trovi nelle foto delle board.]

The card sorting setup: twenty feature cards placed on three concentric rings around a product
Twenty features, three rings, one product at the centre.
Photographs of the card sorting boards filled in by participants
The same board, filled in by different people.
The six steps of the video scanner: capture the environment, find products, ask the community, have a conversation
The video scanner, step by step.

The service, not just the interface

Because the workshop was about services, the deliverable that mattered most wasn't a screen. It was the blueprint: where the blog sits, where the commerce platform sits, and every third party the service depends on — payment gateway, CRM, inventory, shipping, accounting, the post office.

It's the drawing that shows whether a concept is buildable by the company that would have to run it, and it's the one that makes the difference between a proposal and a mockup.

Service blueprint: the ecosystem map connecting blog, platform, payment, logistics and both user roles
The ecosystem map, buyer flow in purple and seller flow in yellow.

Two products inside one service

Buyer and seller got separate architectures, because they're doing genuinely different jobs. The seller's world is a dashboard: insights, wallet, orders, shipping status, training. The buyer's world is a feed: search, wishlist, cart, community, tracking.

One decision here is worth pointing at. The seller side includes paid training — video courses on marketing and photo editing. It answers something the research said out loud: designers know how to make things and not how to sell them. It also gives the platform a second revenue line, which matters when 20% of your sellers won't pay a fee at all.

Information architecture from the buyer's point of view
Buyer architecture.
Information architecture from the seller's point of view
Seller architecture.
Buyer features in wireframe: community corner, contact seller, recommendations
Buyer features: community, contact seller, recommendations.
Seller features in wireframe: dashboard, training, add social content
Seller features: dashboard, training, social content.

Look and feel

Minimal, young, fresh, social, geometric, ordered, tidy — the keywords the moodboard was built around. The interface stays quiet so the objects don't have to compete with it, which is the right call for a catalogue of things people made by hand.

Moodboard with colours and keywords: minimal, young, fresh, social, geometric, ordered, tidy
Colours and keywords.
The Wanted.Buy homepage with editorial content and product categories
The homepage, with the blog's editorial content sitting alongside products.

The concept in motion

[DA COMPLETARE: una o due righe su cosa mostrano i video.]

[DA COMPLETARE: didascalia video 1]
[DA COMPLETARE: didascalia video 2]
[DA COMPLETARE: didascalia video 3]

Where it stopped

[DA COMPLETARE: cosa è successo dopo la presentazione. Design Wanted ha portato avanti qualcosa? Il concetto è stato testato con utenti reali dopo la ricerca iniziale?]

[DA COMPLETARE: il tuo ruolo dentro il team di tre — cosa hai fatto tu in concreto.]

[DA COMPLETARE: la domanda onesta — cosa non ha funzionato, o cosa rifaresti diversamente.]