MOPCON
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Versions and GitHub Sync Note Insights Sharing URL Help
Menu
Options
Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Write
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       owned this note    owned this note      
    Published Linked with GitHub
    1
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    # 讓 UX 落地的求生指南 - 王彥博 {%hackmd rG6pzIawQKe5cHU4rycgYg %} :::success :::spoiler [TOC] ::: ## Speaker 行為改變設計的小訣竅 [填寫問卷會寄簡報](https://docs.google.com/forms/d/e/1FAIpQLScHhamc5Nhg-H94L1AzuO8qEnkzLNb-Zb3Vq6xIEZXuHHqfyA/viewform) 之前是寫部落格、近期帶了工作坊和開了線上課程 [Medium](https://medium.com/@soking) * 業界統計專案統計平均失敗率40% * 歷年來參與的專案開發50次 * 憑數據跟直覺專案上線率60% * (經過UX一些方法學習後)後UX時代專案上線率->70% 經歷:遊戲企劃、產品經理、創業者、產品設計師 信心曲線:自信狂妄->自我懷疑->絕望之谷->重回自信 接下來分享如何使用設計方法論運用在客戶與工作上 > ~~UI/UX 有賺有賠,使用前請詳閱公開說明ㄕㄕ書~~ ## 一個話題 + 我看 UX 像是個壓縮檔 每個人講的 UX 都不太一樣 > Q: 什麼是UX? > A: 這是個科學 [name=柯P] - 從認知科學跑到設計領域 - 糟糕的設計會使人類犯錯 - 起源從二戰時期開始... >但我不想講古,大家自己翻書[name=講者] 介紹書籍:USER FRIENDLY [我們的行為是怎樣被設計的:友善設計如何改變人類的娛樂、生活與工作方式](https://www.books.com.tw/products/0010844948?sloc=main ) ### 情境題 何者是你覺得有讓 UX 落地的想像? - A **設計思考** :在產品發想與需求討論階段。共同定義問題,討論有共識的解決方案 - 推薦的書:google design sprint - B **用戶研究**:開發產品前、開發過程、產品上線營運後都花點時間找人聊聊,觀察如何使用 - C **設計思考--原型設計**:製作真正的產品之前,先用簡單的方法測試目前想法是否可行 - D **資訊架構**:根據商業需求與用戶情境提出產品設計並且工程師能合理評估是否可行 > UX之所以為集合體,就是集結了綜合以上概念A~D 不要靠天才,讓所有人都融入設計流程 | - | 設計思考 | 用戶研究 | 資訊架構 | | ---- | ---------------------------------------------------------- |:---------------------------------------------------------------- | ---------------------------------------------------------- | | 意義 | **引導**跨領域意見參與**設計流程**,不仰賴天才的直覺做設計 | **探索**團隊本來不知道的事情,挖掘使用者未被滿族的**需求與期待** | **組織**商業模式與用戶情境的資訊需求,讓想成為可交付的結果 | | 用法 |運用發散與收斂的思考流程,有意義的嘗試錯誤,淬煉出設計方案|透過訪談與觀察等研究法,接觸使用者與情境,用以設身處地的模擬同理心|規劃用戶取用資訊的流程與互動規則,以達成任務、滿足需求 ### 工具 **需求探索 --->過程共識 ---> 結果交付** 要根據需求去執行,不會使用到所有方法論 設計沒有一個 SOP ,服用時比例要看適用的場合 常見的是今天許願,明天看結果;最後變成一直改產品 :::spoiler 需求探索 * 需求訪談 * 利害關係人分析 * 產品分析 * 競品分析 * 數據分析 * 用戶研究  ::: :::spoiler 過程共識 * Storyboard * 商業模式圖 * 價值主張地圖 * Persona 人物誌 * 同理心地圖 * Prototype * 工作坊 ::: :::spoiler 結果交付 * 易用性研究 * 產品需求文件 * 雛形 * 用戶旅程地圖 * 服務流程圖 * IA文件:sitemap * IA文件:Wireframe ::: ### 「一個話題」的結論 一、人類會犯錯,要配合人類的缺陷來調整設計 二、已經發展出很多方法論,來幫忙產品設計 ## 兩個故事 > 讓B2B業務站在UX這邊讓客戶主動想問用戶研究 ### 故事一、讓B2B業務站在UX這邊 #### 案例:亞洲市場學習語言的B2B產品 * 業務與UX站在不同邊 A: UX對你的產品很重要,你應該多聽聽用戶聲音 [name=UX] B: 可是我們B2B產業,很特別,沒辦法用戶研究 [name=B2B業務] * 於是我們還是去做了(用戶研究),結果... 因為客戶不知道為什麼要做(用戶研究),但我們偷偷跑去做,結果 發現台灣有人在做了(類似產品),發現了以下事情(?: A. 台灣已有競品市場布局 B. 競品依靠當地政府資源推廣,缺乏數位化能力 C. 有許多智庫長期追蹤分析當地市場的教育政策與環境 D. 目標市場教育政策,近年來變化很大 * 根據以上背景資料,我們去做了**用戶訪談**: A. 找到五組目標市場家庭,進行遠端訪談 B. 產業分析了解當地教育政策、教師狀況、教學工具、補習文化等等... C. 分析不同城市客群的經濟與資訊落差,以及教育選擇 | 業務單位的煩惱| 目標市場的家長教育的選擇 | | -------- | -------- | | 新市場的風險| 目標市場的家長教育選擇(A) | | 產品導入的成本| 教育單位的資源教師的工具(B) | | 銷售賣點| 競品的強弱消費者的品牌偏好(C) | ### 故事二、讓客戶主動想問 UX 的用戶研究 > 讓本來對UX沒興趣的客戶,變得會主動問有沒有新的發現 > 讓客戶實際參與 -> 了解用意產生興趣 -> 自己積極 設計師:我們要花點時間做用戶研究 :( 客戶:花什麼時間作研究,直接給我想要的東西就好啦! 客戶對 UX 設計的期待:趕快讓工程師開工 我們(講者)同時動工:把用戶研究計畫切割成一小塊一小塊的話題,每次訪談之後都立刻對客戶說故事(每次花個 10 分鐘說一下) 用戶研究的結果不要一次性全部塞給客戶,分段逐步一點一點的說 (工程師心聲:凍結需求好困難...) **放聲思考法**:在做**易用性測試**很好用的基本方法 有些核心部分就已經看不太懂,用文字或是聲音記錄下來,之後拿去不明講的跟客戶講 每次講點八卦跟inside 每次餵一點點(觀念)給客戶 再每次用 prototype 告訴客戶,客戶便可以接受 讓客戶有興趣,覺得有用,就會變成主動詢問的心態 ## 如何讓 UX 落地--三個行動建議 > 認知同步、即時回饋、擴充選項 ### 1. 認知同步 * 要跟客戶的利益對齊,先同理客戶目標 * 教育客戶你的 UX 專業該如何被利用 設計師:老闆要的東西跟客戶要的東西不一樣怎麼辦? (老闆要的東西是大便) 彼此立場站在對立面,對我們的工作沒有幫助,要梳理利益關係 ### 2. 即時回饋 * 採取最小可見行動,逐漸培養信任感 * 給予隨機變動的回饋,釋放各種有趣又有用的洞見 (像吃角子老虎一樣,隨時都有回饋)遊戲化設計相關的一些訣竅 ### 3. 擴充選項 + 服務客戶最終希望的結果,中間的選項只是手段 + 在探索的過程幫客戶擴充想法彈性,設計才有取捨的空間 在做一些模糊的事情只有一個是直通答案(成本最高),所以要想辦法再多找選項 擴充選項,再收斂。當一個方法不行的時候,先列出多一點方法。 (下班前許願:明天早上就會看到結果) 當我們專注在目的,讓需求在解決方式中,有時我們的設計有時候是錯的,當開發人員知道目的是什麼時,可以提出建議修正需求。 獸群之心/Soking medium.com/@soking 問卷網址: https://docs.google.com/forms/d/e/1FAIpQLScHhamc5Nhg-H94L1AzuO8qEnkzLNb-Zb3Vq6xIEZXuHHqfyA/viewform ###### tags: `MOPCON 2020`

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully