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 covered responsive, mobile-supporting websites and web application interfaces, including Tamil Nadu government projects such as LFAD, DISH and the Election Commission web application. I also conducted interviews with clients and end users to understand pain points and gather feedback, using those findings to clarify requirements and improve UX solutions. Then a year on the UX modernization of IVAPP, a Verizon enterprise application: complex telecom workflows, Verizon's design standards and accessibility requirements, 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 the 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 led and mentored a small team of one to two designers: setting direction, prioritising work, assigning tasks, running design reviews and critiques, mentoring, and providing performance feedback. 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 the enterprise products, the research and validation channel ran primarily through the internal implementation team, who work directly with clients and carry first-hand knowledge of what those clients expect and where they get stuck. Direct end-user interviews and usability sessions were not part of these product engagements.

Earlier in my career at Onward Group, I conducted interviews with clients and end users to understand pain points, gather feedback and clarify requirements.

For the enterprise products, design was validated through UX evaluation, design reviews, prototype walkthroughs, stakeholder demonstrations, technical feasibility discussions with engineering, QA and implementation review against approved designs.

One technical constraint, worked through: Data rehydration initially sat in a side panel. After technical constraints were identified in discussion with engineering, I moved the workflow to a dedicated page, adapting the experience to the implementation constraints