Well, challenges are inevitable. At anytime, you could run into a challenge, such as not being able to agree on something, or simply not knowing what to do next. Building an FRC robot and running an FRC team have many challenges and problems. They always will have challenges and problems mostly because not everyone is the same exact person. Everyone has different views on what should be done and they all solve it in different ways, whether it be efficient or atheistic. Both areas have their own challenges like Eric Ries identified. No one can agree. Plain and simple not everyone can agree and people also need to be more open minded to take in ideas and then become able to mesh ideas and work finally starts getting done.
Our FRC team is a group of entrepreneurs due to how we have to become seen by the public eye and make our own ideas that will be able to be agreed on to make something. We are our own business. We made our team which requires money and resources just like a business.
Productivity is something our team doesn't know much about. Well that is true to an extent, we know when to buckle down and get to work, but we don't always do it well. Productivity is basically how productive you/your team can be. When building an FRC robot, productivity is how well the team is working together to be able to build the robot and how well they communicate. And no. Our team was not productive for the most part.
They thought that the people that used their product wanted to use instant messaging systems that weren't made by IMVU. Customers wanted an IM system that was in the specific game so that when people got onto that game, they could have new, different, online friends instead of the school and work friends. A faster, more efficient and cheaper way for them to find out these stats would be to test it with only a small amount of people and then if they didn't like it then they could've changed it.
We experimented with the ramp to figure out how we could've gotten it to work or if it would've worked at all. We could've had different groups try different things instead of one group doing one thing at a time. Also, we should've worked on better prototypes.
Well Zappos was wise and saw and asked if there was a problem first instead of making a solution for a problem that didn't exist. The Zappos founders were wiser than the IMVU team because of their decision to figure out the problem and then fix it. Also, it was with a small amount of people that they figured out the problem rather than just a whole bunch of consumers.
Overall, I learned that not only I, but the team should figure out the problem before making a solution. Also, we need to work together and not always make a large scale thing right away. We need to start small rather than charging right into the final thing.