Change Details

//Instructions // # Define the problem or opportunity (WHAT). # Outline the importance of addressing the problem or opportunity (WHY). = WHAT? **Write your problem statement using layperson’s terminology. In one sentence, what is the problem or opportunity?** - There is no source of truth for all the different software components we own and maintain. **What does the future look like if this is achieved? ** - Service information like SLOs, API Reference Documentation, and more can be found in one place. - Rules and governance can be codified rather than done manually - Code ownership and clear points of contact will be made available per service **What happens if we do nothing?** - Discoverability of APIs will continue to be difficult - Service information, documentation and code will continue to live in different places with no great way to connect them all - Code ownership will continue to be difficult to manage = WHY? **Identify the value(s) this problem/opportunity provides. Add links to relevant OKRs. ** //Rank values in order of importance and be explicit about who this benefits and where the value is.// **User Value/Organization Value AND Objective it supports and How** # API practitioners (Internal Devs, External Partners, Product Managers, SRE) can easily discover and leverage APIs **Why are you bringing this decision to the Technical Forum?** //What about the scope of this problem led you and your team to seek input across departments/organizations?// - How might we best design a sustainable way to codify pertinent service information like status, owner and documentation? - Understand what efforts have been tried in the past and why haven't they worked well? - Who else would benefit from using/leveraging this product?

**FINAL DECISION STATEMENT OVERVIEW:** https://docs.google.com/document/d/1_C-okd1VBQMmNPMNOOWx0EKC7aXSxplGaOa1x4Yg5sc/edit?usp=sharing __________________________________________________________________________________________________________________ DRAFT PROPOSAL: //Instructions // # Define the problem or opportunity (WHAT). # Outline the importance of addressing the problem or opportunity (WHY). = WHAT? **Write your problem statement using layperson’s terminology. In one sentence, what is the problem or opportunity?** - There is no source of truth for all the different software components we own and maintain. **What does the future look like if this is achieved? ** - Service information like SLOs, API Reference Documentation, and more can be found in one place. - Rules and governance can be codified rather than done manually - Code ownership and clear points of contact will be made available per service **What happens if we do nothing?** - Discoverability of APIs will continue to be difficult - Service information, documentation and code will continue to live in different places with no great way to connect them all - Code ownership will continue to be difficult to manage = WHY? **Identify the value(s) this problem/opportunity provides. Add links to relevant OKRs. ** //Rank values in order of importance and be explicit about who this benefits and where the value is.// **User Value/Organization Value AND Objective it supports and How** # API practitioners (Internal Devs, External Partners, Product Managers, SRE) can easily discover and leverage APIs **Why are you bringing this decision to the Technical Forum?** //What about the scope of this problem led you and your team to seek input across departments/organizations?// - How might we best design a sustainable way to codify pertinent service information like status, owner and documentation? - Understand what efforts have been tried in the past and why haven't they worked well? - Who else would benefit from using/leveraging this product?

**FINAL DECISION STATEMENT OVERVIEW:** https://docs.google.com/document/d/1_C-okd1VBQMmNPMNOOWx0EKC7aXSxplGaOa1x4Yg5sc/edit?usp=sharing __________________________________________________________________________________________________________________ DRAFT PROPOSAL: //Instructions // # Define the problem or opportunity (WHAT). # Outline the importance of addressing the problem or opportunity (WHY). = WHAT? **Write your problem statement using layperson’s terminology. In one sentence, what is the problem or opportunity?** - There is no source of truth for all the different software components we own and maintain. **What does the future look like if this is achieved? ** - Service information like SLOs, API Reference Documentation, and more can be found in one place. - Rules and governance can be codified rather than done manually - Code ownership and clear points of contact will be made available per service **What happens if we do nothing?** - Discoverability of APIs will continue to be difficult - Service information, documentation and code will continue to live in different places with no great way to connect them all - Code ownership will continue to be difficult to manage = WHY? **Identify the value(s) this problem/opportunity provides. Add links to relevant OKRs. ** //Rank values in order of importance and be explicit about who this benefits and where the value is.// **User Value/Organization Value AND Objective it supports and How** # API practitioners (Internal Devs, External Partners, Product Managers, SRE) can easily discover and leverage APIs **Why are you bringing this decision to the Technical Forum?** //What about the scope of this problem led you and your team to seek input across departments/organizations?// - How might we best design a sustainable way to codify pertinent service information like status, owner and documentation? - Understand what efforts have been tried in the past and why haven't they worked well? - Who else would benefit from using/leveraging this product?