[{"data":1,"prerenderedAt":189},["ShallowReactive",2],{"rd-case-studies-count":3,"rd-case-studies":4,"rd-lp-interviews":134},12,[5,19,36,56,76,94,115],{"_path":6,"title":7,"description":8,"date":9,"thumbnail":10,"tags":11,"card":15},"\u002Frd\u002Fcase-studies\u002Fcase-study-1","GA4を\"使えるデータ基盤\"に立て直した支援事例","「入れただけ・見てない」状態の GA4 を、意思決定に使えるデータ基盤へ立て直した要件定義・伴走支援の事例です。","2026-02-16","\u002Fimg\u002Fcontents\u002Frd\u002Fcase-studies\u002Fcase-study-1\u002Fhero-image.jpg",[12,13,14],"データ分析","GoogleAnalytics","Webサービス",{"title":16,"summary":17,"tags":18},"\"データ分析迷子\"を解消","GA4\"入れただけ・見てない\"状態を、意思決定できる\"使えるデータ基盤\"に立て直した支援事例",[12,13,14],{"_path":20,"title":21,"description":22,"date":23,"thumbnail":24,"tags":25,"card":32},"\u002Frd\u002Fcase-studies\u002Fcase-study-2","暗号資産ウォレットを\"使いやすく\"改善したプロダクト設計事例","Web3 の純度より「使いやすさ」をコアに据え、導入を増やした暗号資産ウォレットのプロダクト設計・改善事例です。","2026-03-16","\u002Fimg\u002Fcontents\u002Frd\u002Fcase-studies\u002Fcase-study-2\u002Fhero-image.jpg",[26,27,28,29,30,31],"要件定義","コアバリュー","Web3","暗号資産ウォレット","UX","導入設計",{"title":33,"summary":34,"tags":35},"暗号資産ウォレットを使いやすく改善","Web3の純度より「使いやすさ」をコアに、導入を増やしたプロダクト設計事例",[28,29,26,30],{"_path":37,"title":38,"description":39,"date":40,"thumbnail":41,"tags":42,"card":52},"\u002Frd\u002Fcase-studies\u002Fcase-study-4","広告リサーチをAIで標準化し工数62%削減した業務設計事例","Dify のワークフローを現場が迷わず使える形まで実装し、属人化と情報欠落を止めてリサーチ工数を62%削減した事例です。","2026-04-26","\u002Fimg\u002Fcontents\u002Frd\u002Fcase-studies\u002Fcase-study-4\u002Fhero-image.jpg",[43,44,45,46,47,26,48,49,50,51],"広告","業務効率化","AI活用","Dify","ワークフロー設計","プロンプト設計","属人化解消","引き継ぎ設計","クイックウィン",{"title":53,"summary":54,"tags":55},"広告提案リサーチをAIで標準化、工数62%削減","Difyのワークフローを「現場が迷わず使える形」まで実装し、属人化と情報欠落を止める業務設計・実装事例",[45,46,44],{"_path":57,"title":58,"description":59,"date":60,"thumbnail":61,"tags":62,"card":72},"\u002Frd\u002Fcase-studies\u002Fcase-study-5","オンライン診療プロダクトの開発体制を立て直した事例","要件定義・ロードマップ・改善運用を整え、医療×多職種チームでも納得して前に進める開発体制を構築した支援事例です。","2026-05-09","\u002Fimg\u002Fcontents\u002Frd\u002Fcase-studies\u002Fcase-study-5\u002Fhero-image.jpg",[26,63,64,65,66,67,68,69,70,71],"要求整理","技術負債","バックログ","ロードマップ","PdM組織","合意形成","医療プロダクト","プロセス改善","オンライン診療",{"title":73,"summary":74,"tags":75},"オンライン診療プロダクトの開発を立て直す","要件定義・ロードマップ・改善運用を整え、医療×多職種チームでも納得して前に進める体制構築事例",[26,69,67],{"_path":77,"title":78,"description":79,"date":80,"thumbnail":81,"tags":82,"card":90},"\u002Frd\u002Fcase-studies\u002Fcase-study-6","HRスカウト業務のAI効率化を要件定義で地に足をつけた事例","業務フロー整理と ROI 試算で優先順位を決め、2ヶ月でプロトタイプと定義ドキュメントまで落とし切った設計事例です。","2026-05-19","\u002Fimg\u002Fcontents\u002Frd\u002Fcase-studies\u002Fcase-study-6\u002Fhero-image.jpg",[83,84,85,45,26,86,87,88,89],"人材","HR","スカウト","業務フロー整理","ROI","プロトタイプ","Figma",{"title":91,"summary":92,"tags":93},"HRスカウト業務のAI効率化を要件定義で地に足をつける","業務フロー整理とROI試算で優先順位を決め、2ヶ月でプロトタイプ＋定義ドキュメントまで落とし切った設計事例",[84,45,87,89],{"_path":95,"title":96,"description":97,"date":98,"thumbnail":99,"tags":100,"client":110,"card":111},"\u002Frd\u002Fcase-studies\u002Fcase-study-7","音声ライブ配信アプリの開発体制を整えた支援事例","WBS による可視化と開発プロセスの整備で、経営と開発の期待値を揃えて継続的にリリースできる状態にしたアプリ開発支援事例です。","2026-06-25","\u002Fimg\u002Fcontents\u002Frd\u002Fcase-studies\u002Fcase-study-7\u002Fhero-image.jpg",[101,102,103,104,105,106,107,108,109],"音声配信アプリ","ライブ配信","アプリ開発","スタートアップ","開発体制構築","WBS","要件整理","PdM","リリース設計","Coeto株式会社",{"title":112,"summary":113,"tags":114},"音声ライブ配信アプリの開発体制を整え、継続的にリリースできる状態へ","WBSによる可視化と開発プロセスの整備で、経営と開発の期待値を揃えたアプリ開発支援事例",[103,107,106,104],{"_path":116,"title":117,"description":118,"date":119,"thumbnail":120,"tags":121,"client":129,"card":130},"\u002Frd\u002Fcase-studies\u002Fcase-study-8","契約書管理SaaSをゼロから立ち上げたゼロイチ開発事例","雛形化・差分管理・複数人運用を実装し、構想段階からサービス立ち上げ・継続開発まで伴走したゼロイチ開発の支援事例です。","2026-06-29","\u002Fimg\u002Fcontents\u002Frd\u002Fcase-studies\u002Fcase-study-8\u002Fhero-image.jpg",[122,123,124,26,125,126,127,128],"契約書管理","SaaS","ゼロイチ開発","開発PM","サービス立ち上げ","プロダクト設計","拡張性","Dayz株式会社",{"title":131,"summary":132,"tags":133},"契約書管理SaaSを、クライアントと共にゼロから立ち上げる","雛形化・差分管理・複数人運用を実装して、構想段階からサービス立ち上げ・継続開発まで伴走支援したゼロイチ開発の支援事例",[124,123,126,125],[135,141,147,153,159,165,171,177,183],{"_path":136,"title":137,"order":138,"name":139,"avatar":140},"\u002Frd\u002Finterviews\u002Fseki","要件定義は\"翻訳\"。言外の意図を掬い、\"なんか違う\"を防ぐ",1,"Sekiさん","\u002Fimg\u002Fcontents\u002Frd\u002Finterviews\u002Fseki\u002Fseki-avatar.jpg",{"_path":142,"title":143,"order":144,"name":145,"avatar":146},"\u002Frd\u002Finterviews\u002Fnishitani","要件定義は\"輪郭づくり\"。曖昧な種を形にする",2,"西谷さん","\u002Fimg\u002Fcontents\u002Frd\u002Finterviews\u002Fnishitani\u002Fnishitani-avatar-new.jpg",{"_path":148,"title":149,"order":150,"name":151,"avatar":152},"\u002Frd\u002Finterviews\u002Fnamekawa","要件定義は\"動ける条件\"。混乱を整理し、合意へ導く",3,"行川さん","\u002Fimg\u002Fcontents\u002Frd\u002Finterviews\u002Fnamekawa\u002Fnamekawa-avatar.jpg",{"_path":154,"title":155,"order":156,"name":157,"avatar":158},"\u002Frd\u002Finterviews\u002Fmiura","要件定義は\"コアバリュー\"。優先順位が自然に定まる",4,"Miuraさん","\u002Fimg\u002Fcontents\u002Frd\u002Finterviews\u002Fmiura\u002Fmiura-avatar.jpg",{"_path":160,"title":161,"order":162,"name":163,"avatar":164},"\u002Frd\u002Finterviews\u002Fyamane","要件定義は\"最適化の競技\"。妥協を納得に変える",5,"山根さん","\u002Fimg\u002Fcontents\u002Frd\u002Finterviews\u002Fyamane\u002Fyamane-avatar-new.jpg",{"_path":166,"title":167,"order":168,"name":169,"avatar":170},"\u002Frd\u002Finterviews\u002Fkuwa","要件定義は\"橋渡し\"。先回りして要件の本質を捉える",6,"鍬さん","\u002Fimg\u002Fcontents\u002Frd\u002Finterviews\u002Fkuwa\u002Fkuwa-avatar.jpg",{"_path":172,"title":173,"order":174,"name":175,"avatar":176},"\u002Frd\u002Finterviews\u002Fike","要件定義は\"切り分け\"。要求と要件、理由まで示す",7,"池さん","\u002Fimg\u002Fcontents\u002Frd\u002Finterviews\u002Fike\u002Fike-avatar.jpg",{"_path":178,"title":179,"order":180,"name":181,"avatar":182},"\u002Frd\u002Finterviews\u002Fkubota","要件定義は\"指針\"。Whyに立ち返り、迷走を防ぐ",8,"久保田さん","\u002Fimg\u002Fcontents\u002Frd\u002Finterviews\u002Fkubota\u002Fkubota-avatar.jpg",{"_path":184,"title":185,"order":186,"name":187,"avatar":188},"\u002Frd\u002Finterviews\u002Fishikawa","要件定義は\"誰の・何を解決するか\"を貫くプロセス。ペルソナ起点でブレを断つ",9,"石川さん","\u002Fimg\u002Fcontents\u002Frd\u002Finterviews\u002Fishikawa\u002Fishikawa-avatar.jpg",1790349766816]