I designed modules for procurement, analytics, project and resource management, and access control.

World of Development started as a tool for training employees within a single team. Over time, the product expanded to support project management, resource planning, procurement, financial data, and access control. As these areas became more connected, they could no longer be designed as isolated modules.

I designed key workflows, the overall interface logic, and finance-related modules. I worked out what data each participant needed, what they were allowed to access, and how the interface should adapt at each stage.

I proposed solution options and discussed them with the Product Manager, who made the final product decisions.

Each area had its own users and workflows, but they all relied on shared data about employees, projects, and business units. A decision made in one part of the platform could affect how another part worked.

The module connected budgets, requests, vendors, payments, delivery, and approvals. My job was to turn these steps into one clear workflow, so every participant could understand the current state of the purchase and what they needed to do next.

The overview shows all requests, their current status, the percentage paid, and delivery progress. Related payments and deliveries can be expanded in the same view, making it easier to understand what is happening without jumping between multiple sections.

Different people take part in the process, so each request needs to show its current stage, who is responsible, and what should happen next. This keeps the workflow clear without relying on messages or manual follow-ups.

When creating a request, users specify the organization, budget, purchase category, vendor, and required documents. Tender or payment details can be added when needed. This gives approvers the context they need to make a decision without searching for missing information elsewhere.

The purchase details bring together participants, approval steps, documents, change history, and payment status. Anyone involved can quickly see what has already happened and who is responsible for the next step.

The budget sets the financial boundaries, while payments and delivery have their own data, documents, and statuses. By linking them to the purchase request, the interface keeps the full picture visible while still letting users work with each part separately.

Users may need to save a draft, see a vendor warning, undo an action, or return to the discussion history. These less common situations still need to feel predictable and complete. Some of the workflow also had to remain accessible on mobile.

Permissions determine which sections and actions are available to each employee based on their role and business unit. I worked with a permission matrix to keep these differences clear, predictable, and manageable.

Beyond procurement, I also worked on modules for managing people, projects, and data. Below are a few examples of the problems I solved across these areas of the product.

The platform already had its own design system with colors, typography, icons, and reusable interface components in multiple states. I used these patterns across new workflows and extended the system where existing components were not enough, helping keep the experience consistent across the product.

The modules shown in this case were released into production. Shared patterns, connected data, and clearer workflows made the platform easier to use across different roles and business areas.