Does process hinder innovation and ownership in software development?
David Genn
CEO at Goji, and Head of Product, Alternative and Private Market Funds at Euroclear. Building a global network for private funds, combining technology and financial market infrastructure to create scalability and growth.
Companies like Netflix and Valve have gone on record to explain how they actively remove process from the way they build software to encourage innovation and to allow developers to take responsibility for the code they write.
There’s no doubt that process can cause people involved in building software to see their contribution to the whole with blinkers on. Without thinking about it, they only consider the work they need to do before they’ve finished their part and they can chuck it ‘over the fence’ and it becomes someone else’s problem. Even the best intentioned people can fall into this trap. It’s what happens when our processes and team structures mean we’re only made responsible for one part of the process chain.
There are times when we need process to ensure we do mission critical tasks as mistake free as possible. But how do we prevent process from stifling freedom, creativity and taking responsibility?
Read the full article on Medium.
Follow me on Medium.
Follow me on Twitter @david_genn