Global rollout of the B2B site:
Worked with a team of fantastic designers and developers to create a new upgraded website see ca.ingrammicro.com. Along with other global rollouts. This new website offers Ingram Micro’s partners, customers and stakeholders from around the world a modern, innovative design for easily and quickly finding the information they need to manage their businesses and improve their experiences with Ingram Micro.
– Increase market share
– Expand customer base
– Increase profits
– Raise customer satisfaction rating
– Quickly and easily find the products that they need.
– Convenience of ordering anywhere on mobile and desktop.
– Flexibility and order tracking.
– Assess both the positives and negatives of past design wins, and review the steps that led you there.
Based on a heuristic evaluation of competitors sites we concluded that in order to cater to our target demographic and set ourselves apart from the competition, we needed to focus on creating a seamless and efficient experience. The process of finding items and checking out should be as simplified as possible.
We interviewed users about their experience with IMonline in Canada region. We also observed them initiate a purchase through their account and asked questions as they completed the tasks.
This was to better understand the needs for the Reseller when they are purchasing products. To learn the ‘why’ behind what works or does not work for users.
Research ppt working in collaboration with T3. https://mintflymedia.com/wp-content/uploads/2021/02/Ingram-User-Interview-and-Walkthrough-Insights-1-1.pdf
3 In-depth interview and walkthrough with three resellers. 2 resellers who gave written feedback.
- Users narrated their thought process as they initiated a purchase.
- As users thought out loud, we asked questions to learn more about their thought process.
Wireframes / Low Fidelity:
This connects the conceptual structure that we established through the previous steps, with the visual design of the site. We focused on the hierarchy of information.
Working with the dev team to ensure consistency between our designs and what the dev team was producing.
After finalizing the design system, we started creating the hi-fi mockup in sketch. I then got assigned to IoT where I worked with another group of talented product managers.
We are tackling the site first to serve two primary goals. First, it gives us a well-understood problem space in which to develop the framework for a new version of the marketplace from a technology and design perspective. Since we don’t have to be overly concerned with content or structure, we can focus on making sustainable choices that will carry us forward through the rest of the overhaul project. Secondly, it allows us to show immediate value to our stakeholders by providing a place for the US IoT team to post content that today either goes unposted or is posted to other, IoT-adjacent domains that do not provide the same SEO value and consistent experience that a fully-integrated blog can.
The site should consist of two primary pages, a “category” page and a “post” page. The category page acts as the landing page when someone first enters the blog, to display multiple posts when viewing a category or tag, and as the result of a search, likely with some minor differences between those use cases. The post page is the actual home of the content that populates the blog, with a few different layout templates depending on the content type. In all cases, the primary action we want the user to take is to reach out to our team through some means.
To reduce the design and development maintenance costs of the IoT Marketplace, the category page serves several functions. For now, the two key things it must provide are a “blog homepage” experience and a way to see a subset of available posts defined by a category or tag. The content should be arranged in strictly chronological order by default, but the CMS should support marking some specific posts as “Featured”, in order to specifically call them out on any category page. Since we are very likely to be dealing with limited amounts of content, we should avoid prominently displaying anything relating specifically to dates or to the total amount of available content (for example, prefer a simple “Next” or “Show More” button to a full pagination menu showing “Page 1 of 2”).
The homepage should be visually appealing and entice the user into diving into whatever piece of content they find most interesting. To achieve this, we should strive for a balance of showing a good range of content immediately with not crowding the content together, giving each post room to breathe. The blog homepage should be accessible from any other page in the blog.
Category or Tag Page
This page is accessible primarily by clicking on any tag or category from any post, or by using any blog-specific navigation such as a category menu or a list of popular tags.
While the post page has several different variations, at its core it is a content-first page designed to inform the reader and get them excited about IoT generally and talking to our IoT country teams specifically. The content on these pages will be primarily driven by the marketing apparatus of the various IoT country teams, but we should provide a strongly opinionated layout, to guide them in best practices as to how to present their content and maintain a globally consistent look and feel. The content types that should be present can be broken down into a few broad categories:
Composed primarily of basic articles, case studies, and primers, these are text-heavy content types that should be familiar to anyone who has seen a blog in the last decade. For certain types (case studies and primers especially), the same content will be duplicated into a PDF format that should be downloadable at the end of the post.
Media is a potentially broad category consisting of content like infographics and videos. These are likely very short posts, focused around an embedded piece of content, along with a link to download a copy of that content when relevant. Text is likely to be minimal (except for video transcripts at some point in the future, potentially).
The primary audience for creating and updating content is the relatively non-technical users of the various marketing resources available to the IoT country teams. The editing experience should feel as similar to content creation tools that they are familiar with as possible (reference tools such as Wordpress, Hubspot, and MS Word). The user should have easy access to well-designed atomic elements that can be added to their content to create a visually pleasing content consumption experience. These should include but are not limited to a full range of headings, text variations such as bold and italic, links, pull quotes, horizontal rules, call to action buttons, and media such as images and videos. In the case of rich media, the user should have the ability to specify any important attributes such as sizing, alt text, or captions.
Nuts and Bolts
Both types of page should strive to be as performant as possible. All best practices should be followed with regards to both SEO (proper H1/title/meta/etc. tags) and accessibility (alt text, ARIA, etc.). Care should be taken to ensure that the content creation and consumption experience works well for the environments in which we will operate, namely, a wide range of languages (including RTL like Arabic or Hebrew) and a wide range of browsers (namely Chrome, Firefox, Safari, Edge, and Internet Explorer 11, with potential additions of regional browsers like UC if/when we expand to markets that require it)