This is the second episode of the second season of the Zeenea Effective Data Governance Framework series.
Divided into three parts, this second part will focus on Adaptation. This consists of :
- Organizing your Data Office
- Building a data community
- Creating Data Awareness
For this second episode, we will give you the keys to organizing an efficient and effective data community in your company.
Season 1: Alignment
- RUnderstand the context
- RGet the right people
- RPrepare for action
Evaluate your Data maturity
Specify your Data strategy
Build a SWOT analysis
Season 2: Adapting
- RCreate your personas
- RIdentify key roles
- RSet your objectives
Organize your Data Office
Organize your Data Community
Creating Data Awareness
Season 3: Implementing Metadata Management with a Data Catalog
- RGet to know your data
- RIterate your data catalog
The importance of metadata
6 weeks to start your data governance journey
Spotify Feature Teams: a good practice, or a failure?
In the last episode, we explained how to build your Data Office with Personas and the Spotify Feature Teams paradigm.
The Spotify model has been criticized because there have been failures at companies that tried to implement it.
The three main reasons were:
- Autonomy is nice but it does not mean that teams can do what they want and there is a need to emphasize alignment
- Key results need to be defined at the leadership level and this is why building your OKRs are the right thing to do.
- Autonomy means accountability and the teams have to be measured and the fact that the increments they are working on need to be done and the definition of “Done” has to be specified.
We will focus in this episode on the Chapters and Guilds and how to organize and better leverage your Data Community.
How to organize your Chapters and Guilds
Collaboration in Chapters and Guilds needs specific knowledge and experience and it is wrong to assume that teams know Agile Practices.
When teams are growing, there is a need to have dedicated support and therefore, the Program Managers in charge of data related topics are accountable for the processes and organization of the Data Community.
At the highest level, organizing your data community means sharing knowledge at all levels: technological, functional, or even specific practices around data related topics.
The main drivers to focus on the Chapters organisation are:
- Teams miss information
- Teams miss knowledge
- Teams repeat mistakes
- Teams need ceremonies and agile common agreed practices.
Chapters meet regularly and often.
We advise to meet once a month. When too big, a Chapter can be split into smaller groups. Even if it is a position that can change overtime, a Chapter needs a leader, and not a manager.
They are in charge of animating and making it efficient by
- Getting the right people involved
- Sharing outcomes with upper level management
- Coordinating and moderating meetings
- Helping to establish transparency
- Finding a way of sharing and keeping available all the knowledge shared.
- Defining the Chapter: why, for whom and what it is meant for.
A tip is to define an elevator pitch for the Chapter.
The Chapter leader is also responsible for building a backlog to avoid endless discussions with no outcome.
Typically the backlog consists in the following topics:
- Chapter Data People Culture
- Chapter data related topics in continuous improvement
- Chapter Data Practices
- Chapter Data Processes
- Chapter Data Tools
- Chapter continuous improvement
- Chapter feedback collection
- Chapter Agility Practices
- Chapter generic tools
- Chapter information sharing
- Chapter education program
The Chapter Lead is in charge of communicating outside of his Chapter with other Chapter leaders and has to get time allocation to animate.
How to start a Chapter
- Identify the community and all members
- Name the Chapter
- Organize the first chapter meeting
- Define elevator statement
- Initialize your the Chapter Web Page (and keep it updated for future new members onboarding)
- Negotiate and build the first Backlog
- Plan the meetings
Guilds should be organized differently and in a self organized way.
The reason for Guilds to exist is passion and the teams are only built on a voluntary base.
In order to avoid the syndrome of too many useless meetings, we advise to allow only Guilds to meet in certain circumstances like:
- Trainings, workshops but in short formats like in BBLs (Brown Bag Lunch) for the topics they built the Guild for
- Q&A sessions with top executives to emphasize the Why of the Data Strategy
- Hack days to crack a topic
- Post mortem meetings after a major issue has occurred.
Get our free Data Stewardship Chapter Lead Handbook
Start building your Chapters by downloading our free Chapter Lead Handbook!
Don’t miss next week’s episode!
We will cover all the basics to building your Data Awareness to help you to get an Enterprise wide adoption and rollout of your Data Strategy.
Copyright Zeenea 2021, all rights reserved.