Top 30 Advanced Design Systems Concepts Quiz

30 questions. Pick an answer, or open “Show the answer” to read it.

Answers are graded in your browser. Nothing is saved, and no XP or streak is earned here. The app keeps score.

1. Question 1 of 30

   What is the primary reason for continuously measuring a design system's health and performance?

   • aTo establish a baseline for future comparisons with industry-leading design systems.
   • bTo exclusively monitor design-to-code parity and accessibility compliance for all new features.
   • cTo provide objective insights into its decay, justify ongoing investment, and align maintenance efforts with broader business goals.
   • dTo guarantee that all design system components achieve 100% adoption across all product teams.
   Show the answer

   Answer: c · To provide objective insights into its decay, justify ongoing investment, and align maintenance efforts with broader business goals.

   The card emphasizes that continuous measurement reveals decay, justifies ongoing investment by proving value, and ensures maintenance is tied to broader business outcomes. Option B is a tempting distractor because design-to-code parity and accessibility are critical metrics, but the card states measurement encompasses more and is not exclusively for new features.

   Read the full bite: Measuring Design System Health and ROI

2. Question 2 of 30

   What is the core advantage of implementing a 'system of systems' for design management?

   • aIt mandates that all product teams use the exact same component library for strict visual uniformity.
   • bIt allows for a single, monolithic design system to serve all product needs efficiently.
   • cIt provides a framework to balance shared brand foundations with diverse product-specific requirements.
   • dIt reduces the overall overhead and governance complexity compared to a single design system.
   Show the answer

   Answer: c · It provides a framework to balance shared brand foundations with diverse product-specific requirements.

   The 'system of systems' approach is designed to balance a central core of shared brand elements with the flexibility for individual product-specific design systems to address unique needs. Option B is incorrect because the card explicitly states that a single monolithic system often fails at scale, and this approach is a departure from that.

   Read the full bite: System of Systems: Managing Design Systems at Scale

3. Question 3 of 30

   According to the "supply chain" mental model, what is the primary purpose of the semantic token tier?

   • aTo allow component tokens to override global values without affecting other parts of the system.
   • bTo directly style individual UI elements such as buttons or input fields.
   • cTo translate abstract global values into meaningful, context-specific design properties.
   • dTo define the raw, foundational values like specific hex codes or font sizes.
   Show the answer

   Answer: c · To translate abstract global values into meaningful, context-specific design properties.

   The card explains semantic tokens are "intermediate goods" that "alias values from the global file to give them meaning," translating raw values into context-specific properties. Option A is incorrect because the system establishes a one-way flow; semantic tokens provide meaning, not a mechanism for components to directly override global values.

   Read the full bite: Token Tiers: From Raw Values to Component Properties

4. Question 4 of 30

   What is the primary advantage of LCH over HSL for creating perceptually consistent UI color palettes?

   • aIt provides access to a significantly larger color gamut, including P3, for more vivid displays.
   • bIts Lightness component ensures colors with the same 'L' value appear equally bright to the human eye.
   • cIts Chroma component offers an unbounded scale, allowing for finer control over color intensity.
   • dIts hue angle starts at magenta (0°), offering a more intuitive color progression than HSL's red (0°).
   Show the answer

   Answer: b · Its Lightness component ensures colors with the same 'L' value appear equally bright to the human eye.

   The card states LCH is "perceptually uniform" and fixes HSL's flaw where colors like yellow and blue at 50% lightness appear dramatically different. LCH's Lightness (L) guarantees that colors with the same L value are perceived as equally bright, which is fundamental for consistent palettes. While LCH does enable access to wider gamuts (option A), this is about the range of colors, not primarily about the perceptual consistency between colors within a palette.

   Read the full bite: LCH Color: More Vivid, Predictable UI Colors

5. Question 5 of 30

   What is the primary problem that automated token pipelines are designed to solve for design systems?

   • aAutomating the creation of design documentation and style guides.
   • bReducing the manual effort and inconsistency in translating design decisions into platform-specific code.
   • cManaging the version control of design assets like images and fonts.
   • dEnsuring designers and developers use the same design software.
   Show the answer

   Answer: b · Reducing the manual effort and inconsistency in translating design decisions into platform-specific code.

   Automated token pipelines address the historical challenge of manual, error-prone translation of design decisions into code across multiple platforms, which leads to inconsistencies and high maintenance. While they facilitate collaboration, their core purpose is not to dictate specific design software but to standardize design decisions for automated code generation.

   Read the full bite: Automated Token Pipelines: A Single Source of Truth

