<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Wayne HSU - Medium]]></title>
        <description><![CDATA[The experience in independently designing the products from start-to-finish and leading the UX improvement on the large-scale products. - Medium]]></description>
        <link>https://medium.com/wayne-hsu?source=rss----12a258b89fe0---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Wayne HSU - Medium</title>
            <link>https://medium.com/wayne-hsu?source=rss----12a258b89fe0---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 07:34:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/wayne-hsu" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[製造業複雜軟體的使用者體驗困境｜智慧型製造SaaS]]></title>
            <link>https://medium.com/wayne-hsu/%E8%A4%87%E9%9B%9C%E8%A3%BD%E9%80%A0%E6%A5%AD%E8%BB%9F%E9%AB%94%E7%9A%84%E4%BD%BF%E7%94%A8%E8%80%85%E9%AB%94%E9%A9%97%E5%9B%B0%E5%A2%83-%E6%99%BA%E6%85%A7%E5%9E%8B%E8%A3%BD%E9%80%A0saas-7f379fe4754e?source=rss----12a258b89fe0---4</link>
            <guid isPermaLink="false">https://medium.com/p/7f379fe4754e</guid>
            <category><![CDATA[ui-ux-designer]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[optimization]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[case-study]]></category>
            <dc:creator><![CDATA[Wayne Hsu｜徐偉]]></dc:creator>
            <pubDate>Sat, 20 Nov 2021 12:22:41 GMT</pubDate>
            <atom:updated>2023-01-17T02:41:52.245Z</atom:updated>
            <content:encoded><![CDATA[<h3>製造業複雜軟體的使用者體驗困境｜智慧型製造SaaS的UI/UX案例分析</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6uueefUMM7K5XlcD2vaJgQ.png" /><figcaption>- 本文部分内容已按保密協議調整 -</figcaption></figure><h3>概述</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u1P-4b5YFj08FuQpaucXVw.png" /><figcaption>- 提昇生產合作效率的SaaS、約6個模組筆電端做計畫+手機端做執行的搭配、APP子功能100+個 -</figcaption></figure><p>該平台屬於一家在上海於 2017–2020 年間極速成長的公司，員工人數在 3 年間從數 10 人擴張到 200 多人，主服務是個運行在「筆電、平板與手機」、幫製造業解決「工廠生產流程合作問題」的「SaaS」，隨「業務量短時高速成長」，長期偏重功能開發的策略讓平台的不友好體驗漸漸浮現。</p><h3>角色</h3><p>我的角色是主導「UX 全面優化」並與「6 位產品經理、12 位客戶成功專員、15 位工程師、1 位 UI 設計師」協調溝通，主負責從「專案發起」到「結果追蹤」，包含「專案管理、會議組織、使用者調研&amp;體驗設計」。</p><blockquote><em>1. 調查、分析、整理需求並定義問題</em></blockquote><blockquote><em>2. 實地訪查「焦點工廠」進行使用訪談核實問題</em></blockquote><blockquote><em>3. 繪製「使用者流程圖」與「低保真原形」向相關部門組織溝通會議</em></blockquote><blockquote><em>4. 產出「產品說明文檔」，並與客戶成功與研發部門評估可行性</em></blockquote><blockquote><em>5. 製作「可點擊 Prototype 」輔助客戶成功專員進行易用性測試</em></blockquote><blockquote><em>6. 排定「 Roadmap 」和「切分階段」輔助工程師訂定開發期程</em></blockquote><blockquote>7. <em>與UI設計師合作製作「高保真 UI 原形圖」</em></blockquote><blockquote><em>8. 與測試工程師、UI 設計師開上線前的會議審視視覺與流程</em></blockquote><blockquote><em>9. 追蹤後續客戶使用結果並持續帶回使用者回饋</em></blockquote><h3>挑戰</h3><blockquote><strong>一線使用者：「我的工作是完成任務、不是學習你們的平台怎麼使用…」</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fETOBkhAQu0J34bAapq4hQ.png" /><figcaption>- 原產品中複雜的資訊結構與導航系統 &amp; 使用者反應 -</figcaption></figure><p>製造業「生產流程」根據生產的產品與物料常常千變萬化，再加上常有依照「每次訂單欲生產的品項不同」去重新制定的習慣。因此該平台的「功能彈性多元」始終是一大優勢，直到「不好用、太複雜」的聲音愈來愈大聲。</p><p>我的任務是讓「工廠各部門角色的使用者」都能「快速、無礙使用」，並讓系統的功能多元靈活再次成為優勢。</p><blockquote><em>最高目標：</em></blockquote><blockquote><em>1. 讓各部門職位使用者快速無痛地適應各自流程<br>2. 將大量訊息依據使用情境去精鍊出必要的部分<br>3. 幫助平台後續迭代奠定使用友好的發展基礎</em></blockquote><h3>需求</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QigCyGLOuCY5NU6IvgDuCg.png" /><figcaption>- 150條UX需求 (最終整理結果)：從具體到抽象的匯集整理過程 -</figcaption></figure><p>2019 年起，「平台體驗退步」的聲音開始頻繁流進 CEO 的耳朵，我與負責維繫客戶關係的客戶成功部門 (CS) 發起了「跨所有類型工廠」的調查，一舉帶回了 150 項「複雜程度不同、需求大小迥異」的 UX 優化反饋。</p><p>我從 150 項需求中逐步分析、整理，進而歸納出了最普遍被提起的 2 大痛點。為此，我很好奇為什麼會收到這麼多關於「找東西」的需求？而使用者們究竟都在「找什麼」？</p><blockquote><em>1.「請幫我把 xxx 功能擺得明顯一點，每次都要重找」。<br>2.「請幫我把 xxx 框改得大一點，我一直找不到我需要的資訊」。</em></blockquote><h3>調研/發現</h3><blockquote>：使用者在工作流程中，真正需要的是什麼？</blockquote><p>我請教「各領域專攻」的 CS 專員，同時也參考 CS 部門歸納「以工廠類型為劃分」的「Persona」，先剖析客戶們「個別製造領域」的大業務流程、再細化到部門上下游流程、以至部內各角色的流程。</p><p>從龐大的數據中挖深「各類型工廠、各部門」的「業務流程」與「系統流程」關係並歸納出以下圖表，瞭解到「各工廠部門間的大流程雖相似」，但部分流程或因該平台系統架構未支援，而客戶未能在平台上作業。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SfAR82XEhSTsz1spKxSMTw.png" /><figcaption>- 大流程相依性：業務功能對照流程圖 -</figcaption></figure><blockquote><strong><em>客戶對平台的「依賴性」</em></strong></blockquote><blockquote><strong><em>高</em></strong><em>：平台覆蓋大多步驟，客戶能順利使用，但年長使用者找東西較艱辛<br></em><strong><em>中</em></strong><em>：平台僅覆蓋部分步驟， CS 暫靠人工手段繞過的解法換工廠或不適用<br></em><strong><em>低</em></strong><em>：平台僅覆蓋少許步驟，或底層架構未能支援而平台間數據難以對接</em></blockquote><p>-</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*npkLTY0mM8HK171xsVrSUg.png" /><figcaption>- 家具版材、化工製藥、電子組裝，系統以 QR Code 追蹤記錄物料在生產過程中產生的所有數據 -</figcaption></figure><p>發現即便是「處理類同物料的工廠」，底下「各部門」對平台的依賴性也完全不同，主因是，該平台在適應各種類工廠「原物料不同、處理流程截然不同」的挑戰下衍生了 2 個痛點：</p><blockquote><strong><em>類同功能</em></strong><em>：各種工廠的同角色在處理同類工作時需辨識多種「僅在細微流程上有些許差異」的類同功能。</em></blockquote><blockquote><strong><em>大量資訊</em></strong><em>：生產流程各階段對物料記錄的資訊隨客戶工廠類型增加、而在平台上大量成長，同角色需辨識的資訊也進而倍增。</em></blockquote><p>-</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GKPtOL321jr6cy29VhH-_A.png" /><figcaption>- 細部流程探索：功能交互流程圖 -</figcaption></figure><p>分析完客戶各流程的對比後，為讓團隊能更有依循地聚焦處理挑戰，我決定將當前平台上的 6 個模組在各種工廠「具體的分歧點」總結出來：</p><blockquote><em>1. </em><strong><em>行政業務</em></strong><em>：流程的「繁簡程度不同」衍生使用「第三方 ERP (未串接) 」的工廠只能靠人「手動互通數據」，或各種單據混用，例：原料入庫單同時也當採購單。</em></blockquote><blockquote><em>2. </em><strong><em>資料數據</em></strong><em>：需要的「資料屬性不同」衍生需記錄的資訊大不相同，此為「訊息量激增點」，也是底層架構未能快速變通處，例：多層 BOM 與單層 BOM。</em></blockquote><blockquote><em>3. </em><strong><em>質量檢驗</em></strong><em>：處理的「原物料不同」衍生「檢驗方式、標準」五花八門，記錄的詳細程度也大不相同，甚至有「每次標準都只能生產當下決定」，例：陶瓷當下選一個當合格品。</em></blockquote><blockquote><em>4. </em><strong><em>生產執行</em></strong><em>：生產的「產品種類不同」衍生生產方式有的一條流水線、有的多點同時進行、有的複合型，管控進度的嚴謹程度不同、讓系統流程高度分歧，例：SOP 流程生產跟一般流程生產。</em></blockquote><blockquote><em>5. </em><strong><em>物料管理</em></strong><em>：管理的「原始物料不同」衍生系統中多組「類同功能」，而同功能又需「人眼辨識細部分支」，導航結構已然超過 5 層，例：物料移轉過程。</em></blockquote><blockquote><em>6. </em><strong><em>設備管理</em></strong><em>：設備的「依賴面向不同」衍生有的需要數據雙向串接，有的僅需單方接收，採集的數據也不盡相同，有的更需進一步利用系統反控設備，例：化學加工品需針對質檢狀況控制機具調配方。</em></blockquote><p>-</p><p>另一方面，當我試圖繼續細化歸納「不同工廠」的「各角色職能」時發現，根據「工廠大小、訂單內容」不同，單名角色的工作流程也會產生變化：</p><blockquote><em>1. </em><strong><em>固定流程 (多)</em></strong><em>：單部門單職能、始終一致<br>2. </em><strong><em>變化流程 (次)</em></strong><em>：單部門多職能、每週輪替<br>3. </em><strong><em>複合流程 (少)</em></strong><em>：跨部門多職能、身兼多職</em></blockquote><blockquote>：想歸納出「各職能最簡短流程」幾乎不可能</blockquote><p>-</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kvUswCZw78aear-1UrSQNg.png" /><figcaption>- 實地訪談調研；現場使用概況 -</figcaption></figure><p>為瞭解使用者「找東西的實際痛點」，我跟 CS 發起了到「焦點客戶工廠」的實地調研，跟著該工廠配合著平台完整跑過多遍生產流程，並同時記錄觀察各階段抓取到的痛點與發現。</p><p><strong>人員</strong>：</p><blockquote><em>1. 手機端青年使用者在 25–35 歲為少數 (大多為高中畢業)，而年長使用者在 40–65 歲需配戴老花眼鏡者為多數 (大多為小學、國中畢業)，普遍相對低科技適應而需 CS 輔助。</em></blockquote><blockquote><em>2. 筆電端使用者年齡多在 28–35 歲之間，高度科技適應，除資訊量有時較多的查找問題外，大多使用無礙。</em></blockquote><p><strong>設備</strong>：</p><blockquote><em>3. 手機端從 </em><strong><em>7 吋 iPhone </em></strong><em>到 </em><strong><em>13 吋平板</em></strong><em>都有，走動、定點使用皆有。</em></blockquote><blockquote><em>4. 筆電端多使用 </em><strong><em>13 吋 Windows 筆電</em></strong><em>，多定點。</em></blockquote><p><strong>功能</strong>：</p><blockquote><em>5. 各職能使用者「每週」使用功能數量大致固定、順序不定 (單職能 5 個到多職能 13 個)，不同職能彼此少交集 ，唯有同週身兼多職者例外。</em></blockquote><blockquote><em>6. 完成同項任務時，平台使用者在找功能或資訊時，最極端狀況耗費超過 45 秒 (對比平台上線前在紙本上查找只需 25 秒)。</em></blockquote><h3>現狀</h3><blockquote>：對一線使用者來說，過程中愈快形成「標準化作業」就離「做快、搶時間賺薪水」愈近。</blockquote><p>在製造業裡，一線使用者的聲音最不容易被聽到，但最常使用產品的卻是他們，他們的表現幾乎最直接決定工廠的生產效率，對此，他們最關鍵的痛點是「適應平台的時間佔據了完成工作的時間」，接著我定義了下當前挑戰：</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v0WZnbG3oyXmza8kn1qRJg.png" /><figcaption>- APP每個任務，使用者得辨識「導航大類(2) &gt; 次級類別(20) &gt; 類別子功能(76)」，一天重覆 50 次以上 -</figcaption></figure><ol><li>現有導航未能支援工廠靈活的情境</li></ol><blockquote><em>1.1. </em><strong><em>層級結構多</em></strong><em>：使用者花費較多時間在尋找、而不能專注執行任務<br>1.2. </em><strong><em>大導航失效</em></strong><em>：不同使用者需要的資訊功能皆不同、都希望放到最上層</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*awLMvaOEeiH3m7aqXaiiHw.png" /><figcaption>- 在超過 30 條的資訊裡找需要的 1、2 條，有時因有限的響應設計而無法完整看全 -</figcaption></figure><p>2. 靈活的情境促使衍生大量的資訊</p><blockquote><em>2.1.</em><strong><em> 未過濾的資訊</em></strong><em>：應各工廠需求而訊息漸漸增加，各項訊息得靠人眼過濾<br>2.2. </em><strong><em>有限響應設計</em></strong><em>：筆電端的資訊因有限的響應式設計常未能完善展示</em></blockquote><h3>方案</h3><blockquote>：把「決定」與「時間」還給使用者，讓他們決定自己的流程、也精鍊資訊量到「足夠」即可。</blockquote><p>對工廠大多使用者來說「展現所有資訊」與「資訊分層展示」都較易造成困惑，怎麼讓每個使用者都只看到自己要的、同時又過濾掉不必要的訊息？我決定「<strong>提高自訂化程度</strong>」，鎖定從「<strong>導航結構</strong>」與「<strong>資訊架構</strong>」著手：</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l_fnRxaUQldpoweiMzD_yw.png" /><figcaption>- 利用「導航再聚合」和「書籤」把使用者直接帶到「第3級導航：類別子功能」 -</figcaption></figure><ol><li>導航方式重構</li></ol><blockquote><strong><em>功能以「部門」再聚合（筆電端）<br></em></strong><em>工廠部門間流程大多固定、唯部內人員職能多變化，平台按「生產、檢驗、物料、設備、基礎設定」的導航漸不足支援中大型工廠「各部門嚴格控管部內數據、權限」和「鎖定部門關鍵字找功能與相應設定」的需求。</em></blockquote><blockquote><strong><em>功能以「職能」做聚合（手機端）<br></em></strong><em>許多工廠常配合訂單將固有職能重新組合出新流程，未此決定將「各工廠最常見 13 種職能」作為預設聚合功能的依據，另外「高亮最近 3 筆執行任務」幫助各角色在職能變化時定位先前正執行的任務。</em></blockquote><blockquote><strong><em>功能書籤（筆電端＆手機端）</em></strong><em><br>導航調整讓平台更貼近實務作業外，為達成讓使用者相信「他們能更容易掌握手機端的工具」與「因應需要制定自己當前最必要的工具組合」，我提供了「書籤」的功能，讓使用者自訂自己的置頂導航。</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*spv1AWH2cnA6ngDjnKPtaw.png" /><figcaption>- 資訊展示量自定，並提供多種適配介面空間功能 -</figcaption></figure><p>2. 資訊展示自訂</p><blockquote><strong><em>自訂展示個人最需要資訊（筆電端＆手機端）<br></em></strong><em>為在卡片與列表上提供各職能所需資訊，展示單一物料 30 多項訊息、與連帶生產過程中疊加的變成一大挑戰，實務上，使用者大多僅需「</em><strong><em>辨識特定幾項資訊</em></strong><em>」便能做出決策，為此，我提供「資訊展示開關」的功能。</em></blockquote><blockquote><strong><em>提高空間自由分配彈性（筆電端）<br></em></strong><em>使用 13 吋筆電端的使用者大多需在有限的空間處理比手機端使用者更多的訊息，為此提供了「表格欄寬自訂」與「多種版面配置」的設計以強化展示，另外增加</em><strong><em>「表頭拉把」</em></strong><em>給多仰賴滑鼠拖曳滑動的 Wnidows 使用者。</em></blockquote><h3>執行</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ojLeaf6ENfvyvBh92Th3tA.png" /></figure><p>執行階段共組織了「4 次、每次 1 小時」的會議，會議全程「錄音」以幫助與會者當下將注意力著重在「溝通」而不需因記錄而分心、二來所有成員可隨時回顧決策內容、三來亦能用作後續改良自己表述能力的材料。</p><p>-</p><h4><strong>Wireframe(草稿圖)</strong></h4><p><strong>第一次會議「定調方案」</strong>，我以 Xmind 將新版導航製成心智圖、並用 Axure PR9 繪製了 Wireframe，此次優化跨及 6 個模組與各負責的產品經理，目的是與產品經理們「報告影響範圍」與「展示細節邏輯」並最終定調共識。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QSAlVuchHhLNBTIlBzV4tw.png" /><figcaption>- APP &amp; 開發邏輯注釋 -</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*llp0aHwbv5u-_2XeCsV4Tg.png" /><figcaption>- WEB &amp; 開發邏輯注釋 -</figcaption></figure><p>-</p><h4><strong>Prototype(可點擊原形)</strong></h4><p><strong>第二次會議「測試方案」</strong>，使用 Axure PR9 製作了「可點擊 Prototype」展示給多位 CS 專員，並請他們以各自負責種類工廠的專業角度「評估方案」，並後續帶到現場找各部門<strong>至少 2 名重點使用者</strong>進行「易用性測試」。</p><blockquote><strong><em>一週後的測試成果令人振奮</em></strong></blockquote><blockquote><em>1. 40 歲以下使用者上手完全無礙<br>2. 45 歲以上使用者僅需口頭指導 1、2 次後亦能上手<br>3. 65 歲以上使用者需請 CS 輔助逐步教學</em></blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FFXJgLhO_Zb8%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DFXJgLhO_Zb8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FFXJgLhO_Zb8%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/78c42e7baa6854b6641500b5dba97468/href">https://medium.com/media/78c42e7baa6854b6641500b5dba97468/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FiVNAh9ZpLGI%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DiVNAh9ZpLGI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FiVNAh9ZpLGI%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/896f16b5015ed4ba30d1f35fe70c5110/href">https://medium.com/media/896f16b5015ed4ba30d1f35fe70c5110/href</a></iframe><p>-</p><h4><strong>Roadmap(發展期程圖)</strong></h4><p><strong>第三次會議「排期開發」</strong>，我共有 2 個月的時間完成該次優化，與「工程師」們進行「技術評估」講解方案與排定期程。Q4 的方案最終切割成 2 階段開發、一次上線，並將「產品說明文檔」上傳到 Jira 和 Wiki 共享。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dNB1Avd8jPC31f53fabBxg.png" /><figcaption>150條需求按優先級與可行性分成4階段進行</figcaption></figure><p>-</p><h4><strong>UI Design(介面設計)</strong></h4><p><strong>第四次會議「確認結果」</strong>，為確保開發成果盡可能貼近設計，上線當週與「工程師、設計師」審視最終成果，請工程師向大家「演示操作流程」。因應 APP 訊息展示自訂跨及 6 個模組工程較大，初步權衡先在資訊量膨脹最明顯的「物料」模組先行開發，總地來說，幾乎全部的設計最終都順利上線！</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E_HHSjXoRS-mJRD4-VU1aQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*seLoV0thqI8sVWM_mPVtDA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GyIWw0hT52t5hdRL6Pe15Q.png" /></figure><h3>結果</h3><blockquote>一線使用者：「對嘛！早就該改了，都跟你們提多少次了，這樣快多了」</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8QY94Lj87gR9yVev0zngvg.png" /></figure><p>方案上線後，要給各工廠統一培訓與試跑驗收，有幸 CS 們熟知各自工廠生態，讓客戶適應期僅僅「一週」、非常快速，雖仍需仰賴後續優化所有「功能流程」才可能從根本加速，或是積木化切細功能的組合讓系統能「業務自定義」，但以當前收獲的成果來說，確實讓多數的客戶「大讚改得好」。</p><blockquote><em>1. 一次自訂定的結果最少使用 1 週、</em><strong><em>最久持續 2 個月</em></strong><em>。<br>2. 找東西的最極端時間</em><strong><em>降至 10 秒 (原先 45 秒)</em></strong><em>。</em></blockquote><h3>回顧</h3><p>最後，被新冠肺炎疫情影響快速返臺，無法持續第 3、4 階段的次要優化。但調研成果與使用者反饋已完整地帶回公司與各部門共享，並在專案進展過程，努力輔助產品經理們，在未來的功能設計上能有更多「使用者」的角度可依循，並奠定平台良好 UX 體驗的初步基礎。</p><p>在這專案我達成了：</p><blockquote><em>1. 歸納整理了龐大、複雜的工廠使用者流程與平台功能流程<br>2. 把第一線使用者的聲音大幅度帶回產品開發上游共享所有部門<br>3. 在產品與工程部門強化了 UX 體驗的價值，提高重視程度<br>4. 在平台上重構複雜的導航結構與大量資訊架構的方式</em></blockquote><h3>感謝你的時間與觀看</h3><p>如過有任何想法與指教歡迎在留言區一起討論<br>你也可以在 <a href="http://www.linkedin.com/in/waynehsu0909">LinkedIn</a> 和 <a href="https://www.behance.net/waynehsu">Behance</a> 和 <a href="https://www.cakeresume.com/a870588">CakeResume</a> 上找到我～</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f379fe4754e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wayne-hsu/%E8%A4%87%E9%9B%9C%E8%A3%BD%E9%80%A0%E6%A5%AD%E8%BB%9F%E9%AB%94%E7%9A%84%E4%BD%BF%E7%94%A8%E8%80%85%E9%AB%94%E9%A9%97%E5%9B%B0%E5%A2%83-%E6%99%BA%E6%85%A7%E5%9E%8B%E8%A3%BD%E9%80%A0saas-7f379fe4754e">製造業複雜軟體的使用者體驗困境｜智慧型製造SaaS</a> was originally published in <a href="https://medium.com/wayne-hsu">Wayne HSU</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[服務業櫃檯互動行銷的新契機｜B2B行銷平台的UI/UX案例分析]]></title>
            <link>https://medium.com/wayne-hsu/%E6%9C%8D%E5%8B%99%E6%A5%AD%E6%AB%83%E6%AA%AF%E4%BA%92%E5%8B%95%E8%A1%8C%E9%8A%B7%E7%9A%84%E6%96%B0%E5%A5%91%E6%A9%9F-b2c%E8%A1%8C%E9%8A%B7%E5%B9%B3%E5%8F%B0%E7%9A%84ui-ux%E6%A1%88%E4%BE%8B%E5%88%86%E6%9E%90-a99128a941c4?source=rss----12a258b89fe0---4</link>
            <guid isPermaLink="false">https://medium.com/p/a99128a941c4</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[retail]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Wayne Hsu｜徐偉]]></dc:creator>
            <pubDate>Sat, 20 Nov 2021 12:22:24 GMT</pubDate>
            <atom:updated>2022-12-25T12:02:15.309Z</atom:updated>
            <content:encoded><![CDATA[<h3>服務業櫃檯互動行銷的新契機｜B2C行銷平台的UI/UX案例分析</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JIrR1ioqoViCICWYzVzFaQ.png" /><figcaption>- 本文部分内容已按保密協議調整 -</figcaption></figure><h3>概述</h3><p>2014年，台灣服務業的數位行銷多仰賴APP進行，市面的客製APP比比皆是，但一個品牌、一個APP「對品牌來說迭代成本高；對顧客來說需要強誘因」，品牌有時為特定活動開發的APP，顧客也容易一拿到優惠後就移除。</p><p>故該公司開發了個「以手機號碼做帳號、不需APP」的「櫃檯互動行銷」平台，為各種體量的連鎖品牌提供新解套，在我加入團隊時，該平台已然以「集點行銷」運行於全台200多家實體店面的櫃檯，接下來想進軍全臺年流動額達40億台幣的「票券行銷」。</p><h3>角色</h3><p>我的角色是設計這新「櫃檯互動票券系統」，並與「1位產品經理、1位客戶成功專員、6位工程師」合作，負責「新系統的初期定義、中期設計、後續迭代」，包含「使用者調查研究、使用者體驗設計與介面設計」。</p><blockquote><em>1. 探索、調研台灣消費者使用「票券」的業務場景<br>2. 分析、整理需求並定義問題<br>3. 進行使用者訪談，歸納簡易「人物誌」幫助團隊決策<br>4. 以便條紙搭建「使用者流程」與「業務場景調研」彙整數據<br>5. 以「高保真原形」製作「Prototype」進行易用性測試<br>6. 產出移動端「介面設計視覺規範」與「響應式開發規格標註」<br>7. 實地游擊訪查各客戶的「票券使用狀況」與「持續優化迭代」</em></blockquote><h3>挑戰</h3><blockquote>台灣「櫃檯行銷」特別焦慮，顧客與店員都處在「如我太慢、後面人會不滿」的狀態</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*mHS9PeU4t4qtM47TBh3kTw.jpeg" /></figure><p>台灣在習慣「不給人添麻煩」的社會氛圍中，讓平均結帳時間「30–60」秒的櫃檯行銷特別焦慮，新的「票券功能」要在這前提加入「額外流程」並輔助品牌進行「票券行銷」以「圈住熟客、擴展新客」。</p><blockquote><em>我的任務是：</em></blockquote><blockquote><em>1. 發現、定義新系統的所有業務場景<br>2. 擴展能幫助品牌增加行銷玩法的功能<br>3. 適應櫃檯必需極速便捷的操作體驗</em></blockquote><h3>需求</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n4qVnICxRbChFccNiwVDUg.png" /><figcaption>- CS歸納客戶的顧客數據(左)、APP刪除率統計(右) -</figcaption></figure><h4>品牌的需求</h4><p>當時台灣「電子支付未普及」變相促使品牌的票券行銷多以「紙本」進行，市面線上線下整合數位票券的平台也少，幾個成熟產品都是「客製APP」、而較知名的某免費競品則「無法展示品牌的形象識別」。</p><p>撈出公司數據得知熟客對營業額的貢獻是散客的<strong>2.7</strong>倍，因此客戶更樂意行銷「熟客」，我們發起調查從各品牌客戶帶回需求，跨及「餐飲、零售、服飾、美容、健身、住宿、租賃、醫療」，他們大部分的共同反饋是：</p><blockquote><em>1. </em><strong><em>市面方案不便</em></strong><em>：花錢做APP成本高，且APP刪除率在下載一天後便達38%，而紙本人工管理耗時耗人力</em></blockquote><blockquote><em>2. </em><strong><em>抓住新老顧客</em></strong><em>：希望能藉由票券分享、口碑相傳帶來新客，也期望能藉由「票券」做「會員儲值」增加熟客回流率</em></blockquote><blockquote><em>3. </em><strong><em>精準數據追蹤</em></strong><em>：想自訂各種票券活動與「數據追蹤成效」以深層經營熟客，因應紙本票券僅能憑藉猜測評估效益</em></blockquote><p>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rY0k7yc8mBnlepJjdrOtiQ.png" /><figcaption>- 利用Post-It視覺化蒐集來的數據＆鋪開與團隊探討 -</figcaption></figure><h4>使用者的需求</h4><p>從客戶的顧客中找了10位在「18–55歲」的使用者進行訪談以了解他們對使用票券的習慣，瞭解到「有習慣用票券」的人多半對「優惠精打細算、樂愛組織團購」，另一類「無習慣用票券」多是被前一類人「送禮」的結果。</p><blockquote><em>1. </em><strong><em>行業分帳障礙</em></strong><em>：有時同品牌為防高單價票券偽造；或因直營、連鎖拆帳問題，票券常無法「跨店使用」</em></blockquote><blockquote><em>2. </em><strong><em>紙本麻煩不便</em></strong><em>：大多票券仍是「紙本」，留存一多較易佔滿錢包空間，於結帳時出示亦不容易翻找，而「發票」類有時則易於洗衣服過程損失</em></blockquote><blockquote><em>3. </em><strong><em>APP難用草率</em></strong><em>：顧客傾向不為單一優惠就載新APP。此外，當前市面許多數位券的兌換方式仍是「易被誤觸、且不可逆」的鈕</em></blockquote><h3>調研/發現</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fuJAoq84oFRTeu6oNB0eyQ.png" /><figcaption>- 票券情境與行為關係調研 (最終調研成果累積) -</figcaption></figure><h4>市場的現狀</h4><p>為探索市面現行的「紙本票券」都如何運作？我廣泛收集各種流通於市面上「以行銷為主」的票券，並以「活動形式、用途」去歸納表格。服務業票券行銷基本都是「預售服務、商品」或「下次兌換的優惠、代金」的模式。</p><blockquote><em>1. </em><strong><em>優惠券</em></strong><em>：主為「零售、服飾」用於「吸引新舊顧客」居多，故活動適用的條件變化相對較多</em></blockquote><blockquote><em>2. </em><strong><em>禮金券</em></strong><em>：主在「連鎖品牌」盛行，含金量高達40億台幣，多為企業節慶或年終作為犒賞發放給員工</em></blockquote><blockquote><em>3. </em><strong><em>兌貨券</em></strong><em>：主為「餐飲、健身、美容」愛用，鎖定預售商品、服務以「抓住熟客」提高回流率</em></blockquote><p>-</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hmA92PRb9x1QtfB5TaXBnQ.png" /><figcaption>- 櫃台前各角色旅程圖 (最終調研成果累積) -</figcaption></figure><h4>使用者行為調研</h4><p>我們鎖定票券活動玩得最頻繁的「餐廳、飲料」，並到店觀察現場使用者、與錄影「使用紙本票券的顧客」。透過內部工作營，我們以便條紙製作使用者旅程著眼觀察「行為」，並同時追蹤每個步驟的「耗時」。</p><blockquote><em>1. </em><strong><em>活動參與率</em></strong><em>：櫃前參與新活動機會可分「結帳後立即離開(低)」與「結帳後享受服務、排隊候餐(高) 」</em></blockquote><blockquote><em>2.</em><strong><em>活動黏著性</em></strong><em>：80%的消費者不介意用「個人資料」換取適合的「優惠折扣」，而35%的消費者「一週至一個月」內會「返回同店」二次消費</em></blockquote><blockquote><em>3. </em><strong><em>行銷觸發點</em></strong><em>：櫃前主分「店員推銷」與「顧客發現」，行為可用「獲得」與「兌換」歸納</em></blockquote><blockquote><em>4. </em><strong><em>行銷緊迫度</em></strong><em>：拼流動率的「飲料最高、餐廳次之」，而美容、健身、醫療「服務時間長」而較低</em></blockquote><h3>現狀</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i2VlcinxHttqTO2DBulNmg.png" /><figcaption>- 固有模式：手機做帳號(左)、櫃檯平板互動＆電子印章核銷(中)、簡訊導引交易明細載體(右) -</figcaption></figure><p>新的票券功能會承襲該該公司的固有模式，但該模式當前應用的「集點活動：給點/扣點」的情境在「點數變化」與「發票明細」都相對單純，為此我大致定義了下當前的挑戰：</p><blockquote><em>1. </em><strong><em>票券情境</em></strong><em><br>1.1. 活動「玩法多元」，根據業態不同，種類、形式各有習慣<br>1.2. 活動「品項多種」，且「各品項都有獨立數量 (屬性)」</em></blockquote><blockquote><em>2. </em><strong><em>顧客聯繫</em></strong><em><br>2.1. 以簡訊做「票券明細」載體，內容成本大增，得發展新載體<br>2.2. 客戶想熟客帶新客，票券若想分享給未註冊顧客得依賴簡訊</em></blockquote><h3>執行</h3><blockquote>該公司商業模式幾乎無「前人可參考」，我們算是這新領域的探路人</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zXtXi5hoC3n-p_Ih3NmqLw.png" /><figcaption>- 將公司過往使用者數據＆調研資料彙整了簡易Persona -</figcaption></figure><h3>票券平台：Tick</h3><p>我結合訪談使用者在「食、衣」方面對「行銷態度」與「消費習慣」並整理成「人物誌」幫助執行決策，也搭配CS調出的數據歸納出了三類消費者「<strong>嚴格型(10%)、計畫型(60%)、感覺型(30%)</strong>」。為儘快驗證功能，我們前期目標鎖定去搭配客戶的「行銷活動」來進行「3個月的試運行」：</p><p>.</p><h4><strong>1. 易用性測試</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bxUHMltUY_LNN6eqEwnRfA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o8ONOD_2wu-4Tt09YN48qQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XdfbRxFWTDEM46HBvxW4Kw.png" /><figcaption>團隊命名該功能「<strong>勾勾券 (TICK) </strong>」，取自於它最標誌性的行為，在平板上「勾起」票券</figcaption></figure><p>平板大多「面對顧客」而店員輔助，視覺溝通上的目標就是盡力達到「秒懂」，讓各年齡層顧客都能直覺使用。我製作了最初版本的<strong>高保真原形</strong>進行易用性測試，訪談過後得到的回饋：</p><blockquote><strong><em>精確資訊展示</em></strong><em><br>顧客大多僅專注在「名稱、數量」兩者資訊，其餘次要資訊如「有效期限、票券簡介、流水序號…等」訊息則較常不經意忽略，這與我們早期假設「顧客可能會在平板前慢慢挑選購買」相違背。</em></blockquote><blockquote><strong><em>精準語意溝通</em></strong><em><br>勾勾券最主要的兩個情境是「存入」與「使用」票券，可「存入」易被視為「操作鈕」且有暗示「免費」的意涵；而「使用」則是顧客「未有任何券前」不會聯想到「使用」，在訪談後初步調整成「購買」與「我的」。</em></blockquote><blockquote><strong><em>精鍊操作流程</em></strong><em><br>客戶單次票券增減的範圍常因業態不同而迥異，使用「＋－號：點加、點扣」的模式未能非常好的支援飲料客戶「家庭共同寄杯、一寄30多杯」的狀況，為此，也提供了「數字鍵盤：輸數量」的操作。</em></blockquote><p>.</p><h4><strong>2. 試運行實測</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JEzrQI2083c717LEXs30OA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*juTppcaG6DbcjElliwoj1Q.png" /></figure><p>易用性測試後，功能快速進入開發POC，並在最短時間內推上「親近客戶：餐飲、醫療、美容」的櫃檯去執行3個月的「試運行」，過程中每天如打仗一般、不斷收到品牌的意見反饋，小問題逐條逐優化，而有個主調整是：</p><blockquote><strong><em>清晰區分情境</em></strong><em><br>調研時了解到「櫃檯人事流動極快、店員不總能充分培訓」，為「大大減少UI辨識的負荷」，並最大化利用當前的試運行，便先將兩種情境都是紅色的「購買＆我的」分成「購買票券：紅色」與「我的票券：綠色」。</em></blockquote><p>.</p><h4><strong>3. 情境再省思</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2oafIVs9dmad_dSM3n2_CQ.png" /><figcaption>- 與產品經理2次游擊調研＆錄影 -</figcaption></figure><p>行為上，紙本票券的互動是「店員發1張(或1本套票)或寫在發票」給顧客，顧客下次回訪只需「遞1張(數張)或出示發票」給店員即完成。數位票券的確方便了「品牌」後續數據追蹤、分析、管理，但我們仍未將紙本「簡單、易用」的優勢在數位票券上帶回給「顧客」與「店員」。</p><blockquote><strong><em>店員是主使用者</em></strong><em><br>常參與活動的熟客通常「進店前已想好要用的券」，票券數位化後，顧客「遞券」變成「輸手機」，而後會「全交給店員」，意即「判斷給券/用券、選品項/數量、印章核銷、幫顧客登出」的操作會全在店員身上。</em></blockquote><blockquote><strong><em>兌換是主要情境</em></strong><em><br>集點的「領取使用比」與票券「相反」，在試運行跑了3個月後，公司內部數據發現，客戶票券活動多以「一次領、慢慢用」的模式來設計，數據反應領取使用比便常常是「1：10」，這提供了一個新的導航設計方向。</em></blockquote><blockquote><strong><em>密碼不總是需要</em></strong><em><br>我們假設票券總額關係顧客對帳號安全的顧慮，但後來發現顧客更在乎「券剩多少」而非安全性，我們觀察到某奢侈服飾品牌販售「單券萬元台幣」的儲值券，提供了店員一本「顧客密碼簿」條列了所有顧客密碼。</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uOpE0aHxT1__LCESqi35bw.png" /><figcaption>- 固定型套票(左)、大量型寄杯(中)、快速型優惠券(右) -</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nUESb3fRptKVJi2DWRplxw.png" /></figure><p>在這次的改版中，決定以「節省店員的負擔」為目標，從各業態的票券活動方式去「細化情境」，盡可能重現紙本票券的「簡單、快速」：</p><blockquote><em>1.</em><strong><em> 適應業態多情境</em></strong><em>：固定型套票適應長期定性活動、大量型寄杯輔助多品項數量的兌貨券、快速型優惠券支援消費後折扣優惠活動。</em></blockquote><blockquote><em>2. </em><strong><em>操作區分優先級</em></strong><em>：以「我的票券」作常態首頁，領券頁與其操作則需要時再彈出，給券方式亦新增「一鍵給予套票、註冊自動給予」等設定。</em></blockquote><blockquote><em>3. </em><strong><em>可開關密碼機制</em></strong><em>：仍保留密碼機制，但在後台的活動設定時可作為開關設定，並在平板上判斷「有票券減少」才需在核銷前輸入。</em></blockquote><h3>票券團購：Sharelink</h3><blockquote>鎖定「團購」情境，讓品牌來一波「熟客拉新客的病毒擴散行銷」。</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kX7ft_vGYbhPNUBylCeaAg.png" /></figure><p>以著「勾勾券」為基礎，我進一步設計了「票券分享功能」鎖定高利潤的「團購」情境，因應「情境相對單純」且「無櫃檯緊迫壓力」，除了「首次使用需略微引導」外，後續票券分享操作顧客多能適應。</p><blockquote><em>1.</em><strong><em> 團購情境</em></strong><em>：鎖定「餐廳飲料：單價低、購買數量高」的「團購活動」。<br>2. </em><strong><em>明細載體</em></strong><em>：作為票券系統的「交易明細載體」，並支援「票券分享」。</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SR36d6MSvbVSsyBR2iVkdA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e3pbDgF0aed1k51BVj0DKg.png" /><figcaption>- 撰寫了「響應式規格標註」文件輔助開發 -</figcaption></figure><h3>最終升級</h3><h3>整合收銀：JPOS</h3><blockquote>能不能「店員操作完POS機、就同時把所有點券給到顧客」？</blockquote><p>改版試運行1個月後，各業態「櫃前塞車」多有改善，但我們業務員注意到，大型連鎖餐飲在「人流量高峰」時，店員較容易「略過行銷活動」，為此，新的挑戰突然浮現：</p><blockquote><em>1. </em><strong><em>店員操作流程</em></strong><em>：是否能再次「大幅節省店員的操作負荷」？<br>2. </em><strong><em>顧客獎勵對應</em></strong><em>：如何讓顧客的「消費獎勵」與顧客自動對應起來？</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wq4U1AfcOuAghtxEplDX9g.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mcwOrDpb0mkNSCTtxMNFvQ.jpeg" /></figure><p>調研時知道「店員操作POS的教育訓練」是品牌的定性標準流程。為此我們開始嘗試切入一個新的方向，能否「店員操作完POS機、就同時把點券給到顧客」？</p><blockquote><strong><em>全新想法<br></em></strong><em>1. 點券平台與客戶的POS機串接，打通數據<br>2. 點券獎勵自動根據消費金額換算後傳送到平板 (後台做預先設定)<br>3. 點券獎勵做為「自由領取」則能增加隨機散客參與活動的機率</em></blockquote><blockquote><strong><em>調研回顧<br></em></strong><em>1. 餐飲的平均候餐時間，飲料為「45–120秒」、餐廳為「5–10分」<br>2. 喜愛精打細算的熟客本就習慣「主動參與活動」，鮮有錯失<br>3. 過往餐飲店員推集點，若顧客不參與則「點數視同作廢」或刪除</em></blockquote><p>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j1pIMklMoUoHnTYKQRHvqQ.png" /><figcaption>- 最終流程圖 -</figcaption></figure><p>結帳流水線上，店員普遍會引導結完帳的顧客站到特定區域，新方案的店員照舊順勢提醒「我們有XX活動，您可到這輸手機領您的點券」，便可回頭做產品、或是繼續為下位客人點單，最後，只剩下如何<strong>對應顧客與他的獎勵</strong>：</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wFI43TdsYJtSVFVR-t3kVQ.png" /><figcaption>- 點券卡片動效規則 -</figcaption></figure><blockquote><strong><em>僅留存最近三筆點券<br></em></strong><em>我與團隊展開近一週的推演、探索，考慮「顧客僅會直覺反應」操作，亦即超出「畫面所能呈現(7吋平板)」便容易被忽略，小空間要展示/配對超過3筆點券便會很複雜，而呈現需分「主次凸顯」以便顧客注意到自己的點券。</em></blockquote><blockquote><strong><em>有限的保護顧客權益</em></strong><em><br>以飲料候餐時間「45秒」為基準，到第4位客人結完帳，至少已2分鐘過去，第1位顧客仍未領取可視同放棄，店員亦可直接刪除，而亦於內部達成一致共識「允許自由領取」，因本意上仍希望「增量新顧客」。</em></blockquote><blockquote><strong><em>點券自動推擠機制<br></em></strong><em>我設計了「自動推擠＆置中」的機制來「調整每筆點券的位置」，讓每筆點券盡可能地跳到對應的顧客面前，也考慮同時搭配「語音：168元獲得3點」，但顧慮到社會觀感(高單價消費)而暫留作未來可能的優化選項。</em></blockquote><blockquote><strong><em>平板小後台憑發票補領</em></strong><em><br>內部希望保留靠熟客「營造結完帳就有獎領」的氛圍，而若有「一時忘記」的「熟客」而點券被刪除，我設計了一個簡單的「平板小後台」讓店員可於櫃前幫顧客「憑發票補領」和簡易操作部分「歷史紀錄」。</em></blockquote><p>.</p><h4>方案執行</h4><p>因應「點券」結合後，公司有意將此最終版的「UI」作為往後「擴展更大平台」的開發規範，故而我產出一份完整的「產品開發規格文檔」給工程師，內容主要包含：</p><blockquote><em>1. 介面地圖 Sitemap<br>2. 流程圖 Flowchart<br>3. 介面規範 UI Guideline<br>4. 響應式規格標註 RWD</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7H1lil76YztubxTBrszYZw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*StZNkz-ndBwqbMu-raG_6Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yPeqvGFQ1Epe69fB_JLvjQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qY0fpgijQ9ufvbVMxyzEGA.png" /></figure><p>在<strong>後台</strong>的設計上，最終版本讓客戶可自由設定欲進行的行銷活動，如：點數、票券、刮刮樂等，管理顧客資料、分析蒐集的數據與設定平板上愈呈現的個別品牌形象視覺。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2luSF3JKRHpwh3LA2vKUYQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tFvXmuOi8ypUE2AGM_Hkyw.png" /><figcaption>- 平板主UI(上) &amp; 後台主UI(下) -</figcaption></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fuc-P1ST_Z9Q%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Duc-P1ST_Z9Q&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fuc-P1ST_Z9Q%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/12613176f7932feda5f230964e088715/href">https://medium.com/media/12613176f7932feda5f230964e088715/href</a></iframe><h3>結果</h3><h4><strong>整合收銀：JPOS</strong></h4><p>JPOS 主打大型連鎖餐飲，後續長期使用的客戶跨及「餐飲、醫療、美容、健身」，客人少時，店員便可節省「平板操作」，客人多時，他們索幸搬出2台平板，一台靠近顧客候餐區領取、一台靠近 POS 給顧客使用。</p><h4>票券平台：TICK</h4><p>而「符合多情境」的 TICK 更是讓「活動類型長期穩定」的客戶特別偏愛，其他客戶則多是「3、4個月的短檔活動」，一個從試運行版就簽約的客戶後來持續用了3年多。</p><blockquote><em>單店熟客成長率最高達到3倍，年營收成長40%</em></blockquote><h4><strong>票券團購：Sharelink</strong></h4><p>票券分享的「團購情境」一直跟著特定幾個客戶的活動穩定在跑，最忠誠的顧客間斷使用了2年多直到品牌與公司解約，其他偶有客戶「展新店、發優惠吸客」時會快速做一波「病毒行銷」的短檔活動。</p><blockquote><em>在無引導下，35%的顧客能自行開團團購</em></blockquote><h3>感謝你的時間與觀看</h3><p>如過有任何想法與指教歡迎在留言區一起討論<br>你也可以在 <a href="http://www.linkedin.com/in/waynehsu0909">LinkedIn</a> 和 <a href="https://www.behance.net/waynehsu">Behance</a> 和 <a href="https://www.cakeresume.com/a870588">CakeResume</a> 上找到我～</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a99128a941c4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wayne-hsu/%E6%9C%8D%E5%8B%99%E6%A5%AD%E6%AB%83%E6%AA%AF%E4%BA%92%E5%8B%95%E8%A1%8C%E9%8A%B7%E7%9A%84%E6%96%B0%E5%A5%91%E6%A9%9F-b2c%E8%A1%8C%E9%8A%B7%E5%B9%B3%E5%8F%B0%E7%9A%84ui-ux%E6%A1%88%E4%BE%8B%E5%88%86%E6%9E%90-a99128a941c4">服務業櫃檯互動行銷的新契機｜B2B行銷平台的UI/UX案例分析</a> was originally published in <a href="https://medium.com/wayne-hsu">Wayne HSU</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX Challenge of a complex Manufacturing SaaS Platform]]></title>
            <link>https://medium.com/wayne-hsu/ux-predicament-of-the-complex-manufacturing-platform-a-ui-ux-study-of-manufacturing-saas-942b9bc60576?source=rss----12a258b89fe0---4</link>
            <guid isPermaLink="false">https://medium.com/p/942b9bc60576</guid>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[manufacturing]]></category>
            <category><![CDATA[saas]]></category>
            <dc:creator><![CDATA[Wayne Hsu｜徐偉]]></dc:creator>
            <pubDate>Sat, 20 Nov 2021 10:03:16 GMT</pubDate>
            <atom:updated>2023-02-14T09:43:32.051Z</atom:updated>
            <content:encoded><![CDATA[<h3>UX Challenge of a complex Manufacturing SaaS Platform — An UIUX Case Study</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6uueefUMM7K5XlcD2vaJgQ.png" /><figcaption>The confidential information in this case study has been altered</figcaption></figure><h3>Intro</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4EsOQ51jUOmR-IOBlWxpHQ.png" /><figcaption>A SaaS with 6 main modules on the desktop for planning and 100+ features on mobile for executing, that creates synergy in the manufacturing industry</figcaption></figure><p>This platform belongs to a rapidly-growing company with employees growing from 10 to 200 people during 2017 - 2020 <strong>in Shanghai</strong>. The major service is a SaaS platform that streamlines the production flow and creates synergy in the manufacturing factory.</p><p>It allows the different roles to operate on desktops, tablets, and mobile phones. As the business significantly expanded, the strategy that leaned on the features building revealed more and more unfriendly experience throughout the platform.</p><h3>Role</h3><p>My role was to lead the UX Improvement and facilitate communication between 6 product managers, 12 customer successes, 15 developers. My responsibility was across user research, experience design, project management and partially visual design, including:</p><blockquote><em>1. Analyzed and organized the requirements, and defined the problems</em></blockquote><blockquote><em>2. Conducted </em><strong><em>on-site research</em></strong><em> and </em><strong><em>user interview</em></strong><em> to verify the use cases</em></blockquote><blockquote><em>3. Created </em><strong><em>user flow</em></strong><em> and </em><strong><em>wireframe</em></strong><em> to communicate with stakeholders.</em></blockquote><blockquote><em>4. Wrote the </em><strong><em>PRD</em></strong><em> and evaluated the solution with CS and developers.</em></blockquote><blockquote><em>5. Created an </em><strong><em>Axure PR</em></strong><em> </em><strong><em>interactive prototype </em></strong><em>for </em><strong><em>user testing</em></strong><em>.</em></blockquote><blockquote><em>6. Set up the </em><strong><em>road map</em></strong><em> and </em><strong><em>phases</em></strong><em> for the developers.</em></blockquote><blockquote><em>7. Collaborated with a UI designer to create the </em><strong><em>high-fidelity mockups</em></strong><em>.</em></blockquote><blockquote><em>8. Reviewed </em><strong><em>UI acceptance </em></strong><em>before launching the improvement.</em></blockquote><blockquote><em>9. Followed up on the result and collected feedback from our clients.</em></blockquote><h3>Challenge</h3><blockquote>“My job is to finish the production, not to figure out how to use your platform.” — Frontline Users</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*77K2wBi4zLJKG7OfpjnX_A.png" /><figcaption>The complex information architecture and navigation system on the platform led to negative feedback from the end-users</figcaption></figure><p>In manufacturing, the production flow could be varied and diverse from different products, and the factories may reset the workflow based on different orders every time.</p><p>Therefore, the flexibility of this platform was always an advantage, until the voice of “ <strong>This is too complex!! ”</strong> was getting louder and louder.</p><p>My goal was aiming for helping all roles in the factories to locate and operate the required features efficiently and smoothly, and make flexibility become an advantage again.</p><blockquote><strong><em>The high-level goals</em></strong></blockquote><blockquote><em>1. Let the different roles adapted into different workflow painlessly<br>2. Refined the massive information by the contexts that the users required<br>3. Laid the groundwork of a user-friendly platform for the future iterations</em></blockquote><h3>Requirement</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QYQfc9MfmATH6pgMMpcsPA.png" /><figcaption>150 raw requirements of user experience aggregated from pieces to clusters.</figcaption></figure><p>Since 2019, the CEO has received more and more feedback about “unpleasant experiences” toward this platform, therefore, the customer success team (CS) and I launched a survey across our clients’ factories, deciding to bring back the voice of the end-users. However, the feedback are raw and diverse.</p><p>I analyzed all of the responses and aggregated them from the scattered pieces into the clusters, and further to find the 2 KEY denominators. Regarding the feedback received, I wondered why there were numerous comments related to “searching &amp; locating”.</p><blockquote><em>1. Please make xxx feature more obvious, so that I can find it quicker.<br>2. Please make xxx section larger, so that I can find the information I need.</em></blockquote><h3>Research/Insight</h3><blockquote>：What do the users really require in their workflow?</blockquote><p>I asked the help from the CS that specialize in different types of factories, and took a look at the “Factories Persona” for my reference. I intend to find their pattern of workflow top from factories, departments, and down to the roles.</p><p>As shown in the flowchart I summarized below, although many factory departments share the similar workflow, it had been noted that the departments may choose to use other platforms in the different steps of their tasks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UqsIkjtyTVYJdtpzOKz19A.png" /><figcaption>The same departments in different factories might not use our platform for the same tasks.</figcaption></figure><blockquote><strong><em>Clients’ Dependence on our Platform</em></strong></blockquote><blockquote><strong><em>High</em></strong><em> - We covered the majority of steps in their workflow on our platform, but for senior users finding what they need was still time-consuming.</em></blockquote><blockquote><strong><em>Middle</em></strong><em> - We only covered part of their workflow, our CSs could use some ways to go around for the uncovered steps, but it only worked for a few factories.</em></blockquote><blockquote><strong><em>Low</em></strong><em> - We only covered a few steps of their workflow, or we didn’t support the format of their data structure, in which data couldn’t be connected between platforms.</em></blockquote><p>-</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*npkLTY0mM8HK171xsVrSUg.png" /><figcaption>Diverse types of factories, such as wood and chemistry processing, and electronic device assembly. Our platform uses QR codes to trace and document each batch of products throughout the production line.</figcaption></figure><p>To support all types of factories that process different materials, our platform tried to cover as many scenarios as possible. Therefore, I spotted the 2 major pain points:</p><blockquote><strong><em>Similar Features</em> </strong><em>- The similar features with subtle differences in the flow created confusion to the same roles in different factories.</em></blockquote><blockquote><strong><em>Overload Information</em></strong> - <em>The same roles in different factories were required to identify the specific information from each other throughout the production.</em></blockquote><p>-</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*huSIOYzqgYm3tDr8TmrbaQ.png" /><figcaption>The detailed features flow on the platform (WEB &amp; APP)</figcaption></figure><p>After the comparison of clients’ workflow, in order for us to focus on where we may begin, I decided to find the detailed differences across the features in 6 modules:</p><blockquote><em>1.</em><strong><em> Administrative Task</em></strong><em> - Different factories required different levels of details from the data, part of the factories were heavy on manually filling the data gaps to transfer data between platforms. Also, the small factories tended to use the same forms for different purposes while other sizes had strict policies on it, such as using the Purchase Order as the Stock-in Form.</em></blockquote><blockquote><em>2.</em><strong><em> Data Structure</em></strong><em> - Different factories were required to document the different levels of detailed info, therefore, the information rapidly grew. Some factories were unable to use our platform in every step because of the different data structures they have, such as the multiple and single layers of BOM (bill of material).</em></blockquote><blockquote><em>3. </em><strong><em>Quality Inspection – </em></strong><em>Different materials that different factories process led to the diverse method of quality inspection and info management. Some factories could only set up QI criteria during the production of each batch, such as ceramic factories would choose one finished product as a qualified sample from each batch.</em></blockquote><blockquote><em>4. </em><strong><em>Production Execution</em></strong><em> - Different factories had different combinations of production steps, some products required to strictly go through stations one after another, some products could be processed at once in different stations, and some products were mixed. For example, the strict standard operating procedure and regular production flow regulate the progress to different degrees.</em></blockquote><blockquote><em>5. </em><strong><em>Material Management</em></strong><em> - To support the management of different raw materials, multiple similar features with subtly different workflows were built on our platform. Users would have to identify the difference by sight in more than 5 layers of the navigation. For example, the 2 similar flows of transferring the raw material, work in process, and the final products.</em></blockquote><blockquote><em>6. </em><strong><em>Equipment Maintenance</em></strong><em> - The data integration between the equipment and our platform had diverse requirements, such as some equipment only required to receive the data, some equipment transfer data in 2 ways, and some equipment required to be remotely operated by our platform. For example, the chemical factory adjusted the formula remotely.</em></blockquote><p>-</p><p>On the other hand, when I attempted to summarize the <strong>roles</strong> in different factories. I found out that the workflow of each role might change based on placed orders and different sizes of factories:</p><blockquote><em>1. </em><strong><em>Fixed workflow (Most)</em></strong><em> - One worker with a single role all the time in the same department.</em></blockquote><blockquote><em>2. </em><strong><em>Flexible workflow (Some)</em> -</strong> <em>One worker with multiple roles switch by weeks in the same department.</em></blockquote><blockquote><em>3. </em><strong><em>Random workflow (Rare)</em></strong><em>：One worker with multiple roles switched by orders in different departments.</em></blockquote><blockquote>：It was nearly impossible to summarize the workflow for each role across all factories !!</blockquote><p>-</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kvUswCZw78aear-1UrSQNg.png" /><figcaption>Conducting an on-site survey and observing the user behaviors in a factory</figcaption></figure><p>To understand users’ pain of searching, CS and I conducted an on-site survey in our focus factory. We went through their regular production process from the beginning to the end and documented all insights and challenges we found along the way.</p><p><strong>Users</strong></p><blockquote><em>1. The junior group of </em><strong><em>mobile users</em></strong><em> from </em><strong><em>25 to 35 years old</em></strong><em> are the minority (senior high graduates). However, the senior group of </em><strong><em>40 to 65 years old with reading glasses</em></strong><em> was the majority (elementary school graduates), who were </em><strong><em>low tech-savvy</em></strong><em>.</em></blockquote><blockquote><em>2. The </em><strong><em>desktop users</em></strong><em> are mostly </em><strong><em>28 to 35 years old</em></strong><em>, and </em><strong><em>high tech-savvy</em></strong><em>. They have no trouble operating their tasks on our platform. But searching for the required features was still challenging.</em></blockquote><p><strong>Devices</strong></p><blockquote><em>3. M</em><strong><em>obile devices were from 7 to 13 inches, the users may</em></strong><em> use them during walking or standing.</em></blockquote><blockquote><em>4. D</em><strong><em>esktops are mostly 13 inches with Windows OS</em></strong><em>, the users only use it at a certain location by standing.</em></blockquote><p><strong>Features</strong></p><blockquote><em>5. The </em><strong><em>used features of each role are mostly fixed in a whole week</em></strong><em>, but the order may not be (one user used 5 features as one role and 13 features as multiple roles). Except for the users with multiple roles, the used features of different roles rarely overlap with each other.</em></blockquote><blockquote><em>6. Comparing the same tasks of the same users, the time they spent on </em><strong><em>searching for features or information is 45 seconds </em></strong><em>in some edge cases. (The same info on paper could be found by 25 seconds before the implementation of our platform).</em></blockquote><h3>Challenge</h3><blockquote>：Regarding the tools, the faster frontline-users form their standard procedures, the more payment they get while the less time they take.</blockquote><p>In the manufacturing, the voices of frontline users were hard to be heard, but they were the essential end-users of our platform. How efficient a factory finished their production deeply depended on how fast their workers could operate.</p><p>It was the major pain point that frontline users focus on adapting to our platform more than their tasks. So I defined the current challenge:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v0WZnbG3oyXmza8kn1qRJg.png" /><figcaption>For assigned tasks on mobile phones, users were required to go through “module (2) &gt; task type (20) &gt; features (76)”, and repeat this process 50 times at most per day.</figcaption></figure><ol><li>The navigation system couldn’t support the flexible scenarios</li></ol><blockquote><em>1.1. </em><strong><em>Too many Layers </em></strong><em>- Frontline users spent more time on searching for the feature than finishing the tasks.</em></blockquote><blockquote><em>1.2. </em><strong><em>Redundant Layers </em></strong><em>- Different users need the different features to be placed on the top layers.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*awLMvaOEeiH3m7aqXaiiHw.png" /><figcaption>Users were required to find certain items from the massive info on mobile, and the RWD on the desktop couldn’t fully support the requirements.</figcaption></figure><p>2. Flexible scenario led to massive information</p><blockquote><em>2.1. </em><strong><em>Unfiltered Information </em></strong><em>- Frontline users needed to identify their required information by sight.</em></blockquote><blockquote><em>2.2. </em><strong><em>Limited RWD </em></strong><em>- Some information displays were unfriendly because of the limited RWD on desktops.</em></blockquote><h3>Solution</h3><blockquote>：Let frontline users set up their intuitive flow, and trim the information down to the least.</blockquote><p>To most workers, displaying all the information and organizing the info with layers both confused them largely. How do I help each user only see what they require while filtering out the irrelevant information?</p><p>I have decided to build the <strong>Customization on Navigation &amp; Information Displaying:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l_fnRxaUQldpoweiMzD_yw.png" /><figcaption>“Restructuring the navigation” based on the feedback from most of our clients and providing the “Bookmark” for them to bring the frequently-used features up to the first layers on mobiles and desktops</figcaption></figure><ol><li><strong>Restructuring the Navigation</strong></li></ol><blockquote><strong><em>Reorganizing the features by Departments (Desktop)</em></strong><em> - Our platform used to lay out major tasks on the top-layer navigation by Production, Inspection, Material, Equipment, and Setting. However, this structure couldn’t support middle &amp; large-size factories with strict permission between departments, their users tended to search for features and settings by the name of their departments.</em></blockquote><blockquote><strong><em>Reorganizing the features by Roles (Mobile) </em></strong><em>- The workflow of each role across factories were highly flexible, some factories even created new flows every week. I reorganized the most frequently-used features by the most common 13 roles that all factories shared. Also, highlighting the 3 most recent tasks that each user currently executing in case they were jumping between tasks as role switching.</em></blockquote><blockquote><strong><em>Providing the bookmark (Desktop &amp; Mobile)</em></strong><em> - A better navigation for locating required features in a shorter time, I have decided to help our users bring their most frequently-used features up to the top and let them be in charge of their tools set with no need to search.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*spv1AWH2cnA6ngDjnKPtaw.png" /><figcaption>The customization on the amount of displayed information and the settings that allowed to select the displayed method</figcaption></figure><p>2. Reorganizing the Information Display</p><blockquote><strong><em>Switching off the irrelevant information (Desktop &amp; Mobile) </em></strong><em>- To display required information on tables and cards, It was challenging that one material with 30+ lines of basic info in a factory, and the more info generated along the production. Therefore, I decided to help users turn off</em><strong><em> </em></strong><em>those relatively irrelevant ones.</em></blockquote><blockquote><strong><em>Reorganizing the space for key information (Desktop)</em></strong><em> - Most of the desktop users with 13 inches devices often process more information than the mobile users in a limited space. I provided the switchable layout on tables and stretchable columns. Also, the sticky scroll bar for Windows OS users who mostly rely on the cursor to scroll horizontally.</em></blockquote><h3>Execution</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ojLeaf6ENfvyvBh92Th3tA.png" /></figure><p>I scheduled 4 meetings for different stakeholders and recorded the discussions. Therefore, the attendees could focus on the communication and subsequently review our decision at any time.</p><p>-</p><h4>Wireframe</h4><p><strong>&lt;FIRST&gt; Finalizing the solution </strong>- This solution required to scope in the 6 modules that were responsible for by different product managers. To align the scope and details, I laid out the new navigation with a mind chart and illustrated the wireframe with Axure PR9 for presentation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QSAlVuchHhLNBTIlBzV4tw.png" /><figcaption>APP’s Wireframe &amp; Functional Specification</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*llp0aHwbv5u-_2XeCsV4Tg.png" /><figcaption>WEB‘s Wireframe &amp; Functional Specification</figcaption></figure><p>-</p><h4>Prototype</h4><p><strong>&lt;SECOND&gt; Testing the prototype </strong>- I created an interactive prototype for CS who were deployed in different types of factories to test the usability and assess the impact of this solution. They found 2<strong> key users </strong>per department for testing. And the result was quite cheerful:</p><blockquote><em>1. The users under 40 years old have zero trouble learning it.<br>2. The users above 45 years old only required 1 or 2 times of help from CS.<br>3. The users above 65 years old were required to go through it step by step.</em></blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FFXJgLhO_Zb8%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DFXJgLhO_Zb8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FFXJgLhO_Zb8%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/78c42e7baa6854b6641500b5dba97468/href">https://medium.com/media/78c42e7baa6854b6641500b5dba97468/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FiVNAh9ZpLGI%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DiVNAh9ZpLGI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FiVNAh9ZpLGI%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/896f16b5015ed4ba30d1f35fe70c5110/href">https://medium.com/media/896f16b5015ed4ba30d1f35fe70c5110/href</a></iframe><p>-</p><h4>Roadmap</h4><p><strong>&lt;THIRD&gt; Prioritizing the requirements </strong>- I had 2 month for this project, I presented the solution to developers and a UI designer to assess the required effort. I broke it down into 2 phases in Q4 for development, and launched the final solution at once. I wrote the product requirement document on Wiki and traced the progress with Jira.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lp9awaW47i0LbKLjDbwMnA.png" /><figcaption>The 150 requirements could be broken down into 4 phases based on their priority and feasibility.</figcaption></figure><p>-</p><h4>UI Design</h4><p><strong>&lt;FORTH&gt; Reviewing the final result </strong>- Ensuring that the final result was close to my design. I organized a meeting for developers to demonstrate the final visual and workflow. However, the ON/OFF information on mobile was more complex than they expected, therefore, we implemented this feature on the most complex material module first. Overall, they brought almost every design to our platform in the end.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oo_utvqjjIoDYHg6t6VRGA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XXk66htak9A87Dqce4MFYQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GyIWw0hT52t5hdRL6Pe15Q.png" /></figure><h3>Impact</h3><blockquote>Worker Manager - Now we’re talking! You should have this done earlier. It is way faster now.</blockquote><p>After launching the optimization, we were required to have employee training and a performance evaluation in each factory. Thanks for the CS’s deep understanding of different type of factories. The whole process was smooth and fast, it only took us one week to finish it. And all of our clients are satisfied.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w2YD15foZbV0rtobR15x3w.png" /><figcaption>The communication record of Customer Success and our Clients</figcaption></figure><blockquote><em>1. One customized setting could last for 1 week, and 2 months at most.<br>2. The time spent on searching was reduced from 45 to 10 seconds.</em></blockquote><h3>Review</h3><p>At the end, I was rushing back to Taiwan because of the COVID-19 outbreak in Shanghai. I wasn’t able to finish the enhancement in phases 3 and 4. However, the insights and feedback from my research could be shared with our departments and further put themselves into the shoes of our end-users. I believed this was the most important part of this project.</p><blockquote><strong><em>My accomplishments</em></strong></blockquote><blockquote><em>1. Clarified and organized the complex and massive user data<br>2. Brought back the feedback from end-users to the product team<br>3. Enhanced the value of UX within PM &amp; RD teams<br>4. Restructured the navigation system and information architecture</em></blockquote><h3>Would you like to share some thoughts?</h3><p>Let me know if you have any questions or comments on this.<br>You can also find me on <a href="http://www.linkedin.com/in/waynehsu0909">LinkedIn</a>, <a href="https://www.behance.net/waynehsu">Behance</a>, and <a href="https://www.cakeresume.com/a870588">CakeResume</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=942b9bc60576" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wayne-hsu/ux-predicament-of-the-complex-manufacturing-platform-a-ui-ux-study-of-manufacturing-saas-942b9bc60576">UX Challenge of a complex Manufacturing SaaS Platform</a> was originally published in <a href="https://medium.com/wayne-hsu">Wayne HSU</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A new Interactive Marketing B2C Platform solution for the Service Industry]]></title>
            <link>https://medium.com/wayne-hsu/new-opportunity-from-an-interactive-marketing-b2c-platform-for-service-industry-a-ux-ui-case-study-92905fbf25bc?source=rss----12a258b89fe0---4</link>
            <guid isPermaLink="false">https://medium.com/p/92905fbf25bc</guid>
            <category><![CDATA[services]]></category>
            <category><![CDATA[ux-ui-design-thinking]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[service-industry]]></category>
            <dc:creator><![CDATA[Wayne Hsu｜徐偉]]></dc:creator>
            <pubDate>Sat, 20 Nov 2021 09:37:40 GMT</pubDate>
            <atom:updated>2022-12-28T05:57:18.424Z</atom:updated>
            <content:encoded><![CDATA[<h3>A new Interactive Marketing B2C Platform solution for the Service Industry — A UX UI Case Study</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JIrR1ioqoViCICWYzVzFaQ.png" /><figcaption>The confidential information in this case study has been altered</figcaption></figure><h3>Intro</h3><p>During 2014 in Taiwan, brands in the service industry mostly engaged in digital marketing via a customized app, which required the high cost of app iteration from the brands and the download motivation from the customers. However, the customers may just delete the app after redeeming the reward.</p><p>Therefore, this company developed an interactive marketing platform with no need to download any apps. The company used phone numbers to register new customer accounts, and aimed for providing a whole new solution for all sizes of chain brands in the service industry.</p><p>When I joined the team, they had a cheerful performance at running loyalty cards on the platform across more than 200 stores in Taiwan. Their next step was targeting the 40 billion NTD business of the coupons market.</p><h3>Role</h3><p>My role was to design this brand-new interactive marketing functionality for the coupons, and facilitated communication between a product manager and developers. My responsibility was across business and user research, user interface and experience design, and the further iteration, including:</p><blockquote><em>1. Explored the </em><strong><em>coupon business</em></strong><em> and user behavior during check-out</em></blockquote><blockquote><em>2. Analyzed and organized the requirements, and defined the problems</em></blockquote><blockquote><em>3. Conducted the </em><strong><em>user interviews</em></strong><em> and summarized the </em><strong><em>persona</em></strong></blockquote><blockquote><em>4. Set up the </em><strong><em>user flow</em></strong><em> and </em><strong><em>business context</em></strong><em> chart through workshop</em></blockquote><blockquote><em>5. Created the </em><strong><em>low-fidelity wireframe</em></strong><em> and prototype for </em><strong><em>usability testing</em></strong></blockquote><blockquote><em>6. Set up the </em><strong><em>UI guideline</em></strong><em> and </em><strong><em>RWD specification</em></strong><em> for the mobile devices</em></blockquote><blockquote><em>7. Launched the on-site survey to follow up the result and collect the insights</em></blockquote><h3>Challenge</h3><blockquote>Marketing, when working at the counter, was usually intense, the staff and customers were both under pressure to check-out quickly</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*mHS9PeU4t4qtM47TBh3kTw.jpeg" /></figure><p>In Taiwan, people generally try not to inconvenience others. Therefore, it was intense that each check-out time had only 30–60 seconds on average. The new Interactive Coupon would be built on the top of this context.</p><blockquote><em>My high-level mission:</em></blockquote><blockquote><em>1. Explored and defined the business context of all marketing coupons<br>2. Expanded the marketing possibilities for the brands in the service industry<br>3. Refined the UX of new functionality to adapt to intense check-out process</em></blockquote><h3>Requirement</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n4qVnICxRbChFccNiwVDUg.png" /><figcaption>The customer analysis of one of our clients (Left) &amp; The global uninstall rate of the APPs (Right)</figcaption></figure><h4>The insights from Brand’s perspective</h4><p>Digital coupons were not yet common in Taiwan then, most brands relied on paper coupons for marketing. From our data pool, we learned that the business contribution of regular customers was <strong>2.7</strong> times of the new ones.</p><p>We launched a survey across different types of service brands among our clients, such as restaurants, beverages, retails, clothing, hair salons, fitness, hotels, rental vehicles, and medical care. Their common feedback was:</p><blockquote><em>1. </em><strong><em>No ideal solution in the market </em></strong><em>— The cost of customized apps was high, so as the paper coupons from manpower. Also, the uninstall rate of an app would reach 38% within 24 hours after it was downloaded.</em></blockquote><blockquote><em>2. </em><strong><em>Increasing the retention rate of customers</em></strong><em> — Our clients would like to expand their new customers via coupon sharing and increase the retention rate of regular customers through the adding-value gift card.</em></blockquote><blockquote><em>3. </em><strong><em>Making the decision based on the data </em></strong><em>— As the paper coupons were difficult to evaluate the performance, our clients would like to digitize their coupons to collect the customer data and summarize the profiles.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rY0k7yc8mBnlepJjdrOtiQ.png" /><figcaption>Conducted a workshop to organize the insights with teammates by the post-it notes</figcaption></figure><h4>The insights from customer’s perspective</h4><p>From the interview, I learned that most coupon users are thrifty and loyal customers who have the habit of organizing group-buying among friends. Therefore, their friends could be the potential customers to our clients.</p><blockquote><em>1. </em><strong><em>Untraceable profit split of coupons </em></strong><em>— In the same brands, the coupons from direct-selling stores may not allow being redeemed in franchised stores due to the forgery of high-value coupons or untraceable profit split.</em></blockquote><blockquote><em>2. </em><strong><em>The inconvenience of paper coupons </em></strong><em>— The paper coupons might take up the space in the wallets or purses. It was inconvenient for most customers to find the right coupons during the check-out.</em></blockquote><blockquote><em>3. </em><strong><em>Unfriendly experience of the customized apps </em></strong><em>— The customers tended to not download the brand’s customized app for any one-time redeem. Also, It couldn’t be reversed when the redeem button was accidentally pressed.</em></blockquote><h3>Research/Insight</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fuJAoq84oFRTeu6oNB0eyQ.png" /><figcaption>The ultimate summary of the business contexts</figcaption></figure><h4>The current coupon business</h4><p>In order to analyze the campaigns and targets of coupons, I collected all types of marketing coupons and learned that the campaigns were mostly focused on <strong>pre-selling commodity &amp; service</strong> or<strong> later-redeeming discount &amp; gift</strong>.</p><blockquote><em>1. </em><strong><em>Discount </em></strong><em>— It was often applied by the retails and clothing targeting for increasing the return rate of new and regular customers. Therefore, the applicable conditions could be diverse.</em></blockquote><blockquote><em>2. </em><strong><em>Gift &amp; Freebie </em></strong><em>— It was highly popular among the large-size chain brands, applied by the enterprises to provide the festival or yearly award for their employees. This was the most profitable type with 40 billion NTD business.</em></blockquote><blockquote><em>3. </em><strong><em>Commodity &amp; Service </em></strong><em>— It was mostly applied by the restaurants, fitness, and hair salons by pre-selling a set of services or commodities to keep the return rate of their regular customers.</em></blockquote><p>-</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hmA92PRb9x1QtfB5TaXBnQ.png" /><figcaption>The user journey of different roles in different brands during the check-out process</figcaption></figure><h4>Users Journey in Check-out</h4><p>The <strong>Restaurant &amp; Beverage</strong> brands are well known for coupon marketing. Through a workshop, we created the user journey from multiple on-site surveys that was focused on the time and user behavior in each step.</p><blockquote><em>1. </em><strong><em>Campaign Participation</em></strong><em> — 2 scenarios after the check-out, one was the customers left immediately, they may miss out on potential campaigns(Low), another one was the customers waiting for their take-out or receiving the service in a queue, which was the entry for the campaigns(High).</em></blockquote><blockquote><em>2. </em><strong><em>Campaign Engagement</em></strong><em> — 80% of customers were willing to have the higher discount by signing in the membership or filling in their personal information for further benefits. Also, 35% of customers returned to the same store within 1 week to 1 month.</em></blockquote><blockquote><em>3. </em><strong><em>Marketing Touchpoint </em></strong><em>— There were 2 touchpoint, one was the staff proactively invited the customers, another one was the customers noticed the campaigns through banners or table stands. The major workflow could be summarized as Acquire &amp; Redeem the coupons.</em></blockquote><blockquote><em>4. </em><strong><em>Marketing Time </em></strong><em>— There were 2 lengths of marketing time, the beverage &amp; restaurant brands had the shortest time for the campaigns, because of the high volume of customer flow. On the contrary, the hair salon, fitness, and medical care brands had the longest time during the service receiving.</em></blockquote><h3>Current Situation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i2VlcinxHttqTO2DBulNmg.png" /><figcaption>The current model — Phone number as customer account (left), Interactive tablet on the counter &amp; the NFC stamp for the redeem verification (middle), SMS as the receipt carrier (Right)</figcaption></figure><p>As the current model for interactive marketing on this platform, to receive &amp; redeem the points on the loyalty card was relatively simple compared to the coupons, so as the receipts. Therefore, I defined the challenges:</p><blockquote><em>1. </em><strong><em>Coupon Context</em></strong></blockquote><blockquote><em>1.1. Based on the redeemable items, the coupon campaign could be flexible and diverse across different types of brands.</em></blockquote><blockquote><em>1.2. The redeemable items in a campaign were mostly multiple, and each item had their own amount to manage.</em></blockquote><blockquote><em>2. </em><strong><em>Customer Platform</em></strong></blockquote><blockquote><em>2.1. The cost of using SMS as the receipts could be unpredictably</em> <em>expensive because of the large amount of coupon information.</em></blockquote><blockquote><em>2.2. Regarding the group buying, the coupon sharing for gaining new customers who were unregistered members may rely on the SMS.</em></blockquote><h3>Execution</h3><blockquote>This is a brand-new model, we may be considered as a pioneer in the market.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UZYvtD7uNME5BmOj5qAG7w.png" /><figcaption>The persona of customers in the restaurant and beverage brands summarized from our data pool and interview</figcaption></figure><h3>The functionality of coupon — TICK</h3><p>I pulled out the data, combined the insights of the customer’s views on coupon marketing and buying habits. The customers could be categorized into <strong>strict type (10%), planning type (60%)</strong>, and<strong> spontaneous type (30%).</strong></p><p>To validate this new functionality as fast as possible, my goal at the early stage was to run the 3 months of trial run with our clients’ campaigns and collect feedback from their customers.</p><p>.</p><h4>1. User Testing</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bxUHMltUY_LNN6eqEwnRfA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o8ONOD_2wu-4Tt09YN48qQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XdfbRxFWTDEM46HBvxW4Kw.png" /><figcaption>The team named this new functionality as <strong>TICK</strong>, inspired by its major action of checking the coupons on tablets.</figcaption></figure><p>In most of the scenarios, the tablets would be facing the customers and the staff may only provide the support. Therefore, the UI should be intuitive enough in reducing confusion to the customers of any age.</p><blockquote><strong><em>Minimized Information </em></strong><em><br>The customers only focused on the coupon </em><strong><em>name &amp; amount</em></strong><em>, other information was more irrelevant to them, such as description, serial number, or expiration date. As a result, It was against our early assumption that the customers may surf the coupons on tablets.</em></blockquote><blockquote><strong><em>Precise Terminology</em></strong><em><br>Acquire &amp; Redeem were the 2 main contexts in TICK. However, </em><strong><em>Acquire</em></strong><em> may suggest that the coupons were always free, and </em><strong><em>Redeem</em></strong><em> was understandable only when users were aware of their available coupons in the accounts. I altered the terms into Coupon Menu &amp; My Coupons afterward.</em></blockquote><blockquote><strong><em>Fastest Workflow</em></strong><em><br>The range of coupons amount could be diverse in different types of campaigns. The single-tap to add or remove 1 coupon couldn’t well support the buy-in of 10–30 coupons at once in the beverage brands. Therefore, I also provided the keyboard for the faster input.</em></blockquote><p>.</p><h4>2. Trial Run</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JEzrQI2083c717LEXs30OA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*juTppcaG6DbcjElliwoj1Q.png" /><figcaption>We choose the restaurant, beverage, hair salon, and medical care brands for the trial run of TICK</figcaption></figure><p>After the user testing, TICK was immediately brought into the development. We launched its Proof of Concept for 3 months of trial run in the <strong>restaurant, beverage, hair salon, and medical care brands</strong> among our clients.</p><blockquote><strong><em>Distinguishable Contexts<br></em></strong><em>As knowing the turnover rate of staff was high in most of the service brands, the training time for the staff on campaigns was mostly short. In order to largely reduce the effort for UI learning and make the best use of trail run, I decided to change the tabs color of My Coupon from red to green.</em></blockquote><p>.</p><h4>3. Context Reflection</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2oafIVs9dmad_dSM3n2_CQ.png" /><figcaption>The product manager and I launched the second survey on the TICK in check-out</figcaption></figure><p>Regarding the paper coupons, the staff may just hand over a single coupon, a set of coupons, or document the pre-purchased items on receipt for further redeeming. As well as the customers in handing over back at next return.</p><p>Digital coupons boost the marketing decisions by data collection on the brand’s side. However, we yet brought back the advantage of paper coupons to the staff and customers. In the second survey on TICK, we learned:</p><blockquote><strong><em>Staff were the Main Users<br></em></strong><em>Generally, the regular customers had items on their mind that they want to redeem before entering the stores. On the TICK, they would only input the phone number and inform the staff. Therefore, the staff would go through selecting the redeeming items and amount, verifying the redeeming with NFC stamp, logging out the accounts for each customer.</em></blockquote><blockquote><strong><em>Redeeming coupons was most common <br></em></strong><em>In contrast to loyalty cards, our data in 3 months of trial run showed that the count on coupon redeeming to the coupon acquiring was 10 to 1 in most of the restaurant and beverage brands. Their long-term campaign of buying 10 at once for a higher discount suggested that we could provide a new structure of navigation.</em></blockquote><blockquote><strong><em>Password wasn’t always required<br></em></strong><em>In our early assumption of passwords, we believed that how much the customers value the security was mostly based on the value of their coupons. However, we noticed that a luxury clothing brand had a password sheet for all their regular customers, who were used to having a trusting relationship with the staff.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k74GiF_TsMkTk5GJ9Ls65A.png" /><figcaption>Fixed Set (Left), Large Set (Middle), and Speedy Set (Right)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nUESb3fRptKVJi2DWRplxw.png" /></figure><p>I aimed for reducing the effort from the staff by specifying the 3 types of major campaigns across all the brands.</p><blockquote><em>1. </em><strong><em>Specified Contexts</em></strong><em> — Fixed Set for the same campaign in long-term, Large Set for the commodities &amp; service coupons, and the Speedy Set for discount.</em></blockquote><blockquote><em>2. </em><strong><em>Prioritized Action</em></strong><em> — Displaying customer’s coupons as home page, popping up the coupon menu and acquiring action only when it was required.</em></blockquote><blockquote><em>3. </em><strong><em>Switchable Password</em></strong><em> — On the backend panel, passwords was switchable for the campaigns. Also, users could skip it if no coupons were added or used.</em></blockquote><h3>The feature of Group Buying — Sharelink</h3><blockquote>Targeting for the group buying from the regular customers, giving a boost for the brands on the viral marketing.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XCIy_zPRLL0W6uMQCgUYHA.png" /></figure><p>With <strong>TICK</strong> as the foundation, we therefore built a coupon sharing feature as website on the mobile to support the <strong>lucrative group buying</strong>. The workflow was simple and the customers won’t be under pressure as operating it.</p><blockquote><em>1.</em><strong><em> Group Buying </em></strong><em>— Targeting the campaigns of group buying for the low unit-price and high purchased-amount items in restaurant and beverage brands.</em></blockquote><blockquote><em>2. </em><strong><em>Receipt Carrier </em></strong><em>— On the customers side, this feature also provided a carrier for the large information of coupon receipt.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SR36d6MSvbVSsyBR2iVkdA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e3pbDgF0aed1k51BVj0DKg.png" /><figcaption>Creating the RWD specification on mobile and tablet device for the developers</figcaption></figure><h3>Leap Upgrade</h3><h3>The functionality of POS Integration — JPOS</h3><blockquote>Is it possible for the customers to receive the loyal points and coupons by staff’s action on the POS register?</blockquote><p>After the trial run, our sale agents noticed that the staff in large-size chain brands may skip the campaign during the massive volume of customer flow. Therefore, a new challenge emerged:</p><blockquote><em>1. </em><strong><em>Staff Workflow</em></strong><em> — Could staff’s effort on campaign be largely reduced?<br>2. </em><strong><em>Reward Mapping</em></strong><em> — How do we auto-match the rewards to its owners?</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wq4U1AfcOuAghtxEplDX9g.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mcwOrDpb0mkNSCTtxMNFvQ.jpeg" /></figure><p>Regarding the staff training, in contrast to campaign, we learned that the POS register training was the standard procedure. A question was raised as could the staff remotely operate the campaign on the register during check-out?</p><blockquote><strong><em>New Idea<br></em></strong><em>1. The data integration between the POS registers and our platform<br>2. The automatic convert from spending amount to campaign reward<br>3. The claim of campaign reward would be optional to the customers</em></blockquote><blockquote><strong><em>Insights reflection<br></em></strong><em>1. Waiting time for takeout was 45–120s for beverage, 5–10m for restaurant <br>2. Regular customers rarely missed out on any campaign and reward<br>3. The non-claimed reward could be viewed as free-to-claim or invalid items</em></blockquote><p>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j1pIMklMoUoHnTYKQRHvqQ.png" /></figure><p>After the check-out, we saw that the staff would guide the customers to the waiting zone for their takeout and inform them of the campaigns. Therefore, placing the tablets in front of the waiting customers could spare further effort from the staff. The left challenge to be solved was <strong>Reward Mapping</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wFI43TdsYJtSVFVR-t3kVQ.png" /><figcaption>The interaction specification for mapping the customers and their reward.</figcaption></figure><blockquote><strong><em>3 reward cards at most<br></em></strong><em>The mapping structure may grow larger and more complex as the number of reward cards we preserved for the customers. Therefore, JPOS would only preserve the most recent 3 reward cards on the tablets.</em></blockquote><blockquote><strong><em>Optional claim on the rewards<br></em></strong><em>As the beverage wait was 45 second on average, it gave 2 minutes for the first customer to claim their rewards before check-out of the forth customers. Also, the staff could delete the cards if customers declined the rewards.</em></blockquote><blockquote><strong><em>Mapping mechanism of the reward cards<br></em></strong><em>The automation for the reward cards to move, the most recent cards would be the center of tablets by default, and the latter cards would be automatically moved to the center when the previous one was claimed.</em></blockquote><blockquote><strong><em>Staff panel for the reward records<br></em></strong><em>A lightweight staff panel on the tablets for any slight adjustment on the reward mapping, such as the customers asking for claiming the missed rewards or the staff required to correct the claimed record.</em></blockquote><p>.</p><h4>Execution</h4><p>We combined the loyalty cards and coupons on this overall marketing solution. In order to provide this scalable platform the design consistency for any extension. Therefore, I set up a few guideline for the further feature:</p><blockquote><em>1. Sitemap<br>2. Flowchart<br>3. UI Guideline<br>4. RWD Specification</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7H1lil76YztubxTBrszYZw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*StZNkz-ndBwqbMu-raG_6Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yPeqvGFQ1Epe69fB_JLvjQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qY0fpgijQ9ufvbVMxyzEGA.png" /><figcaption>The document for the develops &amp; the guideline for the further designs</figcaption></figure><p>On the <strong>backend panel</strong>, users could configure the campaign of loyalty, coupons, and scratch cards, manage the customer profiles, analyze the collected data, and set up brand’s visual identification elements on the tablets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2luSF3JKRHpwh3LA2vKUYQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tFvXmuOi8ypUE2AGM_Hkyw.png" /><figcaption>UI on tablet (Top) &amp; UI on desktop (Bottom)</figcaption></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fuc-P1ST_Z9Q%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Duc-P1ST_Z9Q&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fuc-P1ST_Z9Q%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/12613176f7932feda5f230964e088715/href">https://medium.com/media/12613176f7932feda5f230964e088715/href</a></iframe><h3>Impact</h3><h4>JPOS</h4><p>The restaurant, beverage, hair salon, fitness, and the medical care brands became the long-term clients of JPOS. During the high customer flow, they would place the 2 tablets, one for the redeeming near to the register, another one for the acquiring in the customer waiting zone.</p><h4>TICK</h4><p>On the other hand, one of our clients signed up for a 3 year of contract with TICK after the trial run, thanks to the specified contexts on the workflow. TICK became their long-term partner in marketing.</p><blockquote><em>The regular customers increased by 300% and the yearly business grew by 40% at most in a single store.</em></blockquote><h4>Sharelink</h4><p>The Sharelink was the favorite feature among beverage and restaurant brands, the most loyal clients continuing to run the group buying for 2 years.</p><blockquote><em>With no further instruction, 35% of the customers in age of 18 to 66 could start the group buying on their own.</em></blockquote><h3>Would you like to share some thoughts?</h3><p>Let me know if you have any questions or comments on this.<br>You can also find me on <a href="http://www.linkedin.com/in/waynehsu0909">LinkedIn</a>, <a href="https://www.behance.net/waynehsu">Behance</a>, and <a href="https://www.cakeresume.com/a870588">CakeResume</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92905fbf25bc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wayne-hsu/new-opportunity-from-an-interactive-marketing-b2c-platform-for-service-industry-a-ux-ui-case-study-92905fbf25bc">A new Interactive Marketing B2C Platform solution for the Service Industry</a> was originally published in <a href="https://medium.com/wayne-hsu">Wayne HSU</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>