Daniel Kumar M

I trained as a multimedia visualiser and started by building interfaces by hand: HTML, CSS, JavaScript, jQuery, WordPress. That is where the technical fluency comes from, and it is why I design around engineering constraints rather than discovering them in QA.

Seven years at Onward Group went on responsive, accessible websites and web application interfaces, including Tamil Nadu government projects (LFAD, DISH and the Election Commission web application), where accessibility, usability and compliance were requirements rather than preferences. Then a year on the UX revamp of IVAPP, a Verizon enterprise application: complex telecom workflows, someone else’s design standards, and implemented screens reviewed against approved designs.

Since 2019 I have owned the UX for an enterprise data platform family end to end: the ETL tool that moves the data, the platform that holds it under retention and governance, and the internal system that turns consumption into an invoice. Eight modules, five user roles, nine source families, one design system across two products.

I established a review gate before high-fidelity work: ideation and rough design, UX review, feedback and refinement, then high-fidelity mockup. UX issues surfaced before high-fidelity work started, rework dropped because direction was agreed first, and established patterns got reused rather than reinvented.

I directed a small UX team of one to two designers: direction, prioritisation, assigning work, reviews and critiques, mentoring and performance discussions. Designers owned feature-level execution.

The harder job was not either product. The ETL tool and the archive platform were built on one shared component language, and most of the design leadership was deciding which differences between them were real and which were habit.

On these products the research channel ran through our internal implementation team, who work directly with clients and carry first-hand knowledge of what those clients expect and where they get stuck. Interviews and usability sessions with end users were not part of the engagement.

Design was validated through UX and design reviews inside the team, stakeholder walkthroughs and demonstrations, technical feasibility discussions with engineering, QA and design review before release, and implementation review against approved designs.

One input, worked through: the implementation team raised a need for an application count on the listing. Without it, the volume of the estate was only inferable by scanning the grid. The count now sits in the listing header, beside the title.