Aug 10, 2020

Design systems' area of influence: Service (3/3)

After system users start to use the offering, new challenges and tension will occur.

The design systems team will soon realize they need to help system users how to report issues, support the team when there is new need or question, and maintain the system.

While maintaining the system, more questions will come to mind: What should we do when the product teams found the border color is not accessible for customers? What if product teams need to request icon in a hurry? What if product teams need a pie chart that haven’t on the library? Can product teams make new components? How do we handle all of these challenges? The scenario will vary depends on how the team works in the company. The maturity of design systems can be valued based on how well the team designing this experience.

Identity, offering, and service: These are the three area for design systems team will need to influence directly to support product teams to build experience in a more efficient manner. If design systems lack in one of these three, it can cost issues.

2020

2019

2018

2020

Sep 30

When was the last time you reflect?

Sep 29

Methods are tools

Sep 24

How can I get a bigger project?

Sep 23

Entering product design – Chapter 7: Craft and analysis

Sep 22

Entering product design – Chapter 6: Narrow collaborator

Sep 21

Entering product design – Chapter 5: Soloist product designers

Sep 17

Entering product design – Chapter 4: Product designer key skill areas

Sep 14

Entering product design – Chapter 3: Misunderstanding of business

Sep 11

Entering product design – Chapter 2: Principles over steps

Sep 10

Entering product design – Chapter 1: Silver bullet

Sep 10

Entering product design – Overview

Sep 04

SAR: A framework for concise storytelling

Aug 27

Start your design with outcome

Aug 24

New medium post: Collaboration ground for design systems

Aug 17

Action points

Aug 13

Pulse check: Listen to your team

Aug 11

You should actively apply for a new job

Aug 10

Design systems' area of influence: Service (3/3)

Aug 04

Design systems' area of influence: Offering (2/3)

Aug 03

Design systems' area of influence: Identity (1/3)

Aug 01

My mom ran me to the hospital

Jul 29

Reader question: Do we need to build MVP for every product?

Jul 27

Reader question: Do I need formal design education?

Jul 24

Recognize assumptions

Jul 21

Sandbox for your personal growth

Jul 20

Start your week with questions

Jul 17

Specificity in feedback

Jul 15

Don't sell the design. Sell the business impact

Jul 14

Overwhelming inspiration

Jul 13

The framing trap

Jul 10

Everyone vs. Specific

Jul 09

The blind horse designer

Jul 08

Set the context in your meeting

Jul 07

Let's just try and see what happens

Jul 06

Managing expectation

Jul 05

Low UX maturity company

Jun 17

A simple exercise for career reflection

May 31

The “Coach sheet” – A paper-based system for people management

May 26

Bring calm to your remote team

Feb 13

Workshops can be more efficient than meetings

Feb 07

3 questions designers should be asking

Feb 06

Walking 1on1: A refreshing way to connect

2019

Nov 21

My hope for stubborn 'Innovators'

Jul 18

Five simple actions to help you gain more time

Apr 23

Evolving Product Experience Principles at Bukalapak

Mar 09

A framework to give better design feedback: Analyze, Discuss, Suggest

Jan 28

Making a decision is hard, here's my rule of thumb

2018

Dec 04

Essential skills for Product Designers

Nov 16

Quick life update

Nov 06

Things I learned from working at Shopify

Oct 15

About design critique

Sep 17

Common icon design problems you should avoid

Sep 06

Preface: Welcome to yellowstroke.com