Owning the initiative means being responsible for progress being made within the initiative and for it to be completed on time. You need to think through the following and make a clear plan before you create the initiative in Howwe:
- What is the purpose of the initiative, what do you want to achieve? What are its objectives? And within what time frame? It can sometimes be a difficult task to concretize purpose and objectives, but it is time well-invested as it creates clarity among the teams that are expected to contribute!
- Which teams are expected to contribute to the initiative and the sub-initiatives you have identified?
- Are there clear sub-initiatives that are then owned and run by other teams? Sub-initiatives can be a good way to create an even clearer structure and plan.
When the above is clarified and key stakeholders are in agreement on purpose, objectives, structure and responsibility, it is time to firstly create the initiative in Howwe and then to communicate to teams what is expected of them:
Explain and anchor the purpose and objectives of the initiative in relevant teams, describe how you see that these teams can contribute to progress within the initiative.
Then give the teams a deadline to create their first plan.
- When do you want the plan to be ready? For example in 2 weeks.
- How far into the future do you expect teams to have a plan? For example: at least one quarter
Teams that are expected to contribute to the initiative now create the Key Activities in their regular Howwe sprint that are required to make progress on the initiative, and tag these with the correct initiative tag.
Milestones are a way to identify the Key Activities that are more critical than others to achieve in order to progress the initiative. A good way to work is to start with Milestones and in a second step break these down into smaller Key Activities that need to be carried out.
Very important is that the teams or stakeholders who own and drive the initiative then critically review the plans teams have made. Are they of good quality and and well thought out enough for initiatives to be carried out as intended? Provide feedback to the teams.
Very often, initiatives are cross-functional in nature. Then the team that owns and drives the initiative needs to keep the contributing teams together and help them create a realistic plan, identify cross-functional dependencies, and collaborate. A good way to do this is to book meetings with key people, monthly or quarterly, where cross-functional dependencies can be discussed and sorted out.