View Resume LinkedIn
Back to writing

Article · 6 min read

Rendering Faster Without Losing Quality

How building systems instead of one-off scenes reshaped the way I approach motion, 3D and design, and what it takes to make the switch yourself.

Most of my early projects were one-off scenes: hand-tuned, hard to repeat and painful to change. This is the story of moving to a procedural way of working, where the rules matter more than any single result, and of the five steps that made the shift stick.

  1. PlanDefine the system
  2. PrototypeTest one small case
  3. BuildMake it reusable
  4. RefineTrim the controls
  5. ShareDocument and reuse

Steps 1–5 repeat every project. Each build is a refinement on the last.

01 — Setup

Aligning first: the setup.

Before building anything, it helps to answer a handful of questions. They keep the work focused and give every later decision something to be measured against.

  1. 1
    What is the problem?

    One clear sentence on what is being solved, and for whom it matters.

  2. 2
    What are the goals?

    What success looks like once the work is finished, in plain terms.

  3. 3
    Who is it for?

    The people who will use the result, including the person who is future you.

  4. 4
    What are the constraints?

    Time, tools and budget that shape what is realistic to build.

02 — Problem

Defining the problem.

The first part of the process, and the one everything else hangs on. Before a single node or keyframe, the whole project is reduced to one honest statement.

The problem statement

Repeating the same manual work on every project doesn’t just cost time — it slows every creative decision down and makes late changes painful.

Treat the statement as a hypothesis. Revisit it whenever the work starts to drift.

03 — Goals

What are the goals?

The problem breaks down into measurable goals, each paired with the outcome that would prove it worked.

  • Reuse the setupTurn repeated work into one tool
  • Make it flexibleChange late without starting over
  • Keep it readableClear names and tidy networks
  • Standardise the lookOne set of defaults everywhere
  • Surface the controlsExpose only what matters
  • Stay shareableEasy to hand to someone else

04 — Audience

Who it’s for.

Everyone touching the work has different needs. Naming them early stops the design from drifting towards only one of them.

  • Future meOpens the file in six months
  • CollaboratorsNeeds to pick it up fast
  • ClientsCares about the final result
  • LearnersWants to see how it works

Keep reading