top of page

下書き

 

We needed to find ways to explore using the existing module email teams have.

 

Dev at DEPT didn’t recommend stacking images + having them in different sizes. 

 

Also, the new grid proposed would break our system flow if we were implement the design i proposed. 

 

there could be ways to compromise, possibly with keeping the image sizes the same and keep the dynamic image stacking with the current grid system. <will discuss with email team again>

 

overall, the main takeaway was to keep it with what we currently have at the moment. 

 

 

Another project that I would appreciate a quick review from you on is the additional part of the Charity Donation project request.

 

Atul requested a redesign of the “Request item back” component on the ‘Accept with return-action’ page.

 

The scope is this : 

 

Currently, the UI/UX experience is not good and he wants to improve it.

 

For David G meeting next week, we will present both a cleaned-up version and an alternative design option. If he ask us to redo this component, then we show the the alternative design option.

 

The alternative design direction that I am proposing has simplified the section with fewer lines and less text, making it clearer and more concise.

 

____

 

According to the Right rail, as it is a common component, it all should look the same but I see different Typography depending on the products.

 

Please make sure using this spec on all products.

 

Regarding RR ui unification, is it OK to request the new photo size as 120X120 from !60X160 (Return). Due to the future plan to implement multiple item stacked images, it was necessary to reduce the size single photo size. Unauth is already implementing with this size.

 

Regarding 

Due to the future plan of implementing multiple item stacked photos, it was necessary to reduce the size of a single photo for Unauth case. I used 120X120 for single image and the page is already implementing. 

 

For RR UI unification, is it ok to request the new photo size as 120x120 instead of 160x160 (Return)  with the Donation project? As I requested to correct all the typography across the product, this is one additional thing that we can request dev to do if they have enough time to develop on this project.

 

If Chloe mentioned that there is no time for this change, then we can consider it for the next project.

  • we can put your mac into recovery mode2:25 PM
    Shaw, Lynne(AWF)

• I can send the recovery to slack-

For Apple Silicon MacBooks

 

  • Restart or power on your MacBook and then press and hold the power button until you see "Loading startup options."

  • Click on the "Options" icon and choose "Continue."

  • Under the list of users you can log into, click "Forgot all passwords?"

  • Enter the recovery key you obtained from Jamf in the provided field and click the "Next" button.

  • Once you unlock successfully, you will be asked if you want to reset your password. Click "Reset Password" to reset it. After doing so, you will be able to access the Utilities screen. If you don't need to use any of the utilities options, you can restart the computer and log into the device with the newly created password.

  • After resetting the password, if you get a prompt about the Keychain with options that include "Create New Keychain" and "Update Keychain Password". You will want to select "Create New Keychain" to continue.

  • Make sure the user logs into Global Protect and is signed into the Kerberos extension (the key symbol in the menu bar near the upper right). They may be prompted to sync their NT password and the new laptop login password.

WHAT YOU NEED TO DO

Please click on the link below to open Hub Services to check the status of the request and add comments (if applicable).  

 

View this ticket in Hub Services

TICKET DETAILS:

 

Status Update Notification:

Service Request REQ000004176582 status has been updated.

Hub Service  REQ000004176582

---

Sarah https://www.figma.com/design/EG7xtjSQzesTGyD3Dxpkh7/SIR-migration-to-Marko?node-id=38-25537

 

Emi you have scaled the new summary component and checked it for all flows (returns, cancel, etc), correct?

---
 

🚃 Other team:   Shipping label purchase page/ Happy path QR code

 

Happy path label & QR code exp

https://www.figma.com/design/VvGjIsG95lKvgZMGFaXjdY/QR-Code-Experience-Improvements?node-id=0-1&t=o8jRxpKingWu7ItQ-1

 

 

Jieun Yoon

 

We usually send QR code when sellers purchase shipping labels with the QR code label format.

03:10

Please find the shipping label email template here.

 

 

Refund

 

Provide clarity to sellers’ usable funds and charging methods

 

Increase the conversion rate of your funds

Increase comprehension and consistency across platforms

 

Reminder of funds sweep

 

Not aligning all products and experiences

 

 

Goal

 

To make refund summary more comprehensibe to users

 

THey are having troubles understanind everything and causing problems

 

Aligning all producs

 

Same layout for everything experineces

 

Exploring UI UX

 

What shoudl ht regund layout be ?go into what it is now

Explore what not working on regund now

Start with dWeb

Subtotal

Fee credit 

Subcharge- total

Breaking into 2 section to be more readable

Explore layout watch section where each section -left section

Sara  h

 

Explore having refund S here 

Explain what it is 

Fee fredit section— some extra creation on fee credit

---

  1. We finalized other products for our charity donation program and have now completed work on the dispute product as well 

 

  • What we did

 

Along with adding donation information to the pages, we also reviewed the pages to enhance the overall user experience. 

 

Additionally, we aligned the page design with that of other products.

 

  • highlighting some points, we added fee credit to the Accept page. It never show it in dispute (All other prod exceptind Dispute has been showing) now about this project ,we are planning to state.

 

  • Secondly, we made updates to the "Accept with Return Item" page to make the content clearer and more aligned.

 

We saw a lot of feedback from sellers that they are not happy with that kind of pages we have and try to get my item return and confidence- 

 

 

 

 

 

 

 

  • Point out some extra things we did.

    • Fee credit on Accept page- It never show it in dispute (All other prod exceptind Dispute has been showing) now about this project ,we are planning to state.

    • Accept with return use cases: We saw a lot of feedback from sellers that they are not happy with that kind of pages we have and try to get my item return and confidence- We decided to update that content a bit more clear and extra above beyond the look over this charity donation proj.

  • --

Ignite

Cancel

 

https://docs.google.com/document/d/1yTQJWJNzRuDHz9BAYsvGKeG5lR8n0H1yWFVCg2y1-OQ/edit?usp=sh                    aring

 

We’re looking for any current or past usage of the uploaded file thumbnail with the file name showing…

 

The image on the far right shows something in M2M. Is this still appropriate to use?

 

We have also mocked a version with the file name below. If we don’t have a DS thumbnail with a file name, would next steps be office hours and accessibility?

 

 

 

 

 

 

Rio Bell

  1 month ago

@srilmani

 

Kat Carboy

  30 days ago

Hi Rio! 

@Tinsley Ryan

 I believe we created a thumbnail, could you confirm? cc 

@Bascue Randy

 

Ryan Tinsley

  30 days ago

@Carboy Kat

 we created a thumbnail image for when an image isn't available/uploaded. Since this is uploading a specific file type that isn't a standard image, a new one may be helpful... (edited) 

 

1

 

 

 

Randy Bascue

  30 days ago

This would be a great one to standardize

 

1

 

 

 

Kat Carboy

  30 days ago

@Bell Rio

 in that case, sure, we would love for you to drop by office hours and share use cases that you know of so we can get started on this 

 

 

Ryan Tinsley

  30 days ago

Agreed! And also what the capabilities are... are we always able to pull in a preview, use cases to use a preview and/or an icon if there is an issues showing the preview, always defaulting to an icon, etc...

 

 

 

 

 

 

Carly Johnson

Can we ever align a toggle closer to the label? In the case I show below, the toggle seems a bit disconnected from the label since most things in the section are left aligned. When the toggle is right aligned it seems to me that the toggle looks like it is for the whole section (item tile and all), rather than instantly recognizable as belonging to the label.

 

 

Randy Bascue

  If you find it’s more successful for your users, then sure. We don’t have a strict rule on it being full width pinned to the right. We just recommend toggles sit to the right of the label in most cases.

 

 

Ryan Tinsley

 

And to build off of Randy's comment, if there are multiple rows of toggles we wouldn't want them to have different positions based on text length. If there is only one this can work, but multiples should be aligned on the right. (edited) 

​---

