Reflections

This is where almost every RDF project starts: a clear idea in mind, and no idea what the first concrete step

This is a common question, and the honest answer is: rarely fully free, but sometimes accessible on a small bu

This is often the first question, and often the hardest to answer alone.

A prototype doesn't need to be perfect: it just needs to answer one precise question.

The right person depends mostly on what stage your idea is at, not on how ambitious it is.

Budget limits how fast a project moves, rarely whether it can exist at all.

An invention is rarely developed alone in a vacuum: it moves forward through back-and-forth between idea and p

Protecting an idea depends mostly on what you'd actually risk losing by sharing it.

Improving a mechanism first requires understanding precisely what's sticking, before trying to change everythi

Optimising a part isn't about making it more complex — often it's the opposite.

A standard object doesn't always match a precise use — customising it can be enough, without starting from scr

An almost-perfect product doesn't always deserve to be replaced — sometimes a targeted modification is enough.

A custom part exists for one precise reason: nothing standard exactly matches the need.

A discontinued model doesn't mean an object has to end up in the bin.

Not every repair follows the original instructions, and that's often just fine.

An object that no longer serves its purpose isn't always done for good — sometimes it just needs a small inter

We tend to think an object breaks out of bad luck. In reality, it's almost always one precise point giving way

The absence of an official spare part isn't always a dead end.

3D printing has changed how objects get repaired: what once needed an expensive mould can now be made part by

An object rarely lasts by chance: it lasts because a weak point was anticipated or reinforced in time.

An object isn't always limited to its original function.

There's the official method, and there's how a project actually unfolds, conversation by conversation.

A good diagnosis is often worth more than a fast, poorly targeted solution.

We tend to associate R&D with big labs, when it also plays out at the scale of a broken object on a kitchen ta

Mechanical design is scary because of its vocabulary, rarely because of its actual logic.

Custom work is often associated with a big budget or an ambitious project, but that's not always the case.

It wasn't an initial ambition that created RDF, but a recurring frustration at seeing ideas and objects left w

Most ideas that reach RDF weren't born from a will to innovate, but from a small annoying moment in everyday l

It's tempting to judge a problem too small to take seriously — that's rarely the right instinct.

We tend to picture innovation as something spectacular, when it mostly hides in gestures repeated without a se

A first prototype that doesn't work as expected isn't bad news — it's information.

An idea often gets judged too fast, before it's even really been studied.

The distance between an idea and a useful solution is often shorter than people imagine.

It's the most common question, and also the hardest to answer without precise project details.

Discovering your idea already exists isn't necessarily bad news — sometimes it just confirms it answers a real

Confusing the two often leads to investing too early in a finish that doesn't need to exist yet.

The word "engineer" can feel intimidating, when many everyday objects don't actually need that level of expert

The right material is never the strongest one in absolute terms, but the one suited to the object's precise us

The right time to move to small batch production isn't a matter of timing, but of real validation of the proto

A prototype that works on a table doesn't yet tell you whether it will actually work in real use.

A €300 printer and a professional machine don't aim at the same use, even if the principle looks identical.

Both techniques make parts, but rarely for the same reasons or with the same results.

The question seems simple, but the right answer rarely comes down to price alone.

The term often sounds intimidating, when a good brief can sometimes fit in a few lines.

Most mistakes with a first prototype aren't technical — they come from poorly calibrated expectations.

Technical feasibility and profitability are two different questions, often confused early on.

A standardised object isn't designed for you, it's designed for the largest possible number of people — and th

An object's lifespan is largely decided before it's manufactured, not during its use.

We often settle for an almost-right object, without noticing the small repeated discomfort it imposes.

The sticker price of a disposable object never tells the whole story of its real cost.

We often wait for the ideal moment to get started, when that moment almost never arrives the way we imagine it

A design, development or manufacturing project feels complex mostly because it hasn't been broken into steps y

Concept, prototype and finished product are often treated as synonyms, when each one corresponds to a very spe

People often look for "a partner" in the singular, when a project usually calls on several different skill set

An object's responsibility isn't decided afterwards, it's played out in the very first design choices.

The term sounds technical, but product engineering is really about answering one simple question: how will thi

An object can be technically impressive and yet completely useless — the two don't always go together.

A good idea is often associated with a flash of creative genius, when method usually matters far more.

The two approaches aren't really opposed: they simply answer different needs.

It's rare for one person to have every skill a project needs — and that's not a problem.

Open innovation starts from a simple observation: an idea often moves forward better when confronted with outs

We often imagine a solution appears all at once, when it's almost always the result of a method applied patien