TakeAway - Design System Conversation

image

Approach to the challenge

Challenge

My Applicable Experience

📐
Design System Buy-in

Design Feedbacks ≠ Reviews ≠ Critiques

Why → Who → What

Who are going to reach out? Why?

What is the value of this person in the room?

Who's the decision maker in providing insights?

What setup is worth it for the feedback we expect to have?

Actionable Questions

1. What are your overall impressions?

2. What do you like about this?

3. What could be better?

4. What problems do you foresee?

5. Any questions for me?

Ideal Response

  1. Identify the problem
  2. Describe the solution
  3. Empathise with the users
  4. Appeal to the business
  5. Lock in Agreement

Reference Open Source Site

Driving Adaptation

Communicating Change

Advocacy

Contribution

Hiring and mentoring experience to give back

My principles

  • Start with the problem
  • We deeply understand the customer problem, their goals and worlds. It is our foundation for action and, ultimately, she is our only judger for success.

  • Outcome over output
  • We measure the quality of our work by the outcome, a behavioural or emotional change, it is creating with our customers. We care for our work until and after it reaches the hands of our customers.

  • Think big, act small
  • We set a clear, ambitious vision, and take baby steps to get there. We don’t settle for band-aids, yet act small to enable faster learning and value creation.

  • Diversity of minds
  • We drive collaboration and diversity from the first moment, so that we enable the best insights and ideas to come to the surface. Share early and often, iterate and feedback, is the past to great work.

  • Continuous learning and growing
  • Just as design is never finished, so are we not as human beings nor as a team. We encourage learning and helping each other grow, so that we do better.

Outcomes-Based Planning
We think we can increase the rate of early meetings with [this idea] measured by X, and with [other idea] measured by Y
  • Create a customer journey map with designers
  • Review with the magic question that encourage behaviours
  • “What behaviours at each step predict success and satisfaction? And what behaviours at each step predict failure and dissatisfaction?”
Product Design Improvement
  1. I'm going to try to understand the business situation and our objective in more details.
  2. I will focus on defining the target user and brainstorming what problems we could solve for them.
  3. I will generate solutions for these problems, prioritize them, and make a recommendation.
  • Business objective
  • User problems
    • Select a user type
    • List user problems
    • Prioritise user problems
  • Solutions
    • List solutions
    • Prioritize solutions
    • Summarize
  • Recap

Business 1-o-1 Strategy
  • Set a business objective: You should start by making sure you understand the question properly and by defining a specific strategic objective with your interviewer
    • Confirm your understanding
    • Define the business objective
  • Generate solutions: Once you know what the objective is, it’s time to generate a structured list of solutions to solve the strategic problem you face
    • Create a structure
    • Generate solutions within that structure
  • Discuss solutions: After generating solutions, a discussion will naturally follow with your interviewer around the trade-offs and priorities of different solutions
    • Highlighting trade-offs
    • Prioritizing as necessary
  • Conclude: Finally, you should conclude the discussion by making a recommendation and answering the initial question you were asked
    • Make a recommendation
    • Highlight risks and next steps
Managing stakeholder

They will still need for work at a certain date. How do we set expectations?

Stop working on something when we’ve made enough progress to feel satisfied.

When will we be satisfied?

Get an agreement on a direction and then commit to reviewing the performance for a series of months.

Hypothesis and measures success before start on an effort.

Design System

How would you document updates to our Design System?

  • Write guidelines that act as a source of truth, or reference material.
  • When, where, why, and how do you use it?”
  • Document and/or demonstrate any functionality, animation, or conditional logic.
  • Lead by example and show example use cases.
  • Include as much detail as is appropriate, code included.

What to expect

You will get the role. What will you practically do next?

  • Research and discover new and improved ways to manage and maintain the system — whether it’s technology, processes, or design tools that could help the team.
  • Establish design system processe and ensure that any processes for updates and maintenance are upheld.
  • Run usability testing and internal surveys to educate designers on system design best practices
  • Promote and seek opportunities for designers and developers to work together.
  • Keep everyone up-to-date and engaged with the system.
  • Find and discover new ways of improving users, teams and business objectives
  • Deal with any resistance to the system, guiding with an example-approach

Ensuring quality of delivering across:

  • Content -- The language to design a more thoughtful product experience.
  • Design -- The visual elements of the brand inside the design system
  • Components -- The building blocks for developing new products and features.
  • Patterns -- The individual pieces for creating meaningful product experiences.

Design System Workflow

image

Arguments

Eng. Topics

📌
Design Tokens
🥅
Context - Shared Variables Dilemma
🙂
User-friendly documentation for your component library with Storybook

Resources, Community, Inspiration:

Design System Designer Freelancer Notion Ambassador