This is interesting because I know I do much better at analysis work later in the day. That could be the case for this worker.
One of the problems I had with a 7-3 shift is my productive time for writing is 1-4. Luckily I could find tasks that needed to be done that would support the thinking work later. Trying earlier = wheelspinning.
https://www.askamanager.org/2018/07/my-employee-works-late-every-night-but-it-seems-to-be-her-fault.html
I live in a small Canadian Prairie city with a spouse and a dog. We retired in 2018. This is what life is like.
Subscribe to:
Post Comments (Atom)
-
Weight loss is more than calories in and calories out. Research using a pool of 10,000 participants. People tend to gain weight back. Differ...
-
We were in Edmonton so I took the opportunity to visit the Microsoft Store, check out the Go and finally purchased it. I knew there was a ...
-
Have you checked out your google info? Now much clearer! https://www.androidcentral.com/google-account-page-android-updated-new-ui-and-featu...
Yeah, my problem with working 8-5 is that I'm rarely productive before lunch. My body doesn't naturally wake up until around 10 ... so I'm going hours in zombie mode every day. Some of my most productive days are actually the times I come back after dinner and plug away. No interruptions, distractions, and my brain is actually firing on all cylinders.
ReplyDeleteOh this is exactly what comes of mismanagement. Set smaller goals.
ReplyDeleteI am a man who is motivated by deadlines, okay? So I set four deadlines for every project: how many days until delivery? Divide by four. The first quarter is mostly screwing around, finding where everything is gonna live, getting the team in chairs and computers, getting everyone set up with passwords, writing the initial use cases.
The second quarter, until the halfway point, is a set of feeble-minded prototypes, until I've found out who's actually going to use this thing and bless it.
At the halfway point, everyone puts down tools, does a frank and brutal assessment of what Done means - and starts the hell over, this time, doing it right.
At the three-quarters point, management is summoned, the alpha user ( who was found, hopefully during the first quarter, but usually around that first quarter point ) explains what's been done to date. Nobody emerges from this meeting entirely happy, but they know what Done means and sometimes, if things have gone well in the second quarter, are quite happy with how much they understand about what they're going to get.
The fourth quarter is when things get finished. And on the delivery date, the alpha user delivers. Not me, not my team. The alpha user.
I have done my share of overnights. I've slept in my office. I've slept on the floor of the client's office, on his couch cushions. I deliver on time.
But this manager is as much of the problem as the subordinate. Long hours don't mean jack. Achieving objectives is all that matters. So the manager ought to set smaller objectives. Force the subordinate into a meeting every morning. Lasts 15 minutes. It's called an Agile Stand Up. What did you get done yesterday, what will you do today - and if yesterday is the same as today, there's an intervention, right there.