Facilitating the right balance
In order to complete the daily process of stewarding mass balance for a production facility, enormous amounts of data need to be consumed and updated in order to reach targets or make corrections. The problem? The data in its current format is cumbersome to consume, leading to daily issues for stewardship and monthly issues for reporting. The workshop for this project was meant to help document processes for all parties involved, and prioritize pain points in order to prioritize features for a solution MVP.
Presentation documents are available upon request.
Role: Project Lead, Co-Design Facilitator
Designing the workshop
There had been some pre-work done for the workshop at an earlier session, so we had to make sure our activities weren’t repetitive to the participants. When we met with the project team we aligned on the scope and objectives of this workshop. My favorite question to ask is “When this workshop is over, what do you want to walk away with?”. This helps me design activities and tools to use during the workshop to get us there. Based on their response, I crafted different activities and templates to help capture processes, define personas, prioritize MVP features, and plan a Roadmap to move forward with.
Prioritizing needs and features
The first step during the workshop was mapping the end to end processes and identifying the roles involved in those processes. The participants collaborated through these activities and gave us the material to work through the rest of the workshop. We identified a lot more personas involved in the process than originally discovered through interviews and research. We then prioritized the Personas so that the MVP addressed the most vital roles in the process first, later expanding to meet the needs of the different roles involved.
Once this was completed, ideation around features was next on the agenda.
Gaining MVP consensus
After 2 days of diligently mapping out processes, prioritizing personas, and thinking of features that could address the pain points surfaced, we got the workshop participants to vote and prioritize the main features to be included in the first MVP.
We had participation from technical architecture teams in addition to those involved in the day to day process. This helped clarify some questions around some of the feature ideas and manage expectations in terms of the feasibility to help narrow what was viable for the 1st MVP.
