Product strategy · Experience architecture · Design systems

I turn complexity into product direction.

I’m Aneesha Watve. I frame product opportunities, structure complex systems, and translate strategy into clear experiences that teams can build and people can understand.

View Research & Design Strategy Start a conversation

Research & Design Strategy

Three case studies show how I connect research framing, product strategy, information architecture, and experience design.

Colorful street in Old San Juan, Puerto Rico

01 · Civic technologyUX audit & concept

The public’s window into recovery progress

A responsive transparency platform bringing together financial data, project progress, education, procurement visibility, and public accountability.

Human-centered designData visualizationResponsive UXCMS

Aerial view of Puerto Rico homes during disaster recovery

02 · Enterprise platformProduct UX

A command center for recovery operations

A connected dashboard, mega menu, assistant, and visual system designed to help power users act without losing context.

DashboardNavigationConversational UX

Fresh salad with tomatoes, cucumber, greens, and red onion

03 · Consumer productBrand & app concept

Making healthy choices easier to sustain

An end-to-end concept connecting positioning, brand identity, mobile product design, and campaign execution.

ConceptStrategyBrandingMobile UX

CASE 01

Focus: Public recovery transparency
Work: Product strategy, website rebrand, data UX, content system
Context: Implemented public portal

COR3 Transparency Portal

A rebranded public window into Puerto Rico’s recovery—combining complex financial data, project progress, educational content, procurement visibility, and accountability in one responsive experience.

Visit the Transparency Portal ↗

MY PROCESS

Designing for public understanding

I treated the Transparency Portal as an information-clarity problem, not only a dashboard problem. The process connected audience needs, recovery terminology, content hierarchy, visual trust, and data interaction into one public experience.

1 · Understand

I began with the questions different audiences bring: Where is the money going? What is happening near me? Which agency or program is responsible? What stage is a project in?

2 · Structure

I organized disasters, programs, finances, contracts, documents, and project details around those public tasks—using plain-language pathways before exposing deeper data.

3 · Make data legible

I translated funding totals, disbursement trends, project stages, maps, and agency relationships into consistent visual patterns with context, labels, and drill-down paths.

4 · Prototype and validate

I used wireframes and clickable flows to test navigation, filtering, terminology, and comprehension, then refined the interface in collaboration with delivery teams.

5 · Design for change

Because recovery information evolves, the solution included reusable content patterns and a tailored CMS. The design could expand to new disasters, programs, documents, and reporting needs without rebuilding the experience from scratch.

Transparency Portal product strategy connecting public questions, information structure, decision tools, and trust — The product strategy connects real public questions to an information model, useful decision tools, and trustworthy evidence.

DISCOVERY & DEFINITION

Preventing design guesswork

Product direction came from connecting stakeholder evidence, observed behavior, and patterns from comparable civic platforms.

Stakeholder interviews

Surface policy, operational, and public-information constraints.

Field observation

Understand how recovery teams find, interpret, and act on information.

Comparative review

Benchmark civic-data patterns for transparency and comprehension.

CUSTOMER JOURNEY

Customer journey mapping

The map connects each customer question to a specific friction point and product response.

01AwarenessHear about recovery activity

02ArrivalConfirm the source is official

03ExploreFilter funds and programs

04Deep diveInspect projects and documents

05ActDownload, share, or report

06ReturnFollow new recovery updates

MomentCustomer questionFrictionProduct response

Arrival

“Can I trust this source?”

Official information can feel dense and fragmented.

Clear authority cues and a plain-language portal introduction.

Explore

“What applies to my community?”

Large financial datasets are difficult to interpret.

Guided filters by place, disaster, program, and agency.

Verify

“What evidence supports this?”

Documents and technical terms interrupt understanding.

Progressive detail, concise summaries, and visible sources.

Act

“What can I do next?”

Download, reporting, and follow-up paths may be unclear.

Explicit actions for exporting, sharing, reporting, and returning.

Key product opportunity

Move people from a broad public question to plain-language context, then progressively reveal the detailed evidence needed to verify it.

ILLUSTRATIVE PERSONAS

Two different definitions of “useful”

These audience models translate the project framing into design priorities. They are portfolio artifacts—not claims about named research participants.

CONCERNED RESIDENT

Reliable updates, without agency jargon

Needs: infrastructure status, trusted emergency information, and local recovery context.

