Research-led redesign case study
Deliverable: A redesign of an existing Indian app or website, evidenced by user research, with a written case study showing the problem found, the decision taken and the reason for it.
Course
Design taught as decision-making you can justify, not decoration — ending with three case studies that show your reasoning, which is what design hiring actually assesses.
9 modules · 4 months
Deliverable: A redesign of an existing Indian app or website, evidenced by user research, with a written case study showing the problem found, the decision taken and the reason for it.
Deliverable: A complete mobile app design with information architecture, user flows, high-fidelity screens and an interactive prototype, meeting WCAG AA contrast throughout.
Deliverable: A component library built with auto layout, variants and documented usage rules, applied consistently across at least fifteen screens.
Deliverable: A usability test run with five participants on your own prototype, with findings, a prioritised list of changes and a second version demonstrating what changed and why.
Every student gets placement assistance — that is what 100% placement assistance means. It is support for all, not a job for all. We do not promise a specific salary, a specific number of interviews, or placement at any named company, and you should be wary of anyone who does.
The most common way a design portfolio fails is not that the work looks bad. It is that it shows only outcomes.
Twenty beautiful screens with no explanation tell a hiring manager that you can operate Figma. They do not answer the question that actually decides the hire: can this person be given an ambiguous problem and produce a defensible solution?
So every project here produces a case study with the same spine — what the problem was, what you found out, what alternatives you considered, what you chose and why, and what testing showed. That structure is what design interviews probe, and it is the reason three deep projects beat a large gallery.
Research modules in design courses often produce personas that decorate a presentation and influence nothing.
The test we apply is simple and uncomfortable: name the design decision this finding changed. If a piece of research did not change anything, either it was the wrong question or you were not listening to the answer.
That discipline is also what separates a designer from a decorator in a real team, where research time has to be justified against a deadline.
Contrast ratios, touch targets, focus order and keyboard operation are taught as constraints you design within, in the same way you design within a screen size.
Retrofitting accessibility is expensive and usually done badly. Designing within the constraint costs almost nothing and produces better interfaces for everyone — larger targets and clearer contrast help users on a bright street in Delhi as much as they help anyone else.
Generating plausible screens is now fast and getting faster. That has genuinely reduced the value of production speed as a differentiator.
What it has not touched is problem framing, deciding what not to build, negotiating between what users need and what the business wants, and defending a decision when a stakeholder disagrees. Those are the parts this course spends most of its time on, because they are what will still be scarce.
Questions
No. Interface design is layout, hierarchy, typography and judgement about what to remove, none of which requires drawing ability. Sketching in this course means boxes and arrows to explore a flow quickly. Illustration is a separate discipline that some designers add later by choice.
The case study, more than the screens. Anyone can produce attractive mockups, particularly now. What is scarce is a designer who can explain the problem, the alternatives considered, why one was chosen and what testing showed. Three deep case studies beat twenty polished screens, and this course is structured accordingly.
The screen-production part has become faster and cheaper, and that will continue. The parts that have not changed are deciding what to build, framing the problem, and defending a decision to stakeholders with competing priorities. The course weights those deliberately, because that is where the durable value is.
Not to build, but enough to understand constraints. Knowing roughly what is cheap and expensive to implement makes you far easier to work with, and it stops you designing something that cannot be built in the time available. We cover handoff and constraints rather than teaching development.
No. Figma's free tier covers everything taught here, including auto layout, components, variants and prototyping. Paid features become relevant when working in a larger team with shared libraries, which is an employer concern rather than a learner one.
Three details is all we need. A course advisor will call you back.
Front end, back end, databases and deployment taught as one connected system, ending with applications you have shipped to a public URL and can walk an interviewer through.
SEO, paid advertising, content, email and analytics taught around measurement, with real campaigns on real budgets and an emphasis on attributing results honestly.
Next step
Tell us what you want to learn and we will help you pick the right course, batch and mode.