[crdoconnor]

>Is turning up on time for your job a terrible metric?

The worst metric.

That is, unless the "turning up on time" is actually causing a serious and recognizable problem. Then it's the problem that's a problem.

>As the initial commenter said: trust goes both ways.

No it doesn't. If you put the onus on the developer and say "not only do you have to deliver high quality code you have to make me trust that you've delivered high quality code by adhering to these arbitrary metrics I've come up which bear no intrinsic relationship to how you do your job" you're admitting incompetence as a manager.

It's a manager's job to know whom to trust and a manager that trusts the useless developer who turns up at 9am sharp over the excellent developer who turns up at 9:05am requires termination.

>Actually, turning up on time may not make your manager trust you more, but turning up late will definitely make them trust you less.

It will definitely make a bad manager trust you less.

A good manager will either recognize that you're delivering or not.

[titzer]

> A good manager will either recognize that you're delivering or not.

And a great manager will evaluate the wider effects of your behavior on the whole team and over a long timescale. If you being late to your job causes others to start doing the same, and if your manager cuts you slack because you are a "high performer" then social dynamics come into play that must be...well...managed! Performance also slips over time. People get spoiled, sometimes depressed, sometimes lazy.

Managers look at whole teams and long-term trends. Stop focusing on yourself and the immediate moment. Success is a marathon, not a sprint, and requires careful, regular progress.

[IronKettle]

> If you being late to your job causes others to start doing the same

You're missing the point entirely: Who cares if they're also late?

Short of them being late to something important like a meeting, it seriously couldn't matter less than any of the thousand other things you should focus on as a manager.

Unless you work in something with external time pressures (e.g. I used to work in equities and US market hours dictated our need to be available) there's no reason it should matter whether someone shows up at 9 or 9:45. If you're really worried about people missing each other, set core hours (11-3 say) where everyone's expected to be available.

[ionforce]

You're missing his point. Being late could (hypothetically) have side effects that affect the morale of other team members.

[crdoconnor]

>If you being late to your job causes others to start doing the same

If they also are producing and not causing other people problems then I see no problem.

However, if they are not producing then that is a problem. However, if they are coming in on time and not producing that is exactly the same problem.

The point is that one problem is unrelated to the other.

>social dynamics come into play

Social dynamics always come into play but in this instance, they really don't matter. If a manager knows how well everybody is performing and is communicating that then these other intra-team dynamics you are talking about simply don't happen.

It seems to me that you're coming at this from the perspective of a manager who fundamentally does not understand what they are managing and isn't cognizant of who is performing and obviously isn't communicating that because they don't know.

Because that's exactly when you would see the intra-team dynamics which you're describing will happen. That is what happens on most software teams, sadly :(

>Success is a marathon, not a sprint

I never said or implied that it was anything else.

>Stop focusing on yourself and the immediate moment.

I am focusing on neither.

I am beginning to suspect that you are exactly the kind of manager I'm talking about here. Hi.

[FilterSweep]

The dev who showed up at 9:05AM was probably also working on a production issue the night before.

While manager slept.

[dozzie]

>> Is turning up on time for your job a terrible metric?

> The worst metric.

Not really. If your job is to be available to others (IT support is a good example), turning up on time is an adequate metric.

[crdoconnor]

That's kind of what I meant when I wrote "unless the "turning up on time" is actually causing a serious and recognizable problem. Then it's that problem that's a problem".

Yes, for IT support type roles I think measuring online availability as one aspect of job performance is legitimate.