When the Edison Co. team began the project, they had little to no experience with many of the problems that they would end up working on. While process was of course a large part of the problem-solving process, there were also many physical challenges that were specific to Edison Co's problem. As such, the team compiled some recommendations for any other team attempting the same problem.

If anyone else were to attempt to solve the problem of sleep inertia, Edison Co. had a few ideas about things that could be improved. Firstly, the team would recommend exploring different options for a control board before committing to something. Specifically, exploring the possibilities of an Arduino board as opposed to a Raspberry Pi. By the time the team thought of using an Arduino, they were too invested in the Pi and would've had to rebuild their entire system from the ground up a mere few weeks before the showcase. While they considered the idea, it was eventually decided that it would be too much work in too little time, as one of the team members would have to learn how to code in a new language, and then rewrite Parker's program using different tools in a different environment. As such, Edison Co. never got a chance to explore the prototyping possibilities of an Arduino board. Next, Edison Co. would tell another team to keep in mind time restrictions. While the team was able to keep up to date with prototypes, there were certainly a few late nights spent troubleshooting, building, and testing to meet some deadlines. The largest recommendation that Edison Co. would make, however, has to do with documentation. The nature of their prototype was very much a combination of software and hardware. Upon finishing a prototype, they would realize that they had not taken enough photos of the process, and would have to make do with only a couple of photos when they could've used a multitude. Taking many photos, however, was not the only part of that. Edison Co. would also recommend that a team include explanations of how both the physical and software processes work. Flowcharts, paragraphs, and diagrams are all very helpful for this, and the team wishes they would've made more use of them. Last but not least, Edison Co. would reinforce the importance of communication. For this problem especially, there are many pieces all being worked on at once. From the physical prototype, to the code, to the housing, to parts being ordered, many things are happening in tandem. Without coordinating between them, a group would end up with mismatched parts and a sub-par prototype. As such, the team would tell another group to make use of a service like Discord. Making a server, and then making different channels dedicated to different parts of the project allows any team to remain organized and stay in communication about the things they must talk about. The Discord server was an extremely valuable part of Edison Co.'s process, and they would highly recommend it to any team attempting their problem.

When solving any problem, any solution will almost always have some kinks which need to be worked out. This was, of course, also the case with Edison Co.'s design. While overall the design was sufficient, the team still had some improvements that stood out. As for materials, Edison Co. felt that many of their materials, while acceptable for a prototype, would benefit from being improved upon if they were to release the product to a commercial market. As for the brains of the operation, a custom printed board would be ideal. This would allow the team to have only the functionality needed without having to pay for the added features that they wouldn't need like those present in a Raspberry Pi. Branching out from there, building the dimming features directly into the board would provide less room for failure, as there would be less risk of wires coming loose or dislodging. The team would also like to find a way to do analog dimming instead of PWM, as PWM can cause flickering in the bulb when dimming. For the speaker, having an analog speaker which could be controlled directly by the board instead of having to control a separate, battery-powered unit would help ensure that there were no connection issues or failures when operating the product. Also, having a smaller and more elegant housing for the electronics, likely one made from wood or perhaps built directly into the paper lamp itself, would be great. Lastly, for materials, the team would like to maybe have a built-in light so they could ensure no flickering during dimming, as different types of bulbs can cause more extreme flickering.

As for designs, Edison Co. felt that their overall design was relatively spot on. However, there are a couple of spots that the team agrees the design could be improved on. For example, Parker has expressed the desire to make the program used to control the project a bit more functional and user-friendly. This would entail a menu, the ability to add custom sounds, and an easier way to set new alarms. Also, the team wanted to add a snooze button option for the prototype. While their product was supposed to make waking up a better experience, there are still days when one wants those extra 5 minutes.

Lastly, for testing, Edison Co. would've liked to do some more long-term testing of their product beyond the basic functionality tests. For example, tracking someone's sleep for about a month to get a control group, and then testing if the alarm actually helped people wake up feeling more refreshed. Doing so would allow Edison Co. to ensure that they had a truly viable product before going to manufacturing, if they were going to actually make the product into a purchasable item.