This is a team with multi-functional advanced skills. The roles include:
Platform and Tools Architect: Responsible to define the requirements of hybrid multi-sourced IT platform, implement and manage it, integrate tools across different infrastructure providers
Patterns and Practices: Responsible to identify commonly used application patterns, infrastructure patterns, assess re-usability and provide recommendations to the Product Management team
Security and Risk: Responsible to define the security posture of the organization, distinguish the different security levels for applications and data, and provide guidance for the Product Management team to bake the requirements in every product that they develop
Cultural change is required in IT organizations. Every service that they provide to the business users should be a “product” and it has to be dealt with in a product management fashion starting from ideation till revenue-recognition. The roles include:
Business Liaison: Responsible for working with business users and Patterns and Practices team to define the requirements of the offering and feed the inputs to the Service Engineering team
Service Architecture: Responsible for architecting the offering with right parameterization for re-usability
Service Engineering: Responsible to design, develop and test the offerings
Finance Controller: Responsible for developing pricing models for the offerings
This team is a mix of in-house, outsourced and crowdsourced workforces for managing large one-time changes.
Atomizers: Responsible for breaking the large change into micro-tasks. The criteria to break tasks are: 1) one person can independently execute the task, 2) the person has role-based access only to that task and not the entire system
Line Managers: Responsible for a given track of activity, establish the factory-line and populate manual or digital workers to progress on the line
This team is responsible for Day 2 operations and continuous improvement
Automation: Responsible for watching high-traffic, high-effort manual activity to manage Day2 operations and developing runbooks and scripts to minimize effort and time.
Incident/Problem Management: Responsible to manage incidents and service tickets requiring human attention.
Looks like a massive change… How to?
It’s a major cultural change and plenty of re-skilling and normalization may be required to get to such an org structure. And it costs money. Some of the roles can be modified job descriptions for existing skillsets, but a majority will need reskilling. Practically, establishing this org structure could be a 12-18 months’ timeline and it’s worth the effort – a team with frictions and inefficient organization structure may cost more than the actual transformation costs.
The roles and responsibilities are presented at a high-level in this article. For more detailed job descriptions, please reach out to firstname.lastname@example.org.