Now think about your favourite digital services: the ones that just feel effortless to use. Every interaction flows naturally, and it all feels part of the same trusted experience. That’s not by accident. It’s the result of a well-structured design library, working behind the scenes to create consistency, scalability and trust.

As both a designer and a user, I’ve had my fair share of frustrations with clunky interfaces and mismatched branding in UI. And because of that, whenever I kick off a new project, I’m determined to avoid those pitfalls by building a solid foundation: the design library.

So in this article, I hope to share why building a robust design library is the key to tackling these pain points and creating seamless user experiences at scale. It’s also why I’m driven to write this: I’ve seen firsthand how a well-crafted design library can transform not just a single app, but an entire organisation’s digital ecosystem, something I’ll share further as we go along.

Design library vs design system

I will focus specifically on design libraries in this article rather than the broader concept of design systems. In simplest terms, a design library is a curated set of style guides and reusable interface elements like typography, color palettes, and buttons, that help teams maintain a consistent look and feel. A design system, on the other hand, goes a step further by having code-ready components, more extensive documentation, and processes that unify the way teams update and govern the design system.

While design systems offer a more comprehensive framework involving deeper collaboration with developers and product teams, most organisations might not need to start there. Instead, a solid design library lays the groundwork, setting the stage for a more scalable design system as the product and organisation evolve. Think of it as an early-stage design system, delivering immediate benefits in consistency and efficiency without overcomplicating things.

What makes a design library great

In the years designing products across startups and enterprises, I’ve learned one crucial lesson: the bigger or more complex the organisation, the more important this foundation becomes. Let me explain why.

First, design library is your brand’s digital DNA

When most people think about design libraries, they picture a collection of UI components from popular design systems like shadcn/ui, Bootstrap, or the default iOS and Android UI kits. Just grab a UI kit, change some colours, and call it a day. While this might work for simple products, we’ve learned the hard way that it comes with significant costs, especially for complex products and enterprise projects.

When a design library doesn’t carry the brand’s DNA, it leads to a generic-looking product, making it hard for customers to distinguish your brand from competitors. Look at Netflix, Duolingo, or Instagram, you can recognize them instantly, even without seeing their logos. That’s because the most successful businesses invest in design libraries that truly reflect their identity, extending beyond colors and fonts to shape the entire user experience.

I saw this firsthand while we designed a mobile app for manufacturing plant performance monitoring. Rather than defaulting to a generic enterprise style, we worked closely with stakeholders to channel their brand DNA of efficiency and innovation into the design. We introduced a sleek dark mode interface that highlight key metrics without overwhelming the user, while giving the product a modern, cutting-edge feel. These choices not only supported advanced data visualization but also aligned seamlessly with the company’s future-focused vision.

Similarly, our work on the HMI Group hospital website was centered around building trust, an essential factor in healthcare decisions. The brand DNA was translated into the digital experience by focusing on clarity, warmth, and professionalism. We used clean, structured layout to make medical information easily accessible, a reassuring color palette that conveys safety and expertise, and real imagery of doctors and patients to create a sense of reliability and human connection. These design choices helped establish a confident user experience, ensuring patients felt informed and supported at every touchpoint.

Handles the real-world complexity when basic UI kits fall short

One real story stands out. A Global Fortune 500 energy company approached us to revive a project that had failed three times and cost millions. When we looked deeper, we realised the core underlying issue. The previous teams had built solutions without validating their assumptions with actual users. Without a structured design library to support rapid prototyping and testing, each iteration became expensive and time-consuming, making real user validation impractical.

The impact then was clear: users struggled with complex workflows and data visualizations that didn’t match their mental models or daily needs. What could have been caught early through proper user testing had instead led to costly rebuilds.

We knew we had to take a different approach. So we started by asking questions like:

• How can we use a design library to accelerate our user validation process and reduce the cost of iterations?
• What patterns do users actually need for interpreting complex operational data effectively?
• How do we ensure our design system supports continuous user feedback and evolution?

From there, we built a design library that made complex industrial data analysis and reporting more accessible and intuitive. We implemented:

• Legible typography with a clear hierarchy, ensuring key figures stood out for instant recognition.
• Strategic spacing and balanced UI density prevented data overload by grouping related metrics, making dashboards structured yet easy to scan.
• Color coding provided quick visual insights such as greens for positive trends and reds for warning, to help users identify key data points at a glance.
• Visual cues like progress status and last-update indicators enhanced clarity, ensuring users could quickly interpret real-time data without unnecessary friction.

