I like this heuristic, and have a few which are similar in intent to it:https://twitter.com/codinghorror/status/1055607400395231232 …
-
-
An idea is floated for a new business unit / product / whatever the local equivalent is given company/industry/stage. How long until it launches into the hands of customers who perceive it as a generally available offering?
Show this thread -
How many keystrokes would be required to do an A/B test of the H1 on the homepage? How many minutes from first keystroke to first person seeing it in production? (I'm being very generous to the software industry here. *sigh*)
Show this thread -
How long does it take an email from an unrecognized email address to the most generic tier 1 support alias to reach a senior responsible engineer / lawyer / executive given clear relevance to them?
Show this thread -
What percentage of emails which an omnipotent, benevolent deity would route to a senior responsible engineer / lawyer / executive factually make it from tier 1 customer support to a senior responsible engineer / lawyer / executive?
Show this thread -
You might sensibly read these heuristics and think "Hmm, you seem to over-focus on speed. Aren't quality, price, etc also really important?" These questions don't *really* test for speed. They test for *repeatable competence at scale*, which is another thing entirely.
Show this thread -
Incidentally these make good questions to get informal reads on companies and/or fill the "So, any questions for me?" part of interviews, because they're much more specific than "Do you like working here?", less likely to elicit social desirability bias in answers, etc.
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.