Scaling Design Impact Across 12+ Enterprise Products in Mining Technology

As Lead Product Designer / Lead UI/UX Designer at PT Bukit Teknologi Digital, a technology company serving the mining industry, I lead a team of six designers responsible for the end-to-end design lifecycle across the company's entire product ecosystem. Over time, we built a mature, scalable design system that now underpins a diverse portfolio of enterprise products spanning three core streams: Asset Maintenance, Safety, and People, plus executive and AI-driven tooling. This system has enabled consistent, high-quality delivery across every product line, directly contributing to on-time launches, stronger client trust, and measurable commercial growth.

The company's product portfolio had grown organically across multiple business units, but without a shared foundation. A dozen-plus applications were live in production with no centralized documentation, each one built at a different point in time under a different process.

Product lifecycles were inconsistent from one team to the next: some products moved straight from idea to development with no structured requirements, others stalled without clear ownership of what "done" meant. There was no design system governing how products looked, behaved, or were built, every product had effectively been designed in isolation.

Compounding this, individual products were frequently outsourced to different external vendors, each with their own design conventions, tooling, and quality bar. The result was a fragmented product ecosystem: inconsistent UI patterns across products, duplicated design and engineering effort, unpredictable delivery timelines, and rising maintenance overhead as the portfolio kept growing.

Rather than treating this as a purely visual design problem, I approached it as an organizational and process problem — and brought it to leadership directly in an open company forum, proposing a structured product lifecycle the whole organization could adopt.

From there, I put the framework into practice:

• Standardized how requirements get defined. Ran hands-on workshops teaching teams how to write a proper PRD (Product Requirements Document) before any design or development work begins — replacing ad-hoc requests with a shared, repeatable process.
• Built a structured intake and tracking system. Set up a Kanban-based workflow in Jira for every incoming design request, wired directly to the PRD requirements, so every request across every product is logged, scoped, and traceable from day one.
• Designed and documented a unified design system. Built a single design system to replace the fragmented, vendor-by-vendor visual language across the portfolio — giving every product, regardless of who touches it next, a shared set of patterns and standards to build from.
• Introduced Agile and Lean UX into the team's day-to-day. Coached the design team to work in shorter, more iterative cycles focused on validated learning rather than upfront, big-batch design.

The combined effect reshaped how the company ships products. Maintenance became predictable instead of reactive. Products started arriving ready for development ahead of deadline, creating real breathing room for research and testing before launch, instead of rushing straight to production. Design delivery speed increased by roughly 200%, sustained across 12+ concurrent products with a lean design team, and the design system's consistency reduced rework and shortened engineering handoff time, contributing directly to faster, more predictable product releases and stronger revenue outcomes for the business.

The product lifecycle that was once inconsistent and vendor-dependent is now the company's standard way of working.