Game Career Guide is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


Get the latest Education e-news
 
  • Why You Need A Technical Designer

    [04.14.20]
    - Franck Fitrzyk
  • The same way the role of technical artist has won its letters of nobility during the last few years, the technical designer role is starting to take an important space on the game industry job boards. After seen the necessity and the benefits of having a technical supporter to the 3D modelers, environment artists and other visual asset creators, we understand more and more, during productions, the need to help other major content creators: designers.

    Whether they are game designers, level designers, AI designers, system designers or quest designers, those content creators need a technical support during the production, some help to solve and tackle technical issues, simple or complex ones. That reveals the technical designer position as to be a key role in the design team.

    So, the technical design is first a support role dedicated to facilitate the creative designers' job and to be the interface between the designers and the different technical department of the production.

    What is technical design? 

    Technical design is the bridge between the game design principles and the technical problematics (for gameplay programming or tools). Depending on the teams and the projects, the technical design can have different shapes from the definition of the design team's needs in tools and features to create the game content to scripting, prototyping and the creation of any content needing some technical knowledge in programming or different software.

    What's the responsibility of a technical designer?

    Cédric Hauteville, level designer at DeepMind, said during his GDC 2019 conference about technical design that "technical design is the missing link between game designers and programmers."

    Depending on the needs of the project and the skills of the team, the technical designer can become an impactful member of your production. First, his role is to understand the game design and the creative direction of the project in order to anticipate the needs of the designer to create the game content as simply and as efficiently as possible. So, he/she is the right person to express the needs of the game design or level design team to the technical teams, whether it be the gameplay programmers, the tool team, the procedural team or any person that is creating an element that the designer will have to use. He works too with leads and producers to defend the designer's requests by providing prototypes, presentations and proofs of the benefits of their requests.

    For example, while I was working at Ubisoft Annecy as a Technical Level Designer, I was not developing the tools by myself. I was following the development of those with the teams in charge of their development. I was in charge of making sure the requested tools were going in the right direction and were answering my fellow designers needs properly. We were working on an engine needing C++ knowledge, which I don't have. Nevertheless, I was able to give feedback on the tools and features, use them, prepare templates and pre-sets ready to be used by my team.

    From the expression of the design team's needs, the technical designer follows the development of the tools that will be used by the team or any element that'll need settings (quests, procedural generation, exploration content like collectible, AI, interaction with environment, etc). It means that he/she is the first tester of those features and so, the favourite person to talk to for the tools team and other programmers but also to leads who like to know the progress on their future workflow.

    As the start of the project as well as the during the production, the technical designer identifies the weaknesses of the workflow and does what it takes to improve it. This can very well just be the preparation of certain tasks that the designers will have to do later during the production to ease their work, trying to automatize things or just creating templates and pre-sets. For example, for quest scripting, he/she can prepare reusable functions or even full script templates that will be used as a good work base.

    He/she is responsible for the User Experience of the tools used by his team and assures they have tools and features that answer their needs. His/her goal is to reduce the friction and the technical tasks of the creative designers so they can spend more time creating content rather than solving issues due to tools. 

    In the end, he is the support role of the design team all along the production. He/she has a capacity to understand the design and the technical constraints which allows him/her to anticipate the needs and the potential problems. Properly used, he/she can be a serious assert of your production and a core team member. He/she is the technical point of contact of the design team: if they have a workflow or tool issue, they know they can get an answer or help beside him. He/she also becomes the friend of programmers who really appreciate to get only one person to talk to to share their instructions and information.

    It is a position for which you really need a person in which the whole team can be trustful.

    He/she gathers the need, the requests, the feedback, the information, knows how to share them and summarize them. He/she has a full vision of the complete pipeline.

    Then, it is also the responsibility of the technical designer to train his team members to the new tools and other features of the workflow. Training but also documenting! The creation of a proper technical documentation and tutorial is one of his mission too.

    I hope you see now how extremely useful a technical designer can be and how central to your design team it can become: the interface between the content creators (game designers, level designers, quest designers, etc) and your programmers (or any other technical team member).

Comments

comments powered by Disqus