Skip to content

Tag: professional

Fast & Slow

Published by Tj'ièn Twijnstra on 22/11/2025

Previous post I talked about being part of a high performance team and how we’re able to become so effective in term of our output. This post is about a personal observation in how I’m able to work in such an environment and keep up with the team.

I’ve noticed that my contribution is not consistent. It is fast one day and slow the other day. Ow how I used to hate the fact that I’m slow on certain days, or sometimes even extended periods of time, while seeing the fast periods as normal. But I’ve come to understand that these slower days have a purpose.

Sometimes, being slow means that you need to recover and reenergize from a previous high performance day.

At other times the slower days means that for that particular moment I should spend my time working on something else. When it comes to new ideas and design solutions they sometimes it just require me to be in a particular mood, a particular zone in order for ideas and solutions to come naturally and fast.

Sometimes, being slow means I do not have enough input, or just not spend enough time on finding the solution. Sometimes, it means that I just need to stare longer at the particular problem I want to solve.

In the end, I came to realize that being able to be fast and productive I have to accept that being slow at other times is just part of the process and one does not exist without the other. I’m becoming more mindful of my energy, my own flow, my own limitations and my own process. I’m more accepting of myself.

How to use KPIs

Published by Paolo on 21/11/2025

I insist a lot on the importance of entertainment when we design new games. I spoke on this blog regarding the satisfaction of core instincts, and I am aware that someone would need something more actionable and practical. The easy resource is KPIs, which often are seeing like targets to hit. They aren’t in my opinion: they are diagnostic tools for spotting flaws in your gameplay, indicators.

For every feature, we first define the specific utility it provides, and then we measure its impact on player behavior.

Player InstinctThe Utility ProvidedImpact (examples)
Acquisition (Urge to collect)Giving the player interesting things to collect that drive progression.Completion Rate (Quests, levels, and the final game).
Social Connection (Gregariousness)Maintaining engagement and fostering community.Stickiness and high D7 Retention. Track the specific flows to connect with others and also the number of social interactions.
Assertiveness & MasteryThe feeling of power and competence within a core system.Win Rate and Feature Usage.
CuriositySatisfying the urge to discover new things.High Session Length. Qualitatively, the best sign is playtesters who genuinely want more at the end of a prototype. Check also heuristics after a playtest

Prototypes are essential, especially when playtested and attached to heuristics. By leading with the projected impact on player behavior, we demonstrate business value. This is how we continue the pursuit of l’avenir, the radical, unexpected break from the past.

Affording High Performance

Published by Tj'ièn Twijnstra on 18/11/2025

I’ve been working in a high performance environment for many years now. I’m amazed about the output of our small team (6 FTE+1 Free Lancer). To give you an example, we’re currently working on a casual puzzle game with a huge focus on narrative and world building. We’re approaching our 2 week release cadence which includes six to seven new fully animated story chapters and 90+ new levels, while releasing big new features every 4 weeks, with small and big tweaks, SDK updates, data gathering and general improvements, bug fixes and localization in many languages, while making sure we keep analyzing incoming data.

The casual puzzle space in which we’re operating is very competitive with thousands of entries a year with only a handful being able to succeed and enter the top 100. To get there, large teams (50-500 members) and large investments (1M-5M) are our competitors. And even in those teams, pressure to succeed is high and nothing but top performance is expected.

I’ve been thinking how we as a team make sure we are coping with this pressure. I believe we each individually have found a way to cope and collectively as a team found a way to facilitate and support each other. A large contributing factor for our small team is working from home. Not only does it cut out commute every day, saving a lot of time for each member. Working from home also afforded the environment where flexibility can occur. This flexibility in terms of working hours for instance is where some of our team members thrive.

We roughly work between 9-5 with strict attention rules around meetings. At least half of our team enjoys the ability to work during the quiet evenings, or pursuit a particular thought in the night. Others are able to schedule kids pick-up or going to the gym. And all of us enjoy the ability to let life happen and attend any important activity during working hours. Our team treats work as the second most important thing, next to our life outside of work. We cover for each other when someone is ill or experiences life changing events, we plan our schedules and priorities around vacations and time off, we accommodate members traveling the world and working from different time zone and generally we all help each other make it work.

But I think all of this would not be possible without a shared goal, without a shared ambition, without our internal drive to want to succeed. This focus enables us to do all of the above and I’m sure will drive us towards success.

Le futur et l’avenir

Published by Paolo on 16/11/2025

Tatu Pohjavirta, an experienced CEO and futurist, recently posted a brilliant take on why Venture Capitalists, and so developers, get stuck. They ask, “Are you the next Supercell?” or “What’s the next Netflix?”

As Tatu points out, they are looking for le futur, the foreseeable sequel to the present, when what truly changes the world is l’avenir, the radical, unexpected break from the past.

“The true future doesn’t really inherit the present—it breaks from it.”

