289
Ubisoft Insider Alleges That Company Wants Steam To Remove Concurrent Player Counts To Hide Its Failures
(fandompulse.substack.com)
this post was submitted on 27 Nov 2024
289 points (98.7% liked)
PC Gaming
8775 readers
246 users here now
For PC gaming news and discussion. PCGamingWiki
Rules:
- Be Respectful.
- No Spam or Porn.
- No Advertising.
- No Memes.
- No Tech Support.
- No questions about buying/building computers.
- No game suggestions, friend requests, surveys, or begging.
- No Let's Plays, streams, highlight reels/montages, random videos or shorts.
- No off-topic posts/comments, within reason.
- Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Key Performance Indicators (KPIs - I know you know what they are, but for anyone reading who doesn't) are such a terrible metric for performance. Like, yes, well performing teams generate good KPIs because they're performing well. The minute a suit tries to actually tie a KPI to performance, people start gaming them and the product suffers.
A little bit of a segue here, but Factorio recently released some tidbits about their performance when they wrapped up development. They said they have 0.24 sales per line of code. Now they're a very different team making a very different kind of game for a very different kind of market, so I take this as the amusing corelation it is without putting any stock into why that is.
Some project manager from Ubisoft is going to read that and think, "Well we can do better," and start mandating more sales for less code. Next thing you know, devs are being punished for verbosity (an ironic twist on the classic and often abused KPI of how many lines of code are written) and before you know it you've got compound statements, nested ternaries, and inscrutable lambdas out the wazoo that make maintaining the code base impossible.
I wonder if I minified all my source code into a single line before compiling if I could game the system ๐ค
Yeah, product managers and executives will never find a performance metric they won't immediately pollute. They seem totally immune to the idea that once you start trying to directly impact them, they lose all meaning.
When I was interviewing for my first job in the video games industry, I came across an anecdote that spelled the whole thing out to me. Some game team discovered that players who completed their tutorial in under X amount of minutes (let's say 10, to have a concrete number to play with) where significantly more likely to make an in-game purchase (I worked in mobile gaming). So, the team was instructed to reduce the length of the tutorial so that almost anyone could complete it in 10 minutes or less.
Weirdly enough, this did not work.
Decision makers who "use data" to "drive decisions" seem to totally lack the ability to consider what the data means, who their customers are, or why people behave in the ways that they do. It's exhausting.
Relavent xkcd