Client

For the majority of students, the classroom is one of those areas that has been slow to adopt tech innovation. Linteract aims to change that. By empowering teachers and students with the benefits of technology, Linteract makes learning easier, faster and most importantly more fun.

Role

Industry

Linteract

The edtech platform provides a myriad of features for parents, teachers and children/students alike, which include assessment,
reporting, in-app communication, live lessons and many more.

Results and outcomes

• 78% of Increase in the conversion rate. Thanks to better usability, the schools are a lot more likely to upgrade their trial accounts and become paying customers.

• 4x Increase in Perceived Value. Good-looking apps look more trustworthy and valuable, which is why we’ve invested our time in creating a modern and sleek interface.

• Acquisition of new clients. Based on new tailored features and interactive prototypes we helped acquire big Governmental and Corporate clients.

• Reduced costs by 3x: Increased developers’ efficiency and reduced costs by having a user-centered design approach.

• New features for the web version and mobile app from scratch.

• Revamping the existing app.

• Improving the conception ➝ design ➝ validation ➝ dev workflow

1 year 7 months

Boy was this project a journey. We went from an early childish-looking platform to a mature validated edtech product with a sleek modern design
and a number of new features. Not to mention a number of new business opportunities for our client.

This epic design saga took 1 year and 7 months. To help you digest this adventure and not get lost midway, we’ve split this case study into two sections: the design process and the features we designed.

The design process section is the set of activities that constitute a single iteration or sprint. Since this process is relatively consistent for each group of
features, we’ll go over it just once. The features we designed section covers the most important features we designed (duh) by following the process outlined in the design process section.

With that out of the way, let’s get into the case study.

The initial stage of our engagement with the product team naturally involved getting a deep understanding of why they needed our help. It’s exceptionally
important to help clients articulate their needs and understand the basis behind them. A good analogy here is that to shortlist a list of potential diagnoses we’re looking to define the symptoms well.

At this stage, we’ve learned more about the current product version, branding, users, and their workflows. The Linteract team wanted to change the technology of their front-end, and move away from the K-12 look-and-feel, so the product identity is less childish.

Armed with the ideas of product improvement, we proceeded with conducting an audit of the existing designs. The issues we identified were then prioritized and scheduled to be worked on.

One of the major issues was that the LMS mobile app wasn’t consistent with the web one. Additionally, it hadn’t been really intuitive, which was a suspicion of ours that was then further proved by the usage data.

The rest of the improvement areas included working on the existing design components and visual design, reducing cognitive load, better usability.

Now that we had a list of issues to tackle, it’s time to focus on how we could do it. The solutions would first take the form of rough concepts. The more the
better. This stage is all about quantity. The best concepts would be potentially merged and make it into the optimal version.

Having prepared a wide range of potential concepts for the features, we’ve fleshed out the best ones.

Separating the wheat from the chaff in terms of design looks something as follows: