Clearer setup.
Connected work.

TimeXtender’s products had different histories, visual identities and interaction patterns. Users needed both web and established desktop applications to complete the journey: setup and configuration on the web, more complex data transformations on desktop.

My focus was the web experience. I aimed to give it a modern TimeXtender identity and reduce cognitive load through shared concepts, wording and selected interaction patterns. Familiar expectations could help people move between tools that still worked differently.

Adding a data source meant working through one long, uncategorised form. I grouped questions into categories and subcategories, then used earlier selections to show only the fields relevant to that setup.

I wanted the structure to explain the setup as people used it. Categories made relationships between questions visible; conditional fields kept the task focused on what applied. That guidance also needed to stay efficient for users who already understood the work.

Different functions had sometimes shared the same name. I mapped actions to user intent and expected results so labels distinguished what each function did, then used that mapping to guide naming for new features. Consistent meaning could help people carry a concept from web setup into the desktop work that followed.

That vocabulary sat alongside components, interaction states, typography and accessibility as shared design foundations. With designers, product managers and developers, I worked through the details and technical constraints needed to carry those decisions into implementation.