Uma Shankar

UI/UX designer building clear, usable interfaces. Two years in, still learning with every project. Based in Andhra Pradesh, India.

View My Work

scroll

About Me

Passionate about creating intuitive digital experiences.

I design clean, user-focused interfaces, and a background in computer science keeps me grounded in what is actually buildable. Two years in, I am still figuring plenty out — I would rather test an assumption than defend it. What I have learned so far is that the useful work usually happens before the visual design does: understanding the problem properly, and being willing to throw the first idea away.

Download Resume

2+: Years Experience
5+: Projects Completed
100%: Client Satisfaction

Skills & Capabilities

Tools and methodologies I use to bring ideas to life.

Project & Process

Cross-functional Collaboration
Incident Triage
Stakeholder Communication
Problem Formulation
Process Improvement

Design & Research

UI/UX Design
Information Architecture
Usability Testing
User Flows
Wireframing
User Research
User Experience Design
Prototyping
Visual Design
User Interface

Technical

HTML
CSS
Python
GIT

Tools

Figma
Adobe XD
Protopie
Notion
Google Workspace
Microsoft Office
Lovable
Figma Weave
Wonder
Framer

How I Think

My product-thinking framework for ambiguous problems.

Frame the problem

Who is affected, what's happening, why it matters — before jumping to solutions.

Find the signal

Combine usage data, interviews, and support issues. Evidence over assumptions.

Define the opportunity

Turn observations into a focused “How might we” statement, rooted in the actual cause.

Prioritize before building

Impact × value × confidence × effort. One meaningful problem beats several small ones.

Explore multiple solutions

Generate options before committing. Look for the simplest change that shifts the outcome.

Test the riskiest assumption

Find what could make the idea fail, and validate that first.

Measure the outcome

Success isn't shipping — it's the behavior or business result defined up front.

Be curious before being certain. Understand before solving. Prioritize before building. Validate before scaling. Measure outcomes, not output.

When the problem is especially ambiguous

What do we know? → What are we assuming? → What don't we know? → What is the cheapest way to learn it? That keeps me moving without pretending to have certainty I don't have.