Instead of looking at our entire workload as a never-ending pile of features to build, integrations to create and automations to… well, automate, we just look at it as a series of 2-weeks-worth lists of projects to accomplish.
This is a bad Reman U. I mean it. It hasn’t been thought through, agonized over, contemplated, speelchecked or proofreaded. I didn’t have a blinding insight nor did I have one of those everyday experiences that suddenly feels like an analogy for good work/life decisions. What I do have is a deadline, a commitment – ultimately, a promise. I would rather sign my name to a bad Reman U than break a promise. So, this is a bad Reman U, but maybe that’s a good thing.
Imagine with me for a moment that you and your team are working together to build a project vehicle. Because of scheduling challenges, each of you has to take separate turns doing the work. When your turn arrives, you enter the workspace to find all the parts you’ll need. It’s obvious something has been done, but it’s not at all clear how far and where your predecessor left off. You spend the first several minutes of your time figuring out what’s been done and then get to work.