What truly excited us over the years was seeing the design library evolve into a scalable enterprise solution that served diverse user needs, from engineers tracking real-time equipment data to executives analyzing company performance metrics. Despite their distinct needs and technical expertise levels, users experienced a consistent, efficient interface throughout.

Designed for real people and real needs, instead of generic user personas

Sometimes, the most valuable lessons come from specialised projects. Take VivaValet, a digital product we designed to make technology more accessible for elders. Generic design libraries would have failed here because they don’t account for age-related accessibility needs like declining vision, reduced dexterity, and cognitive differences. So we needed to go deeper. Through extensive UI research, we studied how elderly users learn, interact, and think about digital interfaces. This led to crucial design decisions, like:

• Increased text size from 16px to 24px for better readability and less eye strain.
• Carefully selected typography optimized for legibility.
• Enhanced touch targets to prevent accidental taps, accommodating users with reduced motor skills.
• High-contrast color schemes tested with vision disability tools, improving visibility.
• Simplified navigation patterns aligned with elderly users’ mental models.

As surprising as it may seem, culture plays a big role in design libraries. What works well in one region may not translate effectively in another. Working across Southeast Asia has taught me that digital behaviors, expectations, and even visual preferences differ dramatically. A one-size-fits-all design library risks alienating users, making cultural awareness a key factor in creating effective, scalable designs.

Through research and testing, I’ve found that cultural considerations impact several design aspects, including:

• Visual hierarchy and UI density – Apps in Asia often have denser layouts compared to Western counterparts. This reflects cultural differences in written language structure. Asian characters convey more meaning per symbol, leading to a preference for compact, information-rich interfaces. Western apps, by contrast, use more whitespace and minimalistic layouts.
• Color meanings and symbolism – Colors don’t mean the same thing everywhere. In the West, red often signals errors or warnings, but for Chinese, it represents luck and prosperity. Similarly, white conveys purity in Western cultures but is associated with mourning in some Asian traditions. Understanding these cultural associations prevents unintentional miscommunication.
• Bilingual interfaces that feel native, not translated – Direct translation isn’t enough. Sentence structures, reading flow, and emphasis vary across languages. For example, Malay and Thai sentence structures differ significantly from English, requiring thoughtful UI adjustments to ensure readability and natural phrasing.
• Local payment behaviors – Even digital payments aren’t universal; different regions have preferred methods. In Southeast Asia, QR code payments and bank transfers are common, while Western users are more accustomed to credit cards and PayPal. A well-structured design library must support these regional differences without overcomplicating the experience.

By embedding cultural awareness into design libraries, we ensure that digital products resonate with real users, fostering trust and engagement. Rather than applying generic user personas, we tailor experiences based on how people naturally interact with technology in different markets, ensuring usability, familiarity, and long-term adoption.

Not self-limiting but continuously evolve to scale

Early in my journey, I could get away with rigid design libraries for smaller products. But enterprise projects taught me a valuable lesson: if your design library can’t evolve, your digital platform can’t either.

A truly effective design library must anticipate growth, supporting new features, products, and even entire business lines as you scale. Ultimately, a robust design library is key to removing friction when your product suite expands, ensuring consistent user experiences across new markets, functionalities, and digital platforms.

How do you know if your design library is too rigid?

A rigid design library often creates more problems than it solves. Some telltale signs include:

• Hardcoded components that break or require extensive customisation when a new feature or product is introduced.
• Overly prescriptive guidelines that don’t allow flexibility for different teams, leading to workarounds and inconsistencies.
• Minimal documentation or poor onboarding, causing teams to misuse or abandon the library altogether.

What does a flexible design library look like?

Now, I build design libraries that are:

• Component-based and scalable, ensuring that UI elements can be easily repurposed for new services.
• Structured for modularity, so teams can mix and match UI patterns rather than being locked into rigid templates.
• Supported by clear documentation and onboarding, ensuring that internal teams and external vendors can adopt it seamlessly

We treat our design libraries as living documents, continuously engaging with stakeholders and testing with real users to identify pain points and opportunities for improvement. This feedback loop ensures our design libraries remain relevant and effective, allowing organisation to grow without sacrificing brand consistency or user experience.

The joy factor, making digital products people love

Even in business contexts, emotional connection matters. When we worked with TNG ewallet on their in app parking, a locally infused microcopy was essential to making this an immediately resonant touch point for Malaysians. Users loved it so much they shared screenshots of our playful writing on social media.

