Empowering warehouses with their carbon emissions data
Empowering warehouses with their carbon emissions data
Empowering warehouses with their carbon emissions data
I led & designed a lean solution that helps warehouses track their carbon emissions by automatically pulling their consumption data and calculating their carbon footprint. We focused on quick prototyping and meeting client needs with efficiency.
I led & designed a lean solution that helps warehouses track their carbon emissions by automatically pulling their consumption data and calculating their carbon footprint. We focused on quick prototyping and meeting client needs with efficiency.
I led & designed a lean solution that helps warehouses track their carbon emissions by automatically pulling their consumption data and calculating their carbon footprint. We focused on quick prototyping and meeting client needs with efficiency.
Skills
Skills
Skills
Product Strategy, Product Design, Rapid Prototyping
Product Strategy, Product Design, Rapid Prototyping
Product Strategy, Product Design, Rapid Prototyping
My Role
My Role
My Role
Product Designer & Manager
Product Designer & Manager
Product Designer & Manager
Timeline
Timeline
Timeline
2 weeks
2 weeks
2 weeks
Team
Team
Team
Designer, Developer and Carbon Accounting Expert
Designer, Developer and Carbon Accounting Expert
Designer, Developer and Carbon Accounting Expert
Project Goals
Warehouses were a significant but unmeasured part of our client's carbon footprint, and they lacked any system to track or manage these emissions. It was a product opportunity to design a carbon accounting tool to enable them to achieve the following:
Project Goals
Warehouses were a significant but unmeasured part of our client's carbon footprint, and they lacked any system to track or manage these emissions. It was a product opportunity to design a carbon accounting tool to enable them to achieve the following:
Project Goals
Warehouses were a significant but unmeasured part of our client's carbon footprint, and they lacked any system to track or manage these emissions. It was a product opportunity to design a carbon accounting tool to enable them to achieve the following:
Project Goals
Warehouses were a significant but unmeasured part of our client's carbon footprint, and they lacked any system to track or manage these emissions. It was a product opportunity to design a carbon accounting tool to enable them to achieve the following:
01
Gain knowledge of cost reduction from avoided emissions
01
Gain knowledge of cost reduction from avoided emissions
01
Gain knowledge of cost reduction from avoided emissions
01
Gain knowledge of cost reduction from avoided emissions
02
Prepare for regulatory compliance
02
Prepare for regulatory compliance
02
Prepare for regulatory compliance
02
Prepare for regulatory compliance
03
Understand emissions for client sustainability storytelling
03
Understand emissions for client sustainability storytelling
03
Understand emissions for client sustainability storytelling
03
Understand emissions for client sustainability storytelling
How We Identified the Problem
I facilitated a discovery workshop with key client stakeholders including the National Head of Logistics. I led the session with a structured call agenda to ensure we uncovered business, operational, and compliance needs.
How We Identified the Problem
I facilitated a discovery workshop with key client stakeholders including the National Head of Logistics. I led the session with a structured call agenda to ensure we uncovered business, operational, and compliance needs.
How We Identified the Problem
I facilitated a discovery workshop with key client stakeholders including the National Head of Logistics. I led the session with a structured call agenda to ensure we uncovered business, operational, and compliance needs.
How We Identified the Problem
I facilitated a discovery workshop with key client stakeholders including the National Head of Logistics. I led the session with a structured call agenda to ensure we uncovered business, operational, and compliance needs.
Insights from Discovery Call
• Sustainable practices are used as a cost-cutting strategy because generating carbon emissions can also mean losing money. Hence, the emissions saved need to be tracked. • There was no existing digital tool to track consumption but they had an ERP to track their financials and expenses. • Gathering solar electricity consumption data is unstructured & varies depending on weather and amount sold back to the grid.
Insights from Discovery Call
• Sustainable practices are used as a cost-cutting strategy because generating carbon emissions can also mean losing money. Hence, the emissions saved need to be tracked. • There was no existing digital tool to track consumption but they had an ERP to track their financials and expenses. • Gathering solar electricity consumption data is unstructured & varies depending on weather and amount sold back to the grid.
Insights from Discovery Call
• Sustainable practices are used as a cost-cutting strategy because generating carbon emissions can also mean losing money. Hence, the emissions saved need to be tracked. • There was no existing digital tool to track consumption but they had an ERP to track their financials and expenses. • Gathering solar electricity consumption data is unstructured & varies depending on weather and amount sold back to the grid.
Insights from Discovery Call
• Sustainable practices are used as a cost-cutting strategy because generating carbon emissions can also mean losing money. Hence, the emissions saved need to be tracked. • There was no existing digital tool to track consumption but they had an ERP to track their financials and expenses. • Gathering solar electricity consumption data is unstructured & varies depending on weather and amount sold back to the grid.
Analysing & organising information
I collaborated with the carbon accounting team & I immersed myself into understanding the emissions methodology, using the global standard – GHG Protocol.
Analysing & organising information
I collaborated with the carbon accounting team & I immersed myself into understanding the emissions methodology, using the global standard – GHG Protocol.
Analysing & organising information
I collaborated with the carbon accounting team & I immersed myself into understanding the emissions methodology, using the global standard – GHG Protocol.
Analysing & organising information
I collaborated with the carbon accounting team & I immersed myself into understanding the emissions methodology, using the global standard – GHG Protocol.
• Shared a template with the client to collect data on their emission sources & assessed if there are any data gaps. • Mapped the data received to whether it is mandatory or not for calculation, whether it is going to be dynamic or not.
• Shared a template with the client to collect data on their emission sources & assessed if there are any data gaps. • Mapped the data received to whether it is mandatory or not for calculation, whether it is going to be dynamic or not.
• Shared a template with the client to collect data on their emission sources & assessed if there are any data gaps. • Mapped the data received to whether it is mandatory or not for calculation, whether it is going to be dynamic or not.
• Shared a template with the client to collect data on their emission sources & assessed if there are any data gaps. • Mapped the data received to whether it is mandatory or not for calculation, whether it is going to be dynamic or not.
Product Scoping & Designing with Constraints
We had a constraint of 2 weeks & limited resources to build the MVP. I ran a MoSCoW prioritisation to scope what we could deliver without sacrificing integrity. This strategic scoping kept us focused, aligned cross-functionally, and let us deliver a lean but impactful MVP.
Product Scoping & Designing with Constraints
We had a constraint of 2 weeks & limited resources to build the MVP. I ran a MoSCoW prioritisation to scope what we could deliver without sacrificing integrity. This strategic scoping kept us focused, aligned cross-functionally, and let us deliver a lean but impactful MVP.
Product Scoping & Designing with Constraints
We had a constraint of 2 weeks & limited resources to build the MVP. I ran a MoSCoW prioritisation to scope what we could deliver without sacrificing integrity. This strategic scoping kept us focused, aligned cross-functionally, and let us deliver a lean but impactful MVP.
Product Scoping & Designing with Constraints
We had a constraint of 2 weeks & limited resources to build the MVP. I ran a MoSCoW prioritisation to scope what we could deliver without sacrificing integrity. This strategic scoping kept us focused, aligned cross-functionally, and let us deliver a lean but impactful MVP.
For Phase 1 scope, I decided to built a partially automated internal tool that also give us flexibility to manually input data depending on fetching feasibility from the ERP. • Create a structured form to capture warehouse consumption details. • Data gets autofilled in the the form if API is able to fetch data. • User will manually input data that is not filled via the API. • Only show emission factors that are applicable to the pilot warehouse. • The tool processes data and provides emissions calculations
For Phase 1 scope, I decided to built a partially automated internal tool that also give us flexibility to manually input data depending on fetching feasibility from the ERP. • Create a structured form to capture warehouse consumption details. • Data gets autofilled in the the form if API is able to fetch data. • User will manually input data that is not filled via the API. • Only show emission factors that are applicable to the pilot warehouse. • The tool processes data and provides emissions calculations
For Phase 1 scope, I decided to built a partially automated internal tool that also give us flexibility to manually input data depending on fetching feasibility from the ERP. • Create a structured form to capture warehouse consumption details. • Data gets autofilled in the the form if API is able to fetch data. • User will manually input data that is not filled via the API. • Only show emission factors that are applicable to the pilot warehouse. • The tool processes data and provides emissions calculations
For Phase 1 scope, I decided to built a partially automated internal tool that also give us flexibility to manually input data depending on fetching feasibility from the ERP. • Create a structured form to capture warehouse consumption details. • Data gets autofilled in the the form if API is able to fetch data. • User will manually input data that is not filled via the API. • Only show emission factors that are applicable to the pilot warehouse. • The tool processes data and provides emissions calculations
For Phase 2, the plan is to scale it into a fully-automated customer facing dashboard and include advanced data analytics like hotspots identification, multiple warehouse tracking and reduction insights.
Structuring the User Interface
I created an information architecture for structuring the data input form. Also defined all form components, validation checks, mandatory fields, error handling for the form
Structuring the User Interface
I created an information architecture for structuring the data input form. Also defined all form components, validation checks, mandatory fields, error handling for the form
Structuring the User Interface
I created an information architecture for structuring the data input form. Also defined all form components, validation checks, mandatory fields, error handling for the form
Structuring the User Interface
I created an information architecture for structuring the data input form. Also defined all form components, validation checks, mandatory fields, error handling for the form
Quick Prototyping & Iteration
Quick Prototyping & Iteration
Quick Prototyping & Iteration
Quick Prototyping & Iteration
Saved time on building UI with Retool
Eliminated wireframing on Figma and directly created UI on Retool, a developer tool for building apps, fast-tracking development effort for frontend. Below shows how a new warehouse is added to the tool for emissions calculation.
Progressive & Conditional Form
Created conditional logics for input options ensuring user sees only what is necessary.
Affordance for future use cases
Gave affordance for future scalability by displaying all options, but keeping them disabled until we add its emission factors in the backend. For the MVP, we focused only on building for use case that was applicable to our client.
Emissions Breakdown by Consumption
For the MVP, gave functionality to view previously calculated emissions for a particular warehouse so that user can view the breakdown between all consumption categories.
Turning Point & New Way Forward
Post-MVP, we were introduced to the client's IT team for data integration. There was a critical blocker – their ERP only stored financial data, not consumption data. This was a disconnect from earlier stakeholder conversations and shifted the path forward as the tool can not be automated currently. The problem needed a systems level change. To move forward, I proposed two paths:
Turning Point & New Way Forward
Post-MVP, we were introduced to the client's IT team for data integration. There was a critical blocker – their ERP only stored financial data, not consumption data. This was a disconnect from earlier stakeholder conversations and shifted the path forward as the tool can not be automated currently. The problem needed a systems level change. To move forward, I proposed two paths:
Turning Point & New Way Forward
Post-MVP, we were introduced to the client's IT team for data integration. There was a critical blocker – their ERP only stored financial data, not consumption data. This was a disconnect from earlier stakeholder conversations and shifted the path forward as the tool can not be automated currently. The problem needed a systems level change. To move forward, I proposed two paths:
Turning Point & New Way Forward
Post-MVP, we were introduced to the client's IT team for data integration. There was a critical blocker – their ERP only stored financial data, not consumption data. This was a disconnect from earlier stakeholder conversations and shifted the path forward as the tool can not be automated currently. The problem needed a systems level change. To move forward, I proposed two paths:
01
Share manual entry via Excel monthly and we will integrate it via API
01
Share manual entry via Excel monthly and we will integrate it via API
01
Share manual entry via Excel monthly and we will integrate it via API
01
Share manual entry via Excel monthly and we will integrate it via API
02
Direct manual data entry into our centralised tool (Recommended)
02
Direct manual data entry into our centralised tool (Recommended)
02
Direct manual data entry into our centralised tool (Recommended)
02
Direct manual data entry into our centralised tool (Recommended)
03
Understand emissions for client sustainability storytelling
03
Understand emissions for client sustainability storytelling
But the client revealed this would require behavioural shifts across all warehouses as the current process is manual logging in data in registers at each location. It will expand the scope as it will require us to solve problems at a deeper level such as – low tech literacy, resistance to change, absence of a digital device at the location and so on.
But the client revealed this would require behavioural shifts across all warehouses as the current process is manual logging in data in registers at each location. It will expand the scope as it will require us to solve problems at a deeper level such as – low tech literacy, resistance to change, absence of a digital device at the location and so on.
But the client revealed this would require behavioural shifts across all warehouses as the current process is manual logging in data in registers at each location. It will expand the scope as it will require us to solve problems at a deeper level such as – low tech literacy, resistance to change, absence of a digital device at the location and so on.
But the client revealed this would require behavioural shifts across all warehouses as the current process is manual logging in data in registers at each location. It will expand the scope as it will require us to solve problems at a deeper level such as – low tech literacy, resistance to change, absence of a digital device at the location and so on.
Reflection
What worked • Learning how to build fast with rapid MVP scoping + build and strong cross-functional collaboration • Validating ideas with low stakes rather than going after a perfect sophisticated product.
Reflection
What worked • Learning how to build fast with rapid MVP scoping + build and strong cross-functional collaboration • Validating ideas with low stakes rather than going after a perfect sophisticated product.
Reflection
What worked • Learning how to build fast with rapid MVP scoping + build and strong cross-functional collaboration • Validating ideas with low stakes rather than going after a perfect sophisticated product.
Reflection
What worked • Learning how to build fast with rapid MVP scoping + build and strong cross-functional collaboration • Validating ideas with low stakes rather than going after a perfect sophisticated product.
What could be better • Pushing for earlier involvement from technical stakeholders could have helped us plan better • Involve end-users in co-creation to assess digital readiness
What could be better • Pushing for earlier involvement from technical stakeholders could have helped us plan better • Involve end-users in co-creation to assess digital readiness
What could be better • Pushing for earlier involvement from technical stakeholders could have helped us plan better • Involve end-users in co-creation to assess digital readiness
What could be better • Pushing for earlier involvement from technical stakeholders could have helped us plan better • Involve end-users in co-creation to assess digital readiness
"Designing a product is not the same as designing a solution. Systems matter. Habits matter. The people using it must be just as ready as the product itself."
"Designing a product is not the same as designing a solution. Systems matter. Habits matter. The people using it must be just as ready as the product itself."
"Designing a product is not the same as designing a solution. Systems matter. Habits matter. The people using it must be just as ready as the product itself."
"Designing a product is not the same as designing a solution. Systems matter. Habits matter. The people using it must be just as ready as the product itself."
