Home → Articles
Want to receive these updates in your inbox? Sign up for my mailing list using the form on the right. (or below if you're reading this on your phone)
My four-year-old was getting a little mopey in the mornings when it was time to go to preschool. He would tell me that he doesn't have any fun there. Of course every afternoon when I pick him up, he's happily playing with his friends, excited to show me the cars he's made out of LEGOs or the dinosaur city he's built.
When you identify a problem in your process but you don't have any ideas for how to fix it, ask yourself "Why is this happening?". Then ask "Why is that happening?" Don't stop until you get to a root cause with a concrete behavior that can be addressed at a department or organizational level.
Keeping your team's communication protocols standardized and routinized means developers will execute on them more consistently and in greater detail. One great way to make these steps routine is to find hook points in your process. These are steps that you know will always occur, into which you can build reminders for your team to take additional steps.
Imagine for a moment that you are in charge of an end-to-end global supply chain with very high seasonal demand. You spend most of the year prepping for one big contract, with a massive scope and a 100% immovable deadline. One day per year, you work a 24-hour shift to deliver custom orders to every single household on the planet. What's your first step?
You're spending too long deciding the specifics of too many things.
Too often when developers have to pass off a project or some amount of information, we assume that the other developer can instantly read our mind. Our colleagues are smart and capable, so we assume they must be able to look through our code and understand everything that we've done without need for further explanation.
Is your dev team working hard but not shipping? I can help.
"What we got from Ben was more than just expertise: it was expertise plus organized thinking, clear communication, good humor, and an obviously habitual willingness to listen before advising. We recommend him without reservation, and look forward to the next time we work with him ourselves."