Even months removed from their initial play through, Genesis Noir and Observation have stuck with me. It’s not due to either game’s overall quality; both impress with plenty of initial style and swagger, only to narratively stumble in the final acts. Instead, it’s all about their daring approach to user interface and control scheme, both which change frequently throughout the story. The experiences I had with both games made me realize how thrilling it can be when gaming conventions are broken.
For most modern games, the UI and control setup remain consistent throughout the a playthrough. For example, in the most popular game genres today – first person shooters, third person action adventure, and sports – you use a controller’s analog sticks for movement and looking around. For shooter titles like Destiny 2 and the Call of Duty series, there are expected conventions on the HUD to show player health, ammo, and a mini map of the player’s surroundings.
Engineering managers get a high quantity and variety of inbound requests. At any point, you can be on the hook for the status of individual projects, career growth questions, support issues, and more. Questions and expected follow-ups can pop up in many contexts, be it 1:1s with reports, standups, or cross functional meetings. Managerial triage and delegation are commonplace that makes handling asks from all sides especially important.
However, none of this was apparent to me in my first engineering management role. Even when I caught up with reality, I naively expected to handle the increased load without issue. I organized my to dos in a trusted app setup. I could juggle taking detailed notes while simultaneously participating in meetings with ease. But at some point, a few months in as my number of reports increased and work volume spiked my system started to break down. I was dropping follow-ups. I would bury away action items in notes I would forget to review later. It was at that point I realized I had to adjust my workflow. One of the biggest lifts came from adding ticklers to my routine.
I define a tickler as a reminder of anything that I need to review on a future date. For example, a Slack thread where I’m waiting for a response. Or a good idea that comes up in a meeting that I don’t have time to process now but potentially will later. I generally structure ticklers in the form of simple questions: