Skip to content
  1. 2006Graphic &
    web design
  2. 2014Enterprise
    UX/UI design
  3. 2018Teams &
    design leadership
  4. 2026Accurate
    Background
  5. NowProduct Design Lead
    & MBA in AI

01 / MY STORY

Clarity for complex products. Direction for ambitious teams.

I’m Lajapathy Kodiraman, a Product Design Lead with 20 years in design. Since April 2026, I’ve been Product Specialist / Product Design Lead at Accurate Background, leading design for enterprise SaaS and background-screening experiences.

Previously, I worked at Zensar Technologies in senior UX/UI design (Aug 2014–Nov 2017) and senior product design, UX strategy and design systems (Apr 2018–Feb 2026). My career began in graphic and web design at Olympic Media (Jun 2006–Aug 2014).

My portfolio spans payments, security, healthcare, commerce and enterprise platforms. I combine hands-on UX/UI design with product strategy, design systems and team leadership.

Lajapathy Kodiraman wearing a black suit.

Experience across products and teams

Career totals across product delivery, design leadership and mentoring.

02 / PRINCIPLES

Decisions before solutions

The principles I use to frame decisions, work with partners and develop design judgment.

  1. Problem before pixels

    Name the user risk and product decision before comparing solutions. Test assumptions against the available evidence.

    In practice Before drawing a flow, I want the team to agree on the decision it must help someone make. What does the user know, what remains uncertain, and what would a costly mistake look like? Those answers shape the first prototype.

    Related study: E-Wallet
  2. Design with engineering from day one

    Explore interaction behavior, feasibility and failure states together. Make the trade-off visible before choosing the implementation.

    In practice I bring engineers into the conversation while options are still open. We work through permissions, loading behavior, data limits and recovery together, so the design describes a product we can build and maintain.

    Related study: Norton OPS
  3. Access is part of the product

    Treat readable content, keyboard operation and recovery paths as design requirements throughout the work.

    In practice I review the path beyond the ideal screen: navigating without a mouse, understanding an error, reading at a smaller size and completing a task when information is missing. These moments deserve the same attention as the main journey.

    Related study: E-Wallet
  4. AI supports judgment

    Use AI to explore alternatives and accelerate drafts. Keep source checking, privacy decisions and final product judgment with people.

    In practice I use generated alternatives to widen exploration, then compare them against the brief. A convincing draft still needs a source check, an interaction review and a person accountable for the final decision.

    Related study: FluxCRM
  5. Make decisions and ownership explicit

    Agree the release scope, decision owner and acceptance criteria so teams can resolve open questions before hand-off.

    In practice Before delivery, I make the unresolved questions visible: who decides, what must ship, which compromises are acceptable and what evidence will tell us whether the release worked.

    Related study: Norton OPS

03 / DELIVERY

From direction to delivery

A working approach, adapted to the product and the evidence available.

UX research & framing

As a UX designer, I frame the task, user needs and constraints before agreeing what to solve.

Typical deliverable
Problem brief, research questions and assumptions map
Typical partners
PM, researcher and stakeholders

Product Concept & Strategy

Compare product options against customer needs, business priorities and technical constraints.

Typical deliverable
Concept options, scope proposal and decision record
Typical partners
PM and engineering lead

UI design & prototyping

As a UI designer, I refine screens, states and prototypes with product and engineering.

Typical deliverable
Task flows, prototype and validation notes
Typical partners
Researcher, engineering and data partner

Delivery & Scale

Specify behavior, exception states and acceptance criteria; review implementation and agree what to measure next.

Typical deliverable
Component guidance, release checklist and measurement plan
Typical partners
Engineering lead, PM and data partner

04 / EXPERTISE

UX, UI and product design expertise

Product strategy, UX design, UI design and reusable systems, connected through shared decisions.

05 / TOOLKIT

Tools that support the work

A practical toolkit for research, design, prototyping and delivery. The choice follows the problem.

DESIGN & PROTOTYPING

  • Figma
  • Sketch
  • Adobe XD
  • Axure RP
  • ProtoPie

USER RESEARCH & TESTING

  • Maze
  • Hotjar
  • Optimal Workshop
  • Dovetail
  • UserTesting

DESIGN SYSTEMS & HANDOFF

  • Storybook
  • Zeroheight
  • Zeplin

MOTION & ADVANCED DESIGN

  • Adobe After Effects
  • Blender
  • Rive

DATA & ANALYTICS

  • Google Analytics
  • Mixpanel
  • FullStory
  • Amplitude

GRAPHIC & DESIGN

  • Illustrator
  • Photoshop
  • CorelDRAW

AI & EMERGING TECH

THINK & RESEARCH

  • ChatGPT
  • Claude
  • Gemini
  • Perplexity
  • Dovetail
  • Maze
  • Attention Insight
  • Notion AI

CREATE & DESIGN

  • Figma AI
  • Google Stitch
  • Uizard
  • Galileo AI
  • UX Pilot
  • Magic Patterns
  • Visily
  • Relume

PROTOTYPE & BUILD

  • v0
  • Lovable
  • Bolt
  • Builder.io
  • Framer AI
  • Anima
  • Claude Code
  • Cursor
  • Onlook

VISUAL IDEATION

  • Midjourney
  • Adobe Firefly
  • Runway

*AI is used as an augmentation layer—never a decision authority—within clear ethical, privacy, and quality guardrails.

06 / LEARNING

Learning that informs the work

  1. M.Sc. (Software Engineering)

    Madurai Kamaraj University · 2001–2006. A technical foundation for working across design and engineering.

  2. MBA (AI) — In progress

    BITS Pilani Work Integrated Learning Programmes · Jul 2026–Apr 2028 (expected). Connecting AI, business strategy and product decisions.