Design implication: clear source cues, place-based navigation, and plain-language summaries.

SMALL-BUSINESS OWNER

A direct path to recovery resources

Needs: grants, eligibility guidance, application steps, and relevant program updates.

Design implication: task-led navigation, guided filters, and visible next actions.

The challenge

After Hurricanes Irma and María, Puerto Rico faced a long, expensive recovery across damaged power, water, communications, and basic services. Public trust depended on making government-led recovery activity transparent, understandable, and accessible.

The solution

The redesigned portal brought together financial data and descriptive content so the public could understand how funds were obligated and disbursed, how projects moved through recovery, and where to find procurement and accountability information.

Experience pillars

Educational explanations of recovery programs.
Interactive infographics for complex processes.
Visibility into RFPs, contracts, and procurement.
Direct access to report fraud, waste, or abuse.

Responsive public access

The experience was designed for desktop, tablet, and mobile and supported major browsers. Flexible tables, custom visualizations, an island-wide financial map, and project-stage diagrams made recovery information easier to explore.

Illustration cards for Road to Recovery, FAASt project execution, HMGP resilience projects, and Hurricane Fiona recovery — A consistent illustration language differentiates major recovery pathways while keeping the portal approachable and scannable.

Disbursement overview with obligations, quarterly comparison, average and trend — Financial storytelling connects obligations, disbursements, period comparison, and long-term trend.

Map of Puerto Rico municipalities affected by the 2019–2020 earthquakes — Geographic storytelling makes disaster declarations and assistance coverage easier to understand at a glance.

Transparency Portal interactive Puerto Rico recovery project map with filters and project detail panel — **Project-level exploration.** The interactive map connects island-wide recovery activity with filters and a detailed project panel, helping people move from geographic overview to status, phase, funding, and applicant information.

Accelerated project execution financial and project-stage dashboard — Accelerated-project reporting combines agency totals, project hierarchy, and execution stages.

Visual timeline explaining Hurricane Fiona response milestones — Editorial timelines connect major recovery events, policy milestones, and public-assistance context.

A content system built for continuous recovery

The tailored content management system allowed teams to create, edit, and publish pages, images, and video without specialized technical knowledge. It included a searchable document library, reusable content cards, FAQs, interactive flow diagrams, newsroom publishing, and a public glossary.

Documented scale

According to the supplied case study, since the 2018 launch the number of non-FEMA Federal Recovery Fund metrics increased by 175%, while FEMA Recovery Fund metrics increased by 325%.

Broader recovery scope

The portal later expanded beyond Hurricanes Irma and María to include content and data related to earthquakes, the coronavirus pandemic, and Hurricane Fiona—making the content architecture’s adaptability part of the product value.

Outcome narrative

The case study attributes four broader benefits to the platform: increased transparency into public spending, better-informed public decision-making, enhanced accountability through visibility, and more streamlined recovery and procurement processes. These are presented as documented case-study outcomes rather than independently audited causal findings.

CASE 02

Focus: Enterprise workflow
Work: Dashboard, navigation, chat, icons
Context: Product UX concept

Puerto Rico Disaster Recovery System

A coherent operating layer for a complex recovery platform—helping power users orient, navigate, understand, and act without losing context.

The platform strategy creates one coherent system across multiple high-stakes recovery workflows.

Dashboard landing page with announcements, filters, reporting and progress widgets

Dashboard as command center

Announcements, personal lists, recent records, global filters, progress widgets, and reporting shortcuts create a sequence from orientation to action—not a random collection of cards.

Mega menu as mental model

Grouped navigation makes grants, finance, reporting, portals, management, and support legible as one product suite. The menu teaches the system’s structure while respecting roles and permissions.

DRS Assistant

Conversational help stays inside the workflow. It can explain terminology, navigate to the right module, summarize visible information, and guide next steps while preserving source and permission boundaries.

Visual language

Feature illustrations support orientation; functional icons support repeated interaction. Both reinforce explicit labels, consistent metaphors, accessible names, and stable category colors.

Disaster Recovery System illustration library for debris removal, project worksheets, collaboration, grants, formulation, invoicing, PMO, time tracking, and navigation — A distinct but cohesive illustration system helps people recognize modules quickly across a large, multi-workflow recovery platform.

Complete annotated DRS Assistant interface showing conversation, download, new-topic, minimize, response, history, microphone, input, character-count, and submit controls — The full interaction model defines the assistant’s controls, response actions, history, input behavior, and conversational states.