Page sheet(bottom drawerみたい VS formsheet (modalみたい) https://medium.com/@ryu1sazae/modal-presentation-in-ios-e1fa6d89df24

 

 

Page sheet is described as: Partially covers the underlying content on larger devices held in landscape orientation. All uncovered areas are dimmed to prevent interaction with them. Covers the entire screen on smaller devices and in portrait orientation.

And Form sheet as: Appears centered on screen, but may be repositioned if a keyboard is visible. All uncovered areas are dimmed to prevent interaction with them. May cover the entire screen on smaller devices.

What is the real difference in the look of these 2 forms?

I couldn't find the description of Form sheet in the developer docs. Only the page sheet (https://developer.apple.com/reference/uikit/uimodalpresentationstyle/1621358-pagesheet).

 

 

 

You likely have found the answer to this by now, but I wanted to make sure this question has an answer for everyone else who stumbles upon it.

 

 

Page Sheet

On regular-width, regular-height size class devices such as iPad, Page Sheet covers almost all vertical distance but does not go all the way to the top. Horizontally, space is left on both sides. An example of this is Apple's Mail application when composing a new email. Here's a simple screenshot from the simulator:

 

 

 

Form Sheet

A Form Sheet is similar to a Page Sheet except that it leaves even more space on each side and also leaves more space on both the top and bottom. The effect is basically a floating box:

---

Dispute meeting record Atul 

 

I wonder if there are any UX guidelines for the usage of checkboxes versus radio buttons in the case, selecting ‘yes’ on a radio or ‘checked’ on a checkbox shows optional information as an additional/supplemental detail.

If the checkbox is unselected, no extra information will be displayed, and the user can commit submission for the main purpose. 

 

Since this option is additional/supplemental to the main purpose of accepting a dispute and having the money taken from your account, and is optional, we are recommending the use of checkboxes as they better represent this scenario compared to radio buttons.

 

 

9/22

I am finishing up the charity donation mocks today and have a qq:

 

On the outcome page, there is an extension control located beneath the ‘Amount You Owed’ and the ‘Dispute Amount Recovered’ sections. After all the credits have been added below the dispute amount within the control, the disputed amount will be recovered in a separate section with a fully divided amount. In the ‘Dispute Amount Recovered’ section, the payment histories will be displayed.

 

It seems that having both sections in a single section without a full divider would result in a better UX experience. Then we can have the extension control for Fee credits details. Additionally, can the dispute history be relocated to the history drawer (maybe for the next project)?

 

 

 

7/28 exercise

 

 

Each different page, you can pull information from summary drawer into the body or put it back to the RR

 

separately deal other issue

Show all flows

 

First, talk about Unauth

Show anatomy of

 

Mark up 

 

post transaction page--go to the discussion

 

 

We’re deciding today how we’re gonna follow the rules

Anything is critical to taking the primary action is this page on the body. Anything that is secondary ire meaning to be reference, is in the drawer or in RR.

 

Question today is “What is absolutely exactly critical taking action and what is secondary or ref. something is not critical

 

Here is the pattern we need to follow. (Design end story)

<Need to be called out>

Point out this page that the issue here is that Dispute amount and Dispute reason and comment are on every other flow in the body during this point of flow.

 

<Sara wants us to step through each page in the flow> need to see how things will moved around based on what might be point of action

 

These things are all relevant to the current action at hands and on every other flow we put the information into the body because of that . The relevant to the curent action at hands is in the body. That is the pattern we follow every single other flow. 

 

Historically these things are put in the body. Dispute flow is going against the historical decision about where information goes because of point of action (by product decision)

 

This is one point that we need to highlight. We decided these are primary piece of information on ever single other product, so we put in the body and we are tying to follow.

 

It is directly relevant to the main action ,it should go in the body. If the information is for reference and not directly affecting the main action, it goes to RR or summary drawer.

 

————

 

Item tile in Right rail

Multiple orders Payment side needs a lot of changes (2-3 yrs from now)

 

Modal- Entire list of items

 

One image+ 3

 

 

————

 

 

dWeb - move item tile into the right rail

mWeb - create an order tile (you can reference the order tile at the top of Returns for styling)

Both: the "+3 items" should be a link that opens the full list of items

—————————————

 

Mobile : don’t have right rail, 

 

Single item of dispute= Item tile on mobile , today, we have it above the history sec right rail 

Where should it appear on mobile, 

 

———

Mobile

It makes sense to have the Items in a body. 

 

These are items that you are refunding, show you individual pricing. We already have order #tile on top. We can utilize that Dispute to … this is what we do on return. We have the tile on top .. kind of more reference , way finding … type of things. 

 

Having Variation

Cancel having in the body section is valid . Make sense. 

 

possibly put dispute but 

 

Dispute is more informational. Not in body section may not be contextual

 

What Dispute do is, different treatment

 

1  possibility is     Should we show it in item tile?

 

Order level tile is putting in the right rail. Might actually best place for it?

 

having order tile at the top of the flows. So 

 

 

Mobile- in the past, other flow, added an order tile or item tile on the top of flow.

 

What tile works for Dispute?

 

<Sonny> Items or order info taking out of drawers in order not to be hidden in drawers. For most relevant information

 

<Atul> Item tile on right rail, amount, reason… for the event. Implemented mock- top body section, summary, keep in collapse  summary section

 

Bottom section- which items .. user ask questions

 

That solves question.

 

We don’t need to level

 

Align the direction … 

 

Summary

 

 

Change it to consistent

 

Atul’s concern…

 

Refine those… Implement all together.

 

Edits - how it affects all flows.

 

Workshop time. For solution. 

 

  • Atul’s Summarize-

 

We like the concept of the Item tile- you’re going to pick item from the summary section so it is not in the page , not in the collapsible module. We will show the item, on the right rail along with the +3 more link on dWeb

 

mWeb

 

Show the item on the item tile on the top of the page. Along with the sum dispute amount, comments (important) , 

Dispute 

 

Sara’s sign off

 

Next Wed. Final sign up

 

 

 

Not in collapsible module

 

 

Atul

 

When a buyer opens a dispute with their payment institution (for example, their credit card provider or PayPal), the payment institution will inform eBay of the dispute and initiate a process to resolve the dispute with the buyer. 

 

eBay will collect information about the transaction and help the seller build evidence to defend the dispute.

 

The final outcome of the dispute is decided by the payment institution. 

 

However, the seller may be eligible for payment dispute seller protections by eBay. For details on how these protections work – which transactions are eligible or excluded, and what sellers need to do 

 

 

___

 

I just wanted to align with you regarding the Dispute (new) layout. 

 

Rio introduced a new layout and using the wider right rail and narrower left contents format. I saw your mocks are based on Rio’s new layout but the 

 

Rio’s new dispute design is using a different (new) layout from other products which has wider right rail and narrower left contents and your mocks are based on the new layout. Her comp is 

 

I designed the complex cases for the summary page with the other layout and designing the simplest unauth case with the new layout (with narrower left contents). I will adjust the complex content case with the same format right now to see if it works the same with this unauth dispute simple case.     But I saw your mocks does use 

--​

Gandhi meeting +3 more item

 

The design style used at the top of mobile screens is called an ‘Item Tile’. We have used this tile in refund flows and some other flows (i.e. returns flow).

 

 

We have only applied treatment at the item level products, so we need to work on applying the same treatment for the order level products.

 

the General goal of this would be to achieve parity between the flows to use this item tile as a way finding component to provide a bit more info on mweb across all products 

 

We updated the UI a bit with the gray background element. Ideally, we d like to achieve parity with the styling with UI for all the products with this item tile

 

As an idea to get party across all of our products with this item tile in refund flows and others

 

 

  • Remove Item ID

  • To consistent across all protection products

 

Carly is working on the New cancel/ SIR flows with this new component item tile design (in order level product)

 

Order level item tile design

Work for Cancel/SIR flows.

 

Cancel- no need Item ID

 

_________

 

Sonny shows his perspective

Understand +3 items, + 1 item potential mislead

Sonny -product perspective

Potential confusion of total item number

 

See all items, see more items and readdress this issue

 

Or move to more Text base idea or to use clear language 

 

Carly

Background/history of the content “+1 item”" +3 items”…

 

We do have an order level summary that includes stock photos for orders with more than one item in VOD. They use +1, +2… terminology and we are making our content more consistent with that.

 

We also went through design reviews with approvals up to Brian S for the +1, +2 items.

 

 

We do have an order level summary has stock photo more than one item in VOD . They use +1, +2 … terminology and we are making our content more consistent with that

 

We also went through design reviews up to Brian S and all with approvals with this +1,+2 items

 

Kicked into design review on VOD review + content and design as well

 

 

Melissa, AlexA this will having this further discussion on this.

 

 

On the design end

We have a background for design as well as Content design review

Consistent with other place-eBay has order level summary for VOD

--

Carciaagin

 

Something cause cancer

Carciaagin

 

Something cause cancer

As in Protection team Sara Strong Carly and I presented One refund- refund summary project scope and new design layouts a coupe of month ago. We ran the concept testing to get seller feedback on clarity of the new designs. Today I am reporting on what we learned from the uses FEEDBACK And inform you where I am working further Today I am reporting on what we learned from the uses ————— Problems particularly free credits. ____________    We developed 2+1 refund summary layouts, with 1 highlighting of fee credits, and 2 varied level of detail, 3 treatment of positive/negative figures.  showing the outgoing refund total as negative. Inverted number on the test How prominently should the sec information about fee credits be displayed? The small businesses or experienced full-time users do not require the sec information. Simplicity is the key for the user group. unified experience when mentioning fee credits to sellers in our product experience. 1. The new refund summary page design is to create a consistent ‘One refund’ experience throughout protection products. All products will have one same refund experience in order to reduce user’s confusion and facilitate the use of eBay protection products easily. 2. Finding the most clear and intuitive usability and design (UX/UI) to help our customers reconcile the various refund and credit amounts easily and quickly. 1. Providing a brief explanation for each section for ease of understanding.  3. Finding the most transparent and effective UX/UI for our customers to understand fee credit. Reinforcing clarity and transparency of fee credit to  increase our seller’s trust.  1. Providing immediate breakdown of fee credit to be credited.  2. Finding clarity and easy understanding on refund reconciliation. (Symbols( + and -) for the refund money movement) 5. Finding easy accessibility and scannability of info for users who need it.   i.e. itemized receipt and item information. 

Cohesion between all products
Use the same system as forward-moving money movement
Readability, easily understandable
Fee credits are understandable
Take home fee understandable
Updated look - let’s be really tight with our visual design skills
terminology/ headers language

I created a modular system that could represent any rule configuration with clarity and consistency. The design introduced:

  • A unified visual language for expressing conjunctive (AND) and disjunctive (OR) logic

  • Adaptive input modules that switch between single values, multi-select, ranges, and date inputs based on rule type

  • Clear structural patterns for nesting conditions without overwhelming users

  • Scalable component behaviors that remain consistent across lightweight rules and deeply nested logic

This system ensured that every rule—simple or complex—was expressed in a way that users could understand at a glance, while maintaining alignment with the Core Design System.

Condition Builder deep dive----------

The new Condition Builder significantly improved clarity and confidence in rule creation. Users were able to understand AND/OR relationships at a glance and construct accurate conditions with fewer errors. The scalable structure reduced visual noise, minimized edge-case inconsistencies, and aligned the experience across all product surfaces.

For the broader organization, the component became a reusable pattern adopted by multiple teams, strengthening the Core Design System and reducing design and engineering overhead for future rule-based features.

Outcome

eBay Ignite – Eliminate Stockout Gaming in Cancellations and Refunds Moderator Guide Fieldwork Dates: Tuesday 30th May Methodology: x4 20 minute IDIs with eBay sellers TopicObjectiveTiming Welcome and existing experienceTo quickly set participant expectations for the research session and understand their existing experience with cancellations and refunds. 5 mins Concept Test To get feedback on a Cancellation and Refund flow with x2 scenarios. 10 mins Wrap up To ask stakeholder questions, sum up, thank participant, and close the session2 mins Research materials required: Link to Figma prototype pending Prototype 1: [Paid, not shipped. Full refund (cancel). Two reason codes (out of stock and address)] Prototype 2: [Paid, shipped. Partial. Three reason codes] Welcome [5 min] Purpose of this section: To set participant expectations for the research session Moderator: Thank you so much for taking the time to be part of our research efforts, I really appreciate it. My name is Fiona/Joe and I am a researcher who is interested in hearing about your experience as a seller on eBay. I have a few colleagues who will also be observing today as they are really interested in what you have to say. Today’s session will last 15-20 minutes. During the session, I will ask you lots of different questions, mainly to understand your experiences and opinions regarding order cancellations and refunds on eBay, while showing you a prototype of some new ideas from the eBay team. It is important to remember that there are no right or wrong answers; I only care about your honest feedback so any and all positive or negative feedback will be very helpful. Any information you provide today is confidential and will only be used for research purposes. It is also important that anything we share with you today, you keep confidential as well. If at any time any of you feel uncomfortable, please let me know. You are not obliged to answer any questions that you don't want to answer, and you can leave at any time, no questions asked. We will be audio and video recording this session today. The recordings are mostly to help me make sure that I have captured your feedback accurately. Do I have your permission to record this interview? Any questions before we begin? ●To start, could you tell me what you sell on eBay? ●What do you think of the current order cancellations and refunds process? Concept Test – Scenario One [5 mins] Purpose of this section: To get feedback on a Cancellation and Refund flow with x2 scenarios. Moderator narration: Thanks. Now, I’m going to show you a prototype of how a cancellation and refund might work on the eBay site. I’m going to give you a simple scenario, and in response I’d like you to tell me how you would respond using the prototype. I’ll be controlling it so just tell me where you’d click. Please think out loud and voice what you’re thinking, tell me what you’re seeing, what your attention is draw to, what you would do, tell me if what you’re seeing look clear or confusing in any way. Moderator notes: Moderator to share screen and show Figma prototype. Moderator read out Scenario 1: I want you to imagine you’ve made a sale through eBay but you’re out of stock. You’re on this page, what action are you going to take? [Moderator to not use the word “cancel”] [Paid, not shipped. Full refund (cancel). Two reason codes (out of stock and address)] Moderator to probe on each screen •What do you think of this page? •Is it clear? Is there anything confusing? •Is it clear what to do next? •Where do you think this is going to take you? •What are you expecting to see on the next page? Key questions per screen (see appendix for screens): Screen 4 •What do you think of these reason codes shown here? •What do you expect to happen if you select these reason codes? oModerator to probe on expected effect on defect rating if not mentioned. Screen 5 If not mentioned spontaneously, moderator to probe on ‘seller standards policy’ warning. •Did you notice the ‘seller standards policy’ notice at the bottom? oWhat do you think of it? oDo you know what it is? What do you think it might be? oWhat do you think it means for your seller standard if you continue with this process? Screen 6 •How did you find this process to cancel/refund your order? oIf easy, why? What about it was straightforward? oIf hard, why? What was difficult about it? Overall process •Now you’ve been through it, how clear was the process? Did you feel you understood what was happening and what would happen next? •How far does it fit with what you expect from eBay? Scenario Two [5 mins] Moderator read out Scenario 2: You have shipped the order but when the buyer received the item it was damaged. It’s not your fault, but you want them to have a good experience so you decide to give them a partial refund. Please walk me through issuing a partial refund [Paid, shipped. Partial. Three reason codes] Moderator to probe on each screen •What do you think of this page? •Is it clear? Is there anything confusing? •Is it clear what to do next? •Where do you think this is going to take you? •What are you expecting to see on the next page? Key questions per screen (see appendix for screens): Screen 4 •What do you think of these reason codes shown here? •What do you expect to happen if you select these reason codes? oModerator to probe on expected effect on defect rating if not mentioned. Screen 5 If not mentioned spontaneously, moderator to probe on ‘seller standards policy’ warning. •Did you notice the ‘seller standards policy’ notice at the bottom? oWhat do you think of it? oDo you know what it is? What do you think it might be? oWhat do you think it means for your seller standard if you continue with this process? Screen 6 •How did you find this process to cancel/refund your order? oIf easy, why? What about it was straightforward? oIf hard, why? What was difficult about it? Overall process •Now you’ve been through it, how clear was the process? Did you feel you understood what was happening and what would happen next? •How far does it fit with what you expect from eBay? Conclusion [5 min] Purpose of this section: To wrap up the session and provide an opportunity for any final questions ●What was your overall impression of the changes? Moderator narration: That’s all - thank you so much for your time! Appendix – Flow 1 Screen 1Screen 2Screen 3 Screen 4Screen 5Screen 6

Onboard Positivespirit$ or 1?? People You Should Be Aware Of Jamie Iannone - President and CEO * Eddie Garcia - SVP, Chief Product Officer * Aaron Carambula - VP Design, Executive Creative Director * Rob Martin - Brian’s Executive Assistant * Brian Shobe - Design Director: Payments & Protections and the E2E team * Rich Mains - Sr Design Director: Core Product * Tyler Moore - Sr Design Director: One Design * Mahtab Ghazizadeh - Director of Research * Marc Hinshaw - Director of Design Operations * Brent Leffew - Design Director * Julie Loeger- SVP, Chief Growth Officer * Avritti Khandurie- VP Payments Product  Day 1 & 2 * Work with IT to get up and running on your laptop * https://ebay-myit.onbmc.com/  * Get access to the VPN * Set up Ping ID * Outlook email and calendar * Zoom * Day 1: Team Welcome with Carly Johnson, Sarah Hermes and Shannon Whiteman * Zoom * Meet with your Carly Johnson * Meet with your design buddy Sarah Hermes * Meet with your design program manager Shannon Whiteman  * Request/download your design tools: Figma, Figma plug in, Ditto, Adobe * Request access * At this time please do not request access to Monday, Invision and Zeplin * Write an intro and submit to your manager & DPM. Brief description of who you are, where you were prior and hobbies or anything you’d like to include and a photo Week 1 * Watch for an email and complete any required compliance training * Review the “at eBay”, “Design Tools” and Design System 6.5” sections above * Get familiar with eBay design patterns and brand guidelines  * Log in to JIRA with your eBay credentials * https://jirap.corp.ebay.com  * No need to do anything else at this point, you only need to log in to get in the system.  * Shannon will a quick filter so you can filter your projects * Payment & Trust Jira boards * Protections CCUXTRST * Join Slack channels (see Design Tools above) * Your DPM will invite you to the private slack channels listed above Week 2 * Meet with your design buddy to help answer any questions you have on the design patterns, brand guidelines and user personas * Storing files * We use Figma to store projectsPlaybook | eBay * Google drive for everything else (using your eBay credentials), Shannon will add you * Payments & Protections Design google drive * Make sure you get included into the design DL and invited to weekly meetings * Go to https://mytools.corp.ebay.com/DLManager/DL * Your DPM will add you to the DL’s listed above in “DL Distribution LIsts: * Please add other links and tips you think are useful and/or flag anything that was broken or just too confusing so Shannon can update the template. Useful Information Acronyms AcronymsDetailComment eBay Acronymshttps://ebayinc.sharepoint.com/sites/TW34252/SitePages/Home.aspx https://ebayinc.sharepoint.com/sites/TW-30302/Lists/Dictionary/AllItems.aspxA great source for most of the acronyms flying around eBay Ads and Retail Standards Teamhttps://docs.googhttps://ebayinc.sharepoint.com/sites/TW-30302/Lists/Dictionary/AllItems.aspxle.com/spreadsheets/d/1Mn8zoCiIRkSySThUYUCeu5qLJK7kXgwy4VUQeJeiZfw/edit?usp=sharing Payment AcronymsAbbreviations and Acronyms Customer Connection AcronymsAcronyms Merchant Promotion Playbook AcronymsAcronyms NAMP Acronymshttps://wiki.vip.corp.ebay.com/display/NAL Global locations * You can look up the address of any eBay location plus the available services at that location.  Just click on your location on the page to get more information. * Floor plans and other space information for all locations is available here. Headquarters address eBay South Campus 2065 Hamilton Avenue San Jose CA 95125 1-408-376-6151: Main lobby

hank you for considering our proposed designto move it forward for testing and implementation. Ladan presented this project to your team on September 22nd, and since then, I have been following up with various team members to find a way to proceed. We are making a request to implement the new stacked multiple item image sizes for the Unauth Dispute product (and eventually for all Protection products) by incorporating the 2 dweb (x2 mweb) image sizes within the current email grid system used for transactional emails. Please see the attached file for more details I understand that our proposed design was presented to your team by Ladan Nur on September 22nd, and received some feedback. However, we were informed by the developer at DEPT that it is possible to endorse the new image size (widths) within the current email grid system. If we can explore this further with your team and receive your official endorsement, we can turn this into an actual project under @Brittany Kanakis. Our team has developed this new image and presented it to the DS team several times. They have approved the new multiple item images and component. We are in agreement to keep the proposed design within the email grid system."  Regenerate response

Chat is one way to use AI https://hub.corp.ebay.com/site/coreai/chat Dueling is a Machine learning models Caracter personality- feel more compelling Mocks and wire framing before actually validate what Ai will look like in practice for you AI looks for patterns Looks things like a path.. this happens this is going to happen… predict they can tell you how to take action Ebay is selling some products for 20 years IT can predict Something else takes place.. then ai predict something will happen Teach itself Give the machine the data.. and it predict This is the version of AI that you can communicate with and text with and they have answer Open AI is the company They created this language learning app with Open ai GPT-4. GPT is chatbot technology and GPT-4 is the newest version that can text, communicate and interact with allowing more advance level of communication. What this team created was using GPT-4, created some new feature for language learner in the world. New feature they created: They created characters have personality and users can practice conversation with role-play interactively—— —— Forgot about the revision history part of dev mode! Lauren Godwin (she/her) to Everyone (Jun 30, 2023, 12:14 PM) The one thing I miss about Zeplin Kris Young to Everyone (Jun 30, 2023, 12:14 PM) Zeplin… seems like a 100 years ago Kris Young to Everyone (Jun 30, 2023, 12:14 PM) Kinda like InVision ;) Darian Rosebrook to Everyone (Jun 30, 2023, 12:17 PM) As a heads up, our Jira integration is not Cloud Based, which the Jira Figma plugin requires Thomas Dittmer to Everyone (Jun 30, 2023, 12:17 PM) Does anyone know if the Dev Mode plugins work with on-prem JIRA (vs JIRA cloud)? You to Everyone (Jun 30, 2023, 12:18 PM) You tube link Duolingo max https://www.youtube.com/watch?v=zqUi3p-o8wU&t=2259s Carly Johnson to Everyone (Jun 30, 2023, 12:27 PM) I wonder how we could use this for something like our sneakerhead users - can we automate messages for our sellers so they don’t have to reply to questions, but generate help bots specific to certain verticals? Good reminder! Matt Talebi to Everyone (Jun 30, 2023, 12:29 PM) ^ basically want to create an intercom that sellers can customize to their own store ~ actually lots of e-commerce apps in Asia have these features. So it would be good to look there for some research Ru Chen (Pronoun: She/Her/Her) to Everyone (Jun 30, 2023, 12:30 PM) Having distinct characters to humanize the AI is very important for engagement and increasing trust. Richelle Dumond (She/Her/Hers) to Everyone (Jun 30, 2023, 12:32 PM) (Larger) sellers already try to streamline the answers to many of their questions by having a google doc ready with answers to often asked questions. I bet hey would welcome some in-app help with that! Carly Johnson to Everyone (Jun 30, 2023, 12:34 PM) Haha same… anyone else here not good at drawing? Thomas Dittmer (Jun 30, 2023, 12:35 PM) Right here 🤠 Carly Johnson to Everyone (Jun 30, 2023, 12:35 PM) This is a great note for managers and people hiring! Everyone brings something different to the table - diversity in skills is great for pushing our product Richelle Dumond (She/Her/Hers) to Everyone (Jun 30, 2023, 12:32 PM) (Larger) sellers already try to streamline the answers to many of their questions by having a google doc ready with answers to often asked questions. I bet hey would welcome some in-app help with that! Carly Johnson (Jun 30, 2023, 12:33 PM) Yes! Even instagram has auto-replies for business users Matt Talebi (Jun 30, 2023, 12:36 PM) Here is example of one I have used, they let you setup common faq in chat; primitive but effective since it can be anything related to your store https://seller.shopee.com.my/edu/courseDetail/707?lessonId=2212 Carly Johnson to Everyone (Jun 30, 2023, 12:37 PM) Love this quote Bassma Kamal Vanlue to Everyone (Jun 30, 2023, 12:38 PM) Super meaningful! Thank you Jungheee for sharing. I can totally relate Troy Chafin to Everyone (Jun 30, 2023, 12:39 PM) Really great message 🖤

Eli Voronov : 

 

 

Hi Emi, yeah, let me share a few resouces

 

Added to your saved items

13:35

Has the price lines and an example (Sheet5): https://docs.google.com/spreadsheets/d/1OBDYtJCZNWraEM77pG0TFspHx8rWEpyQid5T5qqU-Hc/edit?usp=sharing

 

Added to your saved items

 

Eli Voronov

 

Examples of seller take home designs with some of those pricelines: https://www.figma.com/file/JfLFz9ivBUUDr2wHPrGMuA/2022-Payment-info-enhancements-in-Order?node-id=1653%3A1197247&t=p7xRDiL3skPvcbVx-0

 

And this is how we display some of those priceline on Order VPD

 

 

Phase 2 section is what is in production currently: https://www.figma.com/file/tNRTlmCHL3tjQTeedSXUHJ/Fee-Presentment?node-id=1703%3A2104&t=tyG5uVrK4D7mkzUq-0

 

——

I have a question regarding negative number. In your pages such as VOD or VPD, do you use always red in negative number ? BTW, are you in Susie’s payment team?

 

We don’t want to use red in negative as there were lots of voices from sellers.

Screen Shot 2023-04-05 at 1.34.28 PM.png

 

 

 

Eli Voronov

  14:57

 I'm part of the product organization, and I'm part of the team that owns the seller payments experience which includes payments overview, all transactions view, and VPDs.

Yes, currently we do use red in overview pages, all transactions and VPDs.

Susie is our partner from the design organization

 

VOD also shows refund as negative

 

 

A different team (selling product team) owns VOD 

 

Emi Nishida

I appreciate your input. So we all don’t use green on negative numbers at all. Some other teams use GREEN for saving or discounts. The red usage is for caution in negative cases.

 

If you don’t mind, can you please send me an example of VPD page as well?

Right Rail

Audit consolidation and Terminology/ headers consolidation with PMs and Content team

  • Sara S's workshop (11/14/2022) 

  • meeting with PMs - update the latest Right Rail designs 

 






 

12 Dec 2022 

 

 

 

 

Refund summary

Design Inconsistencies across Refund pages.

As we build out native, inconsistencies are seen in the Refund pages.

  1. Audit the refund pages (across ALL native flows - SIR, Return, INR) and make sure we are consistent and using the most updated refund design for native?

  2. Particularly: "Amount you owe" vs. "Refund amount you owe" and the different sizing

  3. Need to add this to our component library.

  4. Adding the CCM component refund:

https://www.figma.com/file/6TnvvhPO06gua9mxEWeGtX/Stored-Value---Phase-3?node-id=14579%3A332807&t=j5aYSQC6FikFrgGT-4 (edited) 
2 files 

 

 

 

 

12/15/2022

Refund summary section design explorations startCarly
 

12/20/2022mtg with Sarah H. Aligning with Sara's SIR pages as well. She will ask pms for partial refund fee if there is any for partial returns.

 

Tasks (Off Track) : temp

Right Rail ideations: 

16 Dec 2022 

Rio has been working on designs with design systems for the right rail over the last year. We need to hand off the designs to Emi so that Emi will add them to the component library and we can officially finalize the design :)