6. Question 6 of 30

   Which scenario most appropriately demonstrates the use of WAI-ARIA?

   • aApplying role="heading" to a <span> element to visually style it as a heading.
   • bImplementing role="tab" and aria-selected on <div> elements styled to function as a tab in a custom tabbed interface.
   • cAdding role="button" to a <button> element to ensure screen reader compatibility.
   • dUsing aria-label on an <img> tag that already has a descriptive alt attribute.
   Show the answer

   Answer: b · Implementing role="tab" and aria-selected on <div> elements styled to function as a tab in a custom tabbed interface.

   WAI-ARIA is designed for custom interactive components that lack native HTML equivalents, like a tabbed interface built from generic <div>s. Options A, B, and D violate the first rule of ARIA use: if a native element exists for your purpose (e.g., <button>, alt attribute, <h1>-<h6>), use it instead of ARIA.

   Read the full bite: WAI-ARIA: A Script for Custom UI Accessibility

7. Question 7 of 30

   What is a critical consideration for library authors to ensure their code is safely tree-shaken by consuming applications?

   • aCorrectly marking files with side effects in their package.json to prevent accidental removal.
   • bManually specifying which components are used by the consuming application in a configuration file.
   • cAvoiding any global state modifications within their library's modules.
   • dEnsuring all modules are written in CommonJS format for static analysis.
   Show the answer

   Answer: a · Correctly marking files with side effects in their package.json to prevent accidental removal.

   The card explicitly states that if a library is incorrectly marked as "sideEffects": false, crucial imports with side effects can be dropped. The correct approach is to provide an array listing files with side effects. Distractor D is tempting because side effects are the problem, but the card clarifies that side effects can exist if properly marked, not that they must be entirely avoided for tree shaking to function correctly.

   Read the full bite: Tree Shaking: Shipping Only the Code You Use

8. Question 8 of 30

   For a public JavaScript library, what is the most critical reason to dual-publish both ESM and CJS formats?

   • aTo provide flexibility for developers who prefer dynamic module resolution over static declarations.
   • bTo ensure that projects using require() can successfully import the library's modules.
   • cTo allow consuming applications to choose between synchronous and asynchronous module loading.
   • dTo enable advanced tooling features like tree-shaking for all consumers, regardless of their module system.
   Show the answer

   Answer: b · To ensure that projects using require() can successfully import the library's modules.

   The card states that dual publishing provides maximum compatibility, ensuring code works for users with legacy systems reliant on CJS, as CJS cannot require() an ESM module. While ESM enables tree-shaking, dual publishing is not primarily for extending tree-shaking benefits to CJS consumers; it's for CJS compatibility itself.

   Read the full bite: ESM vs. CJS: Navigating JavaScript's Module Divide

9. Question 9 of 30

   When would applying the Slot Pattern generally be considered an anti-pattern or lead to unnecessary complexity?

   • aWhen a component's visual wrapper and layout must remain consistent across all instances.
   • bTo enable developers to completely customize the styling and behavior of a component's core structure.
   • cFor container components that need to display a wide variety of internal content types.
   • dFor atomic UI elements like a basic button or icon that are meant to be fully encapsulated.
   Show the answer

   Answer: d · For atomic UI elements like a basic button or icon that are meant to be fully encapsulated.

   The card explicitly states to avoid slots for simple, atomic components like buttons or icons, as they are meant to be fully encapsulated and adding slots introduces unnecessary complexity. The Slot Pattern aims to provide content flexibility within a consistent structure, not to allow complete customization of the component's core structure itself.

   Read the full bite: The Slot Pattern: Making UI Components Composable

