Suresh Veeramachaneni

Design leader · Hyderabad · Now advising product teams

Good design is good business.

Product teams lose weeks to slow handoffs, bloated reviews and drift. I build the design teams and the systems that win that time back. Eight years at Microsoft on Bing and MSN; most recently Principal Design Manager at Optmyzr.

18years in UX and product design
8.5years embedded at Microsoft, Bing and MSN
13+enterprise product domains
COOdesign's reporting line at Optmyzr

From craft to systems

2026
AI systemsIndependent · Design consultant

Helping product teams redesign how they build with AI. The system itself can be a teammate.

Selected work

Written as decision logs
01

A design system that answers back

Optmyzr · 2024–2026
Problem

The same grey was defined six or seven ways across the codebase. Fit-and-finish audits ran for days.

The bet

Tokens as one source of truth, a component registry, and an MCP server that engineers and AI agents query from their editor.

Outcome

Audits are shrinking and designers are designing again. [ADD ONE NUMBER]

Read the decision log →
02

One senior, five people sharing care

Mariposa · Senior care
Problem

Remote family, a hired caregiver and a spouse each held one piece of a parent's day.

The bet

One care group with role-based invites and a shared feed, so everyone sees the same day without the senior feeling managed.

Outcome

[ADD OUTCOME]

03

[Y-Axis: confirm which project]

Y-Axis · Immigration

Problem, bet and outcome go here once the artifact matches the claim.

I built a design system that talks back. Here's how.Muzli · Jun 2026 · 11 min
The anatomy of a skillComing next
An MCP war storyComing next

Lab

Built · In motion · VisionAll Lab →
[Set status]MagicimagerImage and PDF conversion.
[Set status]VitaloopA caregiver-first family app.
[Set status]PlanesA personal life OS.

Working with me

Set the vision, then open Figma the same week.

  1. Design reports to the businessAt Optmyzr, design moved from an execution layer to a central function reporting to the COO.
  2. Systems before screensTokens and components first, so every screen after ships faster.
  3. Critique on a rhythmA standing cadence and written principles, so feedback is never a surprise.
  4. Grow the peopleA career framework for every designer on the team.