As a Malaysian born and bred UX design and development agency, we know Malaysians well. We believe that adding delightful, culturally relevant details is key to creating memorable experiences. By infusing the local culture into interface elements, microcopy, and overall design, we make digital products feel personal and engaging, even for something as everyday as parking or payment applications. This human touch can transform mundane interactions into moments of genuine delight.

Real business metrics improvements

Remember that Fortune 500 enterprise project we redesigned? The results speak for themselves:

• 90% Monthly Active Users (MAU)
• 30% improvement in Manufacturing Plant Cycle Efficiency
• 50% reduction in plant interruptions
• Expansion across 14 applications

While the design library wasn’t the sole driver of these metrics, it played a crucial role in enabling rapid prototyping, structured validation, and efficient design production, helping teams iterate faster and implement changes at scale.

What surprised me the most was seeing other projects within the same enterprise begin adopting the design library, amplifying its impact far beyond the original scope. With a shared system in place, teams could build upon existing components, reducing duplication and streamlining workflows. This is the testament to what I mentioned in the introduction: a well-structured design library doesn’t just improve a single app; it has the potential to scale across an entire digital ecosystem of the organisation.

Over time, we’ve consistently seen how a well-structured design library accelerates operational excellence:

• Product and development teams release features faster
• Different departments easily maintain a unified brand
• Updates and maintenance become more efficient
• New team members quickly get up to speed
• External vendors deliver high-quality work with fewer inconsistencies

Ultimately, these metrics highlight that a well-structured design library isn’t just about looks; it’s a strategic asset that boosts operational efficiency, ensures user satisfaction, and strengthens brand credibility across the entire organisation.

Hard-won lessons: what actually works

After building design libraries for everything from small startups to major enterprises, here’s what I’ve learned:

Lesson #1: Start with understanding

Instead of jumping straight to UI components, start by understanding your users, operations, and vision. The strongest design libraries are built on deep insights, ensuring they address real needs rather than just assembling UI elements.

Lesson #2: Build for your reality

Focus on creating components that solve your specific challenges. Align your library with your team’s workflow and product requirements so it grows with your needs instead of forcing unnecessary constraints.

Lesson #3: Think long-term

Approach your design library as a strategic investment rather than a quick fix. The most successful libraries support where organisations are going, not just where they are today.

Lesson #4: Test with real scenarios

The true test of a design library is how well it handles your most complex use cases. Every library improves dramatically through thorough testing with users in real scenarios.

In fact, we’ve found that with the right foundational elements in place, you can go from hypothesis to user-tested prototype in a 5-day design sprint. Because the UI components already adhere to consistent branding and standards, teams can focus on testing new ideas, rather than building everything from scratch.

Final thoughts: Building a foundation for lasting impact

A well-designed design library is more than just a collection of UI components. It’s a foundation for digital success. By investing in a robust, flexible library, you can accelerate product development, create user-friendly experiences, and ensure your brand stands out in an increasingly crowded market.

At Stampede, we’ve helped organisations build design libraries that truly transform their digital capabilities. If you’re considering this for your organisation, let’s discuss how we can create something that doesn’t just look good, but delivers real impact. Reach out to studio@stampede-design.com

The post Design Libraries: The Key to Success (or Failure) appeared first on Stampede: the strategic design & technology company.

Avengers Stampede Assemble!

What is The Blitz?

The Blitz is the official name for Stampede’s version of a stand-up meeting, and it occurs every weekday at 1PM (GMT+8) over voice chat using Slack’s voice call feature. During every Blitz, a single person is given the responsibility of the Blitz Master. This person is responsible for facilitating the flow of a Blitz and keeping track of every project’s progress. For every project, there is a team member assigned to it, and the Blitz Master will ask each person on the project(s) they are leading.

What the Blitz Master will ask specifically about each project is the status of each project and its current ETA and percentage of completion. As to not waste any time during the meeting, everyone is expected to be prepared with their project updates. This makes for a rapid discussion that wraps up quickly and cleanly.

This goes in a round-robin fashion until the Blitz Master has taken note of every project. When our usual Blitz Master, Iwan is off for the day, someone else will take over his role and continue meeting as normal.

Blitz Master Iwan in the house! Taken during our Hari Raya Blitz Meeting.

Once the main work-related portion of a Blitz is done, an inspirational quote will be pulled from our quote bank. Among the attendees of a Blitz, one of us will be chosen to best explain the quote. By doing so, we become motivated for the day and everyone learns a new lesson. Here are two examples of quotes that we have shared recently.

Everyone at Stampede is expected to participate in a Blitz unless they are on leave, or have a reason for not being able to attend. In which case, they must inform the Blitz Master, in advance on why they cannot attend.