10. Question 10 of 30

    When pitching a design system to business-focused stakeholders, which approach best balances initial adoption tactics with Frost's warning about long-term organizational success?

    • aPiggyback the system onto an existing redesign, map consistency and reuse to time and money savings, and plan for ongoing collaboration
    • bSecure one-time executive approval by acquiring advanced tools that automate cross-browser testing and component documentation
    • cLaunch a standalone initiative funded by its own budget and lead stakeholder meetings with atomic design methodology
    • dFrame the pitch around component taxonomy and pattern library documentation to demonstrate design team technical sophistication
    Show the answer

    Answer: a · Piggyback the system onto an existing redesign, map consistency and reuse to time and money savings, and plan for ongoing collaboration

    Piggybacking onto an existing redesign and translating design benefits into financial outcomes aligns with Frost's method for securing buy-in, while planning for ongoing collaboration addresses his warning that design systems fail without sustained human effort. Option B is tempting because testing automation sounds like a business efficiency win, but it falls into the exact trap Frost identifies: treating technology, not people and ongoing collaboration, as the solution.

    Read the full bite: Pitching Design Systems with Business Value

11. Question 11 of 30

    What is the main benefit of using Storybook's autodocs feature in a component library?

    • aIt simplifies the manual creation of interactive component examples.
    • bIt ensures that component documentation remains synchronized with the actual codebase.
    • cIt automatically generates new component props based on usage patterns.
    • dIt provides a dedicated environment for writing unit tests for component logic.
    Show the answer

    Answer: b · It ensures that component documentation remains synchronized with the actual codebase.

    The card states autodocs ensures documentation "always reflects reality without tedious manual updates," directly addressing the problem of outdated documentation. While Storybook helps create interactive examples (Option A), autodocs' primary role is to generate documentation from code and stories, not to simplify the manual creation of examples themselves.

    Read the full bite: Automated Prop Docs with Storybook Autodocs

12. Question 12 of 30

    A development team is using Chromatic. Which of the following scenarios represents an inappropriate use of this tool?

    • aCatching visual regressions in a component library when updating third-party dependencies.
    • bEnsuring that a complex data transformation within a component correctly calculates and displays the final output.
    • cStreamlining the design review process by providing a visual history of UI changes for stakeholders.
    • dVerifying that a refactor of CSS styles doesn't introduce unintended visual side effects across components.
    Show the answer

    Answer: b · Ensuring that a complex data transformation within a component correctly calculates and displays the final output.

    Chromatic is designed to verify what the user sees, not the underlying data calculations or complex business logic. The card explicitly states it is not for testing data transformations. The other options are all appropriate uses of Chromatic as described in the card.

    Read the full bite: Chromatic: Visual Regression Testing for Components

13. Question 13 of 30

    What is the fundamental mechanism by which Token Studio ensures consistency between design and development teams?

    • aIt provides real-time synchronization of design changes directly into a live production environment.
    • bIt allows designers to directly apply platform-specific styling (like CSS or Swift) within the Figma interface.
    • cIt establishes a centralized, version-controlled database of design tokens that developers consume to generate code.
    • dIt automatically converts Figma components into production-ready code for various platforms.
    Show the answer

    Answer: c · It establishes a centralized, version-controlled database of design tokens that developers consume to generate code.

    Token Studio's core function is to act as a "database for your design system's atoms" that is "synced externally, typically to a Git repository" for developers to "consume... to generate code," creating a single source of truth. Distractor A is incorrect because Token Studio manages design tokens, not full Figma components, and the code generation is a separate step by developers.

    Read the full bite: Token Studio: Bridge Figma Designs to Production Code

14. Question 14 of 30

    Under what specific condition is applying "forced-color-adjust: none" to an element considered an acceptable practice?

    • aTo disable Forced Colors Mode entirely for a specific section of the webpage.
    • bTo preserve the visual integrity of interactive components like buttons and form fields.
    • cWhen the element's original color palette already satisfies WCAG contrast guidelines.
    • dFor purely decorative elements that become unreadable when their colors are automatically overridden, provided they convey no essential information.
    Show the answer

    Answer: d · For purely decorative elements that become unreadable when their colors are automatically overridden, provided they convey no essential information.

    The card states that "forced-color-adjust: none" should be used sparingly, specifically for purely decorative elements that become unreadable when their colors are flattened, provided they convey no essential information. It explicitly warns against using it on crucial interactive or informational elements, as this can render them unusable for users who rely on Forced Colors Mode.

    Read the full bite: Forced Colors Mode: When the User Overrides Your Palette

