Why Positive Feedback Matters

When was the last time you complimented someone on work well done? Or when did you last receive praise for work efforts you poured your soul into? Let me share a story from my earliest days as a designer about how positive feedback impacted my career.

We All Start Somewhere

In my first job in the game industry I started out as a data-entry monkey; an entry-level designer whose work involved setting up animation data, action triggers and events in a behavioral state machine to make characters and animated objects in the game come to life.

This was for the most part handled on demand as new characters and animations become ready for setup. No up-front design work was required, no extensive documentation needed to be written—we hooked stuff up on the fly, creating new character states, actions and transitions between states as and when needed, in some cases building up complex states to support new combat moves, quest cutscenes, AI behaviors, etc.

What Makes a Designer

Almost half a year into the job, I had still not written a single design document. The nature of the role I had simply did not require this of me—or even leave room for it. There were no design discussions or meetings to plan ahead, and there were no design reviews. As a result, even though I did the work of a designer, I did not feel like a designer, and I didn’t feel part of the wider design team.

This sentiment was echoed by some team members who, a few years into time there, even questioned—to my face—the necessity of my role, and whether it ever needed to exist in the first place. This did not do wonders for my self-confidence, as you can imagine. I was feeling undervalued and doubted myself, wondering whether I truly belonged.

Source: AI-generated “stock photo”, with correct amount of fingers

However, what kept me going through all that was positive feedback I received for the quality of the work I had done, and for the design documents I had written—in particular the first one I ever wrote!

First Design Document

My first design document was short and simple, and detailed some improvements to an existing feature in the game. It outlined the benefits the improvements would bring to players and to the game, highlighted potential risks of doing them, broke down associated development costs, and provided suggestions for multiple different ways of getting it done.

I poured a lot of heart into the document, even though it was an obvious next step to take and an improvement that both players and devs could see coming from a mile away. So when I received positive feedback on the design from the design team and from higher-ups who reviewed designs, I was over the moon!

Fuel for Long-term Passion

It was a pivotal moment that cemented my future in the game industry, as it made me realize that I was already a game designer, and I did have some small amount of talent for it that went beyond just entering data in a glorified database.

Over time my role there evolved, and I took on more “traditional” design responsibilities, but none of that would have been possible if not for the positive feedback I received from people at multiple levels in the studio hierarchy. It did wonders for me as a budding designer, and it fueled my passion for years to come. Without it I would likely have burned out and left the industry entirely, like so many others I worked with back then. f.

Moral of the Story

Positive feedback can be a game-changer. If you work with someone – whether they’re your colleague, your subordinate or even your boss—acknowledge their good work; let them know! Your feedback might have a stronger impact than you think.

I design, therefore I am

About Game Design, Imposter Syndrome and Soul-searching

Through most of my professional life, I had this nagging feeling in the back of my head that I was not good enough, that I didn’t know what I was doing, and that sooner or later someone would expose me for what I really was – a fraud. Imposter Syndrome hit me hard both when I was a designer at Funcom and when I later went on my own indie adventure.

That situation was not much different when, around four years and seven months ago, I accepted an offer to join a relatively fresh startup studio in Singapore as a game designer, after they initially caught my attention by developing a casual MMORPG on mobile called World of Legends, which would become the first mobile game I ever worked on.

At the time, Mighty Bear Games had somewhere between 12-15 employees. and I was immediately thrown in at the deep end on day one, when I was tasked to take over the reins of the game’s economy and combat design/balancing from the other designer on the team, who had started planning his early retirement from the industry just before I joined!

I still have nightmares about the Excel-sheets I took over, which could only have been created by some mad genius Excel wizard; numerous humongous, interlinked documents with sections that had to be manually updated and exported to CVS files, before being imported into the game’s data server through a careful process and in a very particular order. Modifying one document would have cascading effects to half a dozen others, some of which could take upwards of 5 minutes to load up as a result. Thanks, BK <3

Anyway, it kept me busy, and I learned a lot about Excel in a short amount of time as a result. World of Legends itself eventually made it to global launch on both Android and iOS, but was unfortunately shut down not long after because the number of players coming in, and the revenue those players generated, was not enough to justify continued development of the game.

However, the studio gained lots of valuable experience in the process (and learned first-hand that making MMORPGs is hard), and we moved on to the next projects with boundless zest:

Games I worked on at MBG

Since joining Mighty Bear that fateful day back in 2018, I’ve written game feature designs, scripted AI logic, balanced combat systems and game economies, pitched designs for new games and even done some level design. I’ve contributed across multiple teams in the creation of an MMORPG, two games for Apple Arcade (Battle Royale + Arena Brawler), a Match-3 Adventure, a Merge-game and – most recently – another Battle Royale game in the Web3 space.

Thanks to the opportunity Mighty Bear Games gave me I’ve gained a ton of designer XP and have leveled up my design skills multiple times over, but more importantly, I now feel like I finally know who I am and what I can do.

As a result, I no longer internalize the self-doubt and fear that haunted me for so long, and though there might still be a small lingering remnant of that all-too-familiar feeling of inadequacy lurking somewhere deep in the shadows of my soul, I can now look back at everything I’ve experienced and accomplished and feel confident that I could go into any team and contribute in meaningful ways, regardless of where I go or what game I work on next.

Going forward, I’m eager to continue growing as a game designer and excited to apply the skills and lessons I learn along the way to create new gaming experiences that can stand the test of time!

Lessons learned by working at Funcom for five years

I have an upcoming jubilee of sorts in a few months, at which point I can celebrate having endured life in the game development industry for five (measly) years. This cause for celebration is somewhat diminished by the fact that Funcom announced earlier this month that they are restructuring and consolidating offices – which means that I, along with the majority of the other developers at Funcom’s Montreal office, are being let go. For my part this means that I have at most two and a half month left before my official last day at FC, and having started working for FC in late March 2008, this means I might just about pass the five-year mark (yay!) before I’m officially out of a job (nay!).

Throughout these last soon-to-be five years I’ve had the pleasure and privilege of working with a diverse bunch of awesome people (and I hope that I’ll be able to work with some of them again in the future!) on two different MMORPG projects, and I would not change that for the world, but what exactly have I learned after this time spent working in the game development industry? Which of the preconceived assumptions and expectations I brought with me have held up, and which have been thoroughly shattered? What knowledge have I acquired that I can bring with me where-ever I go next?

I’ve played with the idea of writing a post along these lines in the past year or so, but what I’ve found out is that it’s not easy to summarize several years worth of experience in a simple blog post. Instead, I will try to focus on some of the more obvious lessons I have learned, the ones I can point at and say “that might have been useful to know/realize the value of when I first started”. Some – or maybe all – of them are perhaps obvious enough that they’re hardly worth mentioning, but then again – everything is obvious is hindsight.
Continue reading “Lessons learned by working at Funcom for five years”