Write it down, organize it, report it and do it!
‘I told you by phone that I would write to you by whatsapp when I would send to you the information of the project. t does not fit in one email so you will probably receive more than one’. Everything is alright at this point. :)
Remote working is increasing more and more due to the balance between work, family and private life among other reasons. Sometimes you can also work for companies located outside your city area.
Using an unified communication criteria can help you on reducing the loss of time and confusions that is very commont in this kind of work. This also happens inside a company, even when team members are working together in the same place.
The previous article discussed about how to streamline the workflow by decomposing the process into tasks and how to organize complex scenes. In this case we want to tell you how we manage the flow of communication to optimize the times.
In a simplified way we could say that a visualization project is a set of linked and interdependent tasks. These tasks can suddenly appear, be modified or can even be discarded or replaced by others. It happens more often than desirable, specially when the design of the project and the production of the images are at the same time.
To this process we must add the interests of the head of design and the client. They should know the state of the project at any time.
The communication should be as transversal and synchronized as possible between all participants. It will help to manage tasks and it will be easier to obtain a better result at the end of the assignment.
Maybe for a single person team a sheet of paper is enough. The issue became more difficult when you work with more people and you have to make corrections or questions to different tasks during the process.
The way we deal with information is very close to the task management mthod known as GTD (Getting Things Done). The key is to organize the inputs correctly to waste the least possible time.
When we receive the information of a project every task, whether modeling, mapping or postproduction, follow the same cyclical process. It does not matter which software we use. Any input we receive is queued, processed and returned to the clients to ask for their confirmation about it or to correct it until everything it is alright.
We follow this scheme:
It is different when a visualization project is focused on the final client (public or private company) or it is being done together with the design team for a presentation (architects / designers). In latter case, the dashed line may not exist and the task list could be shared (writable mode) to reduce the response times as much as possible.
As for software, you may have preferences for tasks managers like ASANA or Trello. We completely agree with you. Sometimes we have used them but it depends on the project and the client. It is possible that in medium/large teams or projects projects they will help us.
But let us repeat it one more time, the software that we use does not matter at all, but the cycle which follows every input.
Anyway in future articles we will write about these tools, not about their features, but how we use them for. Until then we will be glad to receive your comments about this topic.