CASE 03

Focus: Consumer wellness
Work: Concept, brand, strategy, app
Context: End-to-end concept

Green Platter

A connected concept, brand, product strategy, and execution system centered on one behavioral goal: making healthier eating easier to sustain.

Green Platter identity applied to packaging, tags, notebook, and sign

The opportunity

Healthy intent breaks down under time, budget, knowledge, variety, and consistency constraints. The product was conceived as a lightweight decision system—not only a delivery interface.

The proposition

Personalized, nutritious meals made convenient enough to become part of everyday life, supported by transparent information and flexible control.

Brand strategy

The GP monogram and sprout metaphor communicate growth, freshness, and food. Deep green adds trust; yellow-green brings energy; food imagery proves appetite and variety.

Product strategy

Relevance, transparency, convenience, enjoyment, and adaptation form the value pillars. Advanced personalization waits until the core loop—good meals, clear information, reliable delivery, easy repeat ordering—proves itself.

The mark combines the GP initials with the visual language of growth and fresh ingredients.

Three Green Platter Instagram campaign concepts using fresh ingredients — A repeatable social system turns ingredients into playful visual messages.

Green Platter social campaign displayed on mobile devices — Campaign executions reinforce the fresh, healthy positioning in a mobile-first context.

PRODUCT STRATEGY SYSTEM

Designing for healthier choices without added overhead

The concept reframes nutrition as a support system: reduce planning effort, make recommendations relevant, and build motivation into the experience.

Customer frictionProduct implicationStrategic response

Meal planning takes too much time

Healthy intent breaks down when every meal requires research and calculation.

Automated, goal-aware planning

Preparation feels complex

Too many decisions create choice fatigue before the customer even orders.

Curated choices and scheduled delivery

Nutrition tracking adds cognitive load

Manual logging can make healthy behavior feel like administrative work.

Visible nutrition with passive progress cues

BEHAVIORAL MATCHING

From stated intent to a useful daily plan

01Goals

Health objective and desired routine

→

02Constraints

Diet, schedule, preferences, and exclusions

→

03Matching

Relevant meals and balanced recommendations

→

04Daily plan

A clear, actionable meal schedule

MOTIVATION ARCHITECTURE

Value first, motivation second

Progress mechanics support the core job rather than becoming a separate rewards layer.

UTILITY

Make the next choice easier

Recommendations, nutrition context, and delivery planning reduce effort.

PROGRESS

Make consistency visible

Streaks and milestone cues can reinforce habits without judgment.

COMMUNITY

Make support optional

Peer ideas, reviews, and shared milestones create social encouragement.

BRAND

Keep the promise coherent

The identity, packaging, product, and campaign all communicate fresh simplicity.

EVIDENCE BOUNDARY

The screens supplied describe a strategic product concept. Adoption, retention, time-saved, and testimonial claims should only be published when supported by source data.

PRODUCT EXPERIENCE

Turning the brand promise into a repeatable habit

The product flow reduces effort while keeping nutrition, preference, and progress visible.

01DiscoverBrowse meals

02PersonalizeSet goals and preferences

03ChooseCompare nutrition

04ScheduleManage delivery

05ProgressTrack and return

HIGH-FIDELITY PRODUCT EXPERIENCE

From onboarding to sustained progress

The interface translates the strategy into a connected journey across goal configuration, daily planning, nutrition, delivery, and milestones.

Green Platter light-theme screens for onboarding, goal configuration, dashboard, and meal planning — **Core journey:** onboarding, health-goal configuration, daily dashboard, and meal planning.

Green Platter light-theme screens for meal details, nutrition, delivery, and achievements — **Product depth:** meal detail, macro dashboard, delivery schedule, and progress milestones.

VISUAL-SYSTEM EXPLORATION

Testing the same product architecture across themes

Dark-theme studies demonstrate that hierarchy, state, and interaction patterns remain consistent when the visual expression changes.

Dark-theme core journey.

Green Platter dark-theme meal detail, nutrition, delivery, and achievement screens — Dark-theme product depth.

These are high-fidelity product-concept screens. Names, meals, streaks, nutrition values, and progress metrics shown in the interfaces are illustrative.

← Back to portfolioAneesha Watve · Branding & Visual Design