15. Question 15 of 30

    What unique benefit does Accessibility E2E testing offer compared to static code analysis for accessibility?

    • aIt replaces the need for manual accessibility audits by human testers.
    • bIt guarantees 100% compliance with accessibility standards across all user flows.
    • cIt is primarily designed to check for logical content order and confusing link text.
    • dIt identifies issues that only become apparent when a user interacts with the live, rendered application.
    Show the answer

    Answer: d · It identifies issues that only become apparent when a user interacts with the live, rendered application.

    Accessibility E2E testing is crucial because it catches issues that only manifest during user interaction with a live application, unlike static analysis. However, it is not a complete solution and cannot replace manual testing, as automated tools are fundamentally limited and miss issues requiring human judgment.

    Read the full bite: Accessibility E2E Testing: Automating User Journeys

16. Question 16 of 30

    When utilizing an Accessibility Conformance Report (ACR) for product evaluation, what is its fundamental characteristic?

    • aIt is a detailed, self-reported statement on a product's conformance to accessibility standards.
    • bIt provides a simple pass/fail grade, simplifying procurement decisions.
    • cIt is a third-party certification guaranteeing perfect accessibility compliance.
    • dIt represents the blank template vendors use to document their accessibility features.
    Show the answer

    Answer: a · It is a detailed, self-reported statement on a product's conformance to accessibility standards.

    An ACR is a detailed, line-by-line, self-reported statement of how a product conforms to specific accessibility standards, acting as a 'nutrition label' for accessibility. It is explicitly stated not to be a simple pass/fail grade or a third-party certification.

    Read the full bite: VPAT vs. ACR: The Nutrition Label for Accessibility

17. Question 17 of 30

    What is the primary purpose of establishing design system governance as an organization and its products scale?

    • aTo formalize the process for managing contributions and maintaining consistency across a growing number of teams and products.
    • bTo allow individual product teams complete autonomy in customizing UI components for their specific needs.
    • cTo ensure that all UI components are developed by a single, centralized design team.
    • dTo eliminate the need for design reviews by pre-approving all component usage.
    Show the answer

    Answer: a · To formalize the process for managing contributions and maintaining consistency across a growing number of teams and products.

    Design system governance is designed to manage contributions and maintain consistency as teams and products scale, preventing UI drift through formal processes for change. It explicitly aims to prevent individual teams from creating custom component versions that fragment the user experience, contradicting the idea of complete autonomy.

    Read the full bite: Design System Governance: Preventing UI Drift

18. Question 18 of 30

    What is the primary reason a large open-source project would require a Contributor License Agreement (CLA)?

    • aTo guarantee the project owner has clear, perpetual legal rights to all contributed code for future actions like re-licensing.
    • bTo specify the open-source license under which the project's software is distributed to end-users.
    • cTo shield individual contributors from any legal responsibility for bugs or security vulnerabilities in their code.
    • dTo provide a standardized method for contributors to claim intellectual property ownership of their submitted work.
    Show the answer

    Answer: a · To guarantee the project owner has clear, perpetual legal rights to all contributed code for future actions like re-licensing.

    A CLA's main purpose is to provide the project owner with clear, legal certainty over all contributions, enabling actions like re-licensing or commercial use without needing to track down every past contributor. It is distinct from the project's own distribution license, which option B describes.

    Read the full bite: Contributor License Agreement (CLA): A Legal Pre-Nup for Code

19. Question 19 of 30

    What is the immediate legal implication if a design system is published publicly without an explicit open-source license?

    • aIt can be freely used and modified, but any derived works must also be open source.
    • bIt is automatically considered public domain, allowing unrestricted use.
    • cAll rights are reserved by the copyright holder, legally preventing others from using or modifying it without explicit permission.
    • dIts use is restricted to non-commercial projects only, requiring a separate agreement for commercial use.
    Show the answer

    Answer: c · All rights are reserved by the copyright holder, legally preventing others from using or modifying it without explicit permission.

    The card explicitly states that copyright law automatically grants creators exclusive rights, meaning that without an open-source license, the work defaults to 'all rights reserved' and legally cannot be used by others. Options A, B, and D describe scenarios that are either incorrect legal defaults or specific conditions of certain open-source licenses, not the absence of one.

    Read the full bite: Licensing Your Open Source Design System

