Sitemap

How to make the case for a better development workflow

and why properly framing the issue matters

5 min readMar 22, 2014

--

Daunting Tasks

You’re a web developer.

A year ago you watched a YouTube video or a talk at a conference about improving your development workflow. It was full of flashy new tools with magical names like Grunt, Yeoman, and Bower. It was interesting but at the time you were already working on a project. The overwhelming task of fitting these new flashy, mysterious tools into your existing project’s workflow was daunting. You decided to keep your head down and stick with the status quo for now.

Fast forward a year. You’re finally finished with the last project you are about to start another one. You’re considering using some of the new, hip workflow tools that are out there but your project manager wants to get rolling quickly on a new project. The principles advocated by the creators of the new tools make sense and the features are fantastic but you still have reservations. You’ve never used them before, so you need some time to get up to speed from a technological perspective. Additionally, you’re unsure whether you’re the right person to advocate for such a significant shift in the workflow of your team. Will it look like you’re stalling? Will it cut into the timeline of the next project? Will you make enemies on your team or appear bossy by trying to get others to work differently? Is it even worth it if legacy projects will be using the old workflow?

These are important questions and their answers can be challenging, but, the good news is that by thinking about them, you’re already ahead of the curve. You should also know that you’re not alone in asking them and wondering about how best to go about making the argument for their adoption in your organization.

Status quo, friend or foe

Getting other people to change their workflow is really, really hard and this is a good thing. It should be hard to get people to change their workflow. If we spent all of our time changing workflows then we’d never get anything done. In geek speak, context switching is expensive. For this reason, many business structures actively discourage rocking the boat when it comes to the development process. Centralized IT, development managers, and project owners/leads are incentivized on a per project basis. Moving forward, I’m going to label these people project drivers.

Get Jim Cummins’s stories in your inbox

Join Medium for free to get updates from this writer.

Unsurprisingly, many of the most productive developers use their current workflow very effectively. They are so effective, in fact, that they might not know (or care) about vastly improved features that are available to them right now and are relatively pain free.

For you, the risk of changing your workflow is that you may be temporarily unproductive, which could have real consequences to your job, your team and the company. The potential reward is that you could significantly increase your productivity and effectiveness in the long term. The problem for you as a developer is that generally the project drivers are often very good at doing their job. Their job is to keep you focused on the task at hand, and generally to keep refactoring of code or processes to a minimum.

When you’re attempting to make the case for workflow improvements, it is important to see project drivers as an opportunity, not an adversary. Most apprehension on the product drivers’ part is likely to result in the fact that you’re telling them something that is fundamentally contrary to their job role.

At first this might seem to be an insurmountable barrier to getting your changes approved, but don’t give up so quickly. Instead, see this as an opportunity to practice making the case for your position. If you can put together hard documentation of how much time per day this is going to save each developer, then the product drivers are able to convert this into dollars and convince themselves of the benefit.

Additionally, you can make the argument that allowing each developer to upgrade their workflow occasionally, actually spurs innovation without having to hire outside resources or paying for continuing training. It helps to limit turnover and saves the company time and money because rather than any one entity having to manage the workflows of the entire team, there can be asynchronous improvements in the overall workflow. If a given practice obtains enough support, then it will be adopted organically by members of the development team. Often this method, which I’ll call the disjointed workflow approach may look like chaos to managers or infrastructure teams, but as developers we know that this experimentation is necessary to drive creativity and continue to stay on top of the productivity foodchain.

Focus on tinker time, not tech

In the end, regardless of how good a technical argument you make, your exact technical recommendations might not be adopted by product drivers, the rest of your team and the company as a whole. For that reason, focus your argument on general awareness of the issue. Don’t allow the discussion to go into the technical specifics. That’s your job and they need to trust that when you ask for time to improve that function of the business, there’s a good reason for it.

If you’re like me, you don’t want to have the same discussion, asking for workflow improvement time after every single project. So instead, focus on making it habit for product drivers.

Take pride in asking that any resulting allocated time makes it on to all official project and business timelines. You needn’t be expected to squeeze this in on the weekend or at night just because product drivers might not see it as a customer driven project. You are allocating time to it, and it is a business critical function. That means you should be working on it at work, and should be getting the praise and recognition you deserve.

Remember that workflow improvement benefits you, the team, product drivers, and the company, and that as long as you focus on that, the technical details don’t matter.

--

--