After two intense months we managed to finish the proposal of our new IT structure. We discussed all the groups and roles and were ready to get feedback from the team. After putting it to a vote the team preferred to see our progress every time that we had something to share as opposed to waiting to see the finished product. So, while we were finalizing the structure and beginning the work of what the day-to-day activities will look like, we presented our first draft of the new proposed structure to the team
Our presentation starts with the four principles that will guide our new IT operating system:
- We are changing the how not the what. Each associate will keep on doing what he wants and learned to do (if you are DBA, you’ll keep on doing DBA work). We are just going to change the way that we are working together.
- We are going to be purpose focused, and our focus is to reach an overall IT purpose, so therefore we split IT into sub-groups based on the needed functionalities to reach the IT purpose. Each sub-group has a defined purpose and based on that purpose any sub-group might be broken further into a combination of sub-groups and/or roles. Each group, sub-group and role has a defined purpose, domains that they own, and accountabilities they are expected to perform. Each group and role should also have metrics to measure success, but we have not defined all of those yet. This should help ensure that we do not have two groups or roles with the same combination of Purpose, Domains and Accountabilities.
- It is a Role Based game. We will not have positions or job descriptions within IT. Instead, we will have a list of needed roles to reach our purpose. Individuals in our group will perform one or more roles in one, or many groups. The roles that they perform will define what they are doing.
- Self-management and Autonomy. Given that each group and role are well defined, and the accountabilities, domains and purpose of each group and role is known to everyone; each group will have the autonomy to be run by individuals within the group’s roles and to that end each individual that fills a role will self-manage themselves. In essence we are spreading authority across all IT roles, not just the management layer.
Based on these principles we presented:
- A high level view of our IT structure, which includes all sub-groups of IT.
- Definition of IT group
- Definition of each IT sub group (shared service as example)
- All sub groups and roles needed to perform Shared services (an example of Software services as sub-group and Role below)
Following the meeting, we had a few questions that were related to the structure and how daily activities will be done, such as hiring, reviews, compensation, etc. These are all facets that we have now begun to work on.
If you want to get all the available data in PDF file (where all groups and roles are linked) please let me know (at thefriedkincompaniesCIO@gmail.com).