Implementation Pt. 2
At the conclusion of last week we felt like we had discussed most of our features and the logistics that surround them in enough detail that we were ready to move forward in creating a detailed user flow document to include in our final presentation. Our focus shifted towards elevating our idea into business. An important component of this is branding and the company name. This was one of the more challenging parts in our solution. We tossed around some fun ideas, like Schooral (school + rural), but ended up feeling like having a more straightforward name would best maintain a professional vibe for the site. Eventually we landed on RuralTeach because the name clearly communicates who our target audience is for use of the website itself. As a group, we came to the conclusion that our selling audience would be district and school administrators.
We also spent time creating a color palette to use for our site by independently pinning different images and pictures to a shared Pinterest dashboard. Following the lead of the designers in our group, we sorted through the colors we felt would complement each other best and be attractive to the user experience on the site. While working on the specifics of the features, the team came together to share feedback on our initial impressions on the dashboard/home page’s 1st iteration. Some of the feedback shared was that a user may feel somewhat overwhelmed with the number of features that are presented. The designers in our group went back to the drawing board and spent time iterating on the product more, which resulted in removing some features altogether based on what would be our product’s primary goals.
Before departing to do more individual work, we resurfaced our conversation from prior weeks on how to be more productive as a unit. Understanding that we had those in our group who had experience in design and others who were more business oriented, we reviewed the major points that needed to be hit during the presentation of our final product and will work in sub groups for efficiency’s sake. The designers plan to focus on the actual solution to our problem statement, and the business minded teammates will spend time thinking through our team’s problem solving process and telling the story on how we arrived at our solution, as well as how it can be implemented.