Instead of due dates we use next check-in dates for projects at egghead

Have you used Jira?

It's a hellscape of dates, swim lanes, buzzers, metrics, and productivity wanking that leads to an entire career option of full-time employment as a Jira wrangler.

A "project manager" if you will.

At some point in our software journey the entire idea of product management, productivity, tasks, getting things done, working smarter... it's all turned into a pile of dirty laundry that causes stress and pushes people away from the actual activity that we want to participate in:

Collaborating on building nice things that help other people achieve the outcomes they desire.

That's the essence of a project, and as soon as it needs a manager to manage it the entire character of the activity changes.

I'm a shit PM.

This is something that I will freely admit.

I can definitely get work done. I can rally and organize when needed. I can structure work, time box, produce gantt charts, and do all of the other things needed to get a project over the finish line.

But I only want to do this when absolutely needed. Most of the time we are doing work that doesn't require an arbitrary due date. There's no really need to estimate the work.

It's just fuckin' guessing anyway, and pulling numbers out of my ass to paste them into a spreadsheet is definitely not the flavor of collaboration that I am looking for.

One small change we've made at egghead is to remove the idea of a due date and replace it with a next check-in date. This is some time in the future when we are going to check back in on the project. The check in isn't to manage the project, it's simply to say hello, summarize where it's at, decide if it's done, and figure out the next steps with the folks we are collaborating with.

The checkin dates serve as a marker in the future for communication and also represent the general urgency or priority of a given project. Some things will get weekly checkins, or even multiple checkins during the week by setting the next check-in date to tomorrow or the next day.

Other times the next checkin date might be a month, or three months.

The point is that we are designating some point in time in the future when we want to discuss the work, summarize what we know, and layer more context onto the project and see if it's still something we want to work on.

Thanks to Marie Poulin for this idea ❤️

It makes me smile when I see it.

Let's chat about coding, business, learning, and teaching.

I send articles and thoughts occasionally and love to have conversations with folks. Lots of people like them, and I'd love to learn what you think as well. You can always unsubscribe.

Joel Hooks © 2022