About Us – The Practical Player
After the Kids Are in Bed
Most nights I get about ninety minutes. Sometimes less. The kids are six and nine, so by the time dinner is done, baths are finished, and the last story is read, the house finally gets quiet. That’s when I sit down at the PC or pick up the controller. I don’t have the luxury of “just one more hour.” Tomorrow is another full day at work, and I need those ninety minutes to feel like they counted.
I’ve been playing games for roughly twenty years. PC, PlayStation, Switch—whatever fits the night. I’m not chasing leaderboards or perfect completion percentages. I like systems. Resource loops. Skill trees that actually branch into different play styles. Base layouts that reward a little foresight. The kind of games where decisions compound and you can feel the difference between a good evening and a wasted one.
What Product Ops Taught Me About Games
By day I’m a Product Operations Manager at a SaaS company here in Austin. A lot of that job is mapping dependencies, spotting bottlenecks, and figuring out which processes actually move the needle versus which ones just look important on a slide. After a while you start seeing the same patterns in games.
A skill tree that looks exciting on paper can be a trap if the early points don’t open meaningful options. A production chain that “works” can still leave you short every night because the layout forces constant backtracking. Gear upgrades that are “better” on paper sometimes just slow you down because the resource cost isn’t worth the marginal gain when you only have an hour and a half.
I started writing things down because I kept repeating the same questions to myself: What should I actually do in the first two hours of this new survival game? Is this economy punishing me for bad layout or just for not grinding enough? When I come back to a save after three months, where do I even start without feeling lost?
The 3D Printer and the Scrap-Paper Habit
Outside of work and games I run a 3D printer mostly for board-game accessories, controller stands, and the occasional D&D terrain piece. There’s something satisfying about designing a small practical object that solves a real annoyance—extra card holders for Wingspan, a better way to store Root pieces, a stand that keeps the Switch from sliding off the couch arm. The same mindset shows up in games. Before I commit to a major base expansion or a long crafting project, I still sketch the resource flow on a scrap piece of paper. It saves me from realizing two hours later that I built the whole thing facing the wrong direction.
I’m not trying to optimize every second. I just want the time I do have to feel productive and fun instead of frustrating. That means knowing when to stop for the night before I create a mess I’ll have to clean up next session. It means recognizing when a system is deep versus when it’s just time-consuming. And it means giving myself permission to pick the “good enough” option instead of the theoretically perfect one when the clock is running.
Why This Site Exists
I started writing these notes for myself. Then I realized a lot of other adults are in the same spot—full-time jobs, families, limited evenings—and most guides still assume you have unlimited time or that you’re racing toward the optimal route. The Practical Player is simply the place where I put the practical version of those notes. Clear recommendations, honest tradeoffs, and an eye on the clock.
If you only have ninety minutes tonight, I want those ninety minutes to count.
— Mike Bennett
The Practical Player
Austin, Texas