Redesigning the Saahas website: a client project from my design internship.
Saahas has worked in waste management since 2001. Their website was last redesigned about ten years ago. It held all the right information, but people weren’t engaging with it. I worked on research, information architecture, wireframes and responsive UI, through to developer handoff.
A non-profit doing 25 years of good work, with a website that hid it
Saahas (saahas.org) builds communities across rural and urban India and teaches people to manage waste at source by reducing, reusing and recycling.
Their website was last redesigned about ten years ago. It held the right information, but people weren’t engaging with it.
| Role | Design intern: research, information architecture, wireframes, UI |
|---|---|
| Worked with | A design lead (my mentor), 2 developers and the Saahas team |
| Client contact | Saahas team members, through regular client meetings |
| Scope | Research → IA → wireframes → web + responsive UI → UI testing → dev handoff |
The information was all there. The engagement wasn’t.
Low engagement was hurting several of the organisation’s goals at once. We designed for four of them.
Display their work
Make projects easy to find and tell apart.
Collect funds
Clear paths to donate, fund and partner.
Educate
Make waste knowledge easy to explore.
Show careers
Help people find a role and join the team.
Listen to the client, then suggest, not just take orders
Client meetings
To understand requirements, and to suggest changes instead of only taking them.
Stakeholder interviews
6 interviews with the Saahas team, on their vision, priorities and pain points.
Competitive analysis
Of other NGO and environmental websites.
Analytics review
Of user behaviour, popular content and drop-off points.
Detailed user research wasn’t needed for a redesign. We learned the audience by walking through the site and talking to the client.
One week in, we went back to the client with a new plan
The original budget was 180 hours for design and development. After one week of research and IA work, we re-evaluated the whole project and agreed an updated plan with Saahas.
| Phase | Hours | Includes |
|---|---|---|
| Design | 200 | Research, wireframing, web + responsive design, UI testing |
| Development | 120 | Build and implementation |
| Total | 320 |
Raising scope early, with evidence, protects both the client and the team.
Six reasons people weren’t engaging
Outdated design & navigation
Hard to find information quickly.
Messy information architecture
Projects, resources and volunteering were buried.
Low engagement
Little interactivity, a high bounce rate and low time on site.
Not mobile-optimised
A poor experience for visitors on their phones.
Few engagement tools
No easy way to volunteer or sign up for events.
Weak careers page
No detailed job descriptions, guidelines or insight into the culture.
Deep dropdowns, scattered projects and mixed-up groupings
3–4 levels of nested dropdowns
Our work → Program linked website → Becircular, Alag Karo, Aviral Ganga, BE-responsible.
Projects scattered
To compare projects in different verticals, people had to hop between many pages.
Mixed-up groupings
Resources mixed annual reports, videos, rules and blogs, and annual reports were split into 8 separate year links.
No home for careers or learning
Jobs sat under Get involved, and educational content was spread across menus.
A structure built around what each visitor came for
| Section | What lives there |
|---|---|
| Our work | Theory of change, program verticals, work by area (Rural, Urban, Eco-sensitive, Special waste streams), search by geography, partners |
| Knowledge center New | Circular economy, waste hierarchy, source segregation, waste management, sustainable lifestyle, myth vs reality, rules |
| Career New | Jobs with descriptions and an apply flow, internships with a form |
| Get involved | Partner, Donate (with stories), Volunteer (with activities and testimonials) |
| Resources | Annual reports, articles, publications, blogs, podcasts, videos, media mentions |
Every goal got its own path, and every path has a reason
| Goal | Problem | Decision |
|---|---|---|
| Display work | Projects scattered across pages | Our work grouped by Rural, Urban, Eco-sensitive and Special waste streams, plus search by geography |
| Fund / involve | No clear path for each way to help | Get involved split into Partner, Donate and Volunteer, each with its own flow |
| Educate | Lots of content, long journeys | A new Knowledge center: circular economy, waste hierarchy, segregation, myths vs reality |
| Careers | A thin careers page | A dedicated Career section with job descriptions and application forms |
Designing for the build, and what industry taught me
- Designed web and responsive layouts, so mobile wasn’t an afterthought
- Ran UI testing before handoff
- Planned the design within the 120-hour development budget, keeping it buildable
- Handed off in Figma: annotated specs, a shared component library and weekly dev check-ins
- Clients are collaboratorsGood meetings mean listening, and pushing back with reasons.
- Scope is a design decisionFlagging the timeline early kept the project honest.
- Structure before pixelsFixing the IA solved problems no visual polish could.
- Design for the buildKnowing the dev budget shaped what I designed.
- Every goal has a userDonors, volunteers, learners and job seekers each needed their own path.