But this is not always feasible, and when it's not handled carefully, it can turn into a stressful scenario where Software Developers are left feeling frustrated, and some or even many are left feeling as though their contributions don’t matter.
This is dangerous territory when it comes to employee engagement and customer satisfaction. At DotActiv, we have a clear vision for where our software products are headed, and this is because there are a number of people within the company that have different levels of influence over product decisions.
Senior management obviously has their influence. Marketing and sales, for example, consistently give high-level feedback about what it is that Retailers and Suppliers are looking for in their category management solution. IT Support and customer-facing staff also regularly get the features that they ask for, and especially so when they add value to our clients.
But what about Software Developers? Should they have a say over product decisions or should they simply write code that is 100% in line with development specifications? Our answer to these is unequivocal: Software Developers should definitely have a say over product decisions.
Obviously this should be managed; otherwise, it will quickly become a directionless free-for-all. For this blog I am going to highlight a few important reasons why our Software Developers have a say over product decisions here at DotActiv:
1. It creates a sense of ownership and pride
Ever seen a project go well when nobody has any emotional connection with the success or failure of the project? Me neither. Our experience has been that when Software Developers have a say over the products that they work on, they take ownership and pride in a product which they call their own.
This emotional connection and pride contributes significantly to the success of a product.
2. It’s motivating
When Software Developers have a say over product decisions, they tend to have far higher levels of buy-in regarding the future of a product (and business). Nobody in their right mind wants to develop something that they don’t agree with, especially when they didn’t even get the chance to explain why the specification is not good for the business.
Now consider the opposite. Why would you not do everything in your power to bring a specification to life when you contributed towards the specification in the first place?
3. Deadlines and specifications end up being more realistic
It turns out after talking with some of our Developers here in the office, nothing is more frustrating for them than an unrealistic deadline. This is understandably so - if you have a sense of pride and ownership over something, why would you want to rush a feature only to deliver something which is less than your best? You wouldn’t. Also, unrealistic deadlines result in Developers becoming stressed out which has a knock-on effect on the whole work environment and productivity in general. Lastly, unrealistic deadlines set project plans up for failure which is very demotivating.
Including our Software Developers in product specifications and their associated timelines for delivery usually results in more accurate estimates of the time needed to complete new features.
4. Our technology stack keeps up with the latest trends
Now that we have established how there is an open line of communication regarding product decisions here at DotActiv, it is important to know that our technology stack is no exception. In fact, our development team is often asked to spend time researching how we can improve our technology stack. This often results in experimenting with new plugins, API’s, neural networks, cloud infrastructure and others.
When an experiment makes sense for the business, it becomes part of our technology stack.
Conclusion
If having a say over product decisions resonates with you, why don't you go ahead and apply with us? You can browse all of our open positions here apply here.
COMMENTS