Rhino and Grasshopper Workflow Optimisation

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.

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.

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.

You can also open the related Architecture Social podcast page.

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.