Right Rail ideations: RIO's file 

 




 

 

 





 

Review Schedule

Right Rail

Check listReview TypeSections

DateContentsAction itemsfor next step

 

Protections team alignment

12/12/2022Start Refund summary

 

 

01/06/2023Hands off and align project scope with Rio

 

Content design





 

Sara Strong review

sign up (include list of all partner attendees)

 

11/15/2022Sara S. Work hours feedback for Right Rail sec.
 


01/05/2023Initial design review #1
 

 

Brian Shobe Review

sign up (include list of all partner attendees)

03/07/2023Refund summary 1st round

  • Align with our partners where we are going and what are our goals

  • Find research session to back up

  •  

  • in next meeting, research team will be in the room to talk about our destination and feedback from their research

  • content team will be in the room

 

David Gandhi review

Ask PM to sign up





 

E2D review (design/product/eng teams E2E)





 

Engineering review





 

Sara Strong
Prep for Aaron review 
(1 or 2 reviews as needed)

sign up (include list of all partner attendees)




 


Aaron Review(if needed)


 

 

Product Evolution (DS) office hours  sign up





 

A11y review




 

Action items

Summary

Datemeeting titleStatusAttendeeAction items for SaraAction items for CarlyAction items for EmiWhat is next ? Questions.
 



 

 







