CASE STUDY 02 / TIME TRACKING + FINANCE

Forecastify

Making time and project data easier to compare

Read the case study

CENTRAL DESIGN QUESTION

How can a dense time and finance interface support comparison?

Forecastify connected time tracking with financial reporting inside an existing internal product. As the interface grew, the volume of information made everyday work difficult to scan. I redesigned the UI and adapted an existing component system, with particular attention to dense tables, meaningful use of colour and consistency across light and dark themes. Selected features reached production.

MY ROLE

Product designer responsible for the UI and product-level design-system work, collaborating with the product owner.

SCOPE

Time and resource views, table layouts, visual hierarchy, component adaptation and theme variables in Figma.

DELIVERY

Design work within an operating product, with selected features shipped. My contribution was on the design side of the system.

A working product with information competing for attention

The challenge began with an existing product and its accumulated complexity. Time entries, allocations, overtime and time off represented different things, but people needed to read them together to understand a person’s workload and activity. Financial reporting added a further reason for keeping time data understandable: the figures had consequences beyond the timesheet itself.

A manager scanning a table needed to compare values across people and periods while retaining the meaning of each row. Making individual cells look cleaner would have addressed only part of that task. The relationships between values needed to remain visible throughout the table.

I worked with the product owner to shape the interface around these practical reading tasks. The existing software established the functional context, and the component library provided a foundation for rebuilding the screens in Figma. The design problem was to use that foundation coherently across a complex product.

FIG 1 · DECISION DETAIL

Related time categories remain visually distinct within the same table, so users can compare values without losing their meaning.

Designing the table around comparison

I focused on the table as a working surface. Logged time, allocated time and time off needed distinct treatment because a similar-looking value could carry a different operational meaning. Grouping related rows and establishing a consistent hierarchy gave the values context before colour was applied.

The design kept related information close enough to compare. This matters in an operational table: extra whitespace can make each element easier to see while pushing the information needed for a decision further apart. I treated density as something to organise, balancing separation between groups with continuity inside each group.

I used colour to help distinguish categories and highlight differences within the grid. This involved an explicit trade-off. A completely quiet table would reduce visual competition, but would also remove some of the cues that support rapid comparison. The selected approach retained colour where it carried meaning and relied on the table structure to keep that colour interpretable.

OPTION NOT TAKEN

A completely quiet table

Reduces visual competition, but removes some of the cues that support rapid comparison.

SELECTED APPROACH

Colour where it carries meaning

The table structure keeps that colour interpretable.

The intended reading sequence was straightforward: identify the person or project context, understand which kind of time a row represents, then compare its values across the relevant period. That sequence informed the hierarchy more directly than a preference for a particular visual style.

Identify the person or project context

Understand which kind of time a row represents

Compare its values across the relevant period

FIG 2 · SYSTEM BEHAVIOUR

Keeping time categories semantically distinct

Allocation

Planned use of capacity

Logged time

Records activity

Time off

Changes availability

Overtime

Adds a layer to workload

Allocation describes planned use of capacity. Logged time records activity. Time off changes availability, while overtime adds another dimension to the interpretation of workload. These concepts can appear together without being interchangeable.

My UI work made those distinctions visible in the presentation. The aim was to help users understand what they were comparing before drawing a conclusion from the numbers. A high value means little until the interface makes clear whether it is planned, recorded or unavailable time.

This was also a constraint on visual consistency. Applying an identical appearance everywhere would have concealed useful differences. I needed consistency in the way each category behaved, alongside enough distinction between categories to support interpretation. The resulting design used repeated patterns to make a dense screen learnable without flattening its meaning.

Adapting existing design tokens across themes

The work used an established Figma component library, imported into the project file in advance with its variants and variables already defined. I applied the system through those variables rather than fixed values, so a change to a token carried through every screen that used it. I adapted the library to the product, adjusted the relevant variables and aligned the light and dark palettes, then checked their effect on the screens.

This required attention to relationships between colours. A background, a divider and a status treatment might each look acceptable in isolation while producing a weak hierarchy together. The dense tables made those relationships particularly visible: small differences repeated across many cells could change the overall balance of a screen.

I therefore treated the themes as part of the same interface logic. Labels, groups and states needed to retain their relative prominence when the theme changed. The dark theme had to support the same comparison tasks as the light version.

SCOPE NOTE

My responsibility covered design-side adaptation and screen consistency. The original library and its variable structure already existed; the work did not involve creating a token architecture from scratch or implementing a token-to-code pipeline.

Working within an existing product

Collaboration with the product owner helped connect the visual work to the software’s existing functions. Rebuilding the interface in Figma made it possible to consider individual screens within a shared component system, while retaining the realities of a product already in use.

That context also shaped the delivery. Selected features shipped into the live product, so the outcome was incremental. The case demonstrates my contribution to the interface and its underlying design consistency; it does not represent a claim that every area of the product was replaced in one release.

06 · WHAT THE WORK ACHIEVED

How can a dense time and finance interface support comparison?

07 · TAKEAWAY

Forecastify sharpened my approach to dense interfaces. The useful question was how much information could remain understandable together. Table structure, category semantics and colour had to work as one system.

NEXT CASE STUDY · 03 / 06

Leier

Preparing complex B2B orders in a constrained workspace

horvath.bertalan.andras@gmail.com · +36 30 311 8560