Most of what's on this page, nobody asked me to build.

Method partnered with WebPT and GlobalLogic to evolve an early "Gen3" concept into a real product. The work was split into five parallel workstreams — patient, front-office, back-office, clinical, and one more — each owned by a different Associate Director.

Clinical accuracy was non-negotiable, but it couldn't be solved in isolation. Patient, front-office, and back-office workstreams were moving in parallel, each with a different AD driving it, and a lot of decisions had dependencies that crossed those lines.

I owned the clinical workstream end to end — not every decision across the program, but ensuring my area delivered value while staying aligned with the broader product vision, across workshops with leadership from every org involved.

Ran 2–3 pivot concepts down to a single POV for clinical, resolved cross-workstream dependencies with the other workstream leads as they surfaced, and adopted the client's own design system as the shared source of truth.

Boomerang was a 20-person team, including the founder, CTO, and CRO — racing to ship faster rather than pausing to get clarity for their end users.

Instead of designing what was asked for, I started asking why — questioning each proposed solution before building it. That opened a bigger question: what should even be on the roadmap next.

I initiated Warm Referral myself and owned the complete workflow end to end — how a lead gets understood in the CRM, how a warm path gets surfaced, and how the ask gets sent — working directly with the founder, CTO, and CRO.

One early idea — a simple Chrome extension that let the product work inside a rep's existing tools instead of forcing a new one — became a real revenue driver, and the moment the founders started asking what NOT to build. Their first big bet, "Mutual Success Plan," wasn't working — I pushed a different idea instead: Warm Referral, surfacing trusted paths into accounts from CRM data. That one worked in market.

Sales Motivator is Zoho CRM's gamification layer — leads created, calls made, deals won all feed into targets, games, and team leaderboards, on top of the same platform running for 250,000+ businesses worldwide.

The original dashboard was fixed and dark — every point value and rule was hardcoded. If a sales manager's incentive structure didn't match what shipped, there was no way to configure around it.

I initiated this redesign myself and was the sole designer on it, starting from paper wireframes. Shipping it meant coordinating a cross-functional team of 20 across backend, frontend, and product management.

Replaced hardcoded point values with a criteria-based rule builder — module, action, AND/OR conditions — and gave managers two ways to compute points: a flat value per record, or the record's own fields as points. Games, Targets, and Achievements all now read from the same rule engine instead of duplicating logic.

As a parent, I kept hitting the same wall other parents had — school communication scattered across calls, paper diaries, and one-off notices. That's where Scool Panda started.

We didn't start by building. We spoke to 50+ schools first to validate the problem, then built based on what we heard. Speaking to schools was easy. Getting them to actually adopt something new was not.

I owned it end to end — product and design myself, sourced and managed a 10-person distributed dev team to build it, and acted as the founder-led salesperson, talking to hundreds of schools across US, UK, and Indian markets to see where this could actually land.

The honest one: we didn't succeed selling into India. Indian school administrations move slowly on new tools even when the problem is real, because the people approving the decision are business people weighing their own priorities first, not just whether it solves something real.

J-ESTA is a new digital pre-clearance system for visitors from 71 visa-exempt countries, modeled on the US ESTA. We proposed the design directly to Hitachi, GlobalLogic's parent company.

The current process is a dated web and mobile experience — no shared data across family members, no digital identity once approved, and a passport you still have to physically carry.

I created the app screens Hitachi is evaluating for the 2028 release. The E-Card — the idea that most changed the direction of the proposal — wasn't a brief I was handed. It was mine.

Proposed a digital ID (the E-Card) that replaces the physical passport for identity verification, a single shared record for family travel instead of repeat data entry, and two deliberate color directions — blue for continuity with Japan's current app, red for cultural identity.

Every design review at Method catches usability and accessibility issues — eventually. The problem was timing: most gaps surfaced after a build had already started, when fixing them cost real engineering time.

Manual review doesn't scale with three time zones shipping in parallel. Whoever reviewed last, or reviewed fastest, ended up deciding what "good enough" meant that week.

I built a small AI-assisted copilot for the global service team to flag usability and accessibility issues at the design-file stage, before a single line of code gets written.

The team almost treated it as a pass/fail gate. I pushed back — it flags, a person still decides. AI didn't change what good design is. It changed how fast bad design gets caught.

By 2022, BuyerAssist's product had scaled across a 20-person team without any shared design system — every screen was effectively hand-built, and engineering rebuilt the same UI patterns from scratch each time.

Inconsistent UI across the product, an inefficient design-to-development handoff, and high overhead on both sides — every new feature meant re-solving a problem the team had already solved elsewhere.

Nobody asked for this. I identified it as the biggest lever I wasn't pulling, and initiated it myself alongside my product strategy work — owning the component library, documentation, and governance model end to end.

Started small and iterated rather than a big-bang rollout, treated the system as its own product with documentation and governance rather than a one-time Figma cleanup, and validated components with both designers and developers before scaling adoption.