1/8/24: Project Start
Beginning the project
Identifying the problem:
fiberglass accessibility
alternatives to fiberglass insulation
Learning the technology
What can we do?
1/22/24 – 1/26/24: Strike! (kind of)
1/21/24: Meeting with Martin (do we have notes from this day)
1/23/24: First class presentation
1/23/24: ISECs brought to campus
Pete first brings the ISECs to campus and allows Nick Doing to start working on them.
2/1/24: First meeting with Andrew
Andrew has an affordable fiberglass supplier
Top frame: potentially experiment with? Nepal cookers use stainless steel
very impactful on our project because he told us our main problem didn't exist for him
Zoom meeting with Andrew (andrewmayanja@aseiug.org):
What do ISEC users want?
USB charging port for cell phones
Substitute wood frame to more durable and sustainable material
Regulated heat cooking
Night time cooking
Fiberglass insulation is not a priority; needed to switch gears
2/2/24: Meeting the ISEC for the first time
Team met the ISEC for the first time in the lab with Nick and Eli
2/7/24: Learning about Ownership and Failure
Who does the ISEC project belong to?
Long-distance development projects
2/21/24: Moving the ISEC to Bonderson
Team met to move our ISEC to Bonderson anticipating it to be ready for use, but it was not fixed to a usable state yet so we still couldn't use it
2/22/24: Second class Presentation
3/2/24: Second meeting with Andrew
started from square 1: how can we help with our limited knowledge about ISEC?
Andrew's supplier doesn't export: we can't really address this yet, without building the ISEC "market"
ISECs have a short lifespan: related to heat regulation?
plan of action: marketing
refined user manual
adding ISEC images/videos to website
3/6/24: Nick D. and Eli finish fixing the ISECs
Team moves our ISEC to Molly's architecture studio
3/4/24 – 3/11/24: Molly and Nick travelling for school
3/19/24: Nick experiments with the ISEC
3/21/24: Final presentation and potluck!
Finding our place in the ISEC project was a challenge. With just ten weeks to learn about the technology, find the problem, propose a solution, and act, there was little room for anything but progress.
Some problems we ran into:
Communication
e-mailing was not sufficient to grasp the ISEC situation, and conflicting schedules only allowed for occasional Zoom meetings
Miscommunication led to mismatch between the goals of the group and the needs of project leaders (Andrew)
Limited Expertise
None of us were technically qualified to suggest improvements to the ISEC that had not already been thought of
We were given a list of areas of improvement, but most of them were not realistically achievable for our team in the time span and resources given
Limited Resources
Our team was only able to physically interact with an ISEC after over a month into the project
We never actually got to experience the ISEC model in Uganda
However, we also learned a lot of valuable information from this process and personally benefitted from this experience. We learned firsthand how complicated development is, especially in undeveloped countries halfway across the world. We learned to be patient, understand that we probably won't have a big impact, and that failures are imminent but should be perceived as opportunities for progress rather than reasons to quit. It was a true embodiment of Cal Poly's Learn by Doing teaching philosophy, and the opportunity to work with real life people with real life problems was valuable compared to other projects when we would have just learned about them. We learned how to communicate professionally and mitigate the different needs and wants of all the different stakeholders in this project. I think most of all we learned about our place as students – that what we learn should be applied to make the world a better place.