<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Fleep on Medium]]></title>
        <description><![CDATA[Stories by Fleep on Medium]]></description>
        <link>https://medium.com/@fleep-prod?source=rss-414b0a6c7738------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ar9aUVSS7hqSTSUMB05Niw.jpeg</url>
            <title>Stories by Fleep on Medium</title>
            <link>https://medium.com/@fleep-prod?source=rss-414b0a6c7738------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 15:46:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@fleep-prod/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Can Video Game Studios Keep Functioning with Full-Time Employees?]]></title>
            <link>https://fleep-prod.medium.com/can-video-game-studios-keep-functioning-with-full-time-employees-6cfc2fc71658?source=rss-414b0a6c7738------2</link>
            <guid isPermaLink="false">https://medium.com/p/6cfc2fc71658</guid>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[game-design]]></category>
            <category><![CDATA[indie-game]]></category>
            <dc:creator><![CDATA[Fleep]]></dc:creator>
            <pubDate>Thu, 26 Mar 2026 08:15:09 GMT</pubDate>
            <atom:updated>2026-03-26T08:15:09.550Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GpHxOw4iDgtyMHpB6ZUsWg.png" /></figure><p>When people ask this question now, they usually ask it from inside the current crisis. Studios are closing, teams are being reduced, projects are delayed or cancelled, financing has become harder to secure, and payroll feels heavier than it did when many of these teams were built. From that angle, the question sounds almost purely financial. Can studios still afford full-time employees. Can they still sustain permanent teams. Can they still function if every project has become more fragile and the margin for error has become smaller.</p><p>I do not think that is the best place to begin. The question is not only about cost, and it is not even only about employment. It is also about history. The studio model did not appear under one single set of conditions, and the industry has a bad habit of treating one inherited form as if it had always meant the same thing. It did not. The kind of studio that made sense in the 1990s was responding to a different production reality from the one many teams face today, even if the word itself remained unchanged.</p><p>In the 1990s, the company form was not some arbitrary industrial illusion imposed on people who simply wanted to create. It corresponded to the real material difficulty of making games at the time. Building a game often meant building much of the technological foundation that would allow the game to exist in the first place. Teams had to create engines, tools, pipelines, and technical solutions that today are often licensed or inherited. The work was heavier, slower, more infrastructural, and much closer to software engineering in the deep sense than many younger creators have had to experience directly. It demanded experience, duration, capital, and a stable structure capable of carrying technical labor across long cycles. Under those conditions, the studio-company form was not irrational. It fit the reality of the work.</p><p>What changed later was not the need for skill or discipline, but the nature of the base that had to be built before creation could begin. As third-party engines became mature enough to carry more of the technological burden, the threshold shifted. By the 2010s, and even more by the 2020s, smaller teams could make real games without first spending years building the machinery beneath them. That did not make the work easy, but it changed where the difficulty lived. For a growing number of teams, making a game no longer required the same kind of heavy internal software structure that had defined earlier eras. The work could become more directly creative earlier in the process. A smaller team could aim at a meaningful result without first resembling a traditional technology company.</p><p>The problem is that while the production conditions changed, the organizational imagination of the industry changed much more slowly. Teams that no longer needed to reproduce the technical mass of an earlier era were still often taught that seriousness looked like the older studio form. If you wanted to be a real studio, you created a company. If you created a company, you hired people. If you hired people, you built continuity through payroll. If you built continuity through payroll, you started needing the kinds of economic justifications that permanent payroll always creates. In other words, a form that had emerged under one set of constraints kept being transmitted as the obvious model under another.</p><p>This matters because the company form never stays external to the work. Once it is adopted, it begins to shape the work from the inside. A studio with permanent employees does not only have people. It has a monthly structure to carry. That means salaries, continuity, predictability, and the permanent pressure to justify the existence of the organization in active terms. It is in that context that a lot of industry language starts to look slightly different. When studios speak about products, services, platforms, retention, or recurring value, some of those choices are certainly genuine creative or strategic choices. But in many cases they also appear as responses to a structural problem. A permanent company with permanent payroll needs more continuity than a single game naturally provides. The game then starts carrying not only its own intention, but also part of the burden of keeping the structure alive.</p><p>That shift is not always dramatic enough to be named clearly while it happens. It often looks sensible, even inevitable. The studio wants to keep talent. It wants to reassure people. It wants to avoid losing a team between projects or even between phases. Employees want stability too, for obvious reasons. Even if full-time employment in games has repeatedly proved fragile, it still appears more stable than a market in which intermittent work is badly supported and often badly organized. So the decision to keep people on payroll is easy to understand from both sides. The problem is not that nobody has reasons. The problem is that these reasons produce consequences inside production that people do not always fully acknowledge.</p><p>A game does not require the same concentration of labor at every moment. Some phases need many hands. Some need fewer. Some require exploration, validation, hesitation, rethinking, or simply time for a design logic to settle before larger fabrication begins. Some moments need a narrow circle of people making difficult decisions, not a wider body of people pushing more material into existence. Creative work does not move in a perfectly flat industrial rhythm, and games certainly do not. They intensify, contract, hesitate, clarify, accelerate, and sometimes need to stop producing in one area so that another area can become coherent enough to support it.</p><p>A studio built around permanent full-time staff has difficulty obeying that rhythm, because the structure itself keeps time differently. Once people are employed continuously, they cannot simply be left without work. So the project starts adapting itself to the labor architecture. Artists need something to do, so visual production advances even if the underlying design still carries uncertainty. Content gets built because a team exists to build it, even if the conditions for that content are not fully stable yet. A level becomes more finished than it should because empty time feels harder to justify than premature concreteness. None of this looks irrational at ground level. It looks like work. It looks like progress. But it changes the sequence in which the game becomes itself.</p><p>That is one of the reasons I do not think the discussion can be reduced to whether full-time employment is financially viable. Permanent payroll changes more than the cost structure of a studio. It changes the order in which production hardens. If the team is there, the studio will tend to use the team. If the studio uses the team, the project will absorb work that may be slightly ahead of its real maturity. Then, because games are cumulative, that work acquires weight. It becomes harder to step back from it later, harder to revise it cleanly, harder to admit that it exists because the structure needed activity rather than because the project had fully earned that degree of execution. A great deal of rework, compromise, and production friction comes from exactly this kind of temporal misalignment.</p><p>This does not mean the desire to keep people is wrong. In many cases it is entirely legitimate. A studio is not only protecting current output when it tries to retain talent. It is protecting trust, continuity, shared language, production memory, and all the subtle things that disappear when teams dissolve too easily. The difficulty is that the industry has been acting for a long time as if the only serious way to preserve that continuity were to attach it to permanent employment inside one company. That assumption is probably one of the places where the current model has become too rigid.</p><p>If a person earns thirty-six thousand euros a year, and the studio only has eight months of real concentrated work for that person on a specific project cycle, the usual interpretation is that the studio has a utilization problem. Either it must find more work to fill the remaining months, or it must accept that the person has become too expensive to keep. But that interpretation already assumes a very crude way of thinking about labor. It assumes that value is only legible when evenly distributed across a calendar. In reality, the project may very well need the full value of that person’s yearly compensation in order to preserve access to their contribution, even if the actual production intensity is concentrated into a smaller window. The problem then is not that the person is somehow too expensive for the work they bring. The problem is that the budget has not been designed to understand retention, timing, and contribution separately.</p><p>A more intelligent budgeting model would be able to recognize that some roles create decisive value during concentrated phases, while still justifying continuity around those phases. The project would pay for the real value of the contribution. The studio could smooth the salary over time. The person could be retained without forcing the production to generate unnecessary work simply to preserve the appearance of constant efficiency. That is more complex, certainly. It asks for more mature financial thinking, more precise phase management, and a better understanding of what kinds of continuity actually matter. But it is also much closer to the real rhythm of authored work than the fiction that every month must show the same density of useful labor.</p><p>This is one of the reasons studio founders often end up carrying a burden that does not really correspond to why they entered the medium in the first place. Many of them are not natural entrepreneurs in the classical sense. They are creators, designers, directors, artists, producers, or technically capable makers whose competence lies in building games, not in inventing sophisticated legal and financial structures from nothing. Yet the inherited studio model expects them to become exactly that. It expects them not only to carry authorship and production, but also to solve payroll design, labor continuity, entity structure, risk segmentation, and long-cycle financial planning. The fact that so many struggle with those demands should not be surprising. The surprising thing is that the industry has normalized those demands so thoroughly that they are often treated as natural.</p><p>Other creative sectors did not eliminate this complexity, but they distributed it differently. Music did not require every serious artist to personally embody a permanent industrial company employing every person around their work. Cinema did not solve continuity by forcing every creative nucleus to become a monolithic studio carrying all labor, all risk, and all forms of exploitation inside one body. Those sectors built other vehicles. They created managers, agents, production entities, financing structures, rights structures, service structures, and all sorts of imperfect intermediaries that could carry different parts of the burden. Games, by contrast, have often folded too much into the studio itself. The studio creates, employs, holds the IP, carries the investment, absorbs the risk, and, if one game becomes an ongoing service, often tries to operate that service too under the same general logic. Once all of that is fused together, permanent payroll starts doing the work of several missing systems at once.</p><p>That is why I do not think the way forward lies in defending permanent teams as such, nor in celebrating freelance flexibility as if precarity had suddenly become liberating. The real need is probably to separate things that the industry has been forcing to live together for too long. A studio may need a stable core. That core may include the people who hold the identity of the work, the continuity of production judgment, the deeper memory of why certain decisions were made, and the ability to tell whether a project is still becoming itself or merely advancing because the structure needs movement. That continuity is real, and it is difficult to preserve without some durable attachment.</p><p>But from there it does not follow that every valuable person, every production layer, and every economic function should sit inside the same permanent payroll logic. A live service operation does not have the same rhythm as a creative studio. An IP portfolio does not have the same needs as an active project team. A successful service game may very well justify a separate operating company with its own employees, its own cost structure, and its own logic of continuity, financed by the service itself rather than by the entire studio carrying that burden as if it were all one thing. In the same way, IP might in some cases be better protected or managed through another legal structure instead of remaining fused with the day-to-day body that makes the next game. None of this is strange in a broader industrial sense. It only appears unfamiliar because the game industry has been unusually attached to the image of the studio as one unified vessel for everything.</p><p>There is also a talent problem here that cannot be solved only by asking studios to behave more cleverly. Many people in games resist freelance life because the conditions around intermittent work are still weak. They are not wrong to resist it. If discontinuous careers are going to become more viable, the industry needs more intermediaries than it currently has. It needs stronger forms of representation, better ways for rare profiles to remain visible between projects, better mechanisms for matching specialist talent to real needs, and perhaps entirely new ways of organizing continuity outside pure employment. In film and music, people often accept discontinuity because the surrounding ecosystem at least offers forms of mediation and leverage. Games have built much less of that. So full-time payroll remains the default way studios try to keep people close, not only because they love the old model, but because the alternatives are still underdeveloped.</p><p>Seen from that angle, the original question starts to change. Of course some studios can continue functioning with full-time employees, and of course some probably should. The real issue is not whether full-time employment can exist. It is whether the inherited studio-company form should remain the default answer to every continuity problem in a medium whose production conditions have changed so much since the era that made that form feel obvious. The older model made sense when making games demanded a heavy internal technical base. It makes much less sense as an unquestioned template for every smaller modern team whose actual production reality is lighter, more modular, and more directly tied to creation than to foundational software building.</p><p>That is why the solutions, if they come, will probably not arrive through one grand reversal. They will come through distinctions made earlier and more carefully. Some roles will need durable attachment because they protect the continuity of the work itself. Some roles will need stronger project-based compensation because their value is concentrated rather than flat. Some studios will need to learn how to build budgets around real contribution windows instead of around the false reassurance of constant utilization. Some successful projects will need to be separated into distinct operating entities rather than being allowed to reshape the entire studio around the needs of a service model. Some founders will need more support than the industry currently gives them in designing structures that fit the real rhythm of what they are making. And the medium as a whole will probably need more agents, managers, producer-networks, or other continuity systems if it wants talent retention to stop depending almost entirely on permanent payroll.</p><p>None of that is simple. It is certainly more complicated than repeating the old formula that a serious studio is a company with a stable full-time team and then discovering, again and again, that the structure starts forcing the work to move at the wrong times for the wrong reasons. But complexity already exists. The industry has just been hiding it inside one inherited form and asking studios to absorb the consequences.</p><p>The real question may not be whether video game studios can keep functioning with full-time employees. It may be whether the medium is finally ready to admit that full-time employment, permanent payroll, IP continuity, live-service operation, and creative authorship are not all the same problem, and do not all need to be solved inside the same structure.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6cfc2fc71658" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Do Game Studios Really Need All These Tools, Meetings, and Documents?]]></title>
            <link>https://fleep-prod.medium.com/do-game-studios-really-need-all-these-tools-meetings-and-documents-673842a26d07?source=rss-414b0a6c7738------2</link>
            <guid isPermaLink="false">https://medium.com/p/673842a26d07</guid>
            <category><![CDATA[game-design]]></category>
            <category><![CDATA[indie-game]]></category>
            <category><![CDATA[game-development]]></category>
            <dc:creator><![CDATA[Fleep]]></dc:creator>
            <pubDate>Thu, 12 Mar 2026 07:57:31 GMT</pubDate>
            <atom:updated>2026-03-12T07:57:31.922Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VTFapmophxxz1eTn-ReRDA.png" /></figure><p>There is a moment that appears in almost every studio, although it rarely announces itself as an important one. A project begins to feel slightly less readable than it did before. Nothing has necessarily collapsed. The team is still working, discussions are still happening, tasks are still being done, builds may still be arriving, and yet a certain kind of opacity begins to settle over the work. A few things have been said in one room and not repeated in another. A few decisions have been made but not really absorbed. A few unfinished subjects have remained in the air long enough to stop feeling urgent, even though they are still shaping the project in quiet ways. Then someone says that perhaps what is needed now is a better tool, or a more regular meeting, or more documentation, or a clearer process, or simply a stronger framework to keep things under control.</p><p>What is interesting about that moment is not that it happens. It would be strange if it did not. Production is full of moving parts, and any collective creative effort that lasts more than a few weeks begins to produce some amount of friction, some amount of drift, some amount of informational blur. It is perfectly natural that teams try to respond to that. What is more interesting is the form that the response often takes. Very quickly, the conversation stops being about the nature of the problem and becomes a conversation about structures. Which tool should be used. Which meeting should be added. Which document should become mandatory. Which review habit should be formalized. Which reporting layer would reassure everyone. The project becomes harder to see, and the instinctive answer is to add another surface on which it can be represented.</p><p>I do not think this instinct is foolish. In many cases it comes from responsibility. People are trying to protect the project from becoming vague, fragmented, forgetful, or falsely optimistic. They are trying to create continuity where there is a risk of loss. They are trying to make sure that a team does not slowly drift apart while still looking busy. The problem is not that studios create structures. The problem is that they often create them before asking a more important question, which is not yet technical, and not even really procedural in the ordinary sense. They often do not stop long enough to ask what, exactly, is in danger of disappearing.</p><p>That question matters because it changes the order of thought. A studio should not begin by asking whether it needs a tool, a meeting, a document, or a process. It should begin by asking what must remain visible. Only then does it become possible to judge whether a specific structure is necessary, what kind of structure it should be, who it is for, how often it should exist, how heavy it should be, and whether it is clarifying the work or merely surrounding it.</p><p>What I have seen over time is that many studios do not really inherit only tools. They inherit production habits. They inherit the atmosphere of what organized work is supposed to look like. Weekly meetings. Task boards. Minutes. Reports. Status updates. Internal review rituals. Shared documents. Roadmaps. Planning sessions. Retrospectives. Dashboards. Follow-up mails. Comment chains. Alignment decks. In isolation, none of these things are absurd. Many are often useful. Some are indispensable under certain conditions. The difficulty is that they are very often adopted long before their actual function has been clearly identified. They enter the studio not always because the work demonstrated a need for them, but because they belong to the general image of serious production.</p><p>Once that happens, the conversation changes in a subtle way. The question is no longer why this thing exists. The question becomes whether it is being used correctly, whether it is being maintained enough, whether people are filling it properly, whether the team has enough discipline around it. In other words, the structure becomes normal before its purpose has been examined. And because it has become normal, any difficulty in production can easily be interpreted as proof that the structure needs to be strengthened, rather than as a sign that perhaps the team is still unclear about what the structure was meant to protect in the first place.</p><p>This is one of the reasons studios sometimes become heavier without becoming clearer. They accumulate representational layers around the work, but those layers do not always increase visibility in the deeper sense. They increase the amount of recorded material. They increase the number of places where activity can leave a trace. They increase the administrative legibility of motion. But that is not always the same thing as making the project itself easier to understand. In some cases it does the opposite, because once enough surfaces exist, the project becomes surrounded by evidence of movement while remaining strangely uncertain in its direction, its coherence, its risks, or its actual state of becoming.</p><p>The assumption underneath this accumulation is easy to understand. It is the assumption that if more things are tracked, then more things are visible, and if more things are visible, then production is safer. This assumption is rarely stated so clearly, but it is present in many studio decisions. It is visible in the way teams respond to discomfort by adding process, and in the way production maturity is often associated with density of oversight. A larger board feels more serious than a smaller one. A documented meeting feels more professional than a spoken one. A team with several review layers appears more controlled than one with fewer. A detailed reporting ritual can create a strong sense of diligence even before anyone asks whether it is producing the kind of clarity that the project actually needs.</p><p>What tends to disappear in that movement is proportion. Not everything deserves the same degree of visibility, and not everything becomes more readable by being equally formalized. Some things should indeed remain explicit, stable, reviewable, and shared. Other things can remain local, transient, lightweight, or simply carried by direct contact inside the team. A strong production culture is not the one that makes everything visible at the same level. It is the one that knows which disappearances are dangerous.</p><p>That is where the work of a producer becomes more interesting than the usual descriptions suggest. It is common to describe production as the organization of work, and of course there is some truth in that. Work must be structured, coordinated, paced, clarified, and protected from collapse. But the more years pass, the less sufficient that description feels to me. It makes the producer sound like a custodian of activity, as though the real job were simply to manage everything that moves. In practice, the role seems to be both narrower and deeper. A producer is not there to supervise every task equally. A producer is there to prevent certain important truths from becoming invisible.</p><p>Those truths are not always the ones most easily captured by ordinary tracking systems. Sometimes they are, but often they are not. A project may have many completed tasks and still be drifting. A team may be very active and still be losing coherence. A roadmap may be full and still conceal the absence of real proof. A studio may be following all its rituals and still be avoiding the one subject that needs to return to the surface. An impressive amount of production activity can coexist with a growing uncertainty about what the project is actually becoming, what it is still protecting, what it has silently abandoned, or what nobody really owns anymore.</p><p>That is why the prior question matters so much. Before deciding which structures to use, production has to identify what kind of invisibility would actually endanger the project. Is the danger that tasks are forgotten. Is it that ownership becomes vague. Is it that decisions leave no durable trace. Is it that the team no longer sees the same priorities. Is it that external partners cannot tell whether progress is real. Is it that the game is changing in ways nobody has named. Is it that confidence is being maintained socially while evidence is weakening structurally. These are not all the same problem. They should not automatically produce the same response.</p><p>I learned part of this by misunderstanding my own processes. In one company, I ran recurring meetings with leads and directors using a shared live meeting-minutes document. The document was not something written after the meeting by one person and distributed afterward. It was present during the meeting itself. We followed it while we talked. We reviewed previous tasks. We discussed recurring matters and new subjects. We wrote decisions live. When an action emerged, it was assigned to someone in that same shared space. Everything about the ritual suggested a fairly strong production surface. It had memory. It had continuity. It had visible ownership. It had recurring rhythm.</p><p>For a while, I thought the system was only partially successful, because I was evaluating it against a function that was not really its primary one. During the week, many people did not go back to the document very much. They did not use it as an active self-management dashboard. They often rediscovered unfinished actions mainly when the next meeting arrived. Judged by the standards of a classic tracking logic, the process looked weaker than I had hoped. If the goal was to create a constantly consulted operational tool, then something seemed to be missing.</p><p>What took me longer to understand was that the process was not underperforming. I was simply reading it through the wrong lens. The meeting was not primarily valuable because everyone reopened the minutes every day. It was valuable because it functioned as a ritual of collective reappearance. It gave the project a place where unfinished things returned before they could sink too deeply beneath the ordinary momentum of work. It provided a recurring confrontation with continuity. It forced promises, delays, decisions, tensions, and unresolved matters back into shared visibility. Its strength was not that it micromanaged the week. Its strength was that it protected the team from forgetting together.</p><p>That distinction stayed with me, because it revealed something broader about production structures. A meeting is not justified simply because meetings are useful in general. A meeting is justified if it protects something that would otherwise fade too easily. The same is true of a document. The same is true of a review process. The same is true of a ritualized report. Their value is not in their abstract category. Their value lies in the function they perform against a specific kind of disappearance.</p><p>The same kind of misunderstanding exists even in personal habits, which is one reason it is dangerous to universalize one working style too quickly. I have written task lists for almost as long as I can remember. I wrote them as a child for homework, later as a student, and later still in professional life. But if someone watched how I used them, they might conclude that I was using them badly, because I do not reread them very often in order to determine what I should do next. Their main function, for me, has rarely been day-to-day navigation. What matters most is the act of writing them. Writing the list helps me memorize, encode, and clarify. It fixes the tasks mentally. Later, when I revisit the list, I often discover that much of it has already been done, and sometimes more than what was written has already happened. At that point the list becomes something else: a confirmation surface, a fallback reminder, a small proof that movement did occur.</p><p>I would not present that as a universal lesson about how task lists should function. In fact, the opposite seems more useful. The same artifact can serve different cognitive purposes depending on the person using it. For one person it is a navigation tool. For another it is a memory aid. For another it is a reassurance mechanism. For another it is useful only in certain rhythms. Once that becomes visible, it becomes much harder to speak as though every production object had one proper use for all minds and all teams. A structure that supports clarity in one context may become dead weight in another, not because the structure is wrong, but because the diagnosis behind it was never properly made.</p><p>This is one of the reasons I have become increasingly cautious whenever people speak about production maturity mainly in terms of adopting the right systems. The studio world is full of institutional mimicry, even when no one intends it consciously. A large studio uses a certain platform, so a smaller one assumes that using it will make them more professional. A well-known company relies on a certain review cadence, so that cadence is reproduced elsewhere, even though the original context may have involved far more people, far more handoffs, and far more structural distance between decisions and consequences. A school teaches future producers how to write certain documents, run certain rituals, and maintain certain surfaces, because these are recognizably professional artifacts, and the artifacts then acquire a kind of authority independent of their underlying necessity.</p><p>Again, this is not really a matter of blame. It is closer to structural gravity. People reproduce what appears to work in systems they admire, and they often do so before they fully understand which problem those systems were actually solving. A large studio may need several layers of process simply because no one can directly hold enough of the project anymore. A small team may not share that condition at all, yet may still surround itself with comparable structures in the hope of importing the stability without importing the scale. What often arrives instead is a heavier administrative skin around a project that is not actually more legible than before.</p><p>Part of what makes this difficult is that process can provide emotional relief even when it does not yet provide real clarity. It feels better to have something than to have nothing. A board full of visible objects can reduce anxiety simply because the work seems to have somewhere to live. A recurring meeting can reduce uncertainty because there is at least a scheduled place where things may return. A new document template can create a sense of rigor before it has produced any real insight. None of this is false. Structures do affect morale and confidence. The trouble begins when that relief is mistaken for proof that the right problem has been solved.</p><p>In many creative projects, the most important production questions are not questions of total oversight. They are questions of proof, coherence, and trust. Can the team show that progress is real, not only busy. Can it show that decisions accumulate into a direction rather than into a pile. Can it show that responsibility is not dissolving into collective vagueness. Can it show that the game being made still resembles the game being promised, not only in pitch language but in production evidence. Can it show that what is being built is becoming more itself, rather than simply becoming more.</p><p>Once those questions become central, another distinction becomes useful, which is the distinction between tracking and visibility. Tracking records motion. Visibility allows something important to remain legible. These two things overlap, but they are not identical. A studio can track many details without increasing the visibility of what matters most. In fact, an excess of tracked information can make the important things harder to read, because weak signals accumulate quickly and begin to compete with strong ones for the same visual space. A minor operational detail, a serious production risk, a passing local blockage, and a foundational contradiction can all become neighboring units inside a system, equally present and equally documented, while remaining profoundly unequal in their significance for the future of the project.</p><p>This is where the notion of signal density becomes important. A readable project is not necessarily the one with the most information available. Often it is the one where the surfaces that remain visible carry a high degree of meaning. Fewer indicators, perhaps, but sharper ones. Fewer recurring rituals, perhaps, but ones that force useful reappearance. Fewer documents, perhaps, but ones that preserve memory, ownership, and proof without demanding that the team narrate every breath it takes. Too much tracked matter can reduce interpretive clarity. It is possible to know more and understand less.</p><p>That seems especially relevant when thinking about external trust. Producers are not always building visibility only for themselves. Sometimes the audience for clarity includes directors, leads, schools, publishers, grant reviewers, investors, or other partners who need to understand not every detail of internal activity, but whether the project is real, whether it is progressing, whether the team is coherent, and whether meaningful evidence exists.</p><p>This broader way of looking at production also changes how one thinks about the profession itself. I would not make that the starting point of the reflection, but it becomes difficult to avoid once the rest is visible. Many junior or trainee producers are taught the visible artifacts of production before they are really taught how to diagnose a team and a project. They learn how to make documents, how to run meetings, how to maintain boards, how to apply reporting structures, how to use software, how to organize follow-up. These are not useless skills. Some are necessary. But when they arrive first, they can quietly invert the logic of the role. Production begins to look like the application of known structures rather than the interpretation of specific conditions.</p><p>The consequence is not always dramatic at first. A young producer enters a studio and quite naturally reaches for the recognizable instruments of the job. A document is created because producers create documents. A process is applied because process is what gives structure. A meeting is scheduled because meetings are how alignment is maintained. A tool is installed because tools are where visibility lives. And when the project remains hard to read, the instinct is to intensify the structures rather than revisit the diagnosis. More reporting. More follow-up. More rigor. More process. More traceability. What is often missing is the earlier capacity to ask what kind of invisibility is actually creating the difficulty.</p><p>That, to me, is one of the deeper weaknesses in how production is sometimes transmitted. We teach artifacts before judgement. We teach forms before diagnosis. We teach the visible expressions of production before the quieter habit of asking what must remain visible, for whom, at what level, and in what rhythm. Once that order is reversed, tools and processes begin to appear in a different light. They stop looking like solutions in themselves and start looking like chosen supports whose legitimacy depends on the precision of the problem they answer.</p><p>This also protects us from a false opposition that does not help very much, which is the old formula that tools should adapt to teams, or conversely that teams should adapt to tools. Both statements come too late, because they begin after the tool has already been granted a place in the structure of the work. The earlier and more useful question is whether the tool is needed at all, and if it is, what disappearance it is supposed to prevent. The same is true of meetings. The same is true of documentation. The same is true of process in general. The mature issue is not flexibility versus rigidity. It is function before adoption.</p><p>Studios do need tools. They do need meetings. They do need documentation. They do need processes. Collective work cannot remain coherent through goodwill alone, and any romantic fantasy of fully unstructured collaboration tends to collapse as soon as time, complexity, or accountability increase. But this does not reduce the importance of the prior question. In fact it makes it more important. Because once one accepts that structures are necessary, the real work begins in deciding which ones are justified, which are excessive, which are stale remnants of previous conditions, which are meaningful only symbolically, and which truly protect something essential from fading out of view.</p><p>That is perhaps the difference between inherited production and intentional production. In one, the studio reproduces the forms it associates with seriousness and then tries to live inside them. In the other, the studio begins from the realities of the team, the project, the risks, the readers, the promises being made, and the kinds of truth that cannot be allowed to disappear. From there, structures are still built, but they are built with clearer necessity. A document exists because without it memory frays. A meeting exists because without it unresolved matters stop returning. A tool exists because without it ownership or proof would become too diffuse. A process exists because without it a critical continuity would be lost. This is not less rigorous. It is more rigorous, because every recurring burden placed on attention now has a reason to exist.</p><p>Over time, that may be what distinguishes a mature studio from one that is merely accumulating the appearance of maturity. Not the number of systems it uses, nor the density of its reporting, nor the variety of its surfaces, but the clarity with which it can answer a simple question about each of them. Why is this here. What does it protect. What would become harder to see if it vanished.</p><p>A studio does not become stronger by surrounding itself with every recognizable sign of production. It becomes stronger when it knows what must not quietly disappear, and when it is disciplined enough to build only the structures that keep those things visible.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=673842a26d07" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Readme First — Why I do what I do]]></title>
            <link>https://fleep-prod.medium.com/readme-first-why-i-do-what-i-do-2aba08b0c5ed?source=rss-414b0a6c7738------2</link>
            <guid isPermaLink="false">https://medium.com/p/2aba08b0c5ed</guid>
            <category><![CDATA[indie-game]]></category>
            <category><![CDATA[game-design]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[videogames]]></category>
            <dc:creator><![CDATA[Fleep]]></dc:creator>
            <pubDate>Mon, 16 Feb 2026 13:38:03 GMT</pubDate>
            <atom:updated>2026-02-16T13:38:03.215Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1d4YU-p3bNISbM2Yt7Rbkg.png" /></figure><p>About twenty years ago, I started trying to change the way games are made. Not in the abstract sense of having opinions about the industry, but in the practical sense of trying to alter habits: how teams talk about what they are making, how they justify decisions, how they teach design, how they interpret feedback, and how they protect an experience from becoming a pile of disconnected solutions. I kept encountering the same contradiction. Many professionals are able to describe what does not work. They can name the symptoms with intelligence. But the work still continues as if the system is fine. The critique remains something you can articulate without it becoming a constraint that shapes the daily decisions of production.</p><p>Over time, what bothered me was not only the creative cost. It was the human cost. A small number of games succeed, sometimes very well. But a vast majority of projects fail, and failure in this industry is rarely gentle. It is not a clean “product didn’t find its market” story. It is teams being exhausted, relationships being damaged, years of work being swallowed, and people leaving the craft with a quiet bitterness. Each failure also creates a second-order damage: it erodes trust. The people who fund projects — publishers, investors, institutions — learn to treat teams and authors as unreliable, not because creators lack talent, but because the path from intention to final product is too often unstable.</p><p>What makes that instability so persistent is that it rarely comes from a lack of competence. Teams do not fail because they forgot to design, or because they lacked methods, or because they did not care. They fail because the link between intention and production is fragile, and because there is rarely a clear responsibility for guarding meaning through time. In film, it is normal to have producers whose role is not to replace the director, but to protect the conditions of the work, keep it coherent, and ensure that what is being made remains legible to stakeholders without being reduced to logistics. In games, studios should often play that role internally, but they are also pulled into acting like a single “global director” of everything at once — creative, technical, managerial. Publishers could, in theory, push teams to keep their intent coherent, but publishers often act primarily as distributors and commercial operators. The result is that, during production, nobody is clearly tasked with staying on guard for meaning. The project may be managed, tracked, shipped, even polished — and still drift.</p><p>Over the last twenty years, a great number of design approaches have emerged, and many of them brought useful structure to practices that used to be implicit. But most of that progress has focused on what to build, how to iterate, how to validate, how to ship. It has been far less demanding on the deeper question: why this specific experience should exist, what it must protect, and what it must refuse. This weakness also shows up later, when marketing enters the picture. I have seen, many times, marketing teams come after the game is already shaped (or late in production) and try to “find” the right meaning to sell it to a target they decide. Too often that meaning is decorrelated from the actual intent of the team. I have also seen projects built with a certain audience in mind, only to be sold to another audience because the publisher’s commercial narrative took a different direction. When that happens, even a competent project becomes unstable: internally, because the team loses a shared anchor; externally, because the market promise no longer matches what the game truly is.</p><p>This is why “before mechanics” matters, but not as a slogan and not as a call to “do more design.” It is close to the “form follows function” mantra people increasingly repeat, but rarely apply with enough seriousness. “Before mechanics” matters because if the intent is not designed — designed as a reason, as a set of constraints, as an authored target — then mechanics will inevitably become the substitute. Systems, features, content, and production velocity will fill the space that the intent did not occupy with enough force. And this is not only something you do at the start. Intent is not a statement you write once; it is something that must be carried through production until the final product. Otherwise, the project can still ship, sometimes even succeed by external standards, while no longer carrying what made it worth funding, worth building, or worth sacrificing for.</p><p>Two years ago, I stopped trying to “change the industry” in the large sense. Not because the industry is incompetent or fundamentally broken. Many things work. There are real experts, real talent, real craft. What I realized is that the industry does not necessarily need to be transformed into something else. It may need small additions in specific places — small responsibilities, small tools, small forms of discipline — so that intent does not evaporate under pressure. In the past, some people heard me as if I was advocating renaming all existing producers, or inventing a completely new role with completely new practices. That is not what I mean anymore. I am not trying to replace the producer role as the industry uses it. I am trying to add a feather to that cap: a layer of production responsibility that treats intent as a material that must be carried, protected, and expressed through time.</p><p>If that sounds abstract, it becomes concrete very quickly when you look at what teams actually struggle with. A project does not lose its intent through one bad decision. It loses it through a long series of small, reasonable decisions that are never compared back to an explicit authored target. The game becomes a negotiation between forces: design ambitions, production constraints, market assumptions, stakeholder preferences, feedback data, team fatigue, technical debt. None of these forces are illegitimate. The problem is that without a shared structure that protects the “why,” these forces do not negotiate against an intent — they negotiate against each other. The result is rarely an intentional experience. It is an accidental one.</p><p>This is also why the conversation about failure cannot remain purely internal to teams. When projects repeatedly collapse into accident, the ecosystem responds. Funding becomes more cautious. Decision-makers look for guarantees. They seek proven formulas, safe genres, predictable loops, and familiar metrics. They look for reassurance rather than authorship. And when that happens, the industry does not only lose money; it loses the conditions that allow original work to be funded in the first place. Trust is not a moral quality. It is an economic material. Without it, risk capital stops flowing toward teams and starts flowing toward templates.</p><p>So the real question is not “how do we get better at building features.” The real question is “how do we make intent survivable.” How do we make the authored target explicit enough that a team can protect it, reshape it intelligently under constraint, and still recognize when it has been lost. How do we keep production from turning meaning into decoration. How do we preserve authorship without pretending that authorship means control. And how do we produce evidence — inside the work itself — that the process is coherent and trustworthy, not because it is rigid, but because it is legible.</p><p>This is why I am writing now. Much of what I am articulating are things I believed long ago, sometimes more than twenty-five years ago, but believing is not enough. What matters is to build structures that others can use: a vocabulary, a sequence, a set of lenses that can survive production realities instead of collapsing into them. I should have done this work earlier — especially when I had institutional responsibility in education — but I was still caught between two inadequate strategies: trying to change the system from inside, or complying too closely with industry “standards” in order to stay aligned. Neither approach produced the missing layer. Writing is where I can build it with the precision and continuity it requires.</p><p>If you want a simple entry point into this body of work, I do not think everyone should start with the lessons immediately. A lighter entry is the <em>Intent Files</em> series, which is written to introduce the core ideas and vocabulary without demanding a full structured curriculum. For readers who want to go deeper and install the scaffolding, the longer arc is a four-volume series called <em>Foundations of Intentional Game Design</em>. Volume I contains five foundational lessons. They are not “tips.” They are not a list of best practices. They are meant to install an intellectual scaffolding — so that when you talk about mechanics, systems, content, playtests, and scope, you are not improvising meaning on top of them. You are carrying an intent that has been designed clearly enough to resist dilution.</p><ul><li>Read the Intent Files → <a href="https://medium.com/@fleep-prod/the-intention-files-1-the-myth-of-chaos-why-structure-creates-freedom-68c4675c436a">https://medium.com/@fleep-prod/the-intention-files-1-the-myth-of-chaos-why-structure-creates-freedom-68c4675c436a</a></li><li>Foundations Volume I — Lesson 1 → <a href="https://medium.com/@fleep-prod/the-intention-files-1-the-myth-of-chaos-why-structure-creates-freedom-68c4675c436a">https://medium.com/@fleep-prod/the-intention-files-1-the-myth-of-chaos-why-structure-creates-freedom-68c4675c436a</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2aba08b0c5ed" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Craft of Influence 4 — The Continuity Ledger: Making Coherence Survive Contact With Reality]]></title>
            <link>https://fleep-prod.medium.com/the-craft-of-influence-4-the-continuity-ledger-making-coherence-survive-contact-with-reality-0878f6ef49cf?source=rss-414b0a6c7738------2</link>
            <guid isPermaLink="false">https://medium.com/p/0878f6ef49cf</guid>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[indie-game]]></category>
            <category><![CDATA[game-design]]></category>
            <category><![CDATA[videogames]]></category>
            <dc:creator><![CDATA[Fleep]]></dc:creator>
            <pubDate>Fri, 13 Feb 2026 08:57:36 GMT</pubDate>
            <atom:updated>2026-02-13T08:57:36.989Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3xgcsZTtw_iip9OIPJydeQ.png" /></figure><p>Most teams already have documents. They have decks, notes, boards, checklists, folders of references, and a graveyard of decisions that once felt obvious. The issue is not the absence of writing. The issue is that the writing rarely sits where the work actually changes, and therefore it rarely survives the moments when it matters.</p><p>Authored coherence does not disappear because people forgot what they wanted. It disappears because decisions accumulate faster than memory can hold them, and because the project keeps moving even when the logic that justifies it is no longer explicit. At that point, the work is not only built. It is rewritten — quietly, by trade-offs that were locally reasonable and globally invisible.</p><p>This article proposes a minimal remedy: a continuity ledger. Not as documentation, and not as bureaucracy, but as a small trace that makes meaning-carrying decisions legible enough to be protected. This is not a “standard practice” that already exists everywhere under a stable name. Some teams have fragments of it, informally, inside experienced production culture. The point here is to make the missing piece explicit enough to be shared, taught, and maintained when the project becomes heavy.</p><p>There is a practical reason this matters. In most production environments, the unit of truth is what can be closed: tasks, features, bugs, milestones. That language is necessary, but it is incomplete for authored work. A project can be efficient while becoming incoherent, because coherence lives in relationships that can drift without anything breaking.</p><p>So the last question in this series becomes simple to state, and difficult to answer without a method. If influence is not persuasion but architecture, what is the smallest architecture that makes continuity survive fatigue, addition, disagreement, and time.</p><h3>The Unit That Drifts Is Not The Feature. It’s The Meaning-Carrying Relationship.</h3><p>One reason teams lose coherence while feeling productive is that they track the wrong unit.</p><p>Features are countable. Tasks are closable. Milestones can be declared. Bugs can be reduced. All of that matters, and no serious work survives without it. But authored experiences are not assembled from features the way a machine is assembled from parts. They are assembled from relationships that teach the player what matters.</p><p>A mechanic is not only a mechanic. It is a relationship between effort and outcome, between risk and reward, between attention and consequence. A progression system is not only a progression system. It is a relationship between time invested and identity gained, between repetition and mastery, between learning and permission. A narrative beat is not only a narrative beat. It is a relationship between expectation and rupture, between trust and betrayal, between curiosity and closure.</p><p>These relationships are where meaning lives. They are also where drift hides, because they can change without anything “breaking.” A build can function perfectly while the experience quietly shifts what it is training the player to care about. The project can remain efficient while the game’s internal logic becomes ambiguous. This is why teams sometimes reach a late stage and discover a strange discomfort: everything is there, but the work no longer has a clear temperature. It does not fail. It dissolves.</p><p>In practice, protecting authorship means protecting these meaning-carrying relationships. It means treating them as a production reality rather than as a design preference. It means being able to say, at any point in the project, which relationships are currently doing the heavy lifting of the intended experience, and which relationships have become dominant without being intended.</p><p>That ability is rarely present by default, because the daily language of production tends to privilege what can be closed. The craft of influence begins when a team installs a second language: not only what was built, but what the build now does to someone.</p><p>Once the unit is understood as relationship rather than feature, it becomes easier to see why drift is often invisible. Relationships can be rewritten without the project feeling like it made a dramatic decision. Something can be removed or simplified. Something can be added and layered until attention is redistributed. And sometimes nothing is added or removed at all: proportions change, pacing shifts, friction moves, reward balance drifts, and the relationship changes its temperature. In every case, the build can remain stable while the experience becomes different.</p><h3>An Uninterpreted Adjustment Is Not Neutral. It’s A Rewrite.</h3><p>The moment a project becomes heavy, the work begins to rewrite itself in small increments. This rewrite rarely announces itself as a dramatic pivot. It happens through ordinary production moves that are locally reasonable and therefore easy to treat as neutral.</p><p>The most visible moves are subtraction and addition. Something is removed, simplified, postponed, merged. Something is layered on top, expanded, enriched, “just one more loop” that seems to add depth. Both moves can be correct. Both are part of real production. But neither is neutral, because most elements are not only content. They are meaning-carrying relationships. They teach the player what matters, what to attend to, what to repeat, what to fear, what to optimise, what to ignore.</p><p>There is a third move that is often even more dangerous precisely because it leaves the feature list untouched. The project rewrites itself through tuning. Numbers shift, placements move, friction is adjusted, the difficulty curve is softened, rewards are redistributed, pacing is altered, timings are tightened or stretched. Nothing is added or removed, and yet the experience can become a different conversation, because relationships live in proportions. When the ratio between effort and payoff changes, when risk is redistributed, when the game stops demanding a certain kind of attention, intent can remain present in words while being lost in feel.</p><p>This is the common error: treating these moves as if they were only production hygiene. Subtraction feels like scope control. Addition feels like richness. Tuning feels like polish. And because those labels sound responsible, the project continues without naming what was actually altered.</p><p>In authored work, what is actually altered is always the same kind of thing: a relationship. When a meaning-carrying element is removed, the relationship it created does not simply vanish; something else becomes dominant because it remains. When a meaning-carrying element is added, the new relationship does not simply coexist peacefully; it competes for attention, it introduces incentives, it teaches a loop, and therefore it changes what the player learns to value. When tuning shifts proportions, the relationship can invert without the team noticing, because the build still “contains the same systems,” only with a different temperature.</p><p>This is why authored coherence is rarely lost through a single bad decision. It is lost through a series of locally reasonable moves that were never interpreted as meaning-changing. The work keeps moving, the build keeps evolving, and the centre becomes harder to locate because the project has been rewritten without ever naming what was rewritten.</p><p>So the producer craft introduces a rule that applies equally to all three: an adjustment is not complete until its meaning has been interpreted and continuity has been explicitly handled. Not interpreted philosophically, and not at the level of vague intention, but interpreted concretely as relationship. What did this adjustment make more dominant. What did it weaken. What did it displace. What did it replace. What did it force the player to pay attention to now.</p><p>Sometimes that interpretation leads to a replacement obligation. If something was removed, what now carries the function it had. Sometimes it leads to a containment obligation. If something was added, what boundaries must now be enforced so the original conversation does not become secondary. Sometimes it leads to a calibration obligation. If tuning has shifted the temperature of a relationship, what is the deliberate target state, and what does the project choose to preserve by returning to it. In all cases, the project remains authored because the rewrite is made visible rather than accidental.</p><h3>The Continuity Ledger: Where Addition, Subtraction, And Tuning Stop Being Invisible</h3><p>Once meaning-level continuity becomes a unit of responsibility, another need appears immediately: memory.</p><p>Not memory as archive, and not memory as documentation for outsiders, but memory as production infrastructure. In a living project, adjustments accumulate faster than any one person can hold them. And because so many moves are locally rational, it becomes easy to forget which ones threatened continuity at all. The project continues, and drift is discovered only in retrospect, when the game no longer feels like the thing that was being made.</p><p>The continuity ledger is a minimal remedy to that problem. It is not a thick layer of process. It is simply a place where the project records the meaning of its own <strong>continuity events</strong> — moments where coherence was at risk, was interpreted, and was either restored or deliberately rewritten. Some teams do fragments of this implicitly, inside experienced production culture. The point here is to make the missing discipline explicit enough that it does not rely on personal memory, informal power, or heroic attention.</p><p>In most production environments, the unit of truth is “done.” That language is necessary, but it is incomplete for authored work. A team can close tasks efficiently while rewriting the experience unconsciously, because “done” does not require interpretation. The ledger exists to install a second unit of truth: the experiential consequence of decisions, and the way continuity was protected against silent drift.</p><p>In its minimal form, the ledger does not try to log everything. It records only continuity events: meaning-level moments where something became dominant unintentionally, something essential began to fade, or a tuning/addition/cut threatened to rewrite the promise. Many events never need a formal meeting. The producer’s work is continuous: small check-ins, quick verifications, short arbitrations. Large meetings are reserved for crisis, or for moments where the arbitration must become explicit and shared. The ledger is the instrument that allows those continuous interventions to leave a trace when the project genuinely needs to remember.</p><p>Scale matters here. In large teams, this is not a log of every tweak. Most adjustments never enter it. Many tuning moves are bundled into a single event per pass, per milestone, or per sprint, because the point is not the number — it is the direction. The ledger scales through filtering and aggregation, otherwise it becomes noise and defeats its own purpose.</p><p>A continuity event, in its simplest form, captures five facets:</p><p><strong>An intent snapshot</strong> is a restatement of what the game is currently trying to do to a player, expressed as experience rather than as a feature list. It is not the original pitch preserved as a relic. It is the promise the current build is actually making, the one that must remain legible as the work moves.</p><p>A <strong>drift signal</strong> names what was becoming dominant without being intended, or what was fading that must remain present. Drift is not treated as shame. It is treated as a phenomenon the project can observe early, while it is still cheap to correct.</p><p>An <strong>event record</strong> captures what disturbed continuity: what adjustment, addition, cut, or tuning pass triggered the signal, and which meaning-carrying relationship was touched. Not in technical detail, but in experiential consequence: what the player was being trained to care about, what kind of attention was being rewarded, what kind of behaviour was being made dominant. A tuning move belongs here only when it changes the temperature of a relationship, not when it simply fixes a local issue.</p><p>A <strong>resolution record</strong> answers the stabilizing question: how was continuity restored?<br>This is not a description of the adjustment. It is a description of the intervention.<br>Sometimes the correct move is to revert. Sometimes it is to modify the adjustment until it preserves the intended relationship. Sometimes a removed function must be carried elsewhere, because the project cannot afford the original form — but it still refuses to lose the meaning it produced. Sometimes an added layer must be contained so it enriches without becoming the centre. Sometimes tuning must be recalibrated back to a target temperature. And sometimes the team chooses a deliberate rewrite — explicitly updating the promise rather than letting the project drift into it by accident.</p><p>A <strong>decision ownership note</strong> records who arbitrated and under which hat. Direction holds intention. Production holds continuity through constraint. In small teams hats can move, but the ledger preserves which responsibility was being exercised at the moment of arbitration, so continuity does not collapse into informal power.</p><p>These facets are small, but their effect is large because they change what the project remembers. They create a memory that does not depend on mood. They create a way to recover coherence after a difficult week. They create a way to tell the difference between building and rewriting, between enriching and diluting, between simplifying and eroding.</p><p>One unexpected benefit follows from this immediately. The ledger turns playtesting into something more precise. Instead of testing “the game” and collecting noise, the project can test the relationships that were touched by continuity events. Each event implies a hypothesis: if the resolution preserved the promise, then a player inside the intended conversation should read the experience in a specific way, and should learn the same kinds of priorities the game claims to reward. When that reading fails, the answer is not endless addition. It is correction: calibration, containment, replacement, or deliberate rewrite.</p><h3>Feedback Becomes Interpretable When It Enters A Conversation</h3><p>A continuity ledger also changes the way feedback behaves inside a team, because it changes what feedback is allowed to do.</p><p>Feedback is necessary because it reveals what the work actually communicates. It is also dangerous because it arrives mostly as preference, and preference tends to reward expansion. If every comment is treated as equally authoritative, the project becomes a negotiation between incompatible desires, and negotiation almost always pushes toward addition. The work expands toward general accommodation, which is a quiet way to lose authored specificity.</p><p>So the project needs a frame. One part of that frame is the target group.</p><p>This notion can sound external, and it can be misused as a marketing cliché, but at the level we are dealing with here it is simply an authorship tool. A game cannot speak to everyone at once. It chooses, consciously or not, what kinds of players it rewards, what kinds of attention it asks for, what kinds of patience it requires, what kinds of mastery it respects. That is not commerce. That is the identity of the experience as a conversation.</p><p>When that conversation is undefined, feedback becomes a referendum. The team treats every reaction as a vote on what the game should become. Over time, the game becomes a compromise between incompatible conversations.</p><p>When the target group is defined, feedback can be weighted rather than absorbed. A comment from someone inside the intended conversation carries a different kind of meaning than a comment from someone outside it. Outside comments can still reveal friction, confusion, accessibility barriers, and unintentional cruelty. But they do not automatically rewrite the work. Inside comments reveal whether the promised conversation is working, whether the experience is teaching what it intended to teach, and whether the game is actually rewarding the forms of attention it claims to reward.</p><p>The ledger is where this interpretation becomes stable. Drift signals can record when a recurring type of feedback indicates that a new layer is beginning to dominate. Event records can capture what additions were made in response to testing and what those additions risk diluting. Resolution records can capture how a legitimate problem was solved after a cut or a simplification (including replacement after a cut, containment after an addition, or calibration after tuning). Containment and calibration records can capture how a useful new system was kept from becoming the new centre, or how a tuning pass was pulled back toward a deliberate target state so the original promise remains dominant.</p><p>This is how a team stops treating feedback as an instruction set. Feedback becomes what it should be in authored work: information that must be interpreted under responsibility, against a promise that the project is willing to protect.</p><h3>The Doorway To Valuation</h3><p>Once continuity becomes traceable, another shift becomes possible, one that has been present in the background of this whole series.</p><p>When trade-offs, replacements, drift signals, and calibrations are visible, the project no longer relies on mythology to justify its coherence. It contains evidence of its authored labour. Not evidence of quality, because quality is lived by players and cannot be guaranteed by a ledger, but evidence of continuity: the project did not become what it became by accident alone.</p><p>That evidence matters because it changes what can be discussed without betraying the work.</p><p>Without continuity traces, value conversations tend to collapse into two crude extremes. Either meaning is treated as sacred and therefore unmeasurable, which makes it difficult to defend inside production. Or meaning is reduced to metrics that are easy to count, which betrays the work by replacing authored intention with optimisation.</p><p>A continuity ledger does not solve valuation by itself. It makes the right kind of valuation possible later: valuation that begins from what the work was trying to do, what the work actually became, and how the project preserved or rewrote its internal logic through time. It creates a bridge between lived experience and production decisions. It is where intent and meaning stop being talk and become traceable practice.</p><p>That is the moment where a framework becomes relevant, not as a way to turn art into numbers, but as a way to speak about value without betraying meaning, because the work has already learned how to keep meaning continuous long enough to be seen.</p><p>And in that sense, the craft of influence returns to its simplest form. The producer’s real power is not control. It is continuity. It is the ability to keep authored relationships intact while reality tries to rewrite them, and to do so with a method that can be taught, adopted, and carried by a team even when the project becomes heavy.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0878f6ef49cf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Foundations of Intentional Game Design — Lesson 9]]></title>
            <link>https://fleep-prod.medium.com/foundations-of-intentional-game-design-lesson-9-e438fa6f49f0?source=rss-414b0a6c7738------2</link>
            <guid isPermaLink="false">https://medium.com/p/e438fa6f49f0</guid>
            <category><![CDATA[game-design]]></category>
            <category><![CDATA[videogames]]></category>
            <category><![CDATA[indie-game]]></category>
            <category><![CDATA[game-development]]></category>
            <dc:creator><![CDATA[Fleep]]></dc:creator>
            <pubDate>Wed, 11 Feb 2026 17:09:47 GMT</pubDate>
            <atom:updated>2026-02-11T17:09:47.346Z</atom:updated>
            <content:encoded><![CDATA[<p><em>AGENCY: FEELING IN CONTROL (OR NOT)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g4F8L9Vs-9yLZK5x8Ey3LA.png" /></figure><h3>The Strange Moment When a Game Keeps Moving Without You</h3><p>There is a particular discomfort that appears in play, and it is easy to mistake it for boredom. The player is still pressing buttons. The game is still responding. Progress is still happening. And yet something feels slightly removed, as if the experience has begun to carry itself. The hands are present, but the mind is no longer fully inside the action. Later, when asked about the session, the player struggles to describe what they actually decided. They can list what they did, but not what they chose. The memory is procedural rather than lived.</p><p>I’ve watched this happen in projects that are technically competent, sometimes even generous. The interface is clear. The objectives are explicit. The friction is reduced. The game does not want the player to be lost. It does not want the player to waste time. It wants to respect the player’s session. And yet the player’s sense of participation thins out, not because the game is empty, but because the player is no longer being asked to <em>author their own passage</em> through the experience. The game offers tasks, and the player completes them. The motion is real, but the ownership is faint.</p><p>The opposite discomfort exists too, and it can be just as corrosive. A player is highly attentive, even tense, but not because they feel engaged. They feel watched by the system, punished by it, or constantly at risk of being wrong in a way they could not have anticipated. They hesitate before acting, not out of strategy, but out of mistrust. In that state, the game still contains agency in the technical sense — inputs still matter — but the player does not feel in control. They feel managed by hidden rules, or trapped in a contract that does not clearly state what is being asked. The result is not empowerment. It is a kind of learned caution, where agency exists but feels unsafe to use.</p><p>Both discomforts point to the same thing: agency is not simply the presence of interaction. It is the <em>felt relationship</em> between a player’s intentions and the game’s responses. When that relationship is coherent, the player experiences control even in difficulty, because difficulty reads as something they can learn. When that relationship becomes incoherent, the player can lose the feeling of control even in smooth play, because the game begins to feel like a conveyor belt. Agency is a perception before it is a mechanic. It is a sensation of authorship: the feeling that what happens next is meaningfully connected to what the player decided to do.</p><p>This is where the previous lessons feed directly into this one. Time taught us that minutes are not neutral; they are shaped by what the player must hold and what the system holds for them. Contrast taught us that meaning forms through differences that change the player’s posture and make moments legible. Agency sits inside both. If time becomes overly smoothed and contrast becomes overly cosmetic, the player can be kept moving without being asked to decide. If time becomes harsh and contrast becomes punitive, the player can be forced to decide under conditions that do not feel learnable, and decision collapses into fear. The same tools that shape meaning can therefore either strengthen agency or quietly dissolve it, depending on how the contract treats the player’s intention.</p><p>Lesson 9 is about that contract. It is about learning to distinguish between a game that allows the player to act, and a game that allows the player to feel responsible for action. It is about seeing the specific design moves that create a sense of control, and the specific design moves that produce its opposites: passivity disguised as progress, or anxiety disguised as challenge</p><h3>Quiet Agency: The Small Places Where Control Is Granted or Taken Away</h3><p>Agency is often discussed as if it were a headline feature: branching narrative, open world freedom, emergent systems, multiple endings, deep builds. Those are real forms of agency, but they are not where the feeling of control is most consistently made or lost. The feeling of control is usually decided in small places, in the micro-contract that governs minute-to-minute participation: what the game lets the player infer, what it insists on explaining, what it allows the player to attempt, what it quietly forbids, and how it reacts when the player tests the edge of the system.</p><p>One of the simplest quiet tests is to notice what happens when a player tries something slightly off-script. Not sabotage, not nonsense, just a plausible deviation: approaching an encounter from an unexpected angle, ignoring a suggested route, attempting to use a tool earlier than intended, choosing not to pick up the obvious item, lingering in a space when the game seems to want forward motion. In some games, these deviations are met with a form of acknowledgment. The system may not allow everything, but it behaves as if it understands the player is making an intention, and it responds in a way that keeps intention meaningful. A door might be locked, but it reads as a real door with a real reason to be locked. An area might be too dangerous, but it communicates the danger through the world rather than through an invisible wall. The game says, in its own language, “you can try, and the system will answer you.”</p><p>In other games, the same deviations meet a different response. The system does not respond so much as it rejects. The player collides with a boundary that has no meaning except that it is a boundary: an invisible wall in an open landscape, a sudden “cannot do that” prompt, a tool that simply fails without explanation because the sequence has not yet reached the correct flag. The player learns that intention exists, but only inside approved channels. The game still contains a lot of activity, and the player may still enjoy it, but the feeling of control thins because the world does not feel conversational. It feels like a guided track. The player’s mind begins to stop asking “what do I want to do here,” and starts asking “what does the game want from me now.”</p><p>This is not only a matter of open-world versus linear. Many linear games produce strong agency because they treat the player’s intention as something to be respected inside the corridor. They allow experimentation with timing, with risk, with observation. They offer space for the player to choose how to approach the same problem, even if the problem is bounded. Conversely, many large open games produce weak agency because the apparent freedom is mostly navigational, while the meaningful choices are pre-shaped into task completion. The player can go anywhere, but what they can <em>decide</em> becomes thin. The world becomes a map of errands rather than a space of authorship. The player experiences freedom of movement but not freedom of intention.</p><p>Another quiet place where agency forms is in information. A game can be generous with signals while still allowing the player to own inference. It can give hints without giving conclusions. It can guide without removing the work of understanding. In those cases, the player feels in control because understanding feels like something they are doing, not something being delivered. A different kind of generosity externalises intention entirely. The UI holds the thread, the path, the relevance, the urgency. The player follows. The system becomes a director that never stops giving marks. This can produce smooth play, but it also produces a specific loss: the player stops carrying purpose. The player can succeed while remaining passive, and success without internal purpose is one of the quickest ways to make actions feel empty.</p><p>Failure is another micro-contract that determines agency. When failure is readable, it tends to strengthen control even when it is costly, because the player can connect outcome to decision. The player learns what mattered. The player can attempt again with changed behaviour. The system feels learnable, and a learnable system allows agency to survive. When failure is unreadable, it damages control even when it is not particularly punishing, because it breaks the link between intention and consequence. The player feels that outcomes are produced by hidden rules, unclear expectations, or arbitrary thresholds. Even if the game is technically fair, it does not feel fair, because the player cannot form a stable model of how to act responsibly.</p><p>The same applies to success. A success that acknowledges the player’s intention strengthens agency. It tells the player that what they did was not merely permitted but understood by the system. A success that feels automatic weakens agency, even if it is rewarding, because the player cannot locate what their decision contributed. This is why some games feel strangely hollow even when they shower rewards: the rewards are decoupled from ownership. They occur because the player stayed on the track, not because the player authored a solution.</p><p>There is also an often-overlooked form of agency that lives in tempo. Some games allow the player to create their own rhythm: to pause, to plan, to accelerate, to wait, to take a risk now or later. That temporal freedom is a form of control because it lets the player decide what kind of engagement they want in that moment. Other games lock tempo tightly, not only through real-time pressure but through continuous prompting and interruption, so that the player is always being pulled into the next beat. The player may still be busy, but the session feels owned by the system rather than by the player. Agency is reduced not by removing choices outright, but by removing the space in which choice can be inhabited.</p><p>All of these micro-structures point to a central fact that is easy to forget when talking about “agency” as a feature. Agency is not primarily about how many options exist in theory. It is about whether the game behaves as if the player’s intention matters, and whether the player can learn the consequences of intention through play. When the contract respects intention, the player feels in control even inside constraints. When the contract ignores intention, the player can be given enormous content and still feel like a passenger.</p><h3>Agency as the Felt Link Between Intention and Consequence</h3><p>Agency is often treated as a property a game either has or does not have. If the player can move, aim, choose dialogue options, and trigger outcomes, then agency is assumed to be present. But the lesson so far suggests a more precise claim: agency is not the presence of interaction. It is the felt relationship between a player’s intention and the game’s response. A game can be highly interactive and still produce weak agency if the player’s intentions do not seem to matter, or if outcomes do not feel learnable, or if the system carries the thread so completely that the player never needs to author purpose internally. Conversely, a game can be constrained and still produce strong agency if it treats intention as meaningful, answers attempts coherently, and allows the player to build a stable model of consequence.</p><p>This is why “feeling in control” is not a trivial subjective mood. It is an experiential judgment about whether the world is answerable. When the world is answerable, the player can take responsibility for what happens. They can say, even if only implicitly, “that happened because I did this,” and then adjust behaviour in a way that feels rational. When the world is not answerable, the player can still press buttons, but responsibility becomes difficult to hold. Outcomes begin to feel like the product of hidden rules, scripted enforcement, or arbitrary permission. In that state, the player’s posture shifts. They may become compliant, doing only what is clearly signaled. They may become anxious, hesitating because action feels unsafe. They may become apathetic, continuing out of momentum without ownership. These are not personality traits. They are predictable responses to contracts that either support or dissolve agency.</p><p>A useful way to define agency in design terms is to treat it as a three-part loop: <strong>intention, attempt, interpretation</strong>. The player forms an intention, the player performs an attempt through the interface, and then the player interprets the game’s response in order to update their model. Agency is strong when this loop remains stable. The game does not need to reward every attempt with success, but it must reward attempts with information that can be used. Agency weakens when the loop breaks: when intention cannot be expressed because the interface forbids it silently; when the attempt is expressed but the response is rejection without meaning; when the response occurs but is too noisy or opaque to be interpreted; when interpretation becomes pointless because the system overrides intention anyway. The player can still act, but action stops being a form of authorship and becomes a form of compliance.</p><p>This also clarifies the relationship between agency and guidance. Guidance is not automatically anti-agency. Good guidance can support agency by making the space of intention readable: showing what kinds of actions are possible, indicating stakes, preventing wasted experimentation that teaches nothing. The problem begins when guidance shifts from clarifying possibility to carrying purpose. If the system holds the thread so completely that the player never needs to decide what matters next, the player’s agency becomes thin. The player becomes a performer of tasks rather than a holder of intention. That loss is subtle because the game can still feel smooth and respectful, but the feeling of control fades because control is not only about not being lost. It is about being needed as an author of the next step.</p><p>A parallel distinction exists between agency and freedom. Freedom often describes the number of available options. Agency describes whether the options are meaningfully connected to intention and consequence. A game can offer many options and still produce weak agency if options do not lead to interpretable differences, or if the world rejects off-script attempts with boundaries that have no meaning, or if outcomes are largely pre-shaped into the same completion loop. In that case, freedom becomes navigational rather than authorial. The player moves widely but decides narrowly. Conversely, a game can offer few explicit options and still produce strong agency if the player’s intentions can be expressed within those constraints and if the game’s response is coherent. The sense of control comes less from having many doors and more from believing the doors that exist are real.</p><p>Agency is also tightly connected to the previous lesson on contrast. Contrast creates legibility by shaping difference in the contract. Agency depends on legibility because intention cannot be held in a world that does not clarify what matters. When contrast is flattened — when risk never changes, permission never changes, consequences never persist, and the player’s posture never shifts — agency tends to collapse into routine. The player stops forming intentions because nothing requires intention. When contrast becomes punitive and unreadable — when the contract changes without being legible — agency collapses into caution because intention becomes unsafe. In both cases, agency is not “removed.” It simply stops being a stable sensation because the conditions for authorship are not supported.</p><p>Time is equally important here. Agency requires temporal space to exist as a lived thing. If the game is structured so that the player is constantly pulled forward by prompts, markers, interruptions, and immediate rewards, intention has little time to form and settle. The player can still react, but reaction is not the same as authorship. On the other side, if the game demands too much time without giving interpretable feedback, intention becomes costly to maintain and the player may abandon it. Agency is sustained when time is composed so that intention can be formed, tested, and revised. That composition does not require slowness, but it requires room for interpretation. Without interpretation, the player cannot learn, and without learning, control becomes either fragile or illusory.</p><p>From this, a set of practical distinctions becomes possible. Agency is not “the player can do things.” Agency is “the player can form intentions that the game treats as meaningful.” Agency is not “the player has choices.” Agency is “choices change the player’s relationship to the world in ways the player can interpret and carry.” Agency is not “the game is hard.” Agency is “the game is answerable enough that difficulty can be learned rather than endured.” Agency is not “the player is free.” Agency is “the player is responsible,” because responsibility is what makes actions feel owned rather than merely executed.</p><p>This piece is adapted from Lesson 9 of <em>Foundations of Intentional Game Design — Volume II</em>.<br>In the full lesson, this section continues into concrete examples, exercises, and self-evaluation so you can apply this way of seeing to games you already know or to your own projects. If you want the complete five-lesson volume, it’s available as a PDF on Gumroad.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e438fa6f49f0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Foundations of Intentional Game Design — Lesson 8]]></title>
            <link>https://fleep-prod.medium.com/foundations-of-intentional-game-design-lesson-8-60e64cf9e816?source=rss-414b0a6c7738------2</link>
            <guid isPermaLink="false">https://medium.com/p/60e64cf9e816</guid>
            <category><![CDATA[indie-game]]></category>
            <category><![CDATA[videogames]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[game-design]]></category>
            <dc:creator><![CDATA[Fleep]]></dc:creator>
            <pubDate>Wed, 11 Feb 2026 17:09:27 GMT</pubDate>
            <atom:updated>2026-02-11T17:09:27.650Z</atom:updated>
            <content:encoded><![CDATA[<p><em>CONTRAST CREATES MEANING</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5ar7BDOAWsimnUlFSg5JDQ.png" /></figure><h3>Contrast Is What Makes Experience Show Up</h3><p>There is a particular kind of response that shows up in playtests and in private play, and it is easy to misread because it feels so natural. A player finishes a difficult stretch, reaches the next space, and exhales. Sometimes they laugh, not because something is funny, but because tension finally releases. Sometimes they slow down without being told. If asked what happened, they often do not describe a mechanic first. They describe a shift in state: they feel safe, or they feel exposed, or they feel that something is now permitted that was not permitted a minute ago. The experience becomes legible to them as a change, and the feeling that follows is rarely produced by a single element. It comes from the difference between what the player was just living through and what they are living through now.</p><p>This is one reason the language of “keeping the player engaged” can drift into something vague. Under pressure, teams develop a reflex: remove downtime, remove quietness, remove anything that looks like emptiness, keep the loop warm, keep the player busy, keep intensity high. It often comes from a good intention. Nobody wants the experience to feel padded, and nobody wants the player to feel abandoned. But when everything is urgent, urgency becomes background noise. When everything is intense, intensity loses contour. The player may still continue, because motion is not difficult to produce, but the internal ability to register what is happening begins to flatten. The game becomes a single temperature, and inside a single temperature meaning has fewer places to appear.</p><p>In other arts, authors have long relied on emptiness, silence, and restraint to make meaning show up. A pause in music is not a lack of music; it is an opening where the listener can hear what the sound was doing. A quiet shot in cinema is not “nothing”; it is a change in what the viewer is asked to hold. Those traditions can be useful as reminders that absence can speak, that subtraction can create contour. But games complicate the idea immediately, because the player does not merely witness silence. The player inhabits it. A quiet space is not only a moment of perception; it is a moment of responsibility, because the player is still present, deciding whether to move, whether to wait, whether to test, whether to risk breaking the calm. In games, emptiness becomes meaningful only when the contract changes with it, when the design makes the absence legible as a different demand rather than as a missing piece.</p><p>This is the central reason contrast matters. Contrast is not only an aesthetic technique, not only a matter of light and dark, loud and quiet, fast and slow, though those are part of it. Contrast is structural. It is built into how the game modulates the player’s responsibilities, their risk, their knowledge, and the consequences attached to action. Safety means something because danger was credible. Reward means something because effort had weight. Clarity means something because confusion was possible. Even power means something because weakness existed first, or because vulnerability still exists somewhere close enough to keep power from becoming mere noise. Without those relationships, what remains is sensation without contour. The game can still deliver stimuli, but stimuli do not automatically become experiences, and experiences do not automatically become meaning.</p><p>A safe room is a simple example precisely because it is not only a mood. It is a change in the contract. The player is allowed to lower vigilance. The penalty structure temporarily loosens. The player may be invited to reorganise inventory, to read, to plan, to notice details that were irrelevant under threat. That is not the same thing as “nothing happening.” It is a different kind of participation being invited, and it is readable as a difference only because the player has just lived through a different demand. In the same way, a difficulty spike becomes meaningful when it reframes mastery. It tells the player that what they thought they owned is not owned yet, or that ownership has conditions, or that a new layer of attention is now required. A reward becomes meaningful when it sits at a point where the player’s time can be recognised as a passage rather than as mere repetition, when it marks that something changed in the player’s relationship to the system, not merely that an item was delivered.</p><p>This lesson belongs after the lesson on time because time taught us to treat minutes as composed, not neutral, and contrast is one of the main ways composition becomes perceptible. Without contrast, time becomes a continuous flow with few landmarks. With contrast, time becomes shaped: peaks, valleys, returns, ruptures, recoveries, promises. The player begins to feel not only that they are doing things, but that the experience has a rhythm of demands and permissions, a rhythm that makes certain moments count because other moments exist around them.</p><p>The shift in Lesson 8 is therefore not toward “making stronger moments” as isolated highlights. Moments do not become strong on their own. They become legible because something around them changes, because the structure deliberately creates difference and makes that difference inhabitable. Once that becomes visible, the design question changes as well. Instead of asking whether a section is fun or boring in isolation, it becomes possible to ask what it is being contrasted against, what it is allowed to mean because of that contrast, and what the player is being trained to expect as the experience moves forward.</p><h3>The Quiet Shifts That Teach Contrast Without Naming It</h3><p>Contrast is already present in how players read games, long before anyone talks about meaning. It shows up in small, ordinary moments that rarely get credited as design. A menu opens and the world goes silent. A door closes behind the player and the camera settles. A checkpoint sound plays and the body relaxes a little. A HUD element appears and suddenly the player stops exploring and starts executing. A combat track fades out and footsteps become audible again. None of these moments need a speech to be understood. The player reads them because the game has changed something in the contract: what is dangerous, what is permitted, what is expected, what is worth paying attention to.</p><p>The clearest way to see this is to watch how fast attention reorganises when the game changes the status of uncertainty. In many games, the player moves through space with a broad, scanning attention. The eyes and hands are open to possibility. Then, the moment the game declares a clear objective, attention narrows. The player stops reading the space as a world and starts reading it as a route. This is not a moral judgement about guidance systems. It is a description of a perceptual shift that happens almost automatically. The difference between “I am in a place” and “I am moving toward a task” is a contrast in posture. It changes what is noticed, what is ignored, and what kinds of details feel meaningful.</p><p>The same can be observed in the difference between a space that is safe and a space that is merely empty. In a safe space, the player is allowed to lower vigilance, but the experience does not collapse. A safe space still has structure: it often contains tools, reorganisations, conversations, upgrades, small narrative confirmations, or simply the permission to breathe without losing progress. The player’s time becomes usable for a different kind of work. In an empty space, by contrast, the player’s vigilance may lower but nothing replaces it. The player’s attention floats. The time becomes thin. This is a subtle difference, and it is one reason teams can accidentally create boredom while believing they are creating rest. Rest is not the absence of content; it is a change in demand that still respects the player’s presence.</p><p>Contrast also appears in the smallest forms of feedback, because feedback decides whether an action feels like a gesture or like a commitment. A door that opens instantly produces one kind of relationship to space. A door that takes a second, with a sound and a slight delay, produces another. A weapon that reloads silently produces one kind of risk; a weapon that produces a clear audible “click” produces another. A UI that constantly confirms success produces one kind of confidence; a UI that stays quiet unless something goes wrong produces another. These are tiny contrasts, but they accumulate into a larger sense of what kind of world this is and what kind of attention it expects.</p><p>Even repetition produces contrast, not because repetition is contrast by nature, but because repetition creates a baseline. A repeated enemy that stays identical can become invisible. A repeated enemy that changes behaviour slightly can become meaningful. A repeated corridor that offers the same signals becomes dead time. A repeated corridor that changes lighting, sound, or threat becomes a marker. The player does not need to consciously praise the design for this to work. Contrast operates below the level of explicit appreciation. It shapes what the player remembers, because memory often forms at boundaries: the moment something shifted, the moment a promise was made, the moment a rule changed.</p><p>One of the most common quiet contrasts in games is the difference between a failure that teaches and a failure that merely costs. When failure teaches, the player’s model becomes sharper. The player often re-enters the same moment with a different posture: slower, more deliberate, more aware, or more confident. The same minutes repeat, but they are filled with different substance. When failure merely costs, the player repeats without transformation. The time is paid, but it does not evolve. The player’s attention begins to degrade, because the contract is asking for minutes without offering new understanding in exchange. The contrast between these two kinds of failure is one of the main ways a game decides whether it feels like a world that trains mastery or a machine that demands compliance.</p><p>A similar contrast exists in how games handle information. Sometimes a game gives information in a way that invites the player to own it. The player receives a clue, but it remains incomplete, requiring inference. The player feels that they have discovered something, not because the game hid it completely, but because the game let the player participate in connecting it. Other times, information arrives as a full instruction, and the player’s participation becomes execution. Again, this is not an argument that mystery is always superior. It is a reminder that meaning often forms where the player’s mind is needed. When everything is explicit, the mind is not required to connect, and what remains is movement through given steps.</p><p>These quiet contrasts are present in almost every game, including games that do not think of themselves as “meaningful.” A racing game creates contrast between control and loss of control, between grip and slide, between clean lines and recovery. A tactics game creates contrast between certainty and uncertainty, between a safe move and a risky move, between a plan that survives contact and a plan that collapses. A platformer creates contrast between flow and interruption, between rhythm and rupture, between confidence and recalibration. A narrative game creates contrast between what is said and what is implied, between what is known and what is suspected, between what is remembered and what is forgotten. The form changes, but the mechanism is the same: experience becomes legible through difference, and meaning begins to form when difference is not only felt but structurally earned.</p><p>Contrast is often most powerful when it is not announced. The player does not need to be told that a space is safe to behave differently inside it. The player does not need to be told that uncertainty has changed to let attention reorganise. These shifts happen because the contract has changed, and the body notices before language does. That is why the smallest contrasts are worth studying: they are the grammar through which the larger meanings later become possible.</p><h3>Contrast as the Engine of Legibility and Meaning</h3><p>At this stage the word “contrast” can still sound like a stylistic preference, the kind of thing people associate with composition, lighting, pacing, or mood. But what the earlier parts have been circling is more structural than that. Contrast is one of the main ways an experience becomes legible as experience. Without contrast, events happen, actions occur, rewards appear, dangers arrive, but the player’s mind has fewer boundaries to register what changed, and therefore fewer anchors to attach meaning to what just occurred. Contrast is the difference that makes a moment show up as a moment, rather than dissolving into the continuous flow of interaction.</p><p>This is why contrast is not primarily about making things “stronger.” It is about making differences readable. A game can be intense for hours and still feel flat, because intensity by itself does not tell the player what to carry forward. A game can be quiet for long stretches and still feel heavy, because quietness can contain responsibility. The relevant distinction is not between loud and silent. It is between a structure that changes what the player must assume, and a structure that keeps the same contract running so long that the player’s attention no longer distinguishes one state from another. When the contract does not change, the player can still be occupied, but occupation becomes repetitive motion rather than lived contour.</p><p>In games, contrast is inseparable from participation because the player is not only perceiving differences. The player is inhabiting them. This is what separates contrast in games from contrast in many non-interactive forms. A silent moment in film can be meaningful because it changes what the viewer attends to, but the viewer does not have to decide what the silence permits. In games, silence and emptiness are meaningful only if they come with a change in what the player is allowed to do safely, what the player is expected to hold, or what kind of attention the world rewards. A safe room is a simple case precisely because it is not merely calm; it is a permission structure. It gives the player a different mode of being in the world. That different mode becomes meaningful because it is contrasted against a mode that demanded vigilance. The meaning is not in the calm alone. It is in the difference between calm and threat as lived responsibilities.</p><p>This leads to a more precise articulation: contrast is a relational property of experience, not a property of content. Content is what exists. Contrast is how what exists is arranged so that differences become legible in time, and legibility becomes a carrier of meaning. Two scenes can contain identical assets and still feel like different worlds because they place the player under different responsibilities. Two mechanics can be identical and still feel like different actions because they live inside different stakes. Two rewards can be identical and still feel like different achievements because they arrive after different kinds of effort and different kinds of uncertainty. Meaning does not “come from” the object. Meaning emerges from the object placed in a relationship of difference.</p><p>It helps to name a few kinds of contrast that games routinely use, often without acknowledging them. There is contrast of <strong>risk</strong>, where the same action becomes meaningful because what can be lost changes. There is contrast of <strong>knowledge</strong>, where the same space becomes meaningful because what is understood changes, and therefore what is noticed changes. There is contrast of <strong>responsibility</strong>, where the player’s role shifts — solver to survivor, operator to judge, explorer to messenger — and the same inputs now belong to a different posture. There is contrast of <strong>consequence</strong>, where the same decision becomes meaningful because it persists rather than dissolving. There is contrast of <strong>permission</strong>, where the game temporarily allows rest, planning, reorganisation, or reflection, and that allowance becomes a form of care. These contrasts do not require narrative exposition to function. They operate directly on the player’s participation, shaping how attention is distributed and what kinds of engagement are required.</p><p>Contrast also interacts with time in a way that explains why meaning often collapses in experiences that are technically “polished.” Time, as the previous lesson argued, is not only duration; it is the composition of what minutes demand. Contrast is one of the main tools through which that composition becomes readable. When a game repeats the same contract too long — same guidance, same risk level, same kind of reward, same cost of failure — the minutes begin to lose differentiation. Even if content changes, the structure feels the same, and the player’s mind starts treating the experience as one continuous task. By contrast, when a game composes shifts — small or large — in what counts, what is at stake, what must be held, what can be ignored, the player’s time gains landmarks. Those landmarks are where memory forms. They are also where meaning accumulates, because meaning often depends on being able to say, even implicitly, “something changed.”</p><p>This is also where contrast can be misunderstood as a tool for manipulation rather than for authorship. Designers sometimes talk about “peaks and valleys” as if the goal were simply to keep the player’s arousal fluctuating to prevent boredom. That language can be true in a shallow way, but it does not reach the deeper point. Contrast is not merely stimulation management. It is the method by which an experience gives form to participation. It decides what kind of player the game is training. A structure that constantly externalises intention, removes risk, and keeps the path obvious will train a player who moves smoothly but carries little. A structure that withholds too much, punishes too harshly, and offers few permissions will train a player who becomes cautious or exhausted. Contrast is one of the ways a designer composes that training, not by preaching, but by shaping what is required to proceed.</p><p>From this, a clearer set of “what it is not” becomes possible. Contrast is not the same as novelty. A new asset is not a contrast if the contract remains identical. Contrast is not the same as difficulty. Difficulty can exist without meaning if it does not change responsibility or knowledge. Contrast is not the same as surprise. Surprise is a momentary disruption; contrast is a relationship that can persist and structure memory. Contrast is also not the same as variety for its own sake. Random difference does not create meaning; it creates noise. Contrast creates meaning when it is placed so that the player can inhabit the difference, read the difference, and feel how the difference reorganises what they must do and what they must hold.</p><p>What this lesson is really giving is a way to diagnose flatness without defaulting to content volume. When a game feels thin, the question is not only “does it have enough.” The question is often “what differences does it allow the player to live through.” When a game feels exhausting, the question is not only “is it too hard.” The question is often “does it ever change what it demands, or does it keep the same posture running until the player’s attention collapses.” And when a game feels meaningful, the question is not only “what was the story.” The question is often “what contrasts shaped the player’s participation so that moments became legible as shifts, and shifts became something the player could carry.”</p><p>This piece is adapted from Lesson 8 of <em>Foundations of Intentional Game Design — Volume II</em>.<br>In the full lesson, this section continues into concrete examples, exercises, and self-evaluation so you can apply this way of seeing to games you already know or to your own projects. If you want the complete five-lesson volume, it’s available as a PDF on Gumroad.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=60e64cf9e816" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Foundations of Intentional Game Design — Lesson 7]]></title>
            <link>https://fleep-prod.medium.com/foundations-of-intentional-game-design-lesson-7-e6afd55e25d6?source=rss-414b0a6c7738------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6afd55e25d6</guid>
            <category><![CDATA[game-design]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[indie-game]]></category>
            <category><![CDATA[videogames]]></category>
            <dc:creator><![CDATA[Fleep]]></dc:creator>
            <pubDate>Tue, 10 Feb 2026 15:17:32 GMT</pubDate>
            <atom:updated>2026-02-10T15:17:32.031Z</atom:updated>
            <content:encoded><![CDATA[<p><em>TIME IS THE INVISIBLE MATERIAL</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*weREMIq60eeJjZbiLyyqYQ.png" /></figure><h3>When Time Becomes a Design Decision</h3><p>I’ve heard “it’s just pacing” said in two very different moods. Sometimes it’s said as a genuine craft remark, a way to point to rhythm, breath, and the distribution of pressure. But I’ve also heard it said as a dismissal, usually late in production, when something feels wrong and the team is tired of naming it. In that second tone, “pacing” becomes a polite way to avoid a harder sentence: the experience is asking the player to spend time without knowing why, and we don’t yet know whether that time is doing work.</p><p>The reason this matters is that time is not only a container around a game. It is one of the main materials a game is made of. How long something takes, how often it repeats, how much time a mistake costs, how long tension is held before relief is allowed, how long the game asks you to stay attentive before it gives you the information that makes attention feel rewarded. Even when we don’t talk about time directly, we author it constantly, through loop length, checkpoint distance, recovery delays, traversal friction, menu friction, vague objectives, and the design choice to reveal or conceal.</p><p>There is a historical reason we learned to treat time in a slightly suspicious way. In the 90s, we often used time as a form of value. Not as an artistic material, but as a promise to the player: “you will get hours.” The technology and the budgets were different. Content volume was expensive. Space was limited. Reuse was normal. So we built structures where the same locations had to be visited again and again, and we justified it through gating, or through quests that “activated” objects later, or through puzzles that only became solvable after you had fetched the right knowledge somewhere else. Sometimes we did it elegantly, as a way to make the world feel cohesive and to let familiarity become mastery. Sometimes we did it less elegantly, as a way to extend playtime by stretching uncertainty.</p><p>You can see how extreme this can become in games like <em>Alone in the Dark</em> (Infogrames, 1992). The advertised experience might be twenty hours, but once you know exactly what to do — once the uncertainty is removed — you can finish in a fraction of that (Personally I could complete full playthroughs in 45 minutes). This isn’t “speedrunning” in the modern sense, where the player is performing unusual technique for competitive time. It’s simply the difference between playing while confused and playing while informed. The same structure yields radically different durations because the bulk of the time was not action, but search, hesitation, and interpretation under uncertainty.</p><p>That difference is not a moral failure. It is a design fact, and it points to something precise: in many games, time is created not by what you do, but by what you <em>don’t yet know</em>. We can use that intentionally, to create dread, fragility, and careful reading of space. We can also use it unintentionally, and then the player’s hours become a kind of tax.</p><p>This is why time is more than a “pacing” label. It is where the contract becomes lived. When players say a game is “dragging,” they rarely mean the art is bad. They usually mean that something in their body has begun resisting the deal being offered. Attention becomes heavy. Curiosity becomes duty. Decisions stop feeling like choices and start feeling like chores. Very often this happens when the experience stops changing at the same speed as the player’s understanding of it. The player has learned the question the game keeps asking, but the game continues to ask it as if it were still new.</p><p>There is a symmetrical problem on the other side, and it can be harder to admit because it hides behind energy. A game can be dense, fast, intense, and still leave the player oddly blank afterwards. Not because nothing happened, but because nothing had enough time to register as meaningful. The player kept reacting, but the experience did not settle into a posture they could inhabit. It remained a stream rather than a relationship.</p><p>When I was teaching, I saw this mismatch constantly. People could describe what they wanted the player to feel with rich words — fear, wonder, responsibility, pride — and then build loops that treated time as neutral. They tuned mechanics, added effects, wrote scenes, but didn’t look at what the player’s minutes were being asked to do. They didn’t look at how repetition accumulates, how anticipation forms, how fatigue appears, how trust is built or eroded across attempts. Then, when the experience felt “off,” they reached for more content or louder moments, because the underlying issue was hard to name.</p><p>Time is hard to name because it doesn’t sit in one object. You can point to a weapon or a camera or a line of dialogue. Time is what connects everything. It is what turns a mechanic into a habit, a habit into a posture, and a posture into a feeling. It is also what turns failure into learning or into waste. Often the difference is not in the rules themselves, but in how long the rules ask you to remain inside their consequences.</p><p>So the shift this lesson is trying to make is quiet but strict. It is not “time matters,” because everyone agrees with that and nothing changes. It is to start seeing time as part of the contract in the same way we learned to see decisions, effects, layers, patterns, and emotional posture. Not as production scheduling, and not as a vague afterthought called pacing, but as something designed, and therefore something you can learn to read.</p><h3>What You Know Changes How Long It Takes</h3><p>If time is part of the contract, then duration cannot be treated as a neutral consequence of “having a lot of game.” Duration is authored. It is authored not only by how much content exists, but by what the player is allowed to know, when they are allowed to know it, and what it costs to act under imperfect understanding.</p><p>In practice, games often make minutes without adding new objects, new geometry, or new plot points. They make minutes by changing the conditions under which the player moves, decides, searches, commits, and recovers. That change is felt immediately at the smallest scale, in moments that appear so ordinary they rarely get discussed as “time design,” even though they are.</p><p>One familiar moment is the entrance into a space whose safety is not yet readable. Nothing attacks. No scripted beat occurs. Yet the player does not move through the room the way they move through a known safe corridor. Movement slows. The camera checks angles. Attention becomes distributed across corners, silhouettes, and doorways. Small rituals appear — stop, listen, pivot, step, stop again — not because the player has been instructed to perform them, but because the contract implies that ignorance has weight. The time in that room is not created by new content. It is created by the cost attached to not knowing.</p><p>Another moment appears when the game contains interactions whose affordances are not fully legible. A door reads as a door but does not open until a condition is met, and the condition is not made explicit in a way that lets a clean hypothesis form. An object reads as background clutter until a certain state makes it count, but the game has not yet taught the player how to distinguish “prop” from “relevant.” The player tries an action, receives an ambiguous refusal, tries again somewhere else, and then returns later because the uncertainty has shifted from “I missed it” to “I’m not in the right state yet.” What is being produced here is not only uncertainty, but revisitation. Time expands without the world expanding, because the player’s reading of what matters is unstable.</p><p>A related mechanism is deliberate re-use of space through new conditions. A location is visited, understood, and then later revisited because something has changed: an item is now present, a lock has become meaningful, an enemy has appeared, a conversation has activated, a new requirement has turned the familiar space into a new question. This can be used crudely as extension, but it can also be used as a structural way to make the world feel connected, so that memory becomes a navigation tool rather than an annoyance. In both cases, the minutes are not coming from new geometry. They are coming from the player carrying a remembered map and being asked to re-read it under altered stakes.</p><p>There is another quiet variant where the time is not made by travelling back and forth, but by searching for what the game considers relevant. The task is not really “find the thing.” The task is “find what makes the thing count.” The instruction exists, but the interpretive key does not. The player therefore searches not only across spaces but across possibilities: testing actions, testing combinations, repeating a route to check whether something was missed, or whether something simply has not been enabled yet. The player is spending minutes inside a gap between intention and clarity, and that gap can feel like investigation, like dread, like cautious curiosity, or like irritation, depending on whether the search teaches a language or only consumes time.</p><p>The example of <em>Alone in the Dark</em> (Infogrames, 1992) sits precisely in this territory. The striking fact is not “it can be finished quickly.” Many games can. The striking fact is that the duration collapses so radically once the player knows what to do, and that the collapse is not a competitive trick. It is what happens when interpretive uncertainty disappears. A first run can stretch toward twenty hours because the player spends much of that time living inside uncertainty: reading rooms, testing hypotheses, hesitating before acting, rechecking spaces, trying to understand what counts. Once the system’s requirements are known, a large portion of the time vanishes, because the time was not in the actions themselves. It was in the distance between the player’s current model of the world and the model the game demanded.</p><p>At that point, it is tempting to tell a simple story: older structures “wasted time” through vagueness, and modern structures “respect time” through clarity. But that story is too comforting, and it hides what is actually happening. Modern games still author time aggressively. The difference is that they often author it by shifting uncertainty in the opposite direction, not by removing time design.</p><p>Many contemporary games provide markers, logs, objective reminders, highlight shaders, compass pings, layered minimaps, and interface scaffolding that continuously re-states intention. The explicit goal is to prevent the specific form of time loss associated with being blocked by interpretation: wandering without hypotheses, revisiting without insight, failing because a rule was invisible. This does reduce one kind of duration. It reduces the time spent not knowing what the next move is.</p><p>But a different effect can appear when certainty becomes comprehensive enough that the player no longer needs to carry the thread internally. The experience remains long, and it can remain dense with content, but the player’s minutes are no longer filled with the work of interpretation, memory, and inference. The minutes become filled with execution of confirmed instructions. The time is still being spent, but it is being spent under a different posture.</p><p>This can be felt in subtle behaviours. When objective certainty is continuously externalised, the player’s attention reorganises. Instead of rehearsing the situation in the mind — what was said, what mattered, what the motive was, what the chain of causality is — the player can rely on the interface to do the remembering. A quest log will summarise. A marker will return the player to the right spot. A dialogue line can be skipped because the objective will still update. The player is still active, still moving, still completing tasks, but the experience requires less internal reconstruction of meaning, because the system supplies the next intention at the moment it is needed.</p><p>In role-playing and adventure structures, this can become a structural permission: progression without comprehension. It becomes possible to move through a game while holding only a shallow model of the fiction, because the contract no longer demands that the player remember names, infer motives, or maintain a coherent chain of why. The player can complete a long campaign while remaining oddly detached from its narrative logic, not due to lack of intelligence or care, but because the design has made care optional. The game has made success independent from holding the thread.</p><p>This does not mean that clarity is bad, or that withholding information is inherently good. The point is not to advocate for confusion, and it is not to romanticise older frictions. The point is to notice that “reducing wasted time” and “increasing meaning” are not automatically aligned goals. A game can eliminate interpretive friction and still create long durations by sheer volume, by travel, by checklists, by repeated confirmations of an objective that never needs to be personally held. The minutes are protected from being lost to confusion, but they can still become thin, because nothing in the contract requires the player to construct significance beyond compliance.</p><p>This is where the title of the part becomes concrete. What the player knows, and how the player knows it, changes what time is made of. Under uncertainty, time is made of hesitation, search, hypothesis, and the slow construction of a reliable reading of the world. Under comprehensive guidance, time is made of following, executing, and moving from confirmation to confirmation, often without the need for internal narrative continuity. Both structures can produce long games. Both can produce frustration. Both can produce pleasure. The difference is in what the minutes are asking the player to carry.</p><p>Even within a single game, this can shift from moment to moment. A section with strong signalling can feel brisk and clear, and a section with ambiguous affordances can suddenly thicken time into inspection and doubt. A quest chain can alternate between interpretive work and guided execution, and the emotional posture changes accordingly. The same amount of content can therefore feel dense or empty depending on whether the player is required to build an internal model of what matters, or is allowed to outsource that model entirely to the interface.</p><p>All of this can be observed without moralising. It is simply a way of noticing that time is not only added by content, and not only removed by clarity. Time is shaped by knowledge, and knowledge is shaped by design.</p><h3>Time as Contract, Not as Container</h3><p>Up to this point, time has appeared the way it usually appears in play: not as an object you can point at, but as a felt condition. It has appeared through uncertainty that thickens minutes, through certainty that makes minutes easy to spend without carrying much, through loops that expand or compress as the player’s knowledge changes. Part 6 is where that lived material can be gathered into a clearer articulation, not to replace “pacing” with a fancier word, but to make time structurally readable. If time remains only a sensation — drag, speed, density, flow — then it stays difficult to design. It stays in the category of mood: something you hope emerges once everything else is tuned. But games do not merely happen in time. They use time as one of the primary ways the system expresses its relationship to the player.</p><p>A first move is to stop treating time as a neutral container around events. In games, time is one of the ways the contract becomes physical. It becomes physical through costs and permissions attached to minutes: how long actions lock control, how reversible decisions are, how quickly consequences become legible, how long it takes to recover from mistakes, how far failure sends you back, how often repetition changes what you notice instead of only repeating labour. These are often discussed as tempo or “feel,” but they are more consequential than that. They decide what kind of participation the game demands and what kind of responsibility the player can plausibly take. A game that makes correction rare does not only make errors expensive; it changes what it means to commit. A game that makes intention continuously explicit does not only make navigation easier; it relocates where meaning must live. A game that resets the world but preserves knowledge does not only create an interesting loop; it declares that progress is measured in understanding, and that the player’s time is meant to be spent turning uncertainty into a stable model.</p><p>A second move is to separate “time” into distinct layers, because one reason teams fall back to vague pacing language is that they compress all temporal phenomena into one feeling. In practice, a player lives several kinds of time at once, and those times can be designed independently even when they interact. When they are not separated, temporal problems are misdiagnosed. The team tries to “speed things up” when the problem is interpretive fatigue. Or it tries to “slow things down” when the problem is that nothing meaningful is being carried, so slowing simply increases emptiness.</p><p>The most obvious layer is <strong>operational time</strong>: traversal time and task time. How long it takes to reach a place, how long an animation holds you, how long a combat exchange tends to last, how long a dialogue interaction takes before it returns control. This is the layer easiest to measure, and therefore the layer most often discussed. But measured minutes are not the whole experience of duration, because a minute of travel under clarity does not feel like a minute of travel under uncertainty, and a minute of repetition that teaches does not feel like a minute of repetition that only delays. Operational time is what clocks can see, but it is not what attention necessarily experiences as substance.</p><p>A second layer is <strong>epistemic time</strong>: the time it takes the player to know what counts. This includes learning what is possible, learning what is safe, learning what is dangerous, learning what the game considers relevant, learning what signals are trustworthy, and building a model stable enough that the player can act without constant verification. Epistemic time is not identical to “difficulty,” because it is not only about execution. It is about legibility and learnability. It is about whether the game teaches a language the player can acquire, and whether that language stabilises so the player becomes faster not by bypassing play, but by aligning with it. This is one reason “what the player knows changes how long it takes” is not a loose observation. Knowledge changes duration because knowledge changes what the contract requires from the player in order to proceed. In a structure that demands reading, minutes become minutes of forming and refining a model. In a structure that externalises reading into interface scaffolding, minutes become minutes of applying a model already provided.</p><p>A third layer is <strong>penalty time</strong>: what failure costs in minutes. This includes the distance to return, the time to reconstruct a state, the time to re-enter an opportunity window, and the amount of repeated labour required to earn another attempt. Penalty time is often framed morally, as “respecting” or “disrespecting” the player, but as a design lever it mainly shapes posture. When the cost of failure is heavy in minutes, the player’s relationship to experimentation changes, and the player’s relationship to risk changes, regardless of what the game claims thematically. Penalty time can produce care, seriousness, and commitment when it is paired with legible causality and meaningful repetition. But it can just as easily produce resentment when the repeated time does not deepen perception, when the failure feels unearned, or when the return trip is pure administrative labour.</p><p>A fourth layer sits closer to meaning than mechanics, and it is the one teams often ignore when they talk about “playtime.” It can be called <strong>interpretive time</strong>: the time spent holding a thread, remembering motives, inferring what matters, constructing a chain of significance that makes actions feel like more than compliance. Interpretive time is not automatically “better” than clarity, and it is not automatically “waste” either. It is simply a kind of time with a specific substance: time spent owning meaning internally rather than borrowing it continuously from the interface. A game can reduce interpretive time by externalising intention into markers, logs, highlights, reminders, and step-by-step confirmations. When it does, the player’s minutes can become smoother and less blocked, but they can also become thinner if the contract no longer requires the player to carry anything across time. The player may still do many things, but doing becomes less connected to understanding. Progress remains possible without comprehension, and when comprehension is no longer structurally required, it tends to be the first casualty of fatigue.</p><p>This is one place where it becomes important to be precise about participation. When a game makes intention too explicit, the risk is not that the player becomes inactive in the literal sense. The player can still be moving, fighting, collecting, crafting, selecting, navigating. The risk is that the game trains a reduced form of agency: agency as execution of known instructions rather than agency as interpretation, commitment, and ownership. That difference matters because it changes what the player is asked to decide. The question becomes “which task next?” rather than “what does this situation mean, what am I responsible for, and what am I choosing to believe about it?” A structure can keep the player busy while quietly removing the need to hold anything. This is not a condemnation of guidance. It is a statement about what guidance does to the substance of time.</p><p>Once these layers are visible, the word “pacing” becomes smaller than people assume. Pacing is mostly about rhythm: the distribution of pressure and relief, the sequencing of intensity, the alternation of demands. But pacing does not capture how time functions as a contract. Two games can alternate tension and breath at similar intervals and still produce radically different lived durations, because they do not ask the same thing of the player’s mind. One may train mastery by letting knowledge compress loops into fluent action while still requiring the player to hold meaning. Another may train compliance by making objectives explicit enough that the player can complete hours of content with little internal reconstruction. Measured time can look similar while lived time diverges.</p><p>At this point, it helps to place another phenomenon correctly, because it can otherwise look like a fifth layer that sits beside the others. Players often spend time thinking without acting: sometimes with the game closed, sometimes with the game open but paused, sometimes in a safe state where nothing threatens them. That time can look like “nothing is happening,” yet it can be one of the most meaningful forms of participation a game can provoke. The key is that it is not a separate category that replaces the four layers above. It is a way those layers can express themselves through <strong>suspended action</strong>.</p><p>There are at least two different cognitive postures here, and they behave differently in relation to time.</p><p>One is <strong>strategic thinking</strong>, the kind that can survive leaving the play session. It is planning across minutes, hours, or runs: build planning, route planning, hypothesis-building, economic optimisation, puzzle reconstruction, schedule design, long-term risk management. A player can often do this outside the game because the thinking is not dependent on immediate perception. It depends on models, rules, and remembered information. When a game provokes this, it is often because epistemic time has produced a rich enough structure that the player wants to build a stronger model than the session currently allows. Sometimes that export is an enrichment, because the game has created a world whose logic is enjoyable to inhabit mentally. Sometimes it is a repair, because the game makes the cost of learning too high through direct play — too opaque to infer, too punishing to test — so the player seeks external models to reduce waste.</p><p>The other posture is <strong>tactical thinking</strong>, and it usually cannot fully leave the game, because it depends on the immediate configuration of the situation: the layout you can see, the enemies you can count, the timing you are about to commit to, the resources you have right now, the risks created by visibility and position. The player may pause, hold position, slow down, or deliberately stop input, and yet remain intensely engaged, because the thinking is anchored to what the system is currently presenting. This kind of “non-action” is still participation, because it is the player taking responsibility for a decision before committing it. It belongs inside the contract, even if the body is not moving. Operational time continues, but it is being used as interpretive and epistemic time. The player is building and testing a model while still needing the game world present as reference.</p><p>This distinction matters because it prevents a common misreading: that a game either “keeps the player active” or “lets the player be passive.” A design can reduce agency not by letting the player stop moving, but by removing the need for planning and inference. Conversely, a design can provoke deep agency while allowing long pauses and long reflections, as long as the reflection is meaningful, anchored, and connected to consequences. Tactical suspended time can be one of the ways a game restores ownership to the player: the player is not being rushed into execution, and the player is not being carried by automated certainty. The game is letting the player decide what to believe about the situation before they act.</p><p>Seen from this angle, time as contract is not only about how long things take. It is about what minutes are <em>for</em>. Temporal design becomes the design of the substances that fill duration: learning, confirming, rehearsing, remembering, inferring, repeating, waiting, travelling, recovering, planning, committing. These are not neutral categories. They shape what the player becomes while playing, and they shape whether the experience feels inhabited or merely traversed.</p><p>This is also why the question “longer or shorter” is rarely the right question. Duration can be one of the ways meaning accumulates, especially when repetition evolves perception and when responsibility deepens through sustained commitment. But duration can also become dilution when the system produces long stretches in which nothing new is demanded of understanding and nothing new is earned by attention. In those cases, the problem is not that time exists. The problem is that time is being spent without transformation, and the player feels that lack of transformation as erosion: attention becomes heavy, memory becomes optional, and progress becomes movement rather than change.</p><p>Treating time as contract does not require a single ideology about guidance, difficulty, or friction. It requires only that temporal choices be treated with the same seriousness as mechanical choices, because they are the medium through which mechanics become habits, habits become postures, and postures become the lived experience of the game.</p><h3>When Understanding Leaves the Game</h3><p>There is one consequence worth naming explicitly because it can otherwise look like a separate phenomenon. Sometimes the time demanded by a game does not remain inside the play session. It migrates outward, into searches, guides, wikis, videos, forum threads, and conversations. This is not a “fifth layer” that replaces the others. It is a displacement of epistemic time and interpretive time beyond the boundaries of the game.</p><p>Epistemic time can be exported when learning the system’s language through direct play is too expensive. The player cannot reliably infer what counts, cannot test hypotheses without paying excessive penalty time, or cannot stabilise a model because the signals are inconsistent. In that case, the player leaves not because they are unwilling to engage, but because the contract has made engagement inefficient. The player seeks a model elsewhere so that play can resume with less waste. The outside time functions as a substitute tutorial, often provided by culture rather than by the game.</p><p>Interpretive time can also be exported for a very different reason: because the game creates meaning that invites reconstruction. Some designs fragment understanding deliberately. They let lore and causality exist as puzzles, and the pleasure includes collective decoding. Here, exported time can be enrichment rather than repair. Players leave the session to compare theories, share evidence, and build a deeper model together. The time outside the game becomes part of the lived experience because interpretation itself becomes a form of play.</p><p>Both forms of export are consequences of how the game handles knowledge and meaning inside its own contract. The player’s hours do not disappear; they relocate. Whether that relocation is felt as enrichment or as repair depends on whether the game is supporting learnable inference and meaningful ownership, or offloading legibility and coherence onto external culture by necessity.</p><p>This piece is adapted from Lesson 7 of <em>Foundations of Intentional Game Design — Volume II</em>.<br>In the full lesson, this section continues into concrete examples, exercises, and self-evaluation so you can apply this way of seeing to games you already know or to your own projects. If you want the complete five-lesson volume, it’s available as a PDF on Gumroad.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6afd55e25d6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Foundations of Intentional Game Design — Lesson 6]]></title>
            <link>https://fleep-prod.medium.com/foundations-of-intentional-game-design-lesson-6-90ed2472b52e?source=rss-414b0a6c7738------2</link>
            <guid isPermaLink="false">https://medium.com/p/90ed2472b52e</guid>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[videogames]]></category>
            <category><![CDATA[indie-game]]></category>
            <category><![CDATA[game-design]]></category>
            <dc:creator><![CDATA[Fleep]]></dc:creator>
            <pubDate>Tue, 10 Feb 2026 15:16:14 GMT</pubDate>
            <atom:updated>2026-02-10T15:16:14.472Z</atom:updated>
            <content:encoded><![CDATA[<p><em>EMOTION COMES FROM STRUCTURE, NOT DECORATION</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*01syyt-xGaQl6lG4AdyW4g.png" /></figure><p>I have heard the sentence for years, in studios and classrooms, in feedback sessions and pitch meetings, usually said with the same tired certainty: <em>“We need more emotion.”</em> Sometimes it comes out as a complaint — players didn’t care, they didn’t feel attached, nothing landed. Sometimes it is a wish — this could be moving, this could be intense, this could be meaningful. And sometimes it is disguised as a technical request — better music, stronger writing, higher stakes, more cinematic cameras, more facial animation, more “polish.” The sentence changes shape, but the assumption underneath stays stable: emotion is something you add on top, after you have “the game,” as if the game were a skeleton and emotion were the skin you paint on later.</p><p>I understand why that belief survives. There are whole segments of our culture that teach us to associate emotion with storytelling, with acting, with music, with images. We learn early that if you want people to feel something, you show them a face, you write them a line, you swell the soundtrack. In that world, emotion is expressed by content. So when people look at games, they often import the same reflex: emotion must be what surrounds the interaction, not what the interaction itself produces. It becomes normal to treat feelings as decoration — something you can intensify without touching the structure.</p><p>But the more time I spend watching people play, the more that split starts to feel artificial. I have watched players feel real tension in a tutorial room where nothing “dramatic” happens. I have watched relief arrive not from a plot beat but from a sound and a tiny shift in constraint. I have seen frustration grow, not because the story is sad, but because the game keeps asking for the same precision without giving the feedback that would let precision become mastery. I have seen pride appear in players who could not explain the narrative at all, but who could explain, very clearly, what they were finally able to do with their hands.</p><p>The uncomfortable thing is that these reactions are often stronger than the ones we try to manufacture with expensive content. The first time a player barely survives with one point of health, the feeling is not “added.” It is produced. The moment they hesitate before entering a doorway, the feeling is not “painted.” It comes from what the doorway implies in the system. When they finally understand a pattern — when their perception reorganizes and they begin to act differently — the feeling is not a cinematic effect. It is the experience of a mind adapting to a structure.</p><p>And yet, when teams talk about emotion, they rarely talk about structure. They talk about tone. They talk about themes. They talk about narrative arcs, character depth, visual identity, music direction. All of that can matter. But I keep seeing the same failure mode: the team tries to make the player feel something by increasing the expressive layer, while leaving untouched the conditions that actually generate the feeling during play. The result is often a kind of emotional mismatch. The game asks you to perform calm, repetitive labor while telling you that you are in a tragic crisis. The cutscenes beg you to feel urgency, but the loop trains you to optimize and wait. The writing declares meaning, but the decisions the player makes remain weightless. Players sense that mismatch instantly, even if they cannot name it. They call it “hollow,” “forced,” “trying too hard,” or just “I don’t care.”</p><p>What makes this difficult is that the problem hides behind words that seem obvious. We say “emotion” as if it were one thing. But in games, emotion is not a single channel. It is a bundle: tension, curiosity, relief, confidence, suspicion, guilt, pride, irritation, trust, dread, attachment, awe. Some of these are narrative emotions, tied to identification and imagination. Some are bodily, tied to timing and risk. Some are social, tied to fairness and recognition. Some are cognitive, tied to learning and prediction. If you treat them all as something you add through content, you will keep trying to solve structural feelings with decorative tools. And the more you push decoration, the more obvious it becomes that the loop itself is not carrying what you are asking it to carry.</p><p>I’m not saying story and aesthetics are irrelevant. I’m saying they are not where the foundation is. In the first five lessons of this scaffold, we have been training a certain kind of seeing: decisions and effects, layers and responsibilities, patterns and cause, intention as something that can be read in structure rather than declared in a pitch. Lesson 6 does not change the project. It continues it. It takes the same discipline of perception and turns it toward a domain that teams often treat as mystical: feeling.</p><p>Because the truth is simple, but it is not comfortable: most of what players feel in games is not delivered <em>to</em> them. It is produced <em>by</em> the relationship between their action and the game’s responses. Emotion is not an ingredient you sprinkle onto a finished design. It is what the design makes inevitable — through constraints, feedback, pacing, risk, readability, and the kinds of commitments it asks the player to make.</p><p>This lesson is about that shift. Not toward “making emotional games” as a genre, but toward recognizing that emotion is already there, everywhere, whether you intend it or not. Your structure is already generating a feeling in the player. The only question is whether you can see what you are doing well enough to take responsibility for it.</p><h3>The Feeling That Arrives Before the Story</h3><p>There is a moment that happens in games so often we stop noticing it, even though it is one of the clearest proofs that emotion is structural. You start a new play session. Nothing dramatic has occurred yet. No character has spoken. No plot has unfolded. Sometimes you haven’t even moved. And still, within seconds, your body has already made a decision: <em>relaxed</em> or <em>alert</em>. Not because the game told you what to feel, but because the game quietly shaped what you expect will happen if you act.</p><p>Sometimes the first emotional signal is almost embarrassingly small. A menu cursor moves with a certain weight. The sound of the selection is crisp, not decorative — more like confirmation than ambience. You can tell, before you understand anything else, whether the game is going to treat your inputs as careful commitments or as casual suggestions. That difference is already a difference in feeling. One is playful. The other is cautious. The game hasn’t “been emotional” yet, but you have already been placed into a posture.</p><p>Then you reach an opening room, one of those spaces that exist mostly to teach without teaching. The room might be safe. Or it might be empty in a way that doesn’t feel safe. A corridor might be wide enough to run through without thinking, or narrow enough that you instinctively slow down. It is not the visual theme alone that does this. It is the invisible contract the room establishes: can you retreat, can you see far enough, can you recover if you make a mistake, can you understand what the game expects from you?</p><p>Pay attention to what happens the first time you approach a doorway in an unfamiliar game. Doorways are deceptively rich emotional machines. In some games, a doorway is a neutral transition: you pass through it at full speed, because you trust that the game is not going to punish movement itself. In other games, a doorway is a question. It is not even always a scary doorway. It might be well-lit. It might have music. But your hand hesitates anyway, because you have learned, in the first minutes, that entering a new space is a commitment that could cost you something.</p><p>The feeling comes from three things the game has already shown you: what information it gives, what mistakes it tolerates, and how quickly it responds to your attempt to correct yourself. That is already enough to generate tension without a single narrative device.</p><p>Checkpoints do this too. The first time you see a save icon, or a checkpoint symbol, or a brief “saved” notification, the game is not just storing data. It is communicating a philosophy of risk. It is telling you how much of your time it considers disposable. It is telling you whether failure will be treated as a learning loop or as a punishment. You can feel that immediately, even before you can articulate it.</p><p>A game that saves often doesn’t necessarily feel easy. Sometimes it feels generous, or confident, or focused on momentum. A game that saves rarely doesn’t necessarily feel hard; sometimes it feels deliberate, or ritualistic, or like it wants the player to carry a memory of consequence forward. The same mechanical event — saving — produces different emotional climates depending on how it is placed in the structure of play.</p><p>Even enemies, at the micro level, can reveal this. Think of the first repeated enemy you encounter in many games: not the boss, not the spectacle creature, but the “basic unit.” Often, that enemy is less about challenge than about <em>calibration</em>. It exists to teach you what counts as a mistake. Does the enemy punish impatience, or lack of observation, or poor spacing, or sloppy timing? Does it forgive you if you react late? Does it let you recover? Does it telegraph honestly? Does it feint? Does it insist that you learn it, or does it let you brute force through?</p><p>Before story, before theme, before “emotion” as we usually name it, those micro-decisions are already shaping the player’s internal state. A forgiving enemy produces a different kind of curiosity than a punishing one. A clear telegraph produces a different kind of trust than an ambiguous one. A long recovery animation produces a different kind of respect than a short one. None of these are cosmetic. They are structural invitations to feel.</p><p>UI details can be even more quietly decisive. Consider what happens when you take damage. Not the numerical amount, but the texture of feedback. Does the game show you what happened clearly enough that you can learn? Does it give you a window of grace — half a second where you can reorient — or does it chain your failure so quickly that you feel overwhelmed? Does the health bar communicate danger early, or does it collapse suddenly? Does the game give you a chance to stabilize, or does it insist that you keep moving?</p><p>These are not “emotional effects” in the usual sense. They are the conditions for a relationship with the game. Trust, suspicion, confidence, anxiety, irritation — these are relational emotions. They emerge from how the game treats you while you try to understand it.</p><p>And then there is repetition, the thing teams often talk about as if it were a production constraint rather than an experiential tool. The first repeated action in a game is a test of tone. You pick up the same kind of item again. You open another door. You fight another small enemy. You walk another corridor. Repetition can feel like comfort or like fatigue, like mastery or like stagnation, depending on what changes inside it. Does the repetition carry variation in timing, in risk, in information? Does it teach you something new each time? Does it ask a slightly different question? Or is it truly the same question asked again with no new possibility of insight?</p><p>If the repetition is alive — if it shifts your perception even slightly — it produces a feeling of progress that has nothing to do with story. If the repetition is dead, it produces a feeling of waste that no amount of cinematic dressing can fully hide. This is why “we need more emotion” so often becomes “we need more content.” Teams sense a lack of emotional movement, but misdiagnose it as a lack of narrative events, when what is missing is change inside the loop.</p><p>In these early micro-moments, the player is not primarily asking what the world means. They are asking what the game <em>is</em>. What kind of contract it offers. What it will reward. What it will punish. How it will respond when they misunderstand. And the emotions that arise in those moments — caution, curiosity, trust, tension, impatience, calm — are not secondary. They are the first layer of experience, and they come from structure.</p><p>That is why it matters that we stay inside games here. We don’t need analogies to prove the point. The medium already provides the evidence in its most ordinary details. Before any grand example, before any named case study, you can already feel the truth of the lesson: emotion does not begin when the story begins. It begins when the system begins to speak back to you.</p><p>And once you start noticing that, a difficult thought follows: if emotion is already present in the smallest parts of play, then emotion is not something you can choose to “add later.” It is something you are already designing, whether you admit it or not.</p><h3>Emotion as a Consequence of the Contract</h3><p>So far I have tried not to rush toward definitions, not because theory is dangerous, but because it is very easy to name something too early and then stop looking at what actually happens in play. “Emotion” is one of those words that can make us lazy. Once we say it, we feel as if we have identified the problem, when often we have only replaced a lived experience with a label.</p><p>But after the earlier parts, we have enough ground under our feet to articulate the concept carefully, without turning it into a slogan.</p><p>When I say that emotion comes from structure, I am not saying that games are machines that manufacture feelings on command, or that the player is a passive receiver. I am also not saying that story, art, and music are irrelevant. What I am trying to place in focus is something more modest and more practical.</p><p>When people play, they are not only interpreting meaning. They are also negotiating a relationship. They are learning what the game allows, what it expects, what it forgives, what it punishes, and how it responds when they misunderstand. That relationship begins long before narrative meaning has settled in, and it often remains the main source of feeling even when narrative meaning becomes strong.</p><p>In other words, a great deal of what players feel is not an opinion about content. It is a stance produced by the conditions of engagement. Caution, boldness, tension, composure, irritation, trust, suspicion, relief, impatience, confidence. These are not “themes.” They are relational states. They describe the player’s posture toward the system while acting inside it.</p><p>If we connect this to the earlier scaffold, the continuity becomes visible. Lessons 1 to 5 were not building a theory of emotion. They were building a way of seeing decisions, effects, responsibility, repetition, and intention as things that exist in the structure rather than in our descriptions of it. Lesson 6 is not a detour into psychology. It is the same practice of perception, applied to what that structure does to the player’s internal state.</p><p>This is why the sentence “we need more emotion” is often unhelpful. It tends to treat emotion as a substance that can be added later, usually by intensifying expressive layers. But once you begin to read the relationship between action and consequence, you realise that the game is already producing an emotional climate, even in its most ordinary interactions. The question is not whether emotion exists. The question is whether you can describe what your structure is currently doing, and whether it matches the experience you believe you are building.</p><p>To make that less abstract, it helps to name a few recurring structural conditions that tend to shape emotional posture reliably. I’m not offering these as a checklist that guarantees a particular feeling. I’m offering them as the kinds of things that, in practice, keep appearing whenever you try to explain why two games with similar themes can feel radically different to play.</p><p>One condition is how much commitment the game asks for, and what kind of escape it allows after commitment. In some structures, when you act, you are held inside the consequence for a while. You cannot easily retract. You cannot easily correct. When that is true, even small actions acquire weight. Not because the story says they matter, but because the system makes your timing and your reading matter. In other structures, correction remains available more often. You still make mistakes, and you still die, but the system tends to let you re-enter control quickly enough that boldness feels reasonable. This is one of the reasons <em>Dark Souls</em> and <em>Hades</em> produce such different postures without needing to explain anything narratively. Their contracts with the player differ at the level of commitment and recovery.</p><p>A second condition is how information is given, and when. This includes the obvious things, such as telegraphs and UI clarity, but it also includes the less obvious things, such as camera behaviour, spatial readability, and the timing of feedback. What the player knows in the moment affects not only competence but mood. If information arrives clearly and in time, the player tends to develop a form of trust that is hard to fake with presentation. If information arrives too late, or arrives ambiguously, or feels inconsistent, the player’s stance shifts. They may become cautious, or suspicious, or overwhelmed, or sometimes fascinated, depending on how the ambiguity is framed. But the point remains that information is not neutral. It becomes emotional because it changes whether the player can reasonably commit.</p><p>A third condition is the structure of risk, meaning not narrative stakes but practical stakes. What is lost on failure, how failure is framed, how progress is stored, how punishment relates to learning, and whether the player feels their time is respected. A game can be severe and still feel fair. A game can be generous and still feel tense. The emotional signature is often less about the magnitude of punishment than about what punishment communicates. Does the system feel like it is correcting you toward mastery, or does it feel like it is simply extracting a cost? That distinction is one reason players can tolerate repetition in some games and resent it in others.</p><p>A fourth condition is pacing, and with it the way repetition is organised. Pressure that never releases tends to produce a different stance than pressure that arrives in readable waves. Repetition that evolves perception tends to feel very different than repetition that merely consumes time. This is one reason it was useful, earlier, to stay with small moments like doorways, checkpoints, and repeated enemies. Those are not minor details. They are the places where pacing and repetition become personal. They are where the game teaches the player what kind of attention is required, and whether attention will be rewarded with understanding.</p><p>A fifth condition is acknowledgement, and I mean that in a broad way. Sometimes it is mechanical acknowledgement, such as clear hit reactions, crisp state changes, readable indicators that confirm what happened and why. Sometimes it is systemic acknowledgement, such as progression structures that turn failure into iteration rather than into pure negation. A system that acknowledges the player’s actions tends to make responsibility feel possible. A system that withholds acknowledgement tends to make the player feel either detached or mistrustful, even when the underlying rules are technically consistent.</p><p>None of these conditions are “emotion” in themselves. They are the kinds of structural decisions that shape whether the player’s relationship to play becomes cautious or confident, tense or relaxed, determined or resentful. They are also the kinds of decisions teams often make without noticing that they are emotional decisions. They get discussed as balance, as responsiveness, as UX, as economy, as pacing, as encounter design. All of those labels are valid. But when you look from the player’s side, what those choices often become is a felt climate.</p><p>This is also the place where it becomes important to say what this lesson is not claiming.</p><p>It is not claiming that narrative emotion is fake. Narrative emotion can be real, and in some games it is central. But narrative emotion in games is always mediated by the player’s relationship to the system. If the system asks the player to behave in a way that contradicts the intended feeling, the contradiction is felt, even when the writing is strong. Conversely, when the structural posture supports the narrative posture, the narrative can become more powerful without needing to become louder.</p><p>It is also not claiming that aesthetics are merely surface. Aesthetic framing strongly shapes how we interpret what we feel. A soundscape can make caution read as fear. A heroic musical language can make risk read as courage. Visual language can make repetition feel like ritual rather than fatigue. In that sense, aesthetics do not sit outside emotion. They guide it. But they cannot substitute for structure. If the underlying contract produces boredom or mistrust, presentation can mask it briefly, but it rarely sustains it for long.</p><p>So the practical use of this lesson is not “design emotion directly.” It is to make emotion readable as a consequence of your design choices. Once you can do that, the vague request for “more emotion” becomes a more workable question. You start asking what posture the current structure trains in the player, and what structural changes would shift that posture.</p><p>What matters, for now, is simply this: once you begin to treat emotion as a consequence of the contract, you stop looking for it only in what the game says, and you start noticing it in how the game treats the player’s attempts to act. That shift is not difficult to accept intellectually. It is difficult to accept in practice, because it forces a kind of responsibility. It removes the comforting idea that emotion lives “somewhere else,” in story, in tone, in talent, in a mysterious quality you either have or do not have.</p><p>And because that responsibility is uncomfortable, people protect themselves from it. They do it with familiar shortcuts, with half-true statements that feel like wisdom, with arguments that contain a real observation but then use it to avoid looking at structure. If this lesson is going to be usable, we have to surface those misreadings gently and precisely, not to win debates, but to keep the concept from collapsing back into old habits.</p><p>This piece is adapted from Lesson 6 of <em>Foundations of Intentional Game Design — Volume II</em>.<br>In the full lesson, this section continues into concrete examples, exercises, and self-evaluation so you can apply this way of seeing to games you already know or to your own projects. If you want the complete five-lesson volume, it’s available as a PDF on Gumroad.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90ed2472b52e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Craft of Influence 3 — The Indie Crisis: Expansion Without Arbitration]]></title>
            <link>https://fleep-prod.medium.com/the-craft-of-influence-3-the-indie-crisis-expansion-without-arbitration-61322e05b8a6?source=rss-414b0a6c7738------2</link>
            <guid isPermaLink="false">https://medium.com/p/61322e05b8a6</guid>
            <category><![CDATA[indie-game]]></category>
            <category><![CDATA[game-design]]></category>
            <category><![CDATA[game-development]]></category>
            <dc:creator><![CDATA[Fleep]]></dc:creator>
            <pubDate>Thu, 05 Feb 2026 12:29:41 GMT</pubDate>
            <atom:updated>2026-02-05T12:29:41.917Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*74kG463uA-7502jZBz4uDQ.png" /></figure><h3>Why This Is Called A Crisis</h3><p>This is personal, and it’s also repetitive enough in the field that it deserves a name.</p><p>Over the years I’ve been on most sides of the indie table. I’ve produced with indie teams. I’ve been indie with my own studio. I’ve coached indies. I’ve invested in indies. And across all these positions, the same pattern has appeared too often to be dismissed as “bad luck” or “a few teams who weren’t ready.”</p><p>Many teams simply do not release. They circle for years, accumulate systems, restart, rewrite, and eventually run out of energy. Others do release, but in a state that cannot carry them — because the work is unfinished in the only sense that matters: not the number of features, but the coherence and stability required for the experience to stand on its own.</p><p>That is what I mean by the indie crisis. Not an abstract debate about the industry, and not a complaint about visibility. A structural tendency for small teams to lose the ability to bring an authored experience to the point where it can exist in the world without collapsing under its own ambiguity.</p><p>The consequence is predictable. When this pattern repeats at scale, trust erodes. Investors become wary not because indies lack talent, but because so many projects fail to cross the threshold from meaningful intention to shippable coherence. That distrust is not the topic of this series, but it is one of the reasons the production craft matters: the crisis is visible to everyone, even when the language to describe it is missing.</p><p>So this article is not a moral judgement. It is an attempt to name the mechanism, because once it is named, it becomes possible to teach the smallest possible continuity machinery that keeps authorship intact long enough for a game to actually be finished.</p><h3>The Drift That Doesn’t Look Like Failure</h3><p>After a few years around indie teams, it becomes clear that the collapse rarely happens in the dramatic form people imagine. It is not a single argument that breaks the project. It is not one technical disaster. It is not even one “wrong decision” that can be pointed at later and declared the cause. The more common pattern is quieter: the project keeps moving, the team keeps working, the build keeps changing, and yet the centre slowly becomes harder to locate.</p><p>At the start, a project tends to have a temperature. Sometimes it is a mechanic that produces a very specific kind of tension. Sometimes it is a fantasy that wants to be inhabited in a precise way. Sometimes it is a rhythm: a cadence of attention, risk, and relief that gives the experience its identity before anyone can fully explain it. In those early weeks, coherence is almost effortless because the work is still light. Decisions are made close to the source. The whole thing can still be held as one continuous promise.</p><p>Then the project grows, and growth creates a new kind of danger that is often underestimated. The danger is not that constraints arrive. Constraints are expected. The danger is that possibility remains open. In a small team, new ideas keep arriving, and most of them are good ideas. They are good in isolation. They are good on paper. They are good when compared to other games. They are good when imagined as “one more layer” that will enrich the whole.</p><p>This is where drift begins in its most common indie form: not as erosion, but as expansion. Systems are added because they feel like the responsible thing to do. A progression layer appears because it seems to give players a longer arc. A crafting layer appears because it seems to create texture. A narrative wrapper appears because it seems to give weight. A roguelite structure appears because it seems to offer replayability. A skill tree appears because it seems to give variety. Each addition makes sense locally, and because it makes sense locally, it is easy to accept without noticing what it does globally.</p><p>But authored experiences do not behave like a pile of locally good ideas. They behave more like a language. When grammar changes, meaning changes even if every sentence remains correct. When systems multiply, attention is redistributed. Incentives begin to compete. What the game teaches becomes less singular. The original promise is not “broken,” it is diluted, and dilution is harder to notice than failure because it still looks like progress. The build grows. The feature list grows. The project feels bigger. And yet the experience becomes less precise.</p><p>This is one of the reasons so many projects end up in a strange middle state: full of work, full of systems, full of effort, and yet not strong enough to carry itself. Not because the team did nothing, but because the centre was never protected against expansion.</p><h3>Feedback Needs A Frame, Or It Becomes Noise With Authority</h3><p>Feedback is not the enemy of indies. Early feedback can be one of the healthiest habits a team can develop, because it forces contact with reality, and it reveals what the work actually communicates rather than what the team believes it communicates. The issue is what happens when feedback is treated as instruction rather than as material that must be interpreted through intention.</p><p>Most feedback does not arrive as a reading of authored coherence. It arrives as preference. A player asks for what they personally want. They project other games onto the build. They suggest features that would be great in a different experience. They interpret difficulty through their own tolerance rather than through the work’s intention. They interpret repetition as boredom even when the project is designed around mastery. None of this is malicious. It is simply what feedback is when it is not accountable to the work.</p><p>This is where a notion that sounds “external” becomes essential to authorship: the project needs an explicit sense of who it is speaking to. Not as a marketing slogan, and not as a demographic obsession, but as a coherence instrument. A game cannot speak to everyone at once, and pretending that it does is one of the fastest ways to dilute it. If the project has no target player in mind — one or several types of players whose expectations, tolerance, and desires are part of the intended conversation — then every test becomes a referendum on taste, and taste has no stable authority.</p><p>Once a target group is defined, feedback can be weighted rather than absorbed. A comment from someone inside the intended conversation carries a different kind of meaning than a comment from someone outside it. Both can still be useful. Outside feedback can reveal misunderstandings and accessibility barriers. But it should not automatically rewrite the work. Without that weighting, the team is incentivized to respond to the loudest discomfort rather than to the most relevant signal, and the project expands in the direction of generalized appeal, which is often the opposite of authored clarity.</p><p>So “listening” is not the craft. The craft is interpretation under responsibility: deciding what feedback reveals about the experience the project is trying to deliver, and what feedback simply asks the project to become something else.</p><h3>Time Does Not Only Allow A Game To Mature. It Forces Decisions.</h3><p>Time enters the story in a way that is difficult to admit, because a comforting belief sits at the centre of many indie narratives: that taking longer inevitably improves the work. More time means more iteration, more polish, more maturity, more refinement, and therefore a stronger result.</p><p>Sometimes that happens. But time also does something else: it changes the work by changing the people who carry it, and by changing the conditions under which decisions are made. A long project accumulates references, inspirations, doubts, alternate paths, and the slow psychological need to justify duration by making the work bigger. The original promise cools not because it was weak, but because the mind adapts to it. New ideas feel fresher. New systems feel like solutions to fatigue. Unfinished work remains open to reinterpretation, and reinterpretation is a quiet permission to rewrite the centre.</p><p>That is the artistic side of time: the way it can dissolve specificity when continuity machinery is missing.</p><p>But there is also a practical side that cannot be ignored without becoming naïve. Even when a team is self-financed, time is not infinite. People have lives. Energy has limits. The ability to carry ambiguity has limits. A project that takes “as long as it takes” becomes, in practice, a project that risks never closing, or closing only after the work has mutated into something the team can no longer author with confidence. This is not about chasing a commercial calendar. It is about protecting the team’s continuity as a creative entity.</p><p>So the producer responsibility is not to rush the work into an arbitrary deadline. It is to hold the notion of a right amount of time — right not as a universal number, but as a situational truth shaped by scope, team capacity, and the kind of experience being attempted. A small ritual game cannot carry the same timeline logic as a systemic sandbox. A first project cannot carry the same risk appetite as a third. The “right time” changes with circumstances, but it still exists as a question that must be held deliberately, otherwise the project is governed by drift, and drift is what consumes both coherence and stamina.</p><p>In other words, time is not only a solvent. It is also a constraint that forces authorship to become decisive.</p><h3>The Producer As Arbiter, Not As A Manager</h3><p>This is where the producer function becomes unavoidable, and also where it is most often misunderstood.</p><p>In many indie circles, “producer” still sounds like a corporate figure, an external authority, a planning person brought in after funding to add structure to the chaos. That image is so strong that many teams reject the word before they even examine what the function could mean for them. But the producer function being described here is not a job title. It is a stance. It is the cold role in the room, the one that can protect coherence against the natural forces that deform it.</p><p>Those forces are not only technical. They are social and psychological. The desire to add. The desire to respond. The desire to please. The desire to justify time by making the project bigger. The desire to solve discomfort by expanding scope instead of clarifying intention. None of these desires is immoral. They are part of creation. The question is whether there is a counter-force that can say: this addition is locally good but globally dangerous; this feedback is emotionally persuasive but incoherent with the centre; this new idea is exciting but it rewrites the promise; this project does not need more material, it needs sharper protection of what already exists.</p><p>That counter-force is arbitration. Arbitration is not taste, because taste is personal. Arbitration is not control, because control is operational. Arbitration is the preservation of internal logic. It is the ability to treat coherence as something real enough to disappoint good ideas in order to protect the right idea.</p><p>This is also why it is so difficult for the same person to both originate the vision and arbitrate its survival. Creation wants to explore. It wants to keep doors open. It wants to believe the next layer will finally express what is missing. Arbitration must close doors deliberately, not because closing doors is virtuous, but because authorship requires limits. Without limits, the work becomes a negotiation between impulses rather than a coherent language.</p><p>The same stance is what gives target and time their proper place without turning the project into a business exercise. Defining who the game is speaking to is not marketing; it is how feedback becomes interpretable instead of authoritative noise. Defining the right amount of time is not corporate urgency; it is how the team protects its ability to remain coherent long enough to finish what it started.</p><p>So in a small team, the producer stance often requires stepping out of creation for periods of time. Remaining colder than the room. Holding the centre as something external, something that can be named and tested against play, something that does not belong to the producer as ego. In that sense, the producer should not defend “their vision.” The producer defends the coherence of the project relative to the director’s intention, and relative to what the experience is teaching the player now, in the current build, not in an imagined future.</p><p>In a two- or three-person collaboration, these hats can move. They can switch per project, per phase, even per decision category. The point is not to freeze identity. The point is to ensure that when decisions are made, someone is explicitly responsible for protecting the centre, and that this responsibility is not silently replaced by feasibility, fatigue, or negotiation.</p><h3>Software Process Can Make Work Efficient Without Making It Authored</h3><p>There is one more confusion that appears often enough to deserve a gentle naming, because it looks like maturity.</p><p>Many indie teams adopt software process. They run sprints, stand-ups, retrospectives. They use boards and tickets. They become efficient at closing tasks, and that efficiency is real. It reduces chaos, it stabilizes collaboration, it makes integration more reliable. In that sense, it can be a genuine step forward.</p><p>But software process is designed to optimize closure. It is excellent at making work visible, measurable, and manageable. It is not designed, by default, to make coherence binding. It can produce speed without producing authorship. It can generate an impressive volume of finished tasks while the experience itself becomes less specific.</p><p>This is not a condemnation of those methods. It is simply a recognition of what they are for. They solve the problem of delivery. They do not automatically solve the problem of continuity of meaning.</p><p>So the missing layer is not “more discipline” and not “less structure.” The missing layer is a small authored layer on top: a continuity machinery that filters feedback through intention, that treats expansion as a design risk, that forces replacement decisions when meaning-carrying elements are displaced, and that legitimizes interpretation at specific moments rather than leaving interpretation to occasional intuition.</p><p>That is why the indie crisis persists even among teams that work hard, even among teams that use process, even among teams that are technically competent. Without arbitration, the project is governed by expansion, and expansion is a quiet way to lose authorship while still believing progress is being made.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=61322e05b8a6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Craft of Influence 2 — Teach Game Production More Like Filmmaking, and Less Like Software…]]></title>
            <link>https://fleep-prod.medium.com/the-craft-of-influence-2-teach-game-production-more-like-filmmaking-and-less-like-software-84a05ca3c2dd?source=rss-414b0a6c7738------2</link>
            <guid isPermaLink="false">https://medium.com/p/84a05ca3c2dd</guid>
            <category><![CDATA[videogames]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[game-design]]></category>
            <dc:creator><![CDATA[Fleep]]></dc:creator>
            <pubDate>Wed, 28 Jan 2026 15:04:13 GMT</pubDate>
            <atom:updated>2026-01-28T15:04:13.164Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>The Craft of Influence 2 — Teach Game Production More Like Filmmaking, and Less Like Software Development</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xPgRJrXht8wUikPeHBemWw.png" /></figure><h3>A — The Problem Isn’t What We Teach. It’s What We Make Real.</h3><p>There is a way in which game education is unfairly judged. People accuse schools of being outdated, or too theoretical, or too technical, and the criticism often carries an implied fantasy: that if students were simply taught the “real industry way,” everything would solve itself. I don’t believe that. Schools do not create the complexity of game production; they inherit it, and they have to turn it into something teachable, which means they have to choose what can be evaluated, repeated, and improved within limited time and uneven skill levels.</p><p>So the issue is not that schools teach Software Development, tools, and production mechanics. They should. The software layer is not optional in games. Games are authored experiences, but they are authored through systems, and systems are built. Any pedagogy that treats engineering as a secondary inconvenience ends up teaching a form of creation that cannot survive reality either.</p><p>The problem appears elsewhere. It appears in what becomes <em>operationally real</em> during learning. Because education is not only what is said; it is what is rewarded, what is required to be shown, what is inspected, what counts as “done.” And when the only things that reliably count as “done” are implementation milestones and functional deliverables, a quiet lesson is taught: meaning is important, but it is not binding.</p><p>That lesson is almost never taught explicitly. In fact, teachers usually say the opposite. They talk about vision, about intention, about player experience, about unique voice, about design. But if the system of evaluation treats coherence as something you hope for and treats functionality as something you must prove, then the student’s nervous system learns which reality matters. It learns that what survives pressure is what can be validated quickly, and that what cannot be validated quickly must be postponed until “later,” which is how drift becomes normal long before students even have a word for it.</p><p>This is why I’m not arguing for “less Software Development.” I’m arguing for a second layer of rigor that sits above the Software Development layer, the way authored mediums always do, and the way games often forget to formalize: the rigor of continuity, of interpretation, of making intention remain binding as constraints accumulate.</p><h3>B — Two Pedagogies, Two Definitions of Progress</h3><p>If you take a typical game production course shape — anonymized, because this is not about blaming any institution — you often find something like this: teams are formed, a concept is pitched, the project is broken down into tasks, an agile-like rhythm is installed, and progress is tracked through visible delivery. Students learn to estimate, to assign, to coordinate, to merge, to stabilize builds, to ship features, to reduce bugs, to produce presentations that show momentum. The work becomes legible in the language of pipelines.</p><p>That language is useful. It is even necessary. It teaches students that ambition without structure is not freedom, it is chaos. It teaches them that “we’ll figure it out later” is not a plan. It teaches them that collaboration is a real craft and that integration is a form of truth. And because these elements can be evaluated relatively clearly, education naturally leans on them. You can see whether a feature exists. You can see whether the build runs. You can see whether the milestone was hit.</p><p>But notice what is quietly happening in that model: the unit of progress is a deliverable, and the unit of truth is functionality. Meaning is present as an intention, but it is rarely present as a binding evaluation axis. It becomes something you talk about at the start, and then something you hope will emerge from the competence of the parts.</p><p>Now compare that to the underlying shape of a film production course — not in its equipment or its industry customs, but in its relationship to authored coherence. A film course, even when it is teaching logistics, tends to make something else operationally real: not only “did you shoot it,” but “did you preserve what the scene was meant to do.” Students are asked to articulate intention in a form that can be tested against what was produced. They are forced to discover, again and again, that the plan and the result are different things, and that authorship is not a declaration but a continuous act of interpretation.</p><p>In that environment, the unit of progress is not only footage captured. It is continuity preserved. The criticism is not only “is it technically correct,” but “does it still communicate what you think it communicates,” and “what did the constraints do to the meaning.” The system forces students to learn a discipline that is central to authored work: the ability to observe the created material as if it were not yours, to read what it actually does, and to decide what must be protected when reality deforms the plan.</p><p>That is the difference I’m pointing at. It is not a difference of tools. It is a difference of what the pedagogy treats as real.</p><p>Games can be taught with the same seriousness. Not by pretending they are films, but by admitting that interactive meaning also requires continuity, and that continuity does not survive by luck when systems multiply.</p><h3>C — Why “Less Like Software Development” Doesn’t Mean “Against Software Development”</h3><p>It’s worth being careful with this, because the phrase can be misunderstood as a cultural attack. I don’t want that. Software Development culture offers a real form of rigor: decomposition, correctness, reproducibility, integration, debuggability. It is a discipline that gives you a way to tell the truth about what exists. Without it, many game projects remain in a permanent state of imagined coherence because nothing is stable enough to be evaluated honestly.</p><p>The problem is not Software Development. The problem is what happens when correctness becomes the only socially legitimate form of truth inside a production system.</p><p>Correctness is local. Meaning is relational. You can build a perfectly correct system that produces a confused experience, because the experience is not a module. It is the accumulated relationship between what the player attempts, what the game rewards, what it teaches, what it punishes, what it makes obvious, what it makes invisible, what it encourages you to care about, and what it slowly trains you to ignore. That relationship lives across systems, across time, across feedback loops, across pacing, across learning, across expectation. It is not a property you can guarantee by checking whether the build runs.</p><p>So “more like filmmaking” means we teach a second kind of rigor: the rigor of interpretation under constraint. The rigor of asking not only “does it work,” but “what does it do to the player,” and “is that still what we meant.” The rigor of noticing drift while it is still cheap.</p><p>And this is why the producer and director roles matter pedagogically, even in tiny student teams. Because these roles are not corporate hierarchy. They are coherence functions. They are the names of responsibilities that already exist, whether you admit them or not.</p><h3>D — The Indie Duo, Or: You Already Have The Roles, You Just Don’t Name Them</h3><p>There is a common scene in small teams that is so normal we no longer notice it. Two people start a project. One calls themselves “the programmer.” The other calls themselves “the artist.” That’s how they divide reality, and that is how they negotiate: one side speaks feasibility, the other side speaks desire, and both sides gradually discover that neither feasibility nor desire is enough to carry a project all the way to something coherent.</p><p>Because even in a two-person studio, production and direction are not optional. They appear the moment the work becomes more than a sketch. Someone has to hold the intention of the experience — what the game is trying to do to a player, what kind of coherence it must preserve as systems grow. Someone also has to hold continuity through trade-offs — what is protected, what is sacrificed, what is replaced when a meaning-carrying element is cut, and how the project remains itself when reality starts editing it.</p><p>The problem is not that small teams lack these functions. The problem is that they let the functions remain implicit, and implicit responsibilities tend to be governed by default forces. Direction collapses into taste and vibes because no one is formally accountable for translating intention into binding decisions. Production collapses into deadlines and technical necessity because no one is formally accountable for making coherence operational when the schedule becomes loud. The project moves forward, but it becomes progressively harder to say why it is moving in this direction rather than another, because the only shared language that survives pressure is feasibility.</p><p>What changes is not adding new roles. What changes is seeing what you are already doing, and giving it names so it can exist outside personality.</p><p>This is where I want to refine the usual advice. The goal is not to decide once and for all who is “the producer” and who is “the director” for the entire life of the collaboration, as if those were permanent identities that must be assigned like job titles. In small teams, that kind of freezing can be as damaging as having no roles at all, because it locks the project into a social structure instead of letting the structure serve the work.</p><p>The more useful move is to treat producer and director as hats, not destinies. You can be two people and still say: on this project, or on this phase, or for this category of decisions, one of us is holding direction and one of us is holding production continuity — and next time we may choose differently. Sometimes the same person may carry both hats for a while, not because it is ideal, but because the project’s size makes separation impractical; the point is that the team remains conscious of the difference, and therefore remains capable of switching when the work demands it, rather than letting the switch happen accidentally under pressure.</p><p>This is also why it is possible for a creator to have strong impact when directing and strong impact when producing, depending on what responsibility they are holding in the system; the influence comes from the function being carried, not from an identity label carved into the collaboration. The lesson for indies is not “copy film.” The lesson is simply that even when you are only two, you are allowed to choose your hats deliberately instead of letting your disciplines choose them for you.</p><p>When that happens, the conversations shift subtly. Not toward bureaucracy, but toward coherence. A feature is no longer discussed only as “can we implement it” and “can we draw it.” It is discussed as “what role does it play in the experience,” “what does it teach,” “what does it make dominant,” “what does it replace if we cut it,” and only then “how do we build it.” The work stays almost the same. The project becomes different, because the project starts protecting meaning as part of production instead of treating meaning as something that survives if the team stays motivated.</p><p>This is the focus shift I’m defending. Not a revolution. A meta-layer.</p><h3>E — What This Adds To Production Education</h3><p>So the thesis is not that game production should stop being taught through software rigor. The thesis is that software rigor must be placed inside a broader production literacy that makes authored continuity operational.</p><p>In practical terms, this means that courses need recurring moments where the unit of observation is not the backlog but the experience, and where critique is not a bug list but a reading of what the build actually does to the player. It means that “done” cannot be defined only by functionality if the course claims to teach authored work. It means that students must be trained to recognize drift not as a moral weakness but as the predictable result of gravity, and to respond to it with roles, rituals, and decision architectures that keep intention alive.</p><p>And it means that we stop treating “producer” and “director” as labels you earn once you have funding, and start treating them as responsibilities you already hold the moment you start shaping an experience with other humans.</p><p>That is why this belongs in a series called <em>The Craft of Influence</em>. Because influence, in the context of production, is not persuasion. It is the design of conditions where the work remains itself as reality applies pressure. Teaching that craft does not require tearing down what we already do. It requires adding the layer that authored mediums have always known they need: the layer where meaning becomes a thing you can protect, not because you believe in it, but because your process makes it real.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=84a05ca3c2dd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>