This is an inability to step outside the invisible grasp of the present. We assume that our current systems are permanent. But they are just historical accidents waiting for the next great interruption.

Building the Unforeseen

Our job as game designers is to increase the risk of predictability by building something genuinely “other.”. Our work is not to design the next of something; it is to design the first of something else.

But how do you design l’avenir when you don’t even have the language for it? This is where your methodical approach, the discipline you apply to strategy and prototyping, becomes the most powerful creative tool.

Design a game where the question becomes, “What is that?”

  1. Deconstruct Your Genre’s Assumptions (The Historical Accident): Take the genre you know best and list all its “permanent” features (e.g., Shooter: First-Person Camera, Health Bars, Headshots). Identify the Historical Accident, the feature that isn’t essential to the instinct (Combat, Acquisition, Escape) but exists purely because of platform or technology limitations 15 years ago.
  2. Prototype the Vocabulary: Tatu asks, “What’s the wildest thing you can imagine into existence that you don’t yet have language to describe to others?” Your job is to prototype the vocabulary. Build a prototype that demonstrates this “wildest thing” using only simple geometric shapes and text. Playtest it with people and watch their reactions.

Your job is to stop being trapped by le futur and start building the unexpected arrival of l’avenir.

Offline networking

Published by Paolo on 14/11/2025

Here is one of the advices I give to people trying to break into the industry: make sure you constantly meet people in real life.

Instead of staying at home preparing and sending résumés to dozens of applications, it is far better to spend two hours per day outside, perhaps at the gym or at a local course on something entirely unrelated to games.

This approach offers three crucial advantages:

1. Maintain Human Energy

You keep your energy levels high because you are meeting and talking with real humans, not just staring at a screen. Waiting for a response to an online application is passive and draining; engaging with the world is active and vital.

2. Design for Reality

When you meet people outside your professional bubble, you gain invaluable insight into their context. I often use these interactions to think about game design.

For example, I currently attend a Catalan language course twice a week. The class is full of nurses and public service workers who are there primarily to get a better contract, not necessarily to master the language. I notice they are tired, easily bored, and don’t want too much complication. Their lives are already full, balancing jobs and children.

How would I entertain someone like them? Not with a complex console game, right? They need a simple casual game, but it has to load fast and get straight into the gameplay. This helps me stay in touch with reality. It forces me to design for the actual, busy human being, not the idealized, endless-time “gamer.”

3. Unlock Lateral Opportunities

You significantly increase your chance of finding job opportunities in lateral sectors by meeting people who have nothing to do with the virtual bubble you’ve created in your online networks.

I honestly have the feeling that nowadays, it is often easier to find a job by going to the gym than by applying on LinkedIn.

Kondō and Synesthesia

Published by Paolo on 13/11/2025

I recently read a fascinating article on Enhance, the Japanese developer behind Tetris Effect and Lumines: Arise. Their company vision is, simply put, a breath of fresh air:

“Experience is king, synesthesia is queen.”

Synesthesia—the involuntary experience generated by stimulating one sensory pathway—and the concept of Kondō (to move emotionally) are the core of their design process.

I have a huge weak spot for companies with this kind of vision. They are hard to execute, but they make so much sense to me.

We are currently living in the era of the product managerization of game design, where every creative decision is filtered through short-term metrics. These experience-first points of view come like a breath of fresh air, reminding us of the original purpose of our craft.

We are humans making entertainment. Focusing solely on automation and metric-driven tuning can make us forget the human spark that creates great things.

Intense design discussions, deep conceptualization, and messy prototyping—that’s what I strive for.

Enhance starts by making music and then breaking that music down into pieces to design the right stages (levels). It is an inverted process that prioritizes the sensory and emotional outcome. It’s so interesting; I wish I could be in that room to see it.

Structured work

Published by Paolo on 12/11/2025

The other day, I was reflecting on how I carved out my space in this industry.

Today, that reality has changed. I have other responsibilities, and I can no longer dedicate the same time to my work. My energy levels aren’t what they were 15 years ago. I worked extremely hard to secure the professional space and flexibility I have now.

I still engage with the medium: I play games, about two hours a week, and spend my evenings studying books and taking online courses. Lately, I’ve been particularly focused on the history of games.

Otherwise, I dedicate my energy to activities outside of the games industry. My passion successfully evolved into a job, and ultimately, a job is a job. With time, one has to work less not more.

The studio lie

Published by Paolo on 11/11/2025

Tim Plöger on LinkedIn shared a critique of the glib advice given to laid-off developers: “You got fired? Then start your own studio!”. This message often gets mixed up, confusing the business problem with the craft problem.

Tim, coming from a focus on the structural and financial side of the industry, correctly points out that starting a studio is not the answer. A studio isn’t just about making games; it’s about allocating people and financials, legal structuring, and sales. That’s a different type of work, and often, a recipe for quick failure for someone whose expertise is in pure creation.