Why do we do it?

Compared to most companies, the way we manage projects is unique. At Stampede, the role of project manager is shared among all team members. It empowers our team by giving designers and developers the opportunity to learn and practice project management skills.

At a functional level, it is also meant to update the management so that they know what is going on in the company. In addition, team members can know when to jump in and help out on other projects that need extra support.

A glimpse of how it looks like

It will be much easier for you as the reader to understand how a Blitz is run by showing you an everyday example of how it’s done. Iwan is the Blitz Master this round.

• 

  Good day everyone, Happy Monday! Let’ start off today’s Blitz with a few good news! We have confirmation that Telaga Terminal redesign is about to kick-off and the client is excited to see our scheduling. On another note, we also have an RFP request for an e-commerce project and a potential v2 of an Australian project we worked on last year. Shaza will take care of both and will advise us once we have the go-ahead to proceed.

  We shall move on to all the project leads now.

  Jared, how is Constructs doing today?

• 

  We published another article for Angular beginners yesterday and it was shared on a few Facebook groups. I have also asked Zana to give more social media exposure to this particular article because I think it’s something very helpful for people who are interested in Angular.

• 

  Already done. I am watching the number of shares right now across all social media channels. Tony, you have Google Analytics covered?

• 

  Yes, I have already prepared the report and will send it over after this.

• 

  Okay, sounds good. Jared, what about Constructs UX improvements? We were at 60% yesterday. Does the ETA this Friday hold?

• 

  We’re planning to finish up the rest of the improvements as planned on Trello. ETA holds.

• 

  Awesome, thank you Jared! Hakim, how are we doing on Agile training?

This pattern continues one-by-one with each person, and can quickly wrap this up within 20 minutes.

It’s always evolving

The Blitz is an ongoing process to find the best way to run a quick but productive daily meeting at Stampede. It must be able to enable sharing of updates for all projects and to also fit the needs of the current team. In the past we used Skype for conducting our Blitz but have moved over to Slack voice calls ever since. Slack is great for us because we use it as our main working platform, for both internal and external communications.

At its core, we are constantly changing aspects of The Blitz to fit the needs of the current team.

One of the major changes to the Blitz was when we came across the ‘Daily Huddle’ concept. Its quick and rapid updates were perfect for Stampede and we were greatly inspired by its concept. In the past, each person would tell everyone else about what they were doing for the day and what they would be working on. Our current Blitz is tightly controlled, where the focus would be on project leads reporting on the status of their assigned projects. It is faster and more energetic, once again adding to the kick-start that we get at the start of each work day.

Consistency is the key

No matter how many times we change the format, what matters the most for a productive stand-up meeting is consistency. With every Blitz held on the same time every work day, it has become a habit for our team to attend. The Blitz Master doesn’t need to remind the team every time. The best time to hold the meeting however, depends on your team’s schedule.

The scrum is less about strict rules and more about maximizing productivity.

If your team assembles in the office early, then hold your meetings as the very first thing in the morning. If people enter in at different times, then run the stand-up at a time you know everyone is in. This also indirectly helps you identify late comers. But the Blitz is less about strict rules and more about maximizing productivity. Turning the daily or weekly meetings into a regular routine that fits your team’s unique schedule. It also helps ensure that it becomes an effective tool for your development team.

Conclusion

Thanks for reading this post on our culture at Stampede. We hope this has inspired you like how it has for us. How do you run team meetings at your workplace? We’d love to know your thoughts on The Blitz and how you think we can improve it. Drop us a comment and we’ll do our best to reply at the soonest. Again, thanks for reading!

For more Stampede culture and related content, please do consider liking us on Facebook and following us on our Twitter feed. Oh, and we can’t forget about Instagram, where Shaza and Zana posts some of the most amazing imagery ever.

The post The Stampede Way to Scrum: The Blitz appeared first on Stampede: the strategic design & technology company.

An increasing number of design companies have now begun to ditch the unforgiving waterfall project management approach for an agile one. It allows teams — both internal and clients’— to hit key milestones fast, to get greater visibility to the project, and to receive continuous feedback — hence allowing them to reach quicker to change and bottlenecks in the development process. The agile approach helps teams respond to these unpredictabilities through incremental, iterative work cadences, known as sprints.

In an agile paradigm, every aspect of development — requirements, design, etc. — is continually revisited throughout the life cycle. When a team stops and re-evaluates the direction of a project sprints every two weeks for instance, there’s always time to steer it in another direction. The results of this “inspect-and-adapt” approach to development greatly reduce both development costs and time to market. Mistakes are reduced, products are shipped fast, reiterations are made there and then, users’ needs are more addressed rather than initial requirements.

