forge-icon-only
homeHomeforward Get started As a designerDesign to Dev Handoffborder_outer Foundation OverviewAccessibilityBrandingColorData formatsIconographyIllustration: UsageIllustration: LibraryThemingLayout: IntroLayout: GridLayout: SpacingLayout: Page layoutsTypographyProduct analytics - coming soonac_unit Patterns Data visualization: IntroData visualization: ChartsData visualization: ColorsDrag and dropEmpty stateErrorsFaceted filteringFormsLoginMapping & GISNavigationOnboarding - in progressProfile - in progressProgress & loadingsettings_input_component Components AccordionApp launcherAvatarBadge - Coming soonButtonsCardChipsDate picker - coming soonDialogExpansion panelFloating Action ButtonListNavigation drawerOmnibarProgress indicatorsSelection controlsSlidersStepper - coming soonTableTabsToastToolbar - coming soonTooltipphone_iphone Native mobile Basic requirementsFrameworksDesign patternspan_toolFeedback & supporttrending_upStatushelpFAQs

Get started with Forge

The more Tyler Forge is used, the better it will become as it grows and evolves with community contributions and a wider variety of problems to solve. 

forge-getting started-spot hero

Adoption models

Adoption of Forge can vary by product team, depending on product lifecycle stage and roadmap.

Adoption can can range from full adoption – in which a product replaces its existing visual style with Forge’s style and the accompanying web components – to a more incremental approach where a team gradually adopts features over time.

Teams using a more incremental approach can use the following stages to guide their adoption:

0

Non-adopter

Dated visual identity, not complying with the design system

1

Dependency & Plan

Product has groomed work to demonstrate timing and commitment for Forge adoption. Product team works with Forge team.

2

Core Components

Product uses the design system components for new projects relevant to their needs. Product team works with the Forge team. No more than 9 months behind each major Forge release.

3

Full Adoption

Product uses only design system components for new projects relevant to their needs. Product team works with the Forge team and contributes to Forge. No more than 3 months behind latest minor Forge release.

Get started with Forge

Ready to start adopting Forge, but not sure where to start? The Tyler UX team offers the following services and trainings to help your team get started with Tyler Forge and user-centered design.
insert_invitationJUMP START

For Tyler product teams with minimal to no experience with user-centered design, TUX offers a 1-2 day Jump Start workshop to actively work with a team to build out a basic skill set and supporting artifacts. Jump Start fits into the Scrum development methodology and is our recommended development approach. Jump Start facilitators will work with your team onsite in this hands-on training.

Contact Kathy Wolf for more information.

assignmentDesign audit
For Tyler teams looking to adopt Forge or to contribute web components back to the design system, the Forge team offers a half day engagement to review an existing application, product, or feature, and provide UX recommendations for services that offer the greatest value-add to app team, based on tech stack, maturity model, and delivery timeline.

Contact Kathy Wolf for more information.

fastfoodLunch and learn
For Tyler teams looking to learn more about the Forge design system and accompanying TCW Component library, a one hour lunch and learn provides a hands-on demonstration of the full system, with time for specific questions.

Contact Kathy Wolf for more information.

Get started with UX

Interested in getting involved with UX for the first time, or upping your engagement with UX? Contact Kathy Wolf or request a specific level of involvement below.

Levels of UX involvement

Ad hoc engagement

Point of contact

Involvement
One or more UX members provides limited, ad hoc guidance and best practices for a team.
Scope
Product direction is largely defined, so small enhancements only (icon requests, visual hierarchy, adherence to Material styling, etc.)
Deliverables
UX questions, Application consistency, program flow, Forge patterns.
Lead time
1-2 full sprints
Request Point of Contact

Occasional interactions

Consulting

Involvement
One or more UX members consult on select key projects or initiatives for a team.
Scope
Product direction is largely defined, small enhancements only (icon requests, visual hierarchy, adherence to Material styling, etc.).
Deliverables
‘Point of contact’ plus: User research, application layout, low fidelity prototypes.
Lead time
1-2 full sprints
Request Consulting

Regular interactions

Enagaged

Involvement
UX member maintains regular cadence with team (all projects, key meetings, sprint reviews).
Scope
Product direction is open to guidance and facilitation from UX. Product team can commit to medium enhancements to UI, app structure, app organization, and product direction.
Deliverables
‘Consulting’ plus: UX proposed timeline, story mapping, medium fidelity prototypes, user testing / recommendations, multiple prototype iterations.
Lead time
2-3 full sprints
Request Engaged

Dedicated designer / researcher

Embedded

Involvement
Embedded UX designer and / or researcher who remain consistent and in sync with the UX team.
Scope
Investment project, major rewrite of existing project, or new product design. UX is tightly involved in product strategy and direction, user flows, and app look and feel.
Deliverables
‘Engaged’ plus: Full UX involvement (project start to finish), multiple user tests, high fidelity prototypes, unlimited design iterations, UX review.
Lead time
3-4 full sprints
Request Embedded

What UX can do for you

Based on your user and business needs, the UX team will draw from some or all of the following data driven methods as part of a user-centered process.

UX Research

Uses client feedback, modeling, and usability testing to better understand user behavior and provide data driven recommendations for online experiences.

A UX Researcher may

  • Attend product team meetings
  • Provide product strategy
  • Perform user surveys
  • Complete competitive analysis
  • Conduct field studies
  • Provide contextual analysis
  • Create user journey map
  • Define service blueprint
  • Facilitate storyboarding
  • Develop ecosystem map
  • Build affinity diagram
  • Create personas
  • Provide mental model/story map
  • Create empathy map
  • Facilitate informational interviews – remote or onsite
  • Recruit test participants
  • Co-design user tasks with product team – user tasks test scripts
  • Use UX designer’s prototype or development application for user testing
  • Moderate remote testing
  • Record/save user testing sessions
  • Involve stakeholders in UX research (interviews, surveys, user testing, etc.)
  • Analyze user testing data
  • Provide research findings recommendations, document and videos
  • Present/report user testing recommendations

UX Design

Creates conceptual mockups, flows, and site organizations informed by user behavior to guide user centric applications.

A UX Designer may

  • Attend product team meetings
  • Create proposed UX timeline
  • Set usability goals
  • Provide effective and frequent communication with the product team
  • Design flowcharts
  • Define user flow
  • Create system diagram
  • Provide sitemap
  • Create sketches
  • Develop wireframes
  • Design Iterative prototypes (low to high fidelity)
  • Provide guidance on symbology
  • Provide iconography
  • Create data visualization
  • Use interaction design
  • Provide guidance on compliance with WCAG 2.1 and Section 508 ADA Guidelines
  • Participate in user testing (Note taking &/or Subject Matter Expert)
  • Provide design iterations
  • Use version control
  • Provide guidance with style guide/pattern library
Contact

Contact the Tyler Forge Team

Provide Feedback

Request a new component

Timeline & Resources

Forge release schedule

Download our design and development resources

Last modified on October 28, 2019 by: Nick Andrews
Table of contents