Editorial

Rhino and Grasshopper Workflow Optimisation

A practical guide to Rhino and Grasshopper workflow optimisation, based on Michael Pryor’s MADCon tool-making session.

First published 2 min readJoin the discussion
On this page

Rhino and Grasshopper workflow optimisation is not about making everything more complicated. The best tools remove repeated effort, reduce mistakes and free up more time for design judgement.

Michael Pryor’s MADCon session is useful because it frames tool-making as a response to workflow pain. If a process keeps repeating, it may be worth turning into a clearer method, template or tool.

Rhino and Grasshopper workflow optimisation session artwork

Workflow optimisation is most useful when it removes repeated effort and gives designers more time for judgement.

Start by spotting repetition

Before building anything, identify the repeated task. Is the team copying information between models? Rebuilding similar geometry? Renaming files by hand? Producing the same options with small changes?

  • Write down the repeated task in plain English.
  • Check how often it happens and who it affects.
  • Decide whether a tool, template or checklist is the right answer.
  • Test the workflow on a small example before rolling it out.
  • Document enough that someone else can use it.

Tool-making as portfolio evidence

For candidates, workflow optimisation can be strong portfolio evidence. Do not just show the final script. Explain the problem, the old process, the new process and the benefit to the project or team.

Related video: computational design thinking

This related Architecture Social video adds a broader look at computational design, algorithms and the judgement needed behind the tools.

presto-player:video_id=590

as-source-card:workflow-optimization-links

Turn workflow skills into career evidence

If you are using Rhino, Grasshopper, Revit or computational tools, make the practical value visible in your applications.

/as-source-card:workflow-optimization-links

Listen: computational design and algorithms

This related Architecture Social episode adds a broader computational design perspective for readers interested in tools, workflows and design judgement.

Ready when you are.

This Transistor podcast needs media cookies to play here.Enable videos and podcasts, or accept all optional cookies.

Your choice is remembered across the site. Change it any time.

Listen with TransistorOpen on Transistor

Architecture Social view

Stephen’s view is that technical candidates stand out when they explain impact. A tool is more impressive when the practice can see how it saves time, improves quality or reduces coordination risk.

as-reader-action:workflow-optimization-action

Make the workflow evidence visible

Before adding a tool to your CV, write the short story of what it improved.

  • Name the repeated problem.
  • Show the before and after workflow.
  • Explain the benefit in practice language.

Browse BIM jobs

/as-reader-action:workflow-optimization-action as-holistic-seo-end:rhino-grasshopper-workflow-optimization-125894

For related career support, compare the architecture salary guide, browse current architecture jobs, set up architecture job alerts or contact Architecture Social for a recruiter’s view.

Keep the conversation going

What stayed with you? Join the Architecture Social community to share your experience or ask a question.

Log in to joinCreate an account

Keep reading

All articles

Starting an Architecture Practice at 29 with Alex Sutton

Alex Sutton of Studio Sutton explains what starting an architecture practice at 29 really takes, from winning work and procurement to resilience, hiring and business reality.

7 min read

Solaris by Hinal Gosai

Hinal Gosai’s Solaris project turns Liverpool’s Queensway Tunnel edge into a civic cycle hub with public space and sustainable design.

6 min read