20. Question 20 of 30

    What is the most significant risk when applying gamification to a design system?

    • aIt is ineffective for design systems that are still in their early stages of development.
    • bIt risks encouraging low-quality contributions as users prioritize scoring points on leaderboards.
    • cIt can alienate developers who prefer intrinsic motivation over external rewards.
    • dIt necessitates a culture that is already highly competitive and open to public ranking.
    Show the answer

    Answer: b · It risks encouraging low-quality contributions as users prioritize scoring points on leaderboards.

    The card explicitly states that the 'biggest danger' is replacing intrinsic motivation with extrinsic motivation, leading to 'low-quality contributions just to score on a leaderboard.' Option B directly captures this primary risk. While option C is related to cultural fit, it doesn't describe the ultimate negative outcome as precisely as B does.

    Read the full bite: Gamification for Design System Engagement

21. Question 21 of 30

    What core capability distinguishes a codemod from a simple text-based find-and-replace operation?

    • aIt automatically resolves all compilation errors after a refactoring.
    • bIt is designed to perform complex logical refactoring that requires deep architectural understanding.
    • cIt operates on an Abstract Syntax Tree (AST), allowing for context-aware, structural code modifications.
    • dIt eliminates the need for human review by guaranteeing bug-free code transformations.
    Show the answer

    Answer: c · It operates on an Abstract Syntax Tree (AST), allowing for context-aware, structural code modifications.

    The card explains that a codemod's primary distinction is its use of an AST to understand code structure, enabling precise, context-aware changes. It explicitly states codemods are not for complex logical refactoring and do not eliminate the need for human review.

    Read the full bite: Codemods: Automate Design System Upgrades

22. Question 22 of 30

    When is a full Cost-Benefit Analysis (CBA) most appropriate for a design system?

    • aDeciding to build a new, shared component that multiple teams will use
    • bChoosing between two visually similar icon sets for consistency
    • cConducting a quarterly review of component usage metrics
    • dFixing a minor bug in an existing component's styling
    Show the answer

    Answer: a · Deciding to build a new, shared component that multiple teams will use

    The card states that CBA is for major investment decisions, such as adding a resource-intensive feature or building a new shared component, as illustrated by the DataTable example. Minor fixes, aesthetic choices, or routine monitoring (options B, C, D) are explicitly mentioned as scenarios where a full CBA would be overkill.

    Read the full bite: Justifying a Design System with Cost-Benefit Analysis

23. Question 23 of 30

    What is the primary objective of calculating Return on Investment (ROI) for a design system?

    • aTo ensure the design system's components are reusable across all product teams.
    • bTo establish a clear timeline for the development and rollout of the design system.
    • cTo benchmark the design system's performance against competitors' design systems.
    • dTo translate abstract benefits like consistency and efficiency into a financial argument for leadership.
    Show the answer

    Answer: d · To translate abstract benefits like consistency and efficiency into a financial argument for leadership.

    The card states that an ROI calculation exists to "translate the abstract benefits of a design system—like consistency and efficiency—into a concrete financial argument that management can understand and approve." This directly aligns with option D. Option A describes a benefit of a design system, not the purpose of its ROI calculation.

    Read the full bite: Calculating Design System ROI

24. Question 24 of 30

    What specific aspect of the software delivery process does "Lead Time for Changes" primarily measure?

    • aThe time elapsed between a code commit and that specific code running successfully in production.
    • bThe total time from a customer's initial request for a feature until it is live in production.
    • cThe time spent by a team actively coding and testing a feature before it is ready for deployment.
    • dThe duration from when a developer starts working on a task until it is released to users.
    Show the answer

    Answer: a · The time elapsed between a code commit and that specific code running successfully in production.

    Lead Time for Changes specifically measures the duration from a code commit to its deployment in production. Option B describes the broader 'Lead Time' from idea to delivery, which the card explicitly differentiates from this metric.

    Read the full bite: Lead Time for Changes: From Commit to Production

25. Question 25 of 30

    What is the main purpose of employing deprecation telemetry in a design system?

    • aTo identify all consumers of a component before it is removed or significantly altered.
    • bTo determine which new components should be prioritized for development.
    • cTo automatically delete components that are no longer in use.
    • dTo track the performance and accessibility of existing components.
    Show the answer

    Answer: a · To identify all consumers of a component before it is removed or significantly altered.

    Deprecation telemetry's core purpose is to gather data on component usage to understand who relies on it, enabling safe and data-driven planning for removal or significant changes. It does not automatically delete components, nor is it primarily concerned with performance, accessibility, or prioritizing new component development.

    Read the full bite: Deprecation Telemetry: Data-Driven Component Removal