SELECTED BRAND & VISUAL COMMUNICATION

Branding &
Visual Design

A focused collection of identity, packaging, campaign, and product-concept work—presented separately from the primary product-strategy case studies.

Branding & visual design · 01

Bee Organic

A premium raw-honey identity translated across packaging, product photography, and a two-pillar social content system.

Client: Bee Organic
Year: 2026
Role: Strategy · Branding · Content Design

STRATEGIC DIRECTION

Natural purity, expressed with warmth and precision.

I spearheaded the campaign strategy, visual identity, and social content design to position Bee Organic as a premium, authentic provider of raw honey. The system balances an earthy product story with a warm, high-end digital presence.

Logo system. A vintage-inspired bee badge combines botanical details and honeycomb motifs in charcoal and golden-yellow colorways.

Bee Organic raw honey jar packaging and product photography — **Packaging strategy.** Transparent, minimal labels let the honey’s natural color lead, supported by marble, wood, and spring florals.

CONTENT PILLAR 01

“Unapologetically Delicious”

A golden-hour social series designed to create appetite and demonstrate everyday utility through recognizable food pairings and morning rituals.

Bee Organic honey and pancakes social advertisement — Pure raw, liquid gold.

Bee Organic honey and lemon tea social advertisement — Mornings, made golden.

Bee Organic honey and toast social advertisement — Start slow, pour sweet.

CONTENT PILLAR 02

Source & Purity

Macro photography of bees and their habitat shifts the story from appetite to provenance—reinforcing trust, natural origin, and the product’s organic character.

Bee Organic source and purity campaign featuring a bee in its natural habitat — The source becomes the story.

Bee Organic macro bee photography for social media — Macro detail builds authenticity.

Bee Organic nature-led raw honey social content — Purity, provenance, and craft.

Branding & visual design · 02

Photowiz

A typographic identity that positions LenzPro Photowiz as the comprehensive, go-to solution for photography services—from digital interfaces to physical collateral.

Client: LenzPro Photowiz
Focus: Brand Identity · Typography
Role: Concept · Visual System · Applications

BRAND IDEA

A complete photography solution, built into the wordmark.

The core identity integrates the idea of “A to Z” directly into its typography. Stacked forms—PHO, TO, and WIZ—create a clear, memorable structure, while the “for anything in photobiz” tagline reinforces the brand’s all-encompassing promise.

Conceptual typography

The A-to-Z idea is embedded in the mark rather than added as an explanation.

High-contrast palette

Deep red and charcoal retain impact across white and black environments.

Scalable system

A disciplined structure carries from mobile screens to billboards and cards.

Photowiz identity shown on light and dark mobile screens — **Digital interfaces.** The minimalist mark remains distinctive across light and dark screen environments.

Physical collateral. The identity scales from large-format street communication to restrained professional stationery.

Branding & visual design · 03

Jain Farms — Fru2go

A research-led identity and packaging redesign that gives an organic fruit-pulp range a more distinctive, fresh, and approachable presence.

Client: Jain Farms
Studio: Ticket Design
Role: Research · Branding · Packaging · Mascot Naming & Design

THE CHALLENGE

Make natural ingredients and freshness visible at a glance.

The existing visual identity and packaging did not clearly communicate the product’s natural character, freshness, or authenticity. Limited differentiation across the range also made it harder for the brand to build a memorable shelf presence and earn customer trust.

01User research

→

02Market & competitor research

→

03Brand direction

→

04Packaging system

→

05Mascot name & design

DESIGN RESPONSE

One expressive system, three strategic jobs.

Differentiation

A recognizable identity creates a distinct character within the organic fruit-pulp category.

Freshness

Fruit-led color coding and imagery make the range feel immediate, vibrant, and easy to navigate.

Consistency

A unified visual language connects every flavor, pack, and character touchpoint.

Fru2go fruit pulp packaging range for Jain Farms — **Packaging system.** A flexible pouch family uses strong fruit colors, clear flavor differentiation, and a consistent mascot-led architecture across the range.

MASCOT STRATEGY

Frutosaurus: a friendly bridge between fruit and families.

I worked on both the mascot name and design. The development process combined user, buyer, market, and competitor research with exploratory sketches, clay studies, and a flexible final character system.

Frutosaurus mascot naming, research, sketches, clay prototypes and final character designs — **Character development.** From early concepts and physical studies to an expressive digital mascot family designed for packaging and communication.

