Here's what we're thinking about building next. Help by upvoting your favorites or requesting features on our <a target="" rel="noopener noreferrer nofollow" class="link" href="https://product.koi.eco">Feedback page</a>. See <a target="" rel="noopener noreferrer nofollow" class="link" href="https://product.koi.eco/changelog">our Changelog</a> for recent updates.

Under Consideration

Works in Progress

Public Roadmap

We need a better way to organize collections. After adding many collections it becomes difficult to find what you’re looking for from the main collections page.

In Review

Ability to add labels (or tags) to forecasts and collections

Gilman Callsen

When possible, if the baseline and solution GHG intensity attached to a technology cluster are functionally equivalent but not literally equivalent (e.g., Mt CO2e/Mt product for the soln and kg CO2e/kg product for the baseline), the backend performs an automatic conversion to present the dataset within the model in a way that aligns the solution GHG intensity to the baseline. If we are matching to the baseline then the market size should, in theory, not require conversions right now. To be robust for future use cases though, the market size should also be checked for equivalency with baseline GHG units. This will help enable better cross-talk of data sets between models and compatible use of individual datasets within custom modeling.

Automated alignment of units within a technology cluster

science

A step-by-step tutorial showing the in-app process and scientific logic for creating and interpreting an entirely custom model.

Planned

Tutorials for custom modeling

aurora.ginzburg

Expose the lifecycle subphase data through the UI for end users.

Science

Engineering

Product

Add Lifecycle Sub-phases

AmberGold

Include a page with solution details that outlines other impacts of the solution (e.g. waste, water, plastic) and potential risks (e.g. impact to workforce)

Show additional impact and risk factors

Cassie Borish

Have a Koi docs page dedicated to summarizing what we have deep experience modeling and has complete highly QAed models in Koi.Start with a static docs page that includes a table of sectors/categories and a sampling of technologies within each sector (can pull from HMC work). Eventually may want to create our own chatbot so users can type custom requests and it returns results similar to the search engine but in chat format.

Categories and Technologies Covered

It would be awesome to be able to share v0 models that aren’t yet publicly available directly to individuals so we can better showcase Koi’s breadthy (w/o giving access to all v0 models). Basically I’m requesting a manual override/sharing of individual models.

Direct sharing of individual v0 models

seth.sheldon

It would be great to be able to search for and add a forecast directly from the collection management page.<img src="https://fb-usercontent.fra1.cdn.digitaloceanspaces.com/019542db-2d36-7418-9c74-b9ec98982709.png" data-width="100%" data-align="left">

Add forecast directly to collection in collections managment

Currently, the UI doesn’t look good if only a single phase is entered for a lifecycle GHG intensity. However, many reports state the intensity boundaries but do not further segment the lifecycle GHG intensity into phases. It would be beneficial if there is an input option during ingestion, similar to the “excluded” phase option currently available, whereby phases included within the boundaries could be shown visually but not assigned numeric values. Instead, only the total GHG intensity is presented to be consistent with the original data source. Ideally, the phases could say “included” and only the total intensity is reported at the top.

Flexible value chain UI for aggregated phase quantification

Develop onboarding questionnaire that takes ~5 mins to complete and results in a sample of an on-demand model for further refinement.

Onboarding questionnaire

We need to find ways to onboard faster so people can experience the magic first hand. This is confusing work anyway and this is a radically new (better) way to do this, so there is clear apprehension for folks to start without handholding.What would be helpful to you? Please put in the comments or email us at <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="mailto:support@koi.eco">support@koi.eco</a>

In Progress

Docs

Improved Onboarding

Need new documentation that quickly communicates one of the innovations with the Koi approach: rapidly scaffold, then refine as appropriate.This is highly distinct from status quo, which is a series of internal spreadsheets tracking good data sources, baselines, solutions, etc. that are put together ad hoc for new analyses. This legacy approach is time and cost intensive while simultaneously being prone to errors, difficult to maintain, and cumbersome to share/collaborate.Ideally this documentation includes a simple diagram that shows the key steps in the process at a high level.

Describe the Koi Process

Expose Koi Data Lake over public API. Get in touch if you’d like to be a beta tester, <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="mailto:support@koi.eco">support@koi.eco</a>

Public API to Koi Data Lake

Koi will send an email invitation automatically, instructing the invited user how to register for a Koi account.

Email Invite

Limitation addressed: It is unclear to Koi users what data are verified in a model and what data are autogenerated. If they modify data it is up to them to remember what they changed and communicate it. If they are more comfortable working in a spreadsheet, they have no way of doing so.Develop tooling for Koi studio users to understand and manage the QA status of their model. Data should be appropriately tagged at the parameter level for communications of model quality and verified/unverified information.QA tooling to include streamlined “high-level” model refinement options as well as deep refinement using an exported Review.xlsx file that can then be reingested from an updated Google Sheet.

In-app QA process

Help Center

Improved

Fixed

Feature

Completed

Rejected

Needs Discussion

High Priority

Low Priority

Recently completed

If you are reporting a bug, please include as much detail as possible, including any steps you took prior to finding the issue.