3/20/2022meeting with PMs

Sara, Carly, Emi

Ayush, Sri, Chole, Beatrice, Sonny,

 

  • Schedule David G meeting

  • Assign a content partner

  • Emi & Carly will finalize a research session contents

  • Schedule a research session

  • Meet to make sure the refund page takes into account each use case.

  • VOD shows something different from us, and it’s confusing for sellers.

    • meet with VOD team? VPD team? 

    • Emi's audit for VOD and VPD pages

  • Design will meet with seller payments team

    • Meet with Susie's team

  • Meet with content to nail down our descriptions to be aligned with what the user NEEDS (look at the fee credit research).

  • Mock up a mobile ver. that emphasizes the descriptions of the sections. We will test with users.

  1. Contents development

    • Emi will put all info together for aligning seller and buyer's pages

    • I wonder if the content person can be informed and worked on all One refund project including RR all at once.

    • Content person needsto get involved before meeting with Payment team.

  2. Meeting with Payments team

    • Do we need to find the Buyer's side refund experience first? OR it is not a concern for the seller's payment experience for the payment team?

______________________________________________________________________________________________________________________________

  1. Sara's Office hour 1.

    • Discuss Emi's audit for VOD and VPD pages and find the best solution

    • Discuss Buyer's facing after Emi's audit is done

  2. Sara's Office hour 2.

    • Discuss past research sessions

    • Find the best Research session 

      • should VOD  be in on the user testing as well - if it’s a big confusion for our users?