Branding & visual design · 04

ME Toys

A brand and product-concept system built around active participation—children assemble, narrate, construct, and transform each idea through play.

Brand: ME Toys
Scope: Branding · Packaging · Product Concepts
Role: Concept · User, Market & Competitor Research · Strategy · Design

THE MASTER IDEA

Move play from consumption to creation.

The ME Toys system treats the child as an active maker rather than a passive user. Its toy-truck master mark communicates movement, modularity, and discovery, while each product line turns a distinct behavior—storytelling, building, or imaginative making—into the center of the experience.

RESEARCH FRAMEWORK

User research

Explore how children understand instructions, sequence stories, assemble parts, and stay engaged—alongside the priorities of parents and caregivers.

Market research

Map opportunities across educational play, creative construction, storytelling, and environmentally conscious toy categories.

Competitor research

Compare play patterns, age positioning, packaging communication, assembly complexity, durability, and distinctiveness at shelf.

STRATEGIC DIRECTION

Four principles connect the portfolio.

01
Child as co-creator
Every concept asks the child to make, arrange, narrate, or assemble.
02
Learning through action
Story sequencing, spatial reasoning, and construction are embedded in play.
03
Identity reveals function
Each logo visually encodes its product idea—from truck to chair to animal.
04
Material intelligence
Cardboard becomes both a structural medium and a creative constraint.

STORY SYSTEM

Li’l Storyteller

A 12-piece jigsaw series in which every added piece advances the story. “Create and Narrate” makes sequencing, interpretation, and imagination part of the same play loop.

Choose→Connect→Narrate→Continue

Brand and packaging. The truck-shaped ME Toys identity anchors a story-building puzzle system designed as a collectible series.

BUILD-IT-YOURSELF FURNITURE

Li’l Eco Chair

A fully functional chair assembled from interlocking cardboard pieces. The concept turns construction into play while producing a useful object engineered to support up to 90 kg.

Logo concept: the chair silhouette is built directly into the typography, making product function part of the identity.

Product and identity. Flat pieces become a three-dimensional chair; the same transformation is echoed in the wordmark.

PAPER ENGINEERING

Econimals

A make-your-own animal world constructed from cut and colored cardboard pieces. The system combines simple forms with recognizable silhouettes so children can assemble characters and environments.

Logo concept: letterforms combine to suggest an animal, expressing the same part-to-whole logic as the toys.

Brand and product language. A family of folded cardboard animals demonstrates how a consistent construction principle can generate an expandable play world.

How I work

I treat interfaces as visible expressions of a deeper system: user intent, information structure, operating constraints, evidence, and brand promise.

01 · FrameDefine the real job, audience, constraints, and evidence boundary.

02 · StructureBuild the information model and decision path before polishing screens.

03 · ExpressCreate a coherent interaction and visual language across touchpoints.

04 · ValidateTest the riskiest assumptions and separate intent from measured impact.

About

Product strategy, made tangible.

I’m a UX and product design professional with 18+ years across digital experience, visual communication, product design, and design leadership.

My strength is connecting insight to execution—shaping experience vision, defining journeys and interaction models, and translating strategy into prototypes, high-fidelity UI, reusable patterns, and implementation-ready specifications.

UX ManagementProduct StrategyQualitative Research ArchitectureStrategic Metrics Frameworks

Education & certification

Learning grounded in strategy and craft.

2026

Nielsen Norman Group (NN/g)

UX Certification · User Experience Design

Advanced specialization in UX Management, Product Strategy, Qualitative Research Architecture, and Strategic Metrics Frameworks.

2002

Sir J.J. Institute of Applied Art, Mumbai University

B.F.A. (Applied Art) · Advertising & Visual Communication

Gold Medalist · 8 Government and State Awards

Writing & perspective

Ideas shaped through practice.

Reflections on enterprise UX, qualitative research, design leadership, and an evolving product-strategy practice.

4 essays · Read here

Enterprise UX2 min read

Complexity→Structure→Clarity

Designing for Complexity: Making Enterprise Experiences Feel Simple

Why simplicity in enterprise products is not about removing information, but making complex systems understandable without concealing their reality.

Read article →

UX Research2 min read

Question→Evidence→Decision

UX Research Starts Before You Talk to a User

Meaningful qualitative research begins with the architecture of the study—before interviews, observations, and conversations take place.