Simply summarised, Agile project management is the process by which projects can be managed and implemented in small chunks of work. Small victories.

Scrum and Kanban

Scrum and Kanban are two terms that are often (incorrectly) used interchangeably in Agile approach. In reality, there are significant differences between these two Agile methodologies. Understanding these differences is key to choosing the path that will work best for your environment.

Scrum vs Kanban (Source: solutionsiq.com)

Scrum is a tool used to organise work into small, manageable pieces that can be completed by a cross-functional team within a prescribed time period (called a sprint, generally 2-4 weeks long).To plan, organise, administer, and optimise this process, Scrum relies on at least three prescribed roles: the Product Owner, the Scrum Master and the Team Members. Scrum board refers to the visual representation of the work flow, broken down into manageable chunks called “stories”, with each story moved along the board from the “backlog” (the to-do list), into work-in-progress (WIP), and on to completion.

While Scrum limits the amount of time allowed to accomplish a particular amount of work (by sprints), Kanban limits the amount of work allowed in any one condition – so that only a certain number of tasks can be ongoing and completed on the to-do list. Kanban board, just like Scrum board, refers to Kanban’s visual representation of the work flow.

How are agile projects managed?

Using Scrum model rather than Kanban, as previously adopted, we have established that there are three roles: product owner, ScrumMaster and team.

The product owner is largely responsible for the business aspects of the project. She ensures the right product is being built and is the most empowered to make decisions about the product. If an agile project involves teams both internal and client, someone from the client side is usually the product owner as she has the say on what should be established within the requirements.

The Scrum Master is usually the project manager or the project lead, ensuring that the team works together in the most effective manner possible. A good Scrum Master facilitates meetings and discussions within an agile project, remove impediments in the progress, tracking progress and issues — in short, ensuring the teams get what can be done as smoothly as possible.

Then there’s the most important people: the team. They assume each role dedicated in the agile project either as Strategist, Designer, Front End Developer, Programmer etc and together will collaborate on how to best achieve the product goals.

Agile project management divides responsibility among more than one team member, and everyone is involved in every phase of the project, rather than focusing on one member at a team— like waterfall approach. The result is every team member is more informed of every project decision and everyone should be in the same page once done right.

Tools

Scaling agile isn’t easy the first time round – all good things is not the first time round. Luckily there are always tools to help expedite agile approach as good as possible. Here are three of which we have tried out.

Yodiz

We use Yodiz as our Agile project management tool in Stampede. Its features include Scrum tool, issue and bug tracker, Kanban task board, and epics management software. With a visual, Kanban style Scrum board, users are able to see a comprehensive sprint planning view. They effectively manage user stories and sprints, create, edit and re-prioritise them easily, associate them into epics that span across multiple projects, and track daily work progress and burndown charts. It is so far the most comprehensive out of all tools we have tried.

JIRA

JIRA Software gives your team the flexibility to plan and adopt any agile practice, whether it be scrum, kanban, or a mixed methodology. Teams can create and estimate stories, build a sprint backlog, visualize activity, measure team velocity, and report on progress. JIRA seems to be more visual and less cluttered than Yodiz, however, JIRA is more catered towards large enterprise scalability and we serve smaller companies — hence, Yodiz is a better choice for us.

ZebraPlan

If you’re a tech startup, it can be tough to find quality Agile software at a palatable price point. ZebraPlan offers a great solution for small teams with big needs. The software breaks down tasks into sprints, which users can easily drag-and-drop tasks into. The dashboard view has all the necessary charts to keep your team in check, and the software has some overall cool features, like KPI comparisons, code review, and, for those opting for the “ultimate” plan, 16 reports to choose from.

Conclusion

Agile approach might have been touted to be oriented heavily towards software development, but to be honest if we think about it, its core principles of “inspect and adapt” should apply more now where things are often changing and evolving. Agile should be a natural fit, once you figure out how to make it work for you. After all, as each team and project is different, you are best off picking the methods and applications that work and adapt them as you go.

Does your team also run agile? What tool do you use? Do you have any good tips for running agile project management?

Sources:

• Agile Methodology
• Agile Project Management Done Right
• What Is Agile Project Management?
• 3 Differences Between Scrum and Kanban
• Understanding Agile Design and Why It’s Important
• Agile Project Management Software 

The post Getting to Know Agile Development appeared first on Stampede: the strategic design & technology company.