3/12/2022meeting with Beatrice for Cancellation adaption

Beatrice

Sara

Emi

  • Meet with Garima for Buyer exp

  • Look into Buyer's files from Ran

  • Look at files for buyer's unauth exp.   from Ran (Protection) 

  • Find research team for fee discussion, CCM invoice 

 

 

  • Another audit for Buyer side

    • Partial and full refund for buyers

  • Continue the path for seller 

    • work on crazy cases

  • Rekick the part of it next week




3/10/2022

meeting with Atul 

Follow up meeting from yesterday

FIGMA 

 

@Elise Zimbardo-Ensor

Figma admin things.

Or the community-figma channel for additional questions.

 

Figma learning with Thomas Dittmer :QA legend

 https://www.figma.com/file/6iKY0U9x5oBedDx3FgzN0e/%E2%9C%8D%EF%B8%8F-Ditto-%7C-collaborate-on-copy-(Community)?type=design&node-id=0%3A1&mode=design&t=ffEG5Z3F3ZgrQPwl-1

 

https://www.figma.com/file/vmJm2Or4WHviW4idsRvc80/Emi-Ditto-Figma-Prob?type=design&node-id=0%3A1&mode=design&t=7tpY1nD7JgL3kMNe-1

 

 

 

Howdy Emi, Thanks for checking in. My week is going ok, hope yours is going well.

 