Read article →

Design Leadership2 min read

Perspectives→Alignment→Direction

UX Leadership Is Less About Authority and More About Alignment

A perspective on guiding product, engineering, business, compliance, and user priorities toward a shared experience direction.

Read article →

Career Reflection4 min read

Experience→Frameworks→Intentional practice

Why I Went Back to the Classroom After 18+ Years in Design

A reflection on returning to formal study—not to start over, but to better understand and strengthen years of multidisciplinary design experience.

Read article →

Let’s work together

Have a complex product that needs direction?

I’m interested in product strategy, experience architecture, and design-system challenges where clearer structure can change what a team builds and how people use it.

aneeshawatve3@gmail.com

Enterprise UXAugust 31, 2026 · 2 min read

Designing for Complexity: Making Enterprise Experiences Feel Simple

Simplicity is not the absence of complexity. It is the result of structuring complexity around what a person needs, when they need it.

Complexity→Structure→Clarity

By Aneesha Watve

“Make it simple” is one of the most common requests designers receive. It is also one of the most misunderstood.

Simple does not mean removing information until the screen looks clean. In complex enterprise products, simplicity is something much harder: making a complicated system understandable without pretending that the complexity does not exist.

This has been one of the defining challenges of my enterprise UX work.

Complexity has many sources

An enterprise workflow may need to accommodate multiple user roles, different permissions, regulatory requirements, legacy processes, exceptions, large datasets, dependencies between teams, technical constraints, and years of accumulated business rules.

None of that disappears simply because we want a cleaner interface.

The challenge is therefore not, “How can I make this screen simple?” It is, “How can I help this user deal with only the complexity that matters to them, at the moment it matters?” That is a very different design problem.

Start with the user's mental model

Organizations tend to describe products according to how the organization is structured. Users rarely think that way.

A system might internally consist of modules, databases, departments, programs, and approval stages. The user is thinking: “I need to submit this.” “I need to know what happened.” “I need to fix this problem.” “I need to make a decision.”

One of the designer's most important jobs is translating organizational complexity into a structure aligned with the user's goal. That translation affects navigation, information architecture, terminology, workflow, interaction patterns, and content.

Progressive complexity

Not every user needs every piece of information at once. This is where progressive disclosure becomes powerful.

Show what is necessary for the current decision. Make secondary information available when needed. Reveal advanced functionality in context. Provide meaningful defaults. Use hierarchy to distinguish the critical from the merely available.

The system can remain sophisticated underneath while the user's interaction with it remains understandable. That is not “dumbing down” the product. It is good information architecture.

Visual design comes later than structural clarity

My foundation is in visual communication, and I continue to care deeply about typography, composition, hierarchy, and aesthetics. But complex products have repeatedly taught me that visual polish cannot rescue structural confusion.

Before asking whether a screen looks good, I want to know: Does the user understand where they are? Do they know what they can do? Do they know what requires attention? Do they understand what happens next? Can they recover from a mistake? Does the terminology match their mental model?

Only then does visual design amplify the experience.

Simple is an outcome

Some of the best interface work is almost invisible. Users do not notice the information architecture. They do not see the interaction model. They do not know that ten edge cases were resolved behind a single workflow. They simply accomplish what they came to do.

That is why one of my favorite ways to describe the work I do is: Complex → Radically Simple.

Not because the underlying problem became simple. Because careful research, architecture, interaction design, systems thinking, accessibility, and iteration absorbed enough of the complexity that the user no longer had to.

And perhaps that is one of the most valuable things good UX can do.

UX ResearchAugust 31, 2026 · 2 min read

UX Research Starts Before You Talk to a User

A conversation is not automatically research. Good research begins with the architecture of the study and the decision it must inform.

Question→Evidence→Decision

By Aneesha Watve

User research sounds straightforward. Talk to users. Observe them. Ask questions. Identify pain points. Translate those insights into design.

In practice, meaningful qualitative research is much harder.

One of the most important ideas reinforced through my UX research studies is that good research does not begin with the interview. It begins with the architecture of the research itself.

A conversation is not automatically research

It is easy to conduct an interesting user interview. It is harder to conduct one that reliably helps a team make a decision.

Before speaking with a participant, I want to understand: What are we trying to learn? What decision will this research inform? What do we already know? What assumptions are we testing? Who can provide the evidence we need? Which research method fits the question?