The advice tells you to become an Executive/CEO when all you need to do is remain a Designer/Developer. My counterpoint to Tim was simple: “You don’t have money to buy bread? Well, maybe you have it to buy flour and cook your own bread.”

If your job is to design games, your energy should go into designing games. Spending six months, a year, or even two years sending out résumés without a response drains your energies. It is better to do your job every single day than to beg others while your energy wanes.

When you are laid off, you are given a clean slate, a golden opportunity to build the things you need.

Cook Your Own Bread

You have the chance to prove your adaptive insight (your ability to transfer design knowledge across genres). Here are three immediate actions for any designer, artist, or programmer who is waiting for “the next job”:

  1. Stop Applying, Start Prototyping: Turn your application time into creation time. Build simple, fast, collaborative projects. Don’t worry about polish; worry about fun and flow.
  2. Master the Instincts of the Market: Use this time to apply System Thinking. Pick a successful micro-genre (like the recent Friend-slop games) and try to replicate its core loop. Don’t copy the art; map the instincts (Acquisition, Gregariousness, Escape) that make it tick. This process demonstrates analytical skill far better than any résumé.
  3. Join the Flour-Buyers: Seek out other developers who are also “baking their own bread.” Join forces for a focused, two-week game jam or prototype challenge. The goal is not profit; the goal is to keep your creative engine running and generate concrete work that proves you’re a builder, not a waiter.

The best way to get hired is to be actively doing the job, with or without a corporate logo on your title.

Believe, don’t expect

Published by Paolo on 10/11/2025

I spoke with a former client this week about an experiment we ran. The results are good. The concrete indicators, the raw KPIs, show definite potential.

Yet, the project is under fire. Why? Because the team leader, who has to defend the project to business stakeholders every week, told me: “The expectations were higher.”

This is how good games die unfairly.

You execute a clear vision, the indicators are positive, but because they are “not great” or don’t match someone’s projection, the people who only chase numbers pull the plug.

The Fatal Confusion: KPI vs. Goal

This happens because many business owners—many, many of them—confuse indicators (KPIs) with goals.

  • A KPI is a health report. It tells you where you are bleeding or thriving right now. A good CPI or a solid retention rate is a sign that the game’s core has validity.
  • A Goal is the destination. It’s the vision, the human spark that creates something great.

The biggest mistake is treating the KPI as the Goal.

When you confuse the current retention rate with the final vision, you kill the process. You are demanding a marathon runner win the race on the first lap.

Think of every successful game out there: most of them started small. They grew with patience, dedication, and the belief that the spark was there. They iterated, they built, and they compounded their small, good indicators into great results.

ROI Without Understanding is Ruin

People in charge look for their own immediate ROI without being willing to truly understand how creative work, especially game design I have to say, actually works.

Creativity is not a linear spreadsheet. It’s a system of feedback and refinement. It requires room to breathe. When you cancel a project with good, but not great, indicators, you are sacrificing future compounding success for the shallow comfort of hitting an immediate number.

Let’s start the week with a clear intention: Stop letting fear-driven number-chasers kill projects that deserve to grow. Believe in the spark.

The 100 hours weeks

Published by Paolo on 08/11/2025

Michail Katkoff, founder of the brilliant Deconstructor of Fun podcast, recently made an uncomfortable but valid point about 996: 9 a.m. to 9 p.m., six-days-a-week schedule.

He argues that when you’re early in your career, time is your only leverage. You don’t have the pattern recognition yet. The only way to earn that wisdom, like a surgeon or an investment banker, is through sheer, brutal volume. He says you must work hard before you can work smart.

I agree with him. Volume builds experience, and experience is the only thing that separates the dreamers from those who achieve mastery. But there’s a crucial distinction that separates self-sacrifice from exploitation.

Back in 2014, I was staring at a resume with two incomplete projects. I had lost my second job as a game designer. The industry was already demanding a commitment I hadn’t delivered. It was the turning point where I decided: I am going to stay in this industry, no matter the cost.

The cost was high. Achieving what I have now required working more than 100 hours a week. That is the hard truth of earning my space in this sector. I was fortunate to have a wonderful family who provided emotional and financial support; without them, it would have been impossible.

However, I have never accepted working more than eight hours a day for someone else. I have the luxury of being supported emotionally and economically from my family. The story would have been different otherwise.

This is the critical difference:

  • 996 for the Company is often a management failure masked as ambition. It’s an unsustainable practice where you burn your hours and your health to deliver someone else’s messy vision. It’s exploitation, pure and simple.
  • 100 Hours for Yourself is like hard training, instead. It means building your own systems, and your future.

When I was rebuilding my career, I was awake before dawn, spending my days working intensively and alone. I discovered Michail’s podcast, taking notes at night. I developed my own systems, my own frameworks, and my own unique pattern recognition.

I was working for my competence. I was working to build my own gate so that I could one day invite the market in, rather than begging for access. I couldn’t skip the hours and the volume. I am sure that it’s not the only way, but it’s the one that avoids most of the risks.