Skip to content

Commit

Permalink
Respond to review comments
Browse files Browse the repository at this point in the history
  • Loading branch information
choldgraf authored Jul 30, 2024
1 parent c0d406b commit 85bf3e6
Show file tree
Hide file tree
Showing 3 changed files with 11 additions and 43 deletions.
16 changes: 8 additions & 8 deletions product/deliveryflow.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,29 +9,29 @@ Process diagram of 2i2c's [Product Delivery Flow](https://miro.com/app/board/uXj

This document outlines such a process, designed to be transparent to the organization about what’s been worked on at any time, and to provide clear communication and collaboration points between Product, Engineering and any stakeholders, internal or external, that have a vested interest in the outcome of a project.

:::{admonition} ProductBoard is where most Product conversation happens
:::{admonition} Productboard is where most Product conversation happens

We use a tool called [ProductBoard](https://www.ProductBoard.com/) to provide us with a centralized place for storing, tagging and later mining ideas around our product roadmap.
We use a tool called [Productboard](https://www.productboard.com/) to provide us with a centralized place for storing, tagging and later mining ideas around our product roadmap.
This gives our team the ability to fully consider, prioritize, and potentially action the most important ideas.

[The ProductBoard team guide and primer](https://docs.google.com/document/d/1UkFcv2klEBOEnZ4CoB7PnVYS6MNOn5fCfM7unbco2lI/edit?usp=sharing) describes how anyone on our team can use ProductBoard.
[The Productboard team guide and primer](https://docs.google.com/document/d/1UkFcv2klEBOEnZ4CoB7PnVYS6MNOn5fCfM7unbco2lI/edit?usp=sharing) describes how anyone on our team can use Productboard.
:::

## How most team members participate in this process

All team members are encouraged to participate in the Product process by **providing, refining, and discussing Insights**.
To learn how to do this, see [the ProductBoard team primer and guide](https://docs.google.com/document/d/1UkFcv2klEBOEnZ4CoB7PnVYS6MNOn5fCfM7unbco2lI/edit#bookmark=id.27fegmw16krg).
To learn how to do this, see [the Productboard team primer and guide](https://docs.google.com/document/d/1UkFcv2klEBOEnZ4CoB7PnVYS6MNOn5fCfM7unbco2lI/edit#bookmark=id.27fegmw16krg).

## 0. Our product operations principles

First off, read [](principles.md) to understand the high-level goals and principles that drive this work, and lead to the system below.

## 1. The insights board

Insights are tracked in [our Insights Boards](https://2i2c.ProductBoard.com/folder/MTpOYXZpZ2F0aW9uRm9sZGVyOjQ0OTc5ZmRmLWU0MTYtNDNiMS1hYzg1LTllZjFkZmQ4N2Q1Zg==).
Insights are tracked in [our Insights Boards](https://2i2c.productboard.com/folder/MTpOYXZpZ2F0aW9uRm9sZGVyOjQ0OTc5ZmRmLWU0MTYtNDNiMS1hYzg1LTllZjFkZmQ4N2Q1Zg==).

:::{admonition} How to add Insights to Product Board
See the [Guide to adding Insights in ProductBoard](https://docs.google.com/document/d/1UkFcv2klEBOEnZ4CoB7PnVYS6MNOn5fCfM7unbco2lI/edit?usp=sharing).
See the [Guide to adding Insights in Productboard](https://docs.google.com/document/d/1UkFcv2klEBOEnZ4CoB7PnVYS6MNOn5fCfM7unbco2lI/edit?usp=sharing).
:::

Any good product delivery flow starts with establishing a centralized repository for insights, a place to collect our knowledge of the wants and needs of the community partners and other customers we serve, and to record conversations we’ve had with partners about specific product enhancements we may want to consider.
Expand All @@ -46,7 +46,7 @@ Formerly, insights relevant to product improvements were captured on GitHub as c

## 2. The Ideas board

Ideas are tracked in [our Roadmaps boards](https://2i2c.ProductBoard.com/folder/MTpOYXZpZ2F0aW9uRm9sZGVyOjExNGJhMzQxLWQwN2EtNDhlNy05MjVlLWZiNTY4OWVmODBmYw==) as well as [our Feature boards](https://2i2c.ProductBoard.com/folder/MTpOYXZpZ2F0aW9uRm9sZGVyOmQ2YmY3ZTVkLTFhY2UtNGU4My1hMDJjLTRmMzhhOGUyZDkxMw==).
Ideas are tracked in [our Roadmaps boards](https://2i2c.productboard.com/folder/MTpOYXZpZ2F0aW9uRm9sZGVyOjExNGJhMzQxLWQwN2EtNDhlNy05MjVlLWZiNTY4OWVmODBmYw==) as well as [our Feature boards](https://2i2c.productboard.com/folder/MTpOYXZpZ2F0aW9uRm9sZGVyOmQ2YmY3ZTVkLTFhY2UtNGU4My1hMDJjLTRmMzhhOGUyZDkxMw==).

### What is an idea

Expand Down Expand Up @@ -89,7 +89,7 @@ Ideas should be classified as one of the following, each with its own ticket tem

## 3. Product Initiatives

Initiatives are tracked in [our Roadmaps boards](https://2i2c.ProductBoard.com/folder/MTpOYXZpZ2F0aW9uRm9sZGVyOjExNGJhMzQxLWQwN2EtNDhlNy05MjVlLWZiNTY4OWVmODBmYw==) as well as [our Feature boards](https://2i2c.ProductBoard.com/folder/MTpOYXZpZ2F0aW9uRm9sZGVyOmQ2YmY3ZTVkLTFhY2UtNGU4My1hMDJjLTRmMzhhOGUyZDkxMw==).
Initiatives are tracked in [our Roadmaps boards](https://2i2c.productboard.com/folder/MTpOYXZpZ2F0aW9uRm9sZGVyOjExNGJhMzQxLWQwN2EtNDhlNy05MjVlLWZiNTY4OWVmODBmYw==) as well as [our Feature boards](https://2i2c.productboard.com/folder/MTpOYXZpZ2F0aW9uRm9sZGVyOmQ2YmY3ZTVkLTFhY2UtNGU4My1hMDJjLTRmMzhhOGUyZDkxMw==).

Product Initiatives are ideas that we have decided to take a deeper look at, with a view to implementing them to produce value for 2i2c or its communities. The Product Lead, in collaboration with any relevant stakeholders and 2i2c’s Leadership team, will normally determine when an idea is worth taking forward to the Initiative stage.

Expand Down
32 changes: 0 additions & 32 deletions product/overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,35 +4,3 @@ Product describes the services and technology that 2i2c provides, the value they

This section is used to collect and share broad product-related information and strategy.
It is maintained by the {role}`Product Lead <product-lead>`.

## Background

Since its formation, 2i2c has been successful in acquiring and maintaining a good number of client organizations that have benefited from its open, replicable cloud infrastructure services. 2i2c has maintained the ability to remain responsive to the needs of the communities it serves, but in doing so it has taken a somewhat reactive, ad-hoc approach to answering community partner or other customer requests.

As the organization is now more mature, and the breadth and complexity of its offerings and partnerships grow, it needs to shift to a more sustainable approach to the ongoing development of its products and services. This approach should allow it to make more effective use of its people and skills, and ensure that effort is always directed to the activities that are most valuable more closely aligned with its mission and value proposition.

## Identifying a Value Proposition as our North Star

A North Star is a core value, principle or goal that is used to help make decisions about what to do and when to do it. It starts with the organization’s mission, and is refined through a Value Proposition. Having a good understanding of what 2i2c’s North Star is will be key to ensuring that whatever we do is aligned with where we want the organization to be.

[Our Value Proposition is defined here](mission:value-proposition).

## Becoming more intentional

As 2i2c scales up to meet its strategic goals, the way we decide what to put our efforts into will have to shift from a partially reactive approach to product development to a more intentional, careful approach that will allow us to carve out the space for our team to research and deploy the right solutions for the most important problems our communities face.

This will necessarily affect the interaction between Partnerships, Product and Engineering, to ensure that our external conversations with communities, both current and prospective, are carefully considered against what would deliver the most value for the most communities, and be most closely aligned with our strategic objectives as an organization.

The product delivery flow outlined herein is meant to provide a framework whereby input from community stakeholders can be recorded, assessed, triaged and prioritized in alignment with what it is we want to achieve as an organization.

Here are some basic principles we need to keep in mind as we adopt a more intentional way of building product:

- Not all feature requests are equally important.
- Loud does not equate to urgent.
- It’s OK to say no. We will make no promises until we’re sure we can deliver.
- All non-critical feature requests will be triaged and prioritized according to the process.
- We will ensure our resources are not overtaxed, and create space for our work to be proactive, rather than reactive.
- We will limit the number of projects we run at any one time to ensure they can be adequately supported.
- We need to balance competing interests. What’s best for science? What’s best for this community? What’s best for 2i2c? What’s best for the upstream open source projects we contribute to?

By collectively signing up to these principles, we have given ourselves permission to say no to projects that are not aligned with our long term goals or those of the communities we serve, and preserve our ability to intentionally move towards those goals.
6 changes: 3 additions & 3 deletions product/prioritization.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Using ProductBoard for prioritization
# Using Productboard for prioritization

2i2c uses [ProductBoard](https://ProductBoard.com/) to manage product prioritization and collect insights relevant to our product improvement process.
2i2c uses [Productboard](https://productboard.com/) to manage product prioritization and collect insights relevant to our product improvement process.

For those unfamiliar with ProductBoard, [see this short primer on ProductBoard](https://docs.google.com/document/d/1UkFcv2klEBOEnZ4CoB7PnVYS6MNOn5fCfM7unbco2lI/edit?usp=sharing).
For those unfamiliar with Productboard, [see this short primer on Productboard](https://docs.google.com/document/d/1UkFcv2klEBOEnZ4CoB7PnVYS6MNOn5fCfM7unbco2lI/edit?usp=sharing).
This should help you navigate and contribute your input into the Product Delivery Flow.

0 comments on commit 85bf3e6

Please sign in to comment.