A short time ago my new game The Franz Kafka Videogame was released. It's puzzle/adventure game where the atmosphere of absurdity from Franz Kafka's writings is combined with some postmodern ideas.
But the Kafkaesque setting and original puzzles are only the top layer of the project. They aren't the main feature of the project.
The actual main feature (about which nobody suspects) is the fact that it's full improvisation. 100% improvisation in everything: without any plans, design documents, etc. The plot, puzzles and all other game elements were invented only in the course of development. The only thing that I had at the beginning was the idea "to create a game inspired by Franz Kafka's novels".
I had already used partial improvisation during the work on my last game Hamlet or the last game without MMORPG features, shaders and product placement. So in the new project I decided to experiment and use total improvisation.
Why all this?
When I was working in a gamedev company, we were spending a lot of time to write design documents. Then in the course of work on a game we had to make corrections to the design document all the time, because many initially attractive ideas appeared not interesting in practice. As a result, a final game always didn't resemble a game from the initial design document.
By and large, much effort and time are spent for writing and maintenance of the design document, but actually very few people read it. You probably have watched Kevin Smith's talk about making of Die Hard 4 – it completely coincides with my experience of work in video game industry.
In addition, development of games is a creative process. And, as in any creative process, all best ideas appear not before, but in the course of work. So I want to have an opportunity to add all best new ideas to a game. And in traditional model of game development you are more likely to remove many interesting ideas (feature-cut) than to add new ideas.
Usually I use 'the skeleton of design document', the file with the description of all key features and game elements without any details. It allows me to delete, to change, to add game elements/ideas in the course of development without loss of time and not to break integrity of the project.
For The Franz Kafka Videogame I didn't use even 'the skeleton of design document'. Only improvisation.
I divided a game into levels, and I was making them in a chronological order from the first to the last. For every level I looked at the current plot situation and come up with a puzzle specially to it. Thus all puzzles in the game are inseparably connected with the narrative, and the plot of the game reveals through these puzzles.
I don't oppose the traditional model of game development with total improvisation. Obviously, improvisation isn't an ideal system. It has its pros and cons. But I would like to emphasize the two most important factors for me:
Improvisation allows you to introduce new ideas which appear as a result of just obtained information or the experienced emotions. The game is a living organism which changes and develops in the course of development. And thanks to improvisation, the game develops and changes together with you.
For example, the сhancery level initially seemed more classical to me: dusty office and a сlerk wearing spectacles and suit. But when I began to work on it, I understood that it didn't correspond to the atmosphere of the game and the overall level of absurdity. So quickly enough the сlerk turned into a deep diver, and the office went underground to an old flooded mine. And the most important, at that moment I didn't even think of what puzzle would be there. When I was drawing the deep diver on the computer, I noticed how the image from the screen reflected in a smartphone lying nearby. This little observation allowed me to come up with one of the most elegant puzzles in the game. At the beginning of the level the deep diver-clerk gives a gentle hint that the solution is found in the reflection, and indeed, it's enough for player to put a mirror in front of the screen to see the answer in it.
Improvising you feel like a real creator, creating something unique and enjoying the process, not like a robot performing routine mechanical functions according to a pre-made plan. This brings together the game developers with poets and jazz musicians.
I'm not trying to idealize improvisation. I only want to show on the example of my game that you can improvise not only when developing micro-games for Ludum Dare, but also during creation of larger projects.
Even in Hollywood, improvisation is an integral part of many famous movies.
Virtually the whole Marlon Brando's role in Apocalypse Now was improvisation, all jokes in Die Hard movie are Bruce Willis's improvisation, etc.
Therefore I don't see problems to use more improvisation in game developing.
As result, I created an unusual game with a set of original puzzles which you won't see in other games, and a complete multilayered plot.
The game won the Grand Prix at Intel Level Up competition in 2015, and it has a positive player score at Steam.
I've been working in the video game industry for about 14 years.
In 2003-2008 I worked in the Russian company Targem Games as the Lead Game Designer/Level Designer/Scripter. I took part in development of 8 projects of different genres.
Since 2008 I've worked as the independent game developer. I'm best known as the author of such projects, as The Franz Kafka Videogame and Hamlet or the last game without MMORPG features, shaders and product placement.