After you’ve accepted your offer, we’ll handle team formation for you by assigning you to teams based on various criteria such as timezones and skills. After, we'll bring you into the Propel community! Take this opportunity to network with the rest of your cohort and team.
Get to know your team and project. Work with your product manager to plan and run discovery research with users based on the project's scope. This is where you can think of your user journey and problem space.
Communicate your findings from discovery research to your team and finalize your approach for the next few weeks. Collaborate with them to determine feasibility of your designs and ideas.
Turn your ideas into reality! Create, iterate, and handoff your designs to the frontend developer while keeping within project constraints. Work with your developers to implement your designs. Plan your usability tests for when the product is deployed and ready to be tested. Communicate any final changes with your developers.
Pitch and demo the MVP your team has developed, deployed, and validated with real users!
You’re finally done! Pop some champangne and celebrate your hard work.
Establish who your users are and understand their problems through discovery and iterative research.
Create and communicate your fresh ideas and designs based on user insights and business needs.
Collaborate with developers to identify the feasibility of your designs to bring them to life.
Before Propel I had never worked with developers, and I was initially worried that my inexperience would somehow bring the team down. But I learned that despite the differences in our roles, we were all after the same goal of building a great product. I worked with amazing people who were passionate about the project, happy to answer questions about the technical aspects, and who had many great ideas that contributed to my growth as a designer.
Propel gave me a great opportunity to learn and practice doing user research. It was a pleasure working with two other team members that is experienced with front-end and back-end development in a smaller team. This gave me a new perspective to understand the different constraints we had to work with within building a MVP in 10 weeks.
I really enjoyed my time getting to know everyone. I think this was a great program to be apart of because it challenges you to figure out what you know and what you want to build on.
I had a technical interview and showcased Ciku. They were really impressed with the project. Specifically they were interested in the fact that it was a team project with other roles, and that it was about solving a problem we cared about rather than a tutorial project.
Before Propel I had never coded with anyone else, and especially never even committed to a shared repo (or set one up for that matter). To put into words what I have gained is tricky because I gained so much, although I think it was mostly confidence and the skills of working in a team that will see me through my following journeys. I highly recommend Propel to anyone that might be considering giving it a go.
I really enjoyed working on a project outside that allowed me to explore different types of technology. My team was great and I loved the mentorship provided by Propel.
It was an immensely positive experience, offering an opportunity to create something useful in a collaborative environment where people are keen to share their knowledge and experience.
Working on the EyeCommander project was definitely a milestone for me in my career development. The difference between projects with toy datasets and projects with real data is considerable and having a mentor along the way was invaluable. It was a unique experience to be able to contribute to a project as impactful as the EyeCommander and I'm thrilled with what my team was able to achieve in such a short time frame!