Teaching the machine - Understanding the process ourselves
Teaching the machine - Understanding the process ourselves
Before a system can automate something properly, somebody needs to teach it what "properly" means. That also means we and the clients also need to understand what that means.
What happens when the text is too long? What happens when there are three different prices? Which logo belongs to which market? What happens when a translation is longer than the original? Which parts of the design are allowed to change and which parts should never move? What happens when the client wants a completely different format?
These are not just programming questions. They are production, design and flow questions.
Our job at VeeDee is to understand those questions and turn them into a system that both humans and machines can understand. Sometimes that means programming, sometimes After Effects, sometimes data management, sometimes 2D or 3D work, and sometimes it is simply sitting down with a client and figuring out what they actually want to achieve as an end result.
We even spend time teaching teams how to prepare their own information in a way that makes sense, using simple CSV (excel or sheets) structures that people can understand and that our systems can process.
Because good automation isn't about making humans fit the machine. It's about building the machine around the way the humans need to work. And once that part is done, something quite nice happens.
People stop fighting the system.
They can finally get on with their actual (fun) job.
Thanks for reading
People sometimes imagine automation as if you throw a design into a machine, press a big red button and suddenly you have thousands of perfect videos. I wish it was that simple but the truth is actually a bit more interesting.
Before a system can automate something properly, somebody needs to teach it what "properly" means. That also means we and the clients also need to understand what that means.
What happens when the text is too long? What happens when there are three different prices? Which logo belongs to which market? What happens when a translation is longer than the original? Which parts of the design are allowed to change and which parts should never move? What happens when the client wants a completely different format?
These are not just programming questions. They are production, design and flow questions.
Our job at VeeDee is to understand those questions and turn them into a system that both humans and machines can understand. Sometimes that means programming, sometimes After Effects, sometimes data management, sometimes 2D or 3D work, and sometimes it is simply sitting down with a client and figuring out what they actually want to achieve as an end result.
We even spend time teaching teams how to prepare their own information in a way that makes sense, using simple CSV (excel or sheets) structures that people can understand and that our systems can process.
Because good automation isn't about making humans fit the machine. It's about building the machine around the way the humans need to work. And once that part is done, something quite nice happens.
People stop fighting the system.
They can finally get on with their actual (fun) job.
Thanks for reading
1 Guest(s)
1 Guest(s)