Numbers To Know For Managing (Software Teams)

0 - the number of times you should lie
0 - the number of pages your team should get off hours
1 - the number of times you should try to reverse a sincere resignation
2 - minimum number of direct reports anyone should ever have
3 - the minimum number of candidates you should interview before making a decision
4 - the number of minutes to spend on chit chat in the beginning of a meeting
5 - the number of comments on a document before you should ask to talk about the issue
6 - the number people tell you when they’re very unhappy
7 - the number of days before a new hire should have merged a pull request
8 - the % of people that should be rated as underperforming in a growth company during a bull market
10 - the max % you should be looking to negotiate an offer
30 - the number of days before a small support issue becomes a large support issue
50 - the number of Pull Requests a solid engineer should merge per 6 months
70 - the target % close rate for recruiting in a “regular” market
90 - the number of days a role should stay open
100 - the way you should keep it
200 - the maximum size of “small data”
500 - the number of employees before your CEO becomes a political figure
1000 - the size of company when you’re at risk of losing accountability
3905 - the average number of days from initial funding to IPO, for companies that make it