It was a long journey of trying to understand what organisational structure is best for dynamic growth, experiments, agility and change. While trying to understand how it might work had tons of discussions inside my team and series of disconnected posts validating ideas gathered from various sources about principles and challenges:
But all these were kind of separate notes and most often feedback can summarized into this – “ok, seems reasonable. but what should I do? How my team should act from now on?”
Within our work group we made a decision to write down everything on paper and use it as a starting point for our continuous journey. We call it – POD framework.
Some things to keep in mind. Framework doesn’t describe exact roles with units (product managers, developers, analysts, marketers or whoever is needed) or even how to implement it exactly. Framework sets boundaries and principles how growing organisation must work and what is needed for healthy growth and collaboration.
Will continue sharing main aspects of framework in a series of posts, but you can find a link to whole description at the end of the post. Feel free to comment. So, here we go…
There is a tendency to organize around functions when organisation grows, but POD framework suggests to organize around the consumer forming interdisciplinary product development units. PODs are responsible and autonomous to deliver on metrics indicative of awesome customer experiences.
The interdisciplinary product development units have members of all skills needed to complete particular tasks, which is obviously a great approach comparing to the component teams. Normally component teams focus only on software development, and leave other parts of product development (pre-development and post-development stages) less attended.
POD shifts focus from software development only. Focus on market and customer needs extend development teams with additional skills needed to deliver value to the identified client (differs from POD to POD i.e.: feature PODs can have client support <add more if needed> people).
All POD members are focused on meeting market and customer needs (external or internal), and not reaching its own goals that do not always relate to end-user value.
The benefits of it are rapid value delivery due to clear understanding of what and why is valuable and for whom, reduced dependencies, partnership behaviour and increased product quality due to dedicated focus and straightforward communication and feedback. Communication between PODs is based on partnership and value delivery for Company (e.g. Adform).
p.s. Pod framework v 0.2 – https://drive.google.com/open?id=1iHixEsXYKtQB89nFPXiuE6fpFT2sjXs2JpyElCVXie0&authuser=0
Feedback is welcome. Feel free to add comments.