Hobfolk
Drawing · case study

The drawing didn't just look right.
The wing moved.

A render can look correct and still be undriveable. The only way to know a mechanism actually works is to build it — so a design for a moving wing was taken from reference photography, through a dimensioned CAD model, to a physical prototype, and tested.

Start a conversationSee the whole crew
You go home. It doesn't.Every promise gets a row and a due dateEvery enquiry answered, not just loggedA drawing before the quoteUnverifiable is never a passA desk per department, one address eachNothing is sent that a human cannot read backThe folder exists before you price itYou go home. It doesn't.Every promise gets a row and a due dateEvery enquiry answered, not just loggedA drawing before the quoteUnverifiable is never a passA desk per department, one address eachNothing is sent that a human cannot read backThe folder exists before you price it
The story

A design that had to move correctly, not just look correct

A drawing that only has to look right in a still image is a much easier drawing to make than one that has to move the way it claims to.

The brief was an animatronic prototype built around a real bird of prey's wing mechanics — reference photography of the living animal used to understand how the joints actually articulate, not just how the wing looks folded or extended in a single pose.

That reference was translated into a dimensioned CAD model built to be manufactured, not just rendered — every joint, linkage and range of motion specified as a real mechanical assembly rather than an artist's approximation. The model was then physically built and tested, and the mechanism moved as the drawing said it would.

That is the actual claim a drawing desk can make and the only one worth making: not that the picture is convincing, but that a real thing built from it works.

The mechanism, drawn before it was cut
The mechanism, drawn before it was cut

Sourced from Hobfolk's own operational record, dated and on file — see the other cases. Client identity is never named; the numbers and the root cause are not softened.

What changed

How it was made to work, not just to look right

01

Reference used for mechanics, not just likeness

Photography of the real subject was studied for how the joints move, not just how it looks in a single held pose.
02

A dimensioned model, built to be manufactured

Every joint and linkage specified as a real mechanical assembly, with tolerances a workshop can actually cut to — not a sculptural approximation.
03

Built once the drawing was proven, not before

The physical build followed the model rather than running in parallel with a moving target.
04

Tested against real movement, not a still render

The finished mechanism was checked against the same range of motion the reference photography showed, not just approved from a static image.
05

Revisions fed back into the drawing, not around it

Anything the build revealed the model hadn't accounted for was corrected in the CAD file itself, so the drawing stayed the single source of truth.
06

A render is not the deliverable, a working thing is

The picture exists to get the mechanism agreed before cutting material. It is not the proof of the work — the tested prototype is.
How it unfolded

The sequence, in order

  1. Reference photography is gathered

    Of the real subject, specifically for how it moves, not just how it looks.

  2. A dimensioned CAD model is built

    Every joint and linkage specified as a real, manufacturable assembly.

  3. The model is reviewed before anything is cut

    Agreed against the reference, not just against taste.

  4. The mechanism is built

    From the model, not adjusted freehand during the build.

  5. It is tested against real range of motion

    Checked against the same movement the original reference showed.

  6. Anything the build revealed goes back into the drawing

    So the CAD file stays accurate for the next revision or the next unit.

The limits

What this desk will not do

A case study is not a claim of no limits. The same boundary applies here as on the department page this one came from.

Where this desk stops

  • It is not a signed-off engineering calculation. Where a structure, a load path or a regulated element needs a qualified engineer's stamp, this desk prepares the information and an engineer signs it.
  • It does not send drawings to a supplier who has not signed a confidentiality agreement. Dimensions, quantity and finish can go out uncovered so a request for a price is never blocked. Pictures cannot.
  • It does not present a render as a photograph. Ever, and in writing.
Questions

Asked before, answered here

Isn't a convincing render enough to sell a design?
It's enough to sell a look. It says nothing about whether a real mechanism built from it will actually move the way the picture implies — and that gap is exactly what this case study is about closing.
Why start from photography of a real subject rather than a spec sheet?
Because the brief was mechanical realism — how the joints articulate — and that detail exists in the real subject's movement, not in a written description of it.
Does this mean every drawing gets a physical prototype?
No — most jobs don't need one. This one did, because the deliverable was a moving mechanism and a still drawing can't prove a mechanism works. The desk builds what the job needs proof of.
What happens when the build finds something the drawing missed?
It goes back into the CAD model, not just into the physical part on the bench — so the drawing stays the accurate source for the next revision.
The department

This case belongs to the Drawing desk

Drawing

Drawing & visualisation

A dimensioned drawing and a picture of the thing, back before the client has finished thinking about it.

Open the department Case studies

Every case, in one place

Real, dated things that went wrong in the businesses this office already runs, and the fix each one produced.

See all the cases
Two more cases

More from the record

Case study

Every listing live, none of them true

A hunch, checked properly, turned out to be exactly right

Read the caseCase study

The same errors, every time

Codifying the fix didn't retire the problem

Read the case

Has your last drawing ever actually been built and tested?

Tell us what it needs to do, not just look like, and we'll tell you what that changes about how it gets drawn.

Start a conversation Read the method