Marketplace for StyleRow

My role: Conducting and synthesizing interviews, competitors analysis; Leading design system effort, Site mapping; User flows; Low and hi fidelity wireframes; Prototype in Figma; User test.

Duration: 6 month.

Team: 1 designer, 6 developers, 2 project managers.

ABOUT STYLEROW

StyleRow is a startup for interior designers and design firms, that offers a set of tools for designers to manage design projects, bill and communicate with client, clip items from other vendors and many other projects related features. They wanted to expand the product into marketplace for designer furniture and decor. They hired a separate team to focus on the marketplace. While being a startup that needed to start bringing profits there was a bit of pressure from the investors. Transactional marketplace was meant to generate revenue from each transaction and help StyleRow scale.

StyleRow didn’t have a in house designer and used services of various freelancers, which created an inconsistent design and scattered or missing design files.

PROBLEM STATEMENT

StyleRow needs to generate more revenue and tap into ecommerce with some of the most unique products in the industry. The first version needs to get into users hands asap to validate assumption that such marketplace is needed among brands and vendors as well as designers and design firms.

PROJECT GOALS

  1. Build MVP version asap

  2. Validate MVP version with end users

  3. Validate that pricing model will be beneficial for StyleRow as well as brands

  4. Create consisten design based on available brand attributes

  5. Work on full Desin System

  6. Collaborate with engineering to build MVP quickly, but with future and scalability in mind

DESIGN PROCESS

DISCOVER: INTERVIEWS

I conducted rounds of interviews with stakeholders, development, product and sales teams. I wanted to understand:

  • What is the vision for the marketplace project?

  • What are the immidiate and long term priorities?

  • Are there major road blocks or constraints?

  • How has the design development collaboration happen historically?

  • How is StyleRow going to be different than other furniture retailers?

  • How can we adapt design thinking methods in our product development? And by design thinking I mean mainly direct communication with the users, user testing and usability testing, validating assumptions and building a roadmap in collaboration with design and development.

DEFINE: USER FLOWS

Next I mapped out the overall user journey for the MVP product. I have went through a few working sessions, taking in feedbcak and making adjustmets.

PRIORITIZATION FOR MVP


Based on the working sessions and user flows it became clear that not all anticipated features will make the MVP version. We were taking tome required to build as the main decisive factor. And finally settled on these features:

  • add to cart button

  • cart side panel

  • dynamic cart icon

  • qty stepper

  • qty type dropdown

  • shapable product cards

  • shapable badge

  • items cards

  • side-mark per item card

  • payment options: CC, ASH, Apple Pay, PayPal

  • shipping options: standard and express

  • coupon field

DESIGN: LOW FIDELITY

As I documented the list of features for the MVP version I wanted to start quickly sketching them in low fidelity wires, and I decided to use whimsical for it, so I can quickly do happy path user flow and share with our team.

Low Fidelity

I went though a few feedback sessions with the product and dev team I made a fed adjustments based on our product and engineering feedback. Such as shipping options were too complex to include in the MVP, all payment options would be hard to implement, and CC payment getaway would have a UI that we would use instead of our own, stepper isn’t the most preferred option for our stakeholders, no editing is feasible at the order summary screen.

Design: High fidelity

I then moved into higher fidelity, using components that I was designing and documenting in the design system and also creating new ones based on the product needs.

I have been working in 3 main viewports: mobile, tablet and desktop. Reworking and iterating based on the feedback from our team until we landed on something that made or stakeholders and developers happy. At this stage the components and their behavior was determined and I was mainly focused on UI.

There were some changes at this point:
• we de-prioritized mobile design (I have started designing with mobile first approach). We understood from talking to our users that mobile device is very unlikely to be used for shopping by designers, it may be used to browse products, but designers will always need a bigger context of the design project for which they shop as well as bigger screen to make a final decision.

shipping was reduced to approximate estimate with requirement to get in touch with the vendor for final details and cost. As we talked with ur vendors and designers we realized that many f these unique and custom items take long to produce, they are heavy and require special delivery methods, as well as assembly. So it higly depends on the availability, distance and level of customizations to determine shipping cost and time. Designers do not mind to be taking an extra step (for the MVP version), since this is an industry standard currently.

we pivoted from sticky shopping panel to the pop up panel, that disappears after a few seconds. as we learned that our shoppers aren’t the regular e-com impulsive shopper, and they don’t appreciate the guidance toward the check out, which is a standard in e-commerce. Instead they will add many items and think them over, share with their client before they make the final purchase.

reduced all item details per item added in the panel to confirmation that the item was successfully added to cart. We realized that since our shoppers will be thinking and carefully considering all item aspects before making a final purchase there is no much value in providing extensive item details in the pop up cart. Our shoppers will have the option to review the cart and examine item details before they make the purchase a few times any way.

Our engineers were estimating stories for each components, back end data architecture, research on Woo Commerce and payment gateways. I was preparing for user testing to see if we got these foundational flows right. This was when our whole marketplace team was laid off. Unfortunately investors estimated that we wont have enough funds to build this marketplace platform, and the company made a difficult decision to pivot and focus all resources on their design tool vs marketplace. So unfortunately we didn’t get a chance to build this out.

This was a shock and a surprise for the whole company. Non the less we created a great MVP product roadmap, with design and initial implementation that could be picked up when the company is ready. The Design System would serve as a solid foundation on which any new designers can build upon.

Thank you.