ClickorKeyboard shortcut Alt + L

Dragto resize

Nord Design System SearchDeveloperDeveloperGetting startedUsing Web ComponentsWebfontsCDNLocalizationCSS Framework Legacy ESLint PluginWorking with AIFAQDesignDesignGetting startedFoundationsAccessibilityColor SystemColor UtilitiesPrinciplesFigma ToolkitGridIconographyNamingNordhealth BrandTypographyThemesBrand assetsToolsComponentsComponentsAccordion New Aside New Autocomplete New AvatarBadgeBanner Updated ButtonButton GroupCalendar Updated Card Updated Chart New Checkbox Updated Collapsible New Combobox New Command MenuData Table New Date Picker Updated Date Range Picker New DividerDrawer Updated DropdownEmpty StateField New FieldsetFilter Bar New FooterHeaderIconInput Updated Input Group New Item New Kbd New LayoutMessageMeter New Modal Updated NavigationNotificationNumber Field New Otp Field New Outline New Overflow List New Pagination New Popout Updated ProgressProgress BarQrcodeRadio Updated Range Updated Resizable New Rich Text Editor New Scroll Area New Segmented ControlSelect Updated SkeletonSpinnerStackTabTableTagTextarea Updated Time Picker New Timestamp New ToastToggle Updated TooltipTop BarTruncate New Visually HiddenDesign TokensDesign TokensTailwind CSSTailwind CSSBlocksBlocksTemplatesTemplatesIconsIconsPlaygroundPlaygroundLatest UpdatesLatest UpdatesChangelogChangelogMigration guidesMigration guides
GitHub

Clickto expandKeyboard shortcut Alt + L

Backlog Prioritization

Nord’s backlog prioritization model helps us govern incoming feature requests from multiple sources such as product teams, sales, the QA team, and customer support.

Who creates the backlog?

Our Product Manager is responsible for creating, prioritizing, and maintaining the Nord Design System’s backlog. Requests for backlog items come from various sources such as product teams, sales, the QA team, and customer support.

Who prioritizes the backlog?

Product Manager prioritizes our backlog and defines the design system direction. We try to usually find a consensus among stakeholders with conflicting requests.

How do we prioritize the backlog?

We start by deciding what features aren’t critical. Putting low-priority features aside allows us to spend the design system team’s valuable time on higher-priority features.

Once this is done, we utilize the Impact Effort Matrix seen below. Features that require the lowest effort for the highest impact go to the top of our backlog, and items that require greater effort but will have a low impact go to the bottom of the list.

Nord Design System Impact Effort Matrix

Getting support

Have a question about how we prioritize features? Please head over to the Support page for more guidelines and ways to contact us.