26. Question 26 of 30

    A company is deploying a new, critical financial application where stability and security are paramount. Which software release strategy is most appropriate?

    • aImplement a continuous delivery pipeline to always run the absolute newest version available.
    • bChoose a Long-Term Support (LTS) release to ensure predictable maintenance and critical security updates over many years.
    • cSelect a version that is still in its "Current" phase to get early access to upcoming features and provide feedback.
    • dOpt for the latest non-LTS release to benefit from the newest features and performance improvements.
    Show the answer

    Answer: b · Choose a Long-Term Support (LTS) release to ensure predictable maintenance and critical security updates over many years.

    LTS releases are specifically designed for production systems requiring maximum stability, security, and predictability, trading new features for long-term critical bug fixes and security patches. The latest non-LTS releases, continuous delivery of the newest versions, or 'Current' phases introduce too much risk and flux for critical financial applications.

    Read the full bite: Long-Term Support (LTS): Stability Over New Features

27. Question 27 of 30

    When would a design system team most likely opt for individual component versioning over whole library versioning?

    • aWhen the design system needs to be tightly coupled and synchronized with external design tools.
    • bWhen system-wide consistency and guaranteed component compatibility are paramount.
    • cWhen different product teams require maximum autonomy to update only the specific components they use.
    • dWhen the primary goal is to simplify dependency management and reduce application bundle size.
    Show the answer

    Answer: c · When different product teams require maximum autonomy to update only the specific components they use.

    Individual component versioning is favored when team autonomy is the highest priority, allowing teams to update specific components on their own schedule. Option D is incorrect because individual versioning can actually lead to dependency bloat and increased bundle size due to multiple versions of the same component.

    Read the full bite: Design System Versioning: One Package or Many?

28. Question 28 of 30

    For which scenario is using a data-* attribute the most appropriate solution?

    • aTo pass data exclusively between JavaScript functions without any visual impact.
    • bTo provide content that should be indexed by search engines for improved discoverability.
    • cTo enable CSS to apply styles conditionally based on an element's current state.
    • dTo store complex JSON objects directly within an HTML element for JavaScript consumption.
    Show the answer

    Answer: c · To enable CSS to apply styles conditionally based on an element's current state.

    The card states that data-* attributes are perfect for managing component-level state that CSS needs to know about, creating a clean bridge between JavaScript logic and CSS presentation. Storing complex data, providing content for search engines, or passing data only for JavaScript are explicitly mentioned as scenarios where data-* attributes should not be used.

    Read the full bite: Theming with CSS data-* Attributes

29. Question 29 of 30

    Which mechanism primarily enables Jetpack Compose's declarative, hierarchical, and swappable theming system?

    • aGlobal singleton objects that hold the current theme's design values.
    • bCompositionLocal implicitly providing design tokens down the UI tree.
    • cDynamic loading of external XML style resources at runtime.
    • dExplicit parameter passing for every design token in each composable.
    Show the answer

    Answer: b · CompositionLocal implicitly providing design tokens down the UI tree.

    CompositionLocal is the core mechanism that allows theme values to be implicitly passed down the composable tree, acting as a dependency injection system for design tokens. This enables hierarchical overrides and easy theme swapping, unlike global singletons which lack hierarchical scoping, or explicit parameter passing which is cumbersome.

    Read the full bite: Jetpack Compose Theming for Design Systems

30. Question 30 of 30

    Which scenario best illustrates the core benefit of implementing SwiftUI Theming with the Environment?

    • aFacilitating complex data binding and state management across different view hierarchies.
    • bProviding a secure mechanism for passing sensitive user preferences throughout the app.
    • cOptimizing the rendering performance of deeply nested custom views.
    • dEnabling an entire application's visual appearance to be dynamically updated from a single source.
    Show the answer

    Answer: d · Enabling an entire application's visual appearance to be dynamically updated from a single source.

    The card states that theming allows "an entire app's look and feel to change by swapping out a single 'theme' object," which directly aligns with dynamically updating appearance from a single source. While the Environment can pass data, its core benefit for theming is about centralized style management, not general data binding or performance optimization.

    Read the full bite: SwiftUI Theming with the Environment