At a high level, someone should be championing that the overall project succeeds, which includes a lot of different workstreams:
- Defining overall goals for the program and timeline
- Figuring out what needs to happen before we launch this project (e.g. beta roadmap) and working to make sure the pre-reqs are met
- Sourcing and engaging with potential partners, making sure we get applications from projects we want to work with
- Leading process for deciding on top 3, and timeline for onboarding them
- Acting as point-of-contact for the pilot partners
- Working to onboard the pilot partners
- Keeping track of how they’re doing, intervening when issues come up
For some of those tasks, it seems like I’m the natural owner, specifically defining the overall goals, identifying dependencies, and making sure the dependencies are satisfied. However, I’d like to delegate a lot of the BD tasks. So maybe we should think of this as three initiatives:
- Overall Beta Initiative
- Define goals & timeline for the project
- Ensure feature work gets done on schedule so we can launch it
- “The buck stops here” responsibility for the overall beta
- Pilot Partnership Recruitment
- Define what makes a good pilot partner
- Recruit pilot partners, figure out a process for tracking applications, etc
- Lead process to choose 3 partners
- Pilot Partner Point-of-Contact
- Once the program is on, responsible for tracking how they’re doing, ensuring they get support, etc
In that case, I’m the champion for the overall initiative, and we need a champion for the second one (recruitment) to answer @s_ben’s original question. Part of my job as meta-champion is to recruit the sub-champions.