The planner-preparation period becomes a lived route here. Akihito formally entered Human Academy's two-year Game College planning course around mid-to-late April 2025, carrying forward the research questions, community responsibilities, and creative interests developed before enrollment. This chapter follows the surviving record through August 21, 2026. It remains ongoing as the course, projects, and professional direction continue to develop.
From Researcher to Game Planner
Human Academy did not replace Akihito's earlier work; it gave that work another production language. Questions about culture, interpretation, identity, learning, and connection now had to become rules, systems, player choices, specifications, schedules, and experiences that a team could actually build.
- Course
- A two-year Game College route focused on game planning, production documents, communication, presentation, and collaborative development.
- Core Practice
- Turning an idea into a concept proposal, then clarifying mechanics, flows, priorities, requirements, and implementation details through specifications.
- Production Awareness
- Learning enough about programming, art, interface, sound, schedules, and business constraints to understand how planning decisions affect adjacent work.
- Continuing Question
- How can a game communicate through what the player does—not only through what the story says?
The Game Jam: Knowing When to Replan
An early Game Jam became less a record of a finished project than a lesson in leadership, supervision, opportunity cost, and adaptation. Akihito entered expecting meaningful planning practice. As the team settled into a structure centered on instructions from one controlling point, he found that he was neither contributing substantially nor developing the skills he had joined to practice.
Rather than compete for control or remain only to occupy a place on the team, Akihito stepped back. The decision was not framed as quitting at the first difficulty. It was a planning decision: reassess the original objective, measure whether the current route still serves it, and redirect limited time when the answer changes.
- Leadership Lesson
- Direction and accountability matter, but a team should grow more capable instead of becoming permanently dependent on one person.
- Decision Point
- When the experience produced little contribution or learning, continuing only because it had already begun would have confused persistence with progress.
- Reallocated Work
- Time could return to Unity practice, original game ideas, concept documents, specifications, portfolio development, and professional preparation.
- Planner Principle
- A plan is not sacred. Preserve the objective, evaluate the conditions, and change the route when the route no longer works.
Team Production: Responsibility Before Readiness
In a later Team Production class, Akihito expected to support or shadow a more experienced planner. Instead, he was placed in a leadership position within a planning group made entirely of first-year students and asked to help direct a larger programming group. He accepted the responsibility, while recognizing the difference between leadership potential and production experience.
The challenge was structural as much as personal. A team can possess strong programming capacity and still lose time if planning cannot stay ahead of implementation. Concepts must become decisions; decisions must become specifications; specifications must be communicated clearly enough that programmers and artists can work without repeated uncertainty or avoidable rework.
- Unexpected Role
- Lead when necessary, even when the preferred learning route had been to observe, assist, and gain experience beside a veteran planner.
- Team Duty
- Protect the time, effort, portfolio needs, and professional development of the people who depend on planning for clear and meaningful work.
- Communication
- Speaking is only one channel. Written specifications, text, asynchronous updates, translation tools, questions, and review requests can keep work moving.
- Support Standard
- Useful support should help a person participate more independently; it should not turn another teammate into a permanent intermediary or single point of failure.
The leadership model developing here balances three views at once: what serves the game, what serves the team and its members, and what allows Akihito to grow responsibly. Those answers can overlap, but leadership requires noticing when they do not.
Understanding the Industry's Role Map
Course discussion and later reflection sharpened Akihito's understanding of how responsibilities overlap inside game development. Job titles do not form perfectly sealed boxes, especially in Japanese studios. The useful distinction is each role's center of gravity and the adjacent work it must understand.
- Planner
- Designs mechanics, systems, rules, flows, content, balance, and specifications, then communicates them so other disciplines can implement the intended experience.
- Main / Lead Planner
- Owns and coordinates the planning center of the project, including priorities, consistency, planner tasks, schedules, and communication with other section leads.
- Director
- Holds responsibility for the game as a whole: the creative and development direction across planning, art, interface, sound, scenario, technology, and player experience.
- Producer
- Holds the product-facing center: budget, resources, staffing, scheduling, stakeholders, publishers, marketability, and the conditions that allow the game to exist and sell.
For Akihito, the conclusion is not that every planner must perform every job. It is that a planner cannot ignore the work around planning. Decisions create consequences across disciplines, and long-term growth toward lead planning or direction requires understanding those consequences well enough to coordinate people, protect the game's intent, and revise responsibly.
Projects, Documents, and Proof of Work
The course period also pushed Akihito to treat ideas as records that other people can inspect. Concepts, visual sheets, prototypes, design reasoning, development status, and specifications became parts of the same professional archive. Smoothie Slicer and Grow-Me Garden show playable but unfinished work; Sushi Samurai, Rebirth of Retro, StyleBound, and Cocktail Crafter preserve other stages of concept and presentation development. Their value is not that every project is release-ready. Their value is that each exposes what has been imagined, clarified, built, tested, or still needs work.
OPEN DEVELOPMENT ARCHIVE
Loadout Bay
Concepts, prototypes, presentation sheets, documentation, and current completion records
What This Chapter Has Changed
- From Ideas to Instructions
- A good concept must become specific enough for another person to build, review, test, and question.
- From Control to Capacity
- Leadership is not measured only by how much authority one person holds, but by whether the team can understand the goal and act effectively together.
- From Difficulty to Diagnosis
- Some hard situations create growth; others create only stagnation. A planner must tell the difference before time and trust are exhausted.
- From Planner to Director
- The immediate goal remains stronger planning. The longer route points toward coordinating the full experience without losing respect for the specialists who make it real.
The Human Academy chapter is not a victory summary written after everything is finished. It records Akihito while he is still learning how to convert ideas into production, how to lead without reducing leadership to control, how to respect other people's time, and how to adapt without abandoning the larger direction.
ONGOING CHAPTER // LAST UPDATED AUGUST 29, 2026 // SOURCE RECORD THROUGH AUGUST 21, 2026
