UserXper悠識學院
    • Create new note
    • Create a note from template
      • 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
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me 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 New
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
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
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me 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
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    * # 分析師的每一天:產品與使用者行為的量子糾纏 - 姜乃文 Nai-Wen {%hackmd l-xqV_vNRgKqL17looeXlw?view %} ###### ▼▼▼ 開始筆記 ▼▼▼ ## 分析師的日常 - 多工切換,需要對齊定義 - 聽懂問題、和 User 們有品質的溝通(擁有共同語言) ## 分析師的專案進程(陪跑型) > 可以減少溝通上的誤差 ### 專案進程 - 專案前置 - 了解專案目標與任務、共同語言 ➡️ 建立信任感 ex. 與行銷合作著重故事性、業務著重結果 - 專案進行 - 對齊專案協助推進 ➡️ 建立一致且反映專案的數據視角 ex. 同一個 picture 和數據視角去觀看,避免同一個參數的切角指標不同 - 專案收尾 - 協作幫助團隊完成結案 ➡️ 調頻達到對齊,用同一個視角反應成果。 ex.在媒體業,用戶的轉換,是透過廣告還是文章來的?透過某種助攻、交互協作的方式來做歸因。 分析問題的五步驟 1. 問題意識:知道問題是什麼 2. 界定/定義問題 3. 盤點資源/資料 4. 分析/建模 5. 結案/優化 Q:什麼時候加入最好? A:界定/定義問題階段 因如他提早參與,就不會在後面分析、建模的階段卡住。 ## 專案分享 體檢型指標/追蹤型指標 專案目標的客群是誰,這點要很清楚 ### Product Process - 售前:異業合作、產品廣告、品牌廣告、Chrome 適用、KOLKOC - 售中:適用功能、Pro 功能(限時) - 售後:新手教學、冷啟動教學、官方客服、報團討論區 ### 追蹤型指標 vs 體檢型指標 | | 追蹤型指標 | 體檢型指標 | | --- | --- | --- | | 出現頻率 | 頻繁地看/幾乎日日營運都要追 | 一段時間看/每天異動幅度不大 | | 效果 | 可以快速“了解”現況 | 能夠“掌握”現況 | | 使用時間 | 適合營運型會議 | 適合策略、管理型會議 (ex. 接下來有哪些服務要推出等) | | 幫助範圍 | 幫助當下做決定(Decision)(ex:廣告) | 看大方向推薦策略(Stategy)| |相關指標 | 流量、DAU、MAU 等 | 註冊率、WAU / MAU 率、平均客單價等| #### 追蹤型指標 * 出現頻率:頻繁地看/幾乎日日營運都要追 * 效果:可以快速“了解”現況 * 使用時間:適合營運型會議 * 幫助範圍:幫助當下做決定(Decision)(ex:廣告) * #### 體檢型指標 * 出現頻率:一段時間看/每天異動幅度不大 * 效果:能夠“掌握”現況 * 使用時間:適合策略、管理型會議 (ex. 接下來有哪些服務要推出等) * 幫助範圍:看大方向推薦策略(Stategy) * 範例指標: 註冊率、功能使用率、WAU / MAU Z* *不同業態和商模會不同 ### 指標大亂鬥 曾短短一週內被指標 DDos 的紀錄,不同單位拿各種指標轟炸 進行梳理是哪些指標,是追蹤型還是體檢型,以進行哪些要迅速反應 有些人被問問題的時候可能還不清楚自己要的是什麼 ps. 不同專案特性不同,不適用於所有專案 ### 我們最後做了什麼? 整理完指標,在營運會議上對其需亦對其的指標是哪些 追蹤型:每天需要看,且要反映具體的 Action ,需要搭配其他指標來衡量縱效。 體檢型: --- ### 提高產品策略、產品迭代、追蹤數據佐證 RFV + 平均註冊轉換天數 + 導流轉換成本 +產品功能使用率 + 商品銜接率 ➡️ - 以產品教學來說,產品團隊可能會想讓使用者學哪些新功能,但以使用者來說,可能會想要用什麼功能時,才看那個功能的教學。 廣告流量+首頁轉換率+各項服務產品時率+工作階段數+ 新使用者比率 ➡️ 發現 1. 影片型(有教學知識類)帶來的新使用者 首頁轉換率較高(滿多廣告會導入至 LandingPage),且因廣告而來的這類型使用者使用 A 功能滲透率較整體高,後續新增主攻 A 服務的廣告加碼投放 ➡️ **YoY+120%** 2. B 服務的產品流失率較低,但新使用者佔比高 ➡️ 後續搭配訪談,發現該功能較為雞肋,故回訪客後續並不感興趣 ➡️ **列為下一階段優先調整的功能** ### For Example: 追蹤型指標 - 你很常會需要去看的數據 - 拉出一條使用者旅程地圖,使用者進來會先看哪些地方、進行哪些事以及需要追蹤的項目 - 打開 APP 後的進的頁面跟他的行為交叉去看,有沒有符合我們在產品開發上的想像。 ### 媒體訂閱制: 付費牆 - Hard Paywall:必須加入才能觀看(直接撞到牆) - Soft Paywall: 可使用到部分功能(部分干擾使用) - ex. 文章只能看到上半部,需要付費解鎖才可看完整文章內容 - meter paywall: 計次型付費牆(有限制使用:試用期、可看幾篇文章) ### 動態付費牆專案:提升體驗會有助於訂閱嗎? 假設:希望嘗試 從標準的每人閱讀篇數固定狀態下調整成最佳體驗的篇數,是否有可能助益到訂閱? ➡️ 從使用者足跡、文章 metrics、等角度預測設只可能的最佳篇數,以達成每個人「動態」撞牆的動態付費牆實驗 Meter Paywall (圖例) X: 閱讀篇數 Y: 付費動機 Sampling: A, B, C users 從使用者足跡、文章merrics、等角度預測使用者可能的假脧篇數,已達成每個人「動態」的付費 實驗結果: 理想很美好,現實很骨感,實驗的結果,我們有完成提高體驗的目的 ==【回訪天數/閱讀篇數/閱讀滲透率皆有明顯的提高】==,但助益到訂閱的部分效果有限,還在持續努力優化。 根據不同讀者的節奏,去設計付費牆 --- ### 延伸閱讀:搜尋動態付費牆英文媒體案例 - 讀者點擊的順序,會影響牆什麼時候出現(個人化?) - 可參考紐約時報、Netflix, HBO 都有類似的等,實際上會從使用進站時開始追蹤。 ### 其他延伸參考 - [未來轉型路上,《天下》面對哪些跨欄障礙?](https://www.cw.com.tw/digital-transformation-report/2023/chapter-04/) - [2023天下數位轉型報告:一本雜誌為什麼需要AI與MarTech?|天下雜誌 (cw.com.tw)](https://www.cw.com.tw/digital-transformation-report/2023/) - [康健雜誌:APP 糖尿病給你問](https://www.commonhealth.com.tw/channel/22) - [翻轉教育](https://flipedu.parenting.com.tw/):對準台灣老師、教育市場,以訂閱制可以看文章、參加線下講座,登入會員可下載教材 ## Q&A Q:請問商品銜接率的定義是什麼? > A:奶粉產業。一定會看商品銜接率的例子,孕期的媽媽、或開始使用奶粉的人,比如:政府最近在推母乳(0歲是不能賣的),不同階段的奶粉,會有持續銜接的狀況可進行追蹤,會去考慮是否因為競爭對手搶走,或是有成分考量或是其他因素使得產品銜接率無法成功; > 軟體的話,比如是在一些產品中的高階功能會涵蓋部分的功能,從 A 產品銜接到 B 產品的涵蓋率進行追蹤和考量 Q:對於還沒有切入市場,或仍然在尋找 MVP 產品的公司而言,如何透過數據量化分析,來去協助產品功能方向的決策? > A: > > - 釐清 **產品特性** 以回應: 為什麼會產生這個產品?他是不是原本有什麼優勢?需求? > - 進行 **面向市場的競品分析** 以找出:相較競品中,我方可以戰勝的地方 Q:想知道「用同個語言溝通」的例子,有沒有遇到「因為沒用同個語言」而溝通失敗的例子,如果有那時怎麼發現的呢~ > A: > - 喚醒活動(喚醒沈睡用戶) > - 會與行銷業務的同仁同步講到,兩者的喚醒理解不同 > - 對行銷同事而言,喚醒是指產品熱用期(18 個月)的用戶 > - 對業務同事來說,已經離開一年就是沈睡用戶,這樣彼此用的客群就不同,也或許有部分重疊 > - 導致老闆無法理解為什麼哪個喚醒無效等。 ### 感謝 乃文 分享 🎉🎉🎉 --- ## 💬 chat 筆記手們的 chat 空間 怎麼剛剛的不見了@@? 是不是網路卡住? 用成表格清楚很多,感謝 感謝 shoudwang 一同填表格 感謝上面幫忙畫表格的大大 以上感謝各位筆記手(叩首 大家筆記都好厲害 裡面是不是有很多大神@@ 應該有很多習慣做筆記的朋友 參與共筆的大家辛苦了~ 🎉 大家都好厲害!現在網路都很順惹噎 嗚嗚感謝大家,我去後面都打開聊天ㄕ

    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