Kkin Manager Defense (낀과장 디펜스): a office-worker action game about surviving a day, pressed from above and climbed at from below
Translated by AIView original
Screenshots
Screenshot 1 of 5
Kkin Manager Defense (낀과장 디펜스) is a web action game where you play a middle manager stuck between executives and team members, trying to get through the day.
Executive orders come down from the top of the screen, and team members' issues come up from the bottom.
Before an item hits the judgment line, you have to handle it one of three ways.
- ↓ Delegate — pass it to a team member. Team trust goes down.
- ↑ Report — send it up to an executive. Executive patience goes down.
- ◎ Absorb — take it on yourself. Your health goes down.
No matter what you pick, something gets chipped away.
It's not a game about picking the right answer, it's a game about picking the less painful choice.
If any one of the three gauges runs out, that day is over.
Controls
- PC: ↓ or S to Delegate · ↑ or W to Report · Space to Absorb · F for half-day leave · Esc to pause
- Mobile: swipe down to Delegate · swipe up to Report · tap to Absorb (you can also switch to the 3-button bottom navigation mode)
- No install needed, play right in the browser, portrait orientation. Once it's loaded, you can play to the end even if your internet drops. Only the leaderboard and card links need a connection.
First time playing?
Start by opening How to Play on the title screen.
And when you're confused, just press Absorb (Space, tap).
How it was made
I wanted to make a game about the struggles of office workers.
But I didn't have a concrete idea.
So as an experiment, I let Claude handle everything, from coming up with the idea to fleshing it out. **
But then
After it was all built, I got lost for a long time trying to figure out how to play this game myself.
Since it wasn't an idea I came up with, the rules didn't feel natural to me. When bugs showed up, I couldn't fix them myself, because I didn't know where or why they came from.
Honestly, I'm not happy with the polish, and as the person who made it, I don't feel much satisfaction.
Still, I got something out of it, so I'm sharing it.
Lessons learned
- The initial idea has to come from a person. You can hand off the implementation. But if "what is fun and why" isn't in your own head, you have no standard for judging the result and no direction for fixing it.
- **An AI writing a lot of docs and me understanding it are different things.
- Next time, I'm going to decide the one core fun thing myself, build it small, play it myself, and only then try to grow it.
- Built with
Comments 1
Translated by AI·View originals
Read the making-of all the way through. The line "If you don't know in your head what makes it fun and why, there's no direction for fixing it" really stuck with me. When I let AI implement things, I often end up with a pile of docs and yet the criteria for judgment are still empty. The concept of "the less painful choice" is good. Since all three resources get drained, the structure naturally pushes you to weigh gains and losses instead of looking for a right answer, which is clear. One suggestion: the half-day (F) feels almost like a reset button. If you make its cooldown or cost a bit more visible, I think it would add one more "spend carefully" decision. For mobile swipes, giving a little leeway so that a swipe slightly off direction still counts when it's just short of the judgment line would probably cut down on the unfair failures. You mentioned next time you'll pick the core fun yourself and build it small. For that, I'd write the rules down in a one-page doc first and start from there. It'll make balancing much easier later. Nice work.