Those decisions shape the quality of everything that follows. Without them, teams can collect pages of observations and still struggle to answer the original product question.

Ask about behavior, not just preference

There is an important difference between asking people what they like and understanding what they actually do.

Consider: “Would you use a feature that automatically organizes these items?” versus “Tell me about the last time you needed to organize these items. What did you do?”

The first invites speculation. The second begins with real behavior. People are usually much better witnesses of their past experiences than predictors of their future behavior.

The insight is not the quote

Another common mistake is treating memorable user statements as insights. A quote is evidence. An insight requires interpretation.

Imagine several users saying, “I export this information into Excel.” The superficial conclusion might be: “Users want Excel export.” Perhaps. But deeper investigation might reveal that users export because the product does not let them compare records, perform calculations, share information, or create a required downstream view.

The real opportunity may have little to do with Excel. Qualitative analysis moves from individual observations to patterns, from patterns to meaning, and from meaning to implications for the product.

Research should create decisions, not reports

A polished presentation with personas, quotes, photographs, and findings can still have limited impact if nobody knows what to do next.

I prefer research that answers: What did we learn? How confident are we? Which assumption changed? What should the team reconsider? Which opportunity deserves further exploration? What do we still not know?

The output might be a report. But the outcome should be a better decision.

Research is an architecture

I increasingly think of qualitative research as an architecture rather than an activity. The interview is one component. So are participant selection, research questions, methodology, facilitation, analysis, synthesis, bias awareness, communication, and decision-making.

When those elements reinforce one another, research becomes much more than “talking to users.” It becomes a disciplined way of reducing uncertainty.

And that is when research begins to influence product strategy rather than merely document user opinion.

Design LeadershipAugust 30, 2026 · 2 min read

UX Leadership Is Less About Authority and More About Alignment

Some of the most important UX leadership moments happen when nobody on the project reports to you.

Perspectives→Alignment→Direction

By Aneesha Watve

For a long time, I associated design leadership with managing designers. Today, I see it differently.

A product manager has one priority. Engineering has another. Business stakeholders focus on deadlines or outcomes. Compliance teams see risks. Users simply want to accomplish what they came to do. Design sits somewhere in the middle.

One of my biggest takeaways from studying UX management is that UX leadership is often an alignment problem before it is a design problem.

Great design rarely fails because someone cannot draw the interface

Enterprise design teams generally know how to create wireframes, prototypes, components, and interfaces. The harder problems are usually elsewhere.

What problem are we actually solving? Which user need should take priority? Which requirement is truly mandatory? Where can we simplify? What tradeoff are we willing to make? Who has the authority to decide?

Unless those questions are resolved, producing more screens does not necessarily move the product forward. Sometimes it simply makes disagreement more visual.

The designer as translator

Throughout my career, I have increasingly found myself playing the role of translator—not language translation, but perspective translation.

A business stakeholder may describe a requirement through a business objective. An engineer may describe the same requirement through system behavior. A compliance team may frame it around risk. A user may describe the resulting problem as, “I don't know what I'm supposed to do next.”

All four perspectives can be valid. The designer's job is to create a shared understanding of the experience connecting them.

Journey maps, workflows, prototypes, service blueprints, research findings, and even a well-framed design question can become alignment tools. The artifact is valuable, but the conversation it enables is often even more valuable.

Influence is a design skill

Presenting a design is not simply explaining why a button is placed somewhere. It means explaining the reasoning behind a product decision: What problem did we observe? What evidence do we have? What alternatives were considered? What tradeoffs are involved? What would success look like?

Once the conversation moves to that level, design critique becomes less subjective. Instead of “I like option A,” the discussion becomes, “Option A better supports the workflow we agreed is most important.” That shift matters.

Leadership can happen without the title

I have seen this outside professional product teams as well. While coordinating a volunteer educational program, I worked with board members, teachers, parents, students, and volunteers who often had very different priorities.

There was no organizational hierarchy that could solve every disagreement. Progress depended on communication, structure, shared goals, feedback mechanisms, and trust.

UX organizations operate in surprisingly similar ways. You cannot mandate genuine alignment. You have to create the conditions for it.

My definition of UX leadership today

UX leadership is not simply producing the strongest design. It is helping a group of people make better experience decisions together.

Sometimes that requires research. Sometimes a prototype. Sometimes a framework. Sometimes a difficult conversation. And sometimes the most important contribution a designer can make is not another screen at all.

