My name is Ito, and I am the person in charge of the production site at Coding Factory.
I'm busy every day trying to solve all sorts of problems that arise on the production site, but this time I'd like to write about "workflow," which is the foundation of all our work.
At Coding Factory, multiple members, including a salesperson, director (production manager), coder (coding officer), and checker (quality control officer), work on one project.
However, if it is not clear who is responsible for which tasks, people's perceptions of the "scope of their own work" can be surprisingly different.
For example, a coder may think that his or her job scope is limited to coding, or that progress management is the responsibility of the director, or to put it more dramatically, that there is no need to do any work until the director gives instructions.
Even if there was a lack of design data, there were times when the work would stop without an alert being issued. On the other hand, directors tend to assume that even without detailed instructions, the coder will make adjustments or issue an alert if there is a lack of design data, and they tend to feel reassured that the work is progressing unless they are told otherwise.
This difference in perception between the two parties results in "omissions in work."
"Omissions in work" not only result in correction work being required and lowering productivity, but can also cause a significant drop in the quality of the products delivered to customers.
To prevent this, we have created a "workflow" and use it carefully.
A workflow is "a way to visually grasp how a project should be started and completed by breaking it down into individual task units."
This workflow clarifies "who is doing what" and "who will do the next task," helping to prevent anything from being overlooked.
In addition to the basic workflow shown above,
- Projects with many pages
- Few projects
- Short delivery time projects
- Projects that require special skills other than coding
By preparing a variety of flows for different cases, such as those above, we can recognize which part of the overall project each individual "task" belongs to, and work together to complete the project smoothly.
As producers, our major role is to ensure "quality" and "productivity."
While it is important to increase the number of pages you can create per day, it is meaningless if the products are of poor quality and full of omissions.
We believe that creating efficient plans based on workflow and being able to steadily execute them will lead to improved productivity without imposing a burden on the production site.
This is the ratio of the workflow of our service, Coding Factory . In addition to making the coding task itself more efficient, thorough pre-work planning and checking work around it will reduce duplication and backtracking, leading to improved productivity. In addition, if the checking system is thoroughly implemented, it will lead to an improvement in the level of work in the medium term.
ITO Yousuke