In general the process of moving components from one file (or library) to another is fairly straightforward. Figma has a resource page on exactly this. There is a key step that needs to occur so that all connected components stay connected.

  • First and most importantly, you need to temporarily publish the origin file of where the master component you want to move is located (you can unpublished this file later if you don't want to keep that library)

  • cut (not copy) the master component from the temporary library file

  • paste the master component to the target library file - then publish the target library file

  • return to the origin file and select the "update" button (this updates all of the currently linked components to the new location of the master component which is now the target library)

  • (if needed) unpublished the origin library file but only if you don't need to keep that library for other components.

Once these steps have been done, you may have to update files that use instances of the component as you open other files outside of the temporary library you created.

 

 

 

 

FIGMA learning with Ditto

 https://www.figma.com/file/vmJm2Or4WHviW4idsRvc80/Emi-Ditto-Figma-Prob?type=design&node-id=1%3A16720&mode=design&t=ViBEwLOBHlEeiiAN-1

 

 https://www.figma.com/file/UEWpEOmWnXU4vxC693paln/Figma-prob-(TFD)?type=design&node-id=62-122&t=nmL9zUh8dVKh9THi-0

 

3d  Edited

 

Hey animation lovers– we teamed up with our friends at LottieFiles to make a Figma plugin that exports your designs as production-ready animations for web or mobile. 

 

Get started with over 80,000 free(!) ready-to-use Lottie animations to take your designs to new heights.

 

https://bit.ly/3MmYNzT

 

 

#animation #plugin #uxuidesign #designcommunity 

 

https://www.linkedin.com/posts/figma_animation-plugin-uxuidesign-activity-7065421834917142529-9wuh?utm_source=share&utm_medium=member_desktop

 

Figma on LinkedIn: #animation #plugin #uxuidesign #designcommunity | 127 comments

https://www.linkedin.com/posts/figma_animation-plugin-uxuidesign-activity-7065421834917142529-9wuh?utm_source=share&utm_medium=member_desktop

Ignite Research testing https://jirap.corp.ebay.com/browse/CCUXTRST-1052 For Ignite concept for One refund, I put request forms together here if you would like to review before tomorrow 12:00p meeting. https://drive.google.com/drive/folders/1jBZvL6mxzwjghQzZMWSiN6M3WCYIgozi 1. https://docs.google.com/document/d/1_VG8vskAj7IcU4DTrFeIMo6zgF2EXmoOPO2TphidIQE/edit 2. https://docs.google.com/document/d/1HGWr3Lm3HSJPWRKaD3e9LFsw1wVOBHpPJSxq41zi_A8/edit (edited)  Emily Gutierrez result https://docs.google.com/presentation/d/1OccKuhX1rqKMJ80bR7v1dQZbeEPcu5pMkCQUUnR9dGc/edit#slide=id.g24ce8e6a93f_0_7 https://www.figma.com/file/Wz8Y133XEGZeQ8hwebxBJv/Seller-Fee-Credits?type=design&node-id=1550%3A45908&mode=design&t=vOheMBQrOIfqTNWh-1 I believe that this research was an interview to a seller that we based from. Fee credit issue was included in. research session in August result : https://docs.google.com/presentation/d/1OccKuhX1rqKMJ80bR7v1dQZbeEPcu5pMkCQUUnR9dGc/edit#slide=id.g24ce8e6a93f_0_0 This is my presentation dock to execs after our testing: https://www.figma.com/file/wsKh1KzRaYzClVC8fRZFZ6/One-Refund-master_Emi?type=design&node-id=8341%3A96644&mode=design&t=P9CsesFTfnxhlWAQ-1 the recorded sessions for the testing: https://drive.google.com/drive/folders/1jBZvL6mxzwjghQzZMWSiN6M3WCYIgozi My report of the session https://www.figma.com/file/m1jHb3Jn461T1wDi0YIyjs/%F0%9F%93%9D--Refund-Summary_-Research-Ignite-prototype_08012023?type=design&node-id=1%3A12139&mode=design&t=YqimhXunkaU7aPEQ-1 Great News: Eliminate Stockout Gaming in Cancellations and Refunds was selected for an Ignite Concept test on 6.6.23 (date to be confirmed). The files have been set up to support this concept test. eBay Design Google Drive * Research * Ignite Concept Testing * 3_Concept folders * 6/6/2023 Eliminate Stockout Gaming in Cancellations and Refunds The folder includes: * Request form (used in the first meeting with Ignite) * Concept(s), Hypothesis & questions (used for the internal working sessions) * Notes doc (used during the session for our personal notes) @Carly Johnson  please let me know if I should schedule a quick work back schedule meeting to explain how this all works. ________________________________________ Ignite testingRefund summary 1 https://docs.google.com/presentation/d/1OccKuhX1rqKMJ80bR7v1dQZbeEPcu5pMkCQUUnR9dGc/edit#slide=id.g2507cafe558_0_75 Refund summary omitted testing sec Information for each section on the right helpful to understand? * → click Itemized receipt in the line item to collapse  ( Compare with A, which layout is easier to reconcile the refund total? Do you understand fee credit? Is it better or worse to understand the fee credit?) → click the chevron in view itemized receipt tile  * Modal pop-up : review the itemized receipt ( This page shows the details of subtotal. Do the users want more information? Is this clear to understand the itemized receipt?)      3.  * → click Itemized fee expansion control to see itemized details. Click to collapse. → click CTA to submit the refund My concept https://docs.google.com/document/d/1ZY5dp_FM40xT-yd3k_cvlZUoy9GAqspSlUejyTiz80M/edit https://docs.google.com/document/d/1HGWr3Lm3HSJPWRKaD3e9LFsw1wVOBHpPJSxq41zi_A8/edit Reduce seller gaming Concept NameEliminate Stockout Gaming in Cancellations and Refunds Release # and link or
Vision Project nameRELEASE-175077 [Discovery] Reduce seller gaming in the SIR experience RELEASE-150056 [Discovery] Reduce opportunities for seller stockout gaming within Cancel flow InitiativeTRUST Release Priority:Key Launch Writer(s) of this intake formCindy Aknin
Beatrice Chiriacescu
Carly Johnson (Design Manager Protections) Design Program ManagerShannon Whiteman Design LeadCarly Johnson Product LeadBeatrice Chiriacescu Engineering LeadPiyush Dubey Research LeadCasey Skinner Content LeadDeb Aoki Other PartnersDesign: Emi Nishida VP Sponsor(s)/Initiative OwnerDavid Newman Quick Links Concept(s), Hypothesis & questionsDoc NotesTracker TARGET CONCEPT TEST DATES MonthMay 30, 2023 Justification for this month and/or month rangeAn A/B test will be conducted to confirm we are collecting more accurate signals for the Standards team to apply and enforce their policies. Since the proposed experience is different from the site today, it would be important to collect direct seller  feedback to ensure the flow makes sense and is easy to use. DESCRIPTION OF CONCEPT ConceptThe Cancel and SIR flows will be combined into one experience and will present sellers with contextually relevant experiences, leveraging existing ship and paid signals. Katie Locke

Sara fig jam Make sure we cover the template we need Similar experience Different category? Few template content partner Template design for you make your own email after we make template. Fig jam open for you Template cranking for you come back to discuss Figma for you for all products —— Sara’s workshop agenda 7/6 I was requested to add a 2 column module in dispute email. 1comparison between 30/70 and 40/60 Revise the template to the new email system MSLIB for Dispute 1Communication with DS team and email DS team to align the guidelines Unearth needed to update the email template INR- not requested but Sri is updating the email. Component library update –––––––––––––––––––––––––––––––––––––––––––––––––– Owner is DS6.5 is deprecated and we should start to use BCC BCC is another design standard for email —The original email design was put together by the OX team and an external agency prior to onboarding our team on eBay we’re currently onboarding the email modules onto UEP( User Experience Platform), —— Ladan Nur I agree with @Matthew Robinson in that if we will be discussing content stored within the footers, another team may be better suited to help. ____________ Srilakshmi Mani to support-mslib team We needed some clarification on the footers as some of our projects are blocked: * What are the MSLIB footers that exist today? Can you share the content for each of them? * Do the MSLIB footers have different versions based on site? * For payment footers, does MSLIB support different entities- pay in, pay out ,etc? ————————— We need to clarify things and discuss it again to get legal guidance. Sri has set up a meeting tomorrow morning to continue our discussion around the email footer ___________________________ eBay has many different entity even market place has Ebay inc is the marketplace the US. Others are eBay Canada,Ebay UK… European Austraria Payment has different entity. UK limited We are not finalizing and not responsible for what content goes to footers. All we care about is which entity should be finding this email. Eng Global component This content will be sent by marketing entity This footer needs to go from the payments entity — We don’t own the footer If we have one example, this is what footer looks like. And we are not able to Payments team own They are the POC evaluate the content but it seems that They are relatively the new team and they are not doing it. They should make sure that is the right content. Atul is discussing with them —————— 1 Start by grabbing your sticky notes from the journey map. 2. Cluster similar notes into groups and assign each group a theme. 似たようなノートをグループにまとめ、各グループにテーマを割り当てる。 3. Debrief the result of sorting and vote the top 3 group. 仕分け結果を報告し、上位3グループに投票する。

David G meeting Dan Talking Points: * Deletion of Item drawer --> made more visible by moving to right rail on dWeb * "How you were refunded" component --> new addition as part of One Refund project * Deletion of Item drawer --> made more visible by moving to top of page on mWeb Multiple items cases 1. Stack image —— multi-items image 2. Link 1. dWeb- link button 2. mWeb -top item tile component (with chevron) → The whole component is clickable to go to modal bottom-panel. 3. What is the difference using single or multiple image on accessibility? How should the voice over say for the multiple image? “Multiple items, [Item title], [+ x more]” as the description for that row/cell “View items” Order items total Order items “Review items” “Itemized receipt” View itemized refunds”

Hi team! Just going to pin our most recent flows to the top of the channel. Shannon is putting together an awesome onboarding doc (and we will spend some time this year working on our single source of truth figmas), but in the meantime if you need to point someone to our most updated flows, point them here! Refund Return seller side Emails INR Dispute Returns Buyer-side Feedback Unauth SIR (soon to be deprecated/combined w cancel) Cancel (soon to be deprecated/combined w SIR) Protections Library Please comment on this thread with a link if i've missed anything One Refund master_Emi https://api-cdn.figma.com/resize/thumbnails/94d7fff4-275c-40c4-ade5-968309eb2a2a?height=112&bucket=figma-alpha Added by a bot Seller Accept꞉ All Variations for return flows https://api-cdn.figma.com/resize/thumbnails/d6469c71-4856-4fba-b004-b8c478dafdf6?height=112&bucket=figma-alpha Added by a bot TRUST Emails 2021 https://api-cdn.figma.com/resize/thumbnails/4d135192-dd34-45f6-8fa7-163d7f73d0f4?height=100&bucket=figma-alpha Added by a bot INR_Resolutions_redesign_2020 https://api-cdn.figma.com/resize/thumbnails/61d4acc4-72c7-475c-ae51-f23900a51088?height=112&bucket=figma-alpha Added by a bot Challenge / Accept Flow (Multi‒File Upload) https://api-cdn.figma.com/resize/thumbnails/13194c1c-7b6d-4e83-9cd4-4849aaec877d?height=112&bucket=figma-alpha Added by a bot https://webflow.com/ webflow.com Webflow: Create a custom website | No-code website builder Create professional, custom websites in a completely visual canvas with no code. Learn how to create a website by trying Webflow for free! (171 kB) Material design has an updated version: https://m3.material.io/ . They also released a Figma design kit: https://www.figma.com/file/bnebnUPz3Mei9OelOwX0rX/Material-3-Design-Kit-(Community)?node-id=11%3A1833&t=SLhKjCA084cQ5vaK-1 . Thought it might a helpful reference for our eBay Android experiences that sometimes receive less attention than iOS!  m3.material.io Material Design Build beautiful, usable products faster. Material Design is an adaptable system—backed by open-source code—that helps teams build high quality digital experiences. (35 kB) https://m3.material.io/ Material 3 Design Kit (Community) (32 kB) https://api-cdn.figma.com/resize/thumbnails/e19941d8-402e-4144-9e7b-0a4683cdd8a5?height=112&bucket=figma-alpha  I had question earlier today for the error state on text box when the user does not put any comments on it. I’d like to share their response within the team so that we can make it consistent across Protections flow. The DS team said that 0/1000 should remain GREY because the error isn’t related to the character, and the box boarder and the error message need to be RED. @shermes  Mark Lapole seems this error is due to an empty input, not related to the character count. so i’d say we wouldn’t make the character count red unless that is the reason for the actual error state. From a thread in design-system | Mar 15th | View reply

AI For seller to avoid SIR such as OOStock. Ai can generate the warning for sellers when the inventory is low and prevent seller buying the items, For colors, AI can identify what the seller or buyer prefer for visualize transaction. Especially color blind or disable user’s help on customizing colors for them Make transaction more secure to identify strange transaction like unauthorized withdrawal https://hub.corp.ebay.com/site/cpt/page/aiconference2023 —— Figjam board for this brainstorm!   https://www.figma.com/file/vWX15WJ5pcnfyZM8RMMGAQ/eBay-AI-Session?type=whiteboard&node-id=0%3A1&t=SY8DTMirnTztLLBY-1        Team, please join us for a brainstorming session around how we might use AI and Generative AI in our upcoming workflows and help user pain points.   I have created this deck (below) so th at we all have a baseline understanding of AI. Please read this as your homework prior to this meeting.   https://docs.google.com/presentation/d/1TITUDzmRyCfA0DEz7izQkew3o2kKslcKt6GVLTuCokA/edit?usp=sharing    Feel free to forward to partners I may have inadvertently forgotten…. And don’t worry if you are not available at this time. We will record and will also do many more follow-ups in this series ——— Config.figma.com As an industry we’re in a transformative moment: how will AI shape our future and our work? That is exactly what we are tackling on the main stage with some of the most innovative thinkers on AI and product building. DESIGNING WITH AI Speakers: Jordan Singer, Andrew Pouliot, and Vincent van der Meulen How can AI make designers more effective? What are the challenges and opportunities building with AI for design? We’ll talk about the history of generating UI with AI, how AI can make designers more effective, challenges and opportunities in building with AI for design, and breaking down barriers between design and code roles. We’ll share a deep dive - and demos - into the Diagram product evolution and tackle the evolving role of the designer in this future. GENERATIVE AI AND CREATIVE ARMS RACE  Speakers: Ovetta Patrice Sampson There's a new sheriff in creative land and its name is Generative AI. Now that machines can talk to us and each other, can replicate just about anything we can do with text, imagery and art does that mean the age of Human Design is over? Well, Skynet not yet. Learn how this technology revolution can help humans to be more creative, innovative and imaginative if we just keep calm and human on. AI AND EMPOWERING CREATIVE CAREERS Speaker: Scott Belsky, Brooke Hopper  Generative AI is clearly transforming creative work, but we must find ways to train models and integrate features that protect artists’ rights and empower careers. This session will share approaches and learnings from building Generative AI technology that gives creative people superpowers while respecting the value of their work. We’ll use some examples from our work at Adobe to explain our approach -- which was design-driven from Day 1. THE CRESCENDO OF AI IN OUR COLLECTIVE FUTURE Conversation with Reid Hoffman and Kanjun Qiu Artificial intelligence is amplification intelligence: it cultivates and amplifies our better selves. It takes the power of the human mind and makes it stronger and faster. We're going to dig into why we are so optimistic about a future with AI, what Reid learned writing the first book about AI with GPT-4, and the transformative potential AI holds for democratizing societies. ——   AI can simplify the UI?    AI can do patterns AI can help us labereage our design  We spend too much time to debate design    Design today:  Higher the ceiling and lower the floor A share space… Focusing a shared space   How about Figma? Community centered Build practical AI is a platform A tool   AI can find the right file Allowing design faster moving faster DIAGRAM: design for the future Plugin API Design system Models High fidelity prototyper Automation era diagram Intelligence -Era of intelligence Diagram eng: Design sharing tool Magician :How does design and AI come together? Should you name the layer? Name them for you Ai Model talk to you to understand design  Generate Glyphs Help people generate icons Iterate icons —system 作る時    Being designer be more effective Design glyph for design assistant — Diagram design engineer: Design system- Genius Figma layers—JSON Visual Figma canvus to Json   GPT ?? Make suggestion and show recommendation for design system    Magic elements Ex food delivery app Drop magic element and AI find the right components   — What is change the world? Ideas that we have data Interactive experience with AI Genius chat  Talk t oGeneus and you can add it to the file    — Future of the design with AI Still, we design. Designers are not going anywhere. — Google   Large language model  Best tool is a pencil and a piece of paper Neuroscience Selatonen dopamine when we draw- put us in a happy moments Machine can take a chance to explore —Ai is an amplifier not replacing designers or devs Amplications of AI ___ Duolingo They are using AI to allow the language learner to feel as if it is a one on one tutor experience. Also give real time feedback on how the student is using the language. Example, can correct pronunciation immediately. Create AI personas for a personalized experience. For example, you can order something in a cafe, and converse with a cafe worker AI character who has a certain personality to make the interaction interesting. They have custom voices to enhance the experience - so happy or sarcastic… Sent from my iPhone — Emerging thoughts on AI assisted design A Long Rope and a Handful of Knots: Emergent Best Practices in AI-Assisted Design and Research Speaker: Jane Davis The past several years have seen an enormous change in what AI can do—and who it's available to. The advances in LLMs, combined with their broad availability, mean that Design and Research are facing new opportunities and challenges around how and why to apply assistive and automative technologies to our craft. To better understand how to navigate a world with widely available AI, I conducted primary research to see where, how, and when designers and researchers have found applications for AI in their work, as well as how they think about the ethics and best practices involved. Based on this research, I'll outline the emergent best practices (and pitfalls) in applying LLMs to design and research work. I'll also share principles for applying this research to design and research processes, and give attendees practical takeaways for how and when they might want to apply AI to their own practice. Design Systems in Transition: Anxiety, AI, and Where We Go  Speaker: Kathryn Gonzalez Design Systems are made to manage change. Mass layoffs throughout our industry have changed the vibes in tech rapidly, AI is moving quickly to reshape our design and engineering practices from the foundations, and all the bubbling anxiety that comes from it are now here. When the world is changing so quickly, how do we use the frameworks, mindset, and skills we have as system builders to navigate what’s here and what’s to come? And what does that future look like? After eight years building design systems and the organizations that run them at DoorDash, Kathryn Gonzalez quit her job to explore the future of the space and make sense of this moment in time in our industry. She’ll share her stories, what the AI-assisted future of systems could look like, how she’s dealing with the anxiety of this critical time for the work we do, and what it all means for the people in this industry. And yes, this talk idea was created with the help of AI.             Finding patterns Pattern recognition program   Design Systems in Transition: Anxiety, AI, and Where We Go  Speaker: Kathryn Gonzalez door dash Design Systems are made to manage change. Mass layoffs throughout our industry have changed the vibes in tech rapidly, AI is moving quickly to reshape our design and engineering practices from the foundations, and all the bubbling anxiety that comes from it are now here. When the world is changing so quickly, how do we use the frameworks, mindset, and skills we have as system builders to navigate what’s here and what’s to come? And what does that future look like? After eight years building design systems and the organizations that run them at DoorDash, Kathryn Gonzalez quit her job to explore the future of the space and make sense of this moment in time in our industry. She’ll share her stories, what the AI-assisted future of systems could look like, how she’s dealing with the anxiety of this critical time for the work we do, and what it all means for the people in this industry. And yes, this talk idea was created with the help of AI. Where are we now?  Design system as a practice Design system works as a core as people center What we are building for is people who we supports What do we want the future to look like? More inclusive in accessibility Mainstream AI usage How we can use AI in design?  1. Reducing busywork 2. Augmenting creativity 3. Expanding skillsets How we get there?- still in uncertainty = Opportunity

One refund Item level and order level Hello, Garima My name is Emi Nishida in Carly’s protection team. Sarah H and I would like to confirm a couple of questions. When a user purchased multiple items, can you return multiple items in return/ refund not in items level? If so which product is able to do? Sarah told me that SIR allowed to give a partial refund in a specific item. But that might not necessarily mean is order level. Then is SIR transaction is only Item level but not order level? —— Sarah Hermes For example, the seller might want to make it up to the buyer when the product has a scratch. Instead of going through a return he gives some money back What kind of reason sellers initiate refunds? (for SIR ) Carly note IMPORTANT Cancel Notes: sometimes the labels change depending on the use case. But change in the experience is minimal. There are more labels for some use cases. Ex. when we have “quantity”. Labels hide/show while user is completing the flow. Order: tracking on links? the link takes the to VOD. Return ID: how does the seller use the return ID? do we know the use case? is there user insights? what do they user it for? Request amount: ex. buyer requests $130 but gets other number then is it important?. is this the amount the seller needs to see in a refund scenario? Buyer: Date purchase: what dates are important in this context?; is this the date the seller needs to see in this scenario? Return details: overlay that takes them to history; in mobile this is the history section. should this be a section like mobile? Quantity: shows up in multiple items use case. Other follow ups: •Check overlap between history and right rail and summary. •Consider order details and return details do not have delineation. Native has delineation (reference returns native) Carly feedback: Interviews (informal); reserach team ask; existing research; card sorting

For large organizations, internal marketing and onboarding strategies are essential to successfully introduce an enterprise design system. The Capital One Enterprise Design System team soft-launched with an interactive onboarding and education playground to demonstrate the system’s visual appeal, advanced tooling, and robust support model. Playfully titled as the design system “flight simulator”, the Figma-based training tool prepared designers to take flight. Join Jana in a discussion about how informative (and fun!) design system training can build your brand. She’ll share tips on simplifying complex design system concepts into digestible learning plans, and show examples of how she and her team brought training to life in a delightful way. Speakers Jana Choi Design Tools Lead, Capital One

I synced up with Ivana offline and she confirmed that we need to provide the mock and add to the Master Figma and MSLIB team develops it. The main purpose of this meeting is to align on it with you and the Design team on it regarding the next steps THis is the Master Figma link that the MSLIB team asked us to put the new component mock - https://www.figma.com/file/u36AQ6WIIxa1YLndO1xH4M/Email-Design-System?type=design&node-id=6681-25740&t=RWFuwasoYXyb1BPI-0 This is the thread for your reference - https://ebay-eng.slack.com/archives/C01E1URKNBB/p1687254896449399?thread_ts=1686696322.624669&cid=C01E1URKNBB

image.png
bottom of page