Challenging your Developers

8 days ago, two very talented developers (more so than I, I freely admit) and little old me, were given a challenge by our employer to get some software ready for today. Not an ultimatum; not a demand: a challenge.

As much as we've worked very hard to get the software over the line, working hard was made easy because we were armed with all the tools we needed from the start. We felt challenged; not put upon.

In the past week, we've experienced stress, frustration, confusion, anger and a constant sense of impending failure... I would do it again in a heartbeat. This may sound, in some ways, self destructive but hear me out.

We knew the business had our backs. Expectations had already been managed for us. We knew that everyone involved in the project were working as hard (if not harder) than us. Everyone we spoke to genuinely cared about the success of this project. They were personally invested, as well as professionally.

Success was infectious. Their wants became our wants and we felt challenged and empowered. The lesson I have taken from this is simple. When you pressure a developer, you become the enemy. They have no desire to go above and beyond for you. When you challenge a developer, things change. They'll relish it; rise to it and reply with vigour.

If you want them to see what you see, challenge them to take on your vision; invite them into your world and give them creative license. Be open; be honest. Let them share your passion.