It is helping everyone finally see the same problem.

Career ReflectionAugust 30, 2026 · 4 min read

Why I Went Back to the Classroom After 18+ Years in Design

I did not go back to learn how to design. I went back to understand design—and my own experience—more deeply.

Experience→Frameworks→Intentional practice

By Aneesha Watve

After more than 18 years in design, I decided to go back to the classroom. Not because I was starting over. Because I wanted to understand my own experience better.

My career has moved through visual communication, advertising, digital learning, branding, UX, product design, consulting, and complex enterprise platforms. With every transition, my role became less about simply creating something visually effective and more about understanding users, solving complex problems, aligning stakeholders, and helping teams make better product decisions.

Experience had given me strong instincts—but I wanted stronger frameworks behind those instincts. That led me to complete my UX Certification with Nielsen Norman Group, with advanced learning focused on UX management, product strategy, qualitative research, and UX metrics.

Why study UX after already practicing it for years?

After working in design for so long, I had already encountered ambiguous requirements, competing priorities, complex workflows, frustrated users, design-system challenges, accessibility considerations, difficult trade-offs, and the tension between user needs, business goals, and technical constraints.

But experiencing something and having a structured way to reason about it are not always the same thing. I wanted to step away from deadlines and deliverables and examine fundamental questions more deeply.

How should research be structured so it influences product decisions? How do we move UX conversations beyond individual screens? How should designers collaborate with product and engineering? How do we measure whether an experience improved? And as designers become more senior, how does the role evolve from designing the experience to shaping the conditions in which good experiences get created?

Experience gave me patterns. NN/g gave me another lens.

One benefit of working in design for many years is pattern recognition. You sense when a workflow is unnecessarily complicated. You recognize when stakeholders describe symptoms instead of the underlying problem. You can anticipate where users may struggle before formal testing.

That intuition is valuable. But it can become dangerous if we stop questioning it.

The NN/g certification gave me an opportunity to revisit familiar problems through structured frameworks. The learning helped me articulate why something had worked—or why it had not.

Once something becomes explicit rather than intuitive, it becomes easier to explain, repeat, teach, challenge, and improve.

My questions have changed over the years

Early in my career, many questions were about execution: How should this information be presented? What should the visual hierarchy be? How can we communicate the idea more clearly? Those questions still matter deeply.

Over time, additional questions became equally important: Are we solving the right problem? What evidence tells us it matters? Whose perspective might be missing? What assumptions are we making? What trade-offs are we accepting? How does the experience connect with the wider product ecosystem? How will we know whether the design improved anything?

That shift—from focusing primarily on the artifact to thinking about the system surrounding it—has been one of the biggest evolutions in my career.

Enterprise UX made this especially clear

My recent work has involved complex enterprise experiences where design decisions are rarely isolated. A seemingly simple screen may sit at the intersection of customer needs, business processes, regulatory requirements, accessibility standards, engineering constraints, multiple user roles, and legacy systems.

In those environments, UX cannot be reduced to making an interface easier to use. It requires systems thinking, research, experience architecture, product thinking, design systems, measurement, communication, and alignment between people who see the same problem from very different perspectives.

My NN/g learning helped me connect many of these pieces more deliberately.

Going back to the classroom was also humbling

It reminded me how important it is to remain a student. When you have worked in a field for a long time, it is easy to become comfortable with your methods. Formal learning creates an opportunity to question them.

Some concepts reinforced things I already believed. Others gave me new vocabulary for ideas developed through experience. Some challenged assumptions I had carried for years. I found that refreshing.

Design keeps changing. Products change. Technology changes. User expectations and organizations change. AI is changing both the products we design and the way designers work.

Remaining curious is not separate from being an experienced designer. I increasingly believe it is part of the responsibility.

I didn't go back to learn how to design

I went back to understand design more deeply. My NN/g certification did not replace what 18+ years of practice had taught me. It helped me organize, question, and strengthen it.

Earlier in my career, I often asked, “How can I design this better?” Today I ask a broader set of questions: Are we solving the right problem? What evidence supports our decision? How does this experience fit into the larger system? How will we know whether it worked? How can I help the entire team make better experience decisions?

Going back to the classroom was not about adding another credential. It was about becoming more intentional about the designer I want to be in the next chapter of my career.