Your Work Shouldn't Feel This Tedious
Simple ways to spot tasks that computers could handle for you
Do you ever get that feeling that the last 3 hours you've just spent entering data could have been saved or at least shortened? Surely, in a world where we have virtual reality and AI models like ChatGPT, technology should have come far enough for us not to do so much manual work.
Well, I'm here to tell you to trust that feeling because there might actually be a way to turn those three hours into one, or even zero. But it's not with AI or virtual reality - instead, computational design could be exactly what you're looking for. Now, I know it's literally my job to go around yelling "Computational Design is the future!" but I also know it's not that straightforward.
Computational Design (or CoDe for short) is still abstract, and we're all still figuring out how it fits into our work. But that shouldn't stop us from exploring it. Even now, CoDe has already saved countless tedious manual hours - it's just a matter of finding where it can help you.
What is Computational Design, Really?
Let's demystify computational design. It's not about replacing human judgment or turning everything into complex algorithms. It's about letting computers handle the tedious and manual stuff so you can focus on what you do best - solving complex problems.
It's like having a really efficient assistant who's great at repetitive tasks. This "assistant" might be a simple script that puts data in Excel for you, or a more sophisticated program that creates design variations for you to review. Either way, it's there to enhance your work, not complicate it - though it might change how you think about your work along the way.
Spotting Opportunities In Your Work
Listen to Your Frustrations
When you sigh at doing the same thing for the tenth time because the project keeps changing, it's a signal that there might just be a better way of handling that task.
Pay attention to moments when you:
Feel like you're spending way more time on repetitive tasks like data entry than actual design
Catch yourself thinking "I wish this could just happen automatically"
Notice yourself getting more frustrated at doing the same thing over and over again
It might sound obvious as you read this, but the key is to identify gaps where there might be better ways of working - even for the simple tasks you think can't be automated.
Understanding Your Flow
Another way to spot opportunities is by taking a moment to think about your typical workday or your processes. Not in a rigid, process-mapping way, but in terms of where you feel most drained versus most energized.
Try sketching out your workflow and look for:
Tasks that you find yourself rushing through
Tasks that have a lot of data and aren't clear on what's happening
Work that you think is crucial and has to be looked at by a person
This isn't about creating the perfect workflow - it's about understanding your own processes. And hopefully that understanding lets you identify gaps that can be automated or improved.
Finding Your Pain Points
As you understand your own work better, there are bound to be things that you forget. The last two exercises were about identifying what you currently know or remember, but this one is about reminding yourself that there might be a better way to solve what you are currently doing.
Keep it simple - try keeping a note on your phone or desk and jot down moments when you feel:
Overwhelmed and stressed by your work
Frustrated that things keep changing and you have to redo work for the umpteenth time
Worried about making mistakes because there isn't clarity in what's happening
These feelings often signal where computational design could help. Sometimes you don't even realize there might be a better way until someone points it out - like my colleague who didn't see an alternative to his late-night data entry until we happened to meet at a coffee shop. You can read more about that[[CONTENT-42 (CodedShapes) | here]]
Making Solutions Feel Achievable
Once you've identified where you're struggling, don't feel pressured to immediately find the perfect solution, computational or not. Instead:
Start Small: Focus on one task that consistently drains your energy. If what is draining you is complex, try breaking it down into smaller steps and tackle each step at a time.
Imagine Better: Before thinking about technical solutions, simply imagine "What would make this better?"
Share Your Struggles: Sometimes just talking about a pain point with colleagues can reveal that others have similar challenges - or might even have solutions
I know this all sounds like common sense, but I am amazed how I always get caught up in trying to solve the whole problem before starting. It's exciting to think about new ways of working, but we have to keep it practical and small enough to build something actually useful.
Connecting to Computational Design
If you're ready to explore how computational design might help with your pain points, ask yourself:
Could a computer handle the repetitive parts of this task?
Would having multiple design options help me make better decisions?
Am I spending time on calculations that could be automated?
Could rules or patterns help streamline this process?
I know it's hard to envision a solution, especially if you're new to computational design. But understanding your pain points and imagining potential solutions is already a great start.
You can also take it further by exploring existing solutions that relate to your problem - maybe it's a Grasshopper script or even an Excel macro that has solved your pain point before. The key is becoming aware of different ways to work and how CoDe might enhance what you're already doing.
A Final Note
Finding computational design opportunities isn't about forcing technology into your workflow. It's about improving those moments of frustration. Sometimes the best opportunities come from simply giving yourself permission to imagine a better way of working. Even if you don't find one, it's good to understand the pain points that you currently have in your process anyway.
Trust your instincts - if something feels unnecessarily tedious or time-consuming, it probably is.