Explainability Feature
InnovateTerms
Overlay to existing Terms of Service pages that breaks down TOS agreements to improve explainability and user experience
Project overview
Role: UX/UI Design, Development
Timeline: 3 Months
Category: Explainability Feature
What I worked with:
InnovateTerms
[Placeholder: overview of InnovateTerms — what it does, what problem it solves]
What I worked on:
- 01Performed research on the terms of service user experience as well as studies about the overall percentages of user engagement
- 02Iterated on design solutions that would work with a company's existing Terms of Service interface
- 03Implemented a solution by leveraging Claude's API to analyze pre-existing terms of service via URL or pasted content, summarize, categorize, and display in an explainability overlay
Project Ideation & Iteration
The Challenge
The problem to solve
The first step in the user journey of any app or website is viewing and agreeing to Terms of Service, yet according to a 2017 Deliotte study over 90% of people do not read them. The problem is that TOS agreements are often lengthy, filled with legal jargon, and not designed with user experience in mind. This leads to users blindly agreeing without understanding what they are consenting to, which can result in privacy violations, data misuse, and legal issues for companies.
Research & Approach
How I approached it
After drawing out a prototype and the key functionality I wanted, I collaborated with Claude Code to scaffold build and iterate on a full Next.js Terms of Service prototype with explainability that leverages Anthropic’s API to pull terms of service content, summarize and categorize it, and then display it on the overlay.
More Screens
Lessons Learned
- 01
It can be difficult to iterate once you have a product built. Feature branching is one way to test different features, but for this project I built out a prototype that only summarized and categorized demo data, and only after it was completed did I decide it would be better to create a fully functioning option that leverages Anthropic's API to summarize, categorize and display existing terms of service. In the end, it was easier to start fresh with a detailed CLAUDE.md file than iterate on the existing project. This made me realize that the better approach is to always take the time to think through what the core product should be, and then use feature branching to iterate.
Up next