[{"data":1,"prerenderedAt":1882},["ShallowReactive",2],{"article-\u002Farticles\u002Fcopilot-pilot-kouka-sokutei":3,"article-series-m365-copilot":1834},{"_path":4,"_dir":5,"_draft":6,"_partial":6,"_locale":7,"title":8,"description":9,"date":10,"category":11,"series":12,"seriesNo":13,"seriesLabel":14,"author":15,"thumbnail":16,"tags":17,"faq":22,"body":44,"_type":1828,"_id":1829,"_source":1830,"_file":1831,"_stem":1832,"_extension":1833},"\u002Farticles\u002Fcopilot-pilot-kouka-sokutei","articles",false,"","Microsoft 365 Copilotのパイロット導入と効果測定｜導入効果を経営に説明する指標とGo\u002FNo-Go判断","Microsoft 365 Copilotの導入効果を説明できず、契約更新で打ち切られないために。パイロットの設計（対象部門・人数・期間）、時短だけに頼らない効果測定の指標、Go\u002FNo-Go判断の基準、経営への報告資料の型を解説します。","2026-10-23","M365 Copilot導入","m365-copilot",6,"第6回","K.S.ロジャース株式会社","\u002Fimg\u002Fcontents\u002Fnews\u002Fthumb125.jpg",[18,19,20,21],"Microsoft 365 Copilot","効果測定","AI導入","費用対効果",[23,26,29,32,35,38,41],{"q":24,"a":25},"Microsoft 365 Copilotのパイロット期間はどれくらいが適切ですか？","準備を除いて8〜12週を目安にします。Copilot ダッシュボードの指標は過去28日間の集計で最大6日の遅延があり、利用が習慣になったかを見る分類も12週間の利用状況で判定されるため、1か月程度では効果を判断する材料がそろいません。",{"q":27,"a":28},"パイロットの対象人数は何人くらいにすべきですか？","業務の種類がそろった1〜2部門で、10〜30名程度から始めるのがおすすめです。少なすぎると個人差に結果が左右され、多すぎると研修や相談対応が回らなくなります。Copilot ダッシュボードはライセンス数が50未満だとベンチマーク等の一部機能が使えないため、ダッシュボードの全機能で測りたい場合は50ライセンスを目安にします。",{"q":30,"a":31},"パイロットで試す業務はどう選べばよいですか？","効果（定量と定性）、難易度（データがそろっているか）、適合性（今の道具で組めるか、現場に合うか）、重要度（部門の方針にとって大事か）の4つで比べ、最初は確実に成功しやすい業務を選びます。担当者が AI で何ができるかのイメージを持っていない場合は、事例のデモを見てから一緒に業務を出すと選びやすくなります。",{"q":33,"a":34},"パイロットでは研修も必要ですか？","必要です。何も知らずに使い始めた人は、最初の数回で期待した答えが返らないと使わなくなります。ライセンスを配る週に、全員向けのキックオフ研修（できること・苦手なこと、入力してよい情報、頼み方の基本）と、自部門の業務を題材にした部門別の練習を行い、最初の2週間は練習課題で1日1回業務の中で使う習慣を作ります。研修は導入前の数値を測ってから行います。",{"q":36,"a":37},"Copilotの導入効果はどうやって測ればよいですか？","「利用（使われているか）」「効果（業務が変わったか）」「価値（浮いた時間で何をしたか）」の3層で測ります。利用は Microsoft 365 管理センターの使用状況レポートや Copilot ダッシュボード、効果は導入前後で同じ業務の所要時間を測る方法とアンケート、価値はアンケートとインタビューで把握します。",{"q":39,"a":40},"Copilot ダッシュボードの「Copilot アシスト時間」はそのまま削減時間として報告してよいですか？","そのまま削減時間として報告するのはおすすめしません。Microsoft は、Copilot の操作回数に調査に基づく係数を掛けた一般的な推定値だと説明しています。経営報告では参考値として扱い、自社で測った業務の所要時間やアンケート結果と並べて示します。",{"q":42,"a":43},"パイロットの結果、本展開しない判断もあり得ますか？","あり得ます。利用が定着しない、権限やデータの置き場所の整備が足りない、効果を示す数値が取れていないといった場合は、ライセンスを回収・再配分し、整備を先に進めてから再試行する判断も正解です。導入前に判断基準を決めておくと、感覚ではなく基準で判断できます。",{"type":45,"children":46,"toc":1800},"root",[47,66,71,90,95,160,167,179,184,289,310,316,322,327,378,383,388,404,409,421,442,447,457,481,486,520,525,531,536,541,557,565,570,611,619,631,692,697,705,717,722,730,735,755,761,766,799,804,809,824,830,842,872,877,893,1014,1026,1032,1037,1081,1086,1101,1107,1112,1118,1138,1143,1149,1167,1172,1215,1221,1233,1245,1250,1255,1263,1268,1291,1299,1327,1332,1338,1343,1359,1440,1445,1478,1483,1488,1551,1556,1568,1576,1590,1602,1607,1612,1665,1671,1676,1704,1717,1730,1735,1781],{"type":48,"tag":49,"props":50,"children":51},"element","p",{},[52,55,64],{"type":53,"value":54},"text","※ Microsoft 365 Copilot は、2026年8月から「Microsoft Copilot」に名称が変わりました（Copilot Chat は「Microsoft Copilot Chat」）。移行期間中は旧名称も併用されているため、本記事では広く使われている「Microsoft 365 Copilot」の表記で統一しています（出典：",{"type":48,"tag":56,"props":57,"children":61},"a",{"href":58,"rel":59},"https:\u002F\u002Flearn.microsoft.com\u002Fja-jp\u002Fcopilot\u002Fmicrosoft-365\u002Fmicrosoft-365-copilot-privacy",[60],"nofollow",[62],{"type":53,"value":63},"Microsoft Learn「Microsoft Copilot のデータ、プライバシー、セキュリティ」",{"type":53,"value":65},"）。",{"type":48,"tag":49,"props":67,"children":68},{},[69],{"type":53,"value":70},"「Copilot を試しに入れてみたが、便利だったのかどうか説明できない」「来年の契約更新で、経営から費用対効果を聞かれたら答えられない」——Microsoft 365 Copilot の導入で、実は最も多いのがこの状態です。",{"type":48,"tag":49,"props":72,"children":73},{},[74,80,82,88],{"type":48,"tag":56,"props":75,"children":77},{"href":76},"\u002Farticles\u002Fm365-copilot-donyu-roadmap\u002F",[78],{"type":53,"value":79},"第1回：非IT企業のMicrosoft 365 Copilot導入ロードマップ",{"type":53,"value":81},"では、導入の失敗パターンの4つ目として「効果を説明できず、契約更新で打ち切られる」を挙げました。原因ははっきりしていて、",{"type":48,"tag":83,"props":84,"children":85},"strong",{},[86],{"type":53,"value":87},"導入する前に測り方を決めていない",{"type":53,"value":89},"ことです。使い始めてから「効果を出してください」と言われても、比べるための導入前の数字がありません。",{"type":48,"tag":49,"props":91,"children":92},{},[93],{"type":53,"value":94},"本記事はシリーズ第6回として、ロードマップのフェーズ3「パイロット」を扱います。対象部門・人数・期間の決め方、時短だけに頼らない効果測定の指標、Microsoft が提供する利用状況レポートの使い方と注意点、本展開に進むかどうかの Go\u002FNo-Go 判断、そして経営に説明する報告資料の型までを整理します。",{"type":48,"tag":96,"props":97,"children":98},"blockquote",{},[99,107],{"type":48,"tag":49,"props":100,"children":101},{},[102],{"type":48,"tag":83,"props":103,"children":104},{},[105],{"type":53,"value":106},"この記事の要点",{"type":48,"tag":108,"props":109,"children":110},"ul",{},[111,124,136,148],{"type":48,"tag":112,"props":113,"children":114},"li",{},[115,117,122],{"type":53,"value":116},"パイロットは「お試し」ではなく、",{"type":48,"tag":83,"props":118,"children":119},{},[120],{"type":53,"value":121},"本展開の可否を判断するための試行",{"type":53,"value":123},"です。対象を1〜2部門に絞り、準備を除いて8〜12週とります",{"type":48,"tag":112,"props":125,"children":126},{},[127,129,134],{"type":53,"value":128},"効果は",{"type":48,"tag":83,"props":130,"children":131},{},[132],{"type":53,"value":133},"利用・効果・価値の3層",{"type":53,"value":135},"で測ります。時間削減だけでなく、浮いた時間を何に使えたかまで押さえると、経営への説明が通りやすくなります",{"type":48,"tag":112,"props":137,"children":138},{},[139,141,146],{"type":53,"value":140},"Go\u002FNo-Go の基準は",{"type":48,"tag":83,"props":142,"children":143},{},[144],{"type":53,"value":145},"導入前に決めて途中で変えない",{"type":53,"value":147},"こと。No-Go も正しい判断のひとつです",{"type":48,"tag":112,"props":149,"children":150},{},[151,153,158],{"type":53,"value":152},"K.S.Rogers の支援の現場では、対象業務を効果・難易度・適合性・重要度の4つで絞り、品質は",{"type":48,"tag":83,"props":154,"children":155},{},[156],{"type":53,"value":157},"既存の成果物を正解にして項目ごとに比べて",{"type":53,"value":159},"きました。ヒアリングだけでは分からないずれも、試行の中で見つかります",{"type":48,"tag":161,"props":162,"children":164},"h2",{"id":163},"microsoft-365-copilot-のパイロット導入とは",[165],{"type":53,"value":166},"Microsoft 365 Copilot のパイロット導入とは",{"type":48,"tag":49,"props":168,"children":169},{},[170,172,177],{"type":53,"value":171},"Microsoft 365 Copilot のパイロット導入とは、",{"type":48,"tag":83,"props":173,"children":174},{},[175],{"type":53,"value":176},"対象の部門と期間を区切って Copilot を試し、全社に広げるかどうかを判断するための材料を集める取り組み",{"type":53,"value":178},"です。PoC（概念実証）や試験導入と呼ばれることもあります。",{"type":48,"tag":49,"props":180,"children":181},{},[182],{"type":53,"value":183},"「とりあえず何人かに配って様子を見る」との違いは、次の3点を事前に決めていることです。",{"type":48,"tag":185,"props":186,"children":187},"table",{},[188,212],{"type":48,"tag":189,"props":190,"children":191},"thead",{},[192],{"type":48,"tag":193,"props":194,"children":195},"tr",{},[196,202,207],{"type":48,"tag":197,"props":198,"children":199},"th",{},[200],{"type":53,"value":201},"項目",{"type":48,"tag":197,"props":203,"children":204},{},[205],{"type":53,"value":206},"「とりあえず配る」",{"type":48,"tag":197,"props":208,"children":209},{},[210],{"type":53,"value":211},"パイロット",{"type":48,"tag":213,"props":214,"children":215},"tbody",{},[216,235,253,271],{"type":48,"tag":193,"props":217,"children":218},{},[219,225,230],{"type":48,"tag":220,"props":221,"children":222},"td",{},[223],{"type":53,"value":224},"目的",{"type":48,"tag":220,"props":226,"children":227},{},[228],{"type":53,"value":229},"使ってみる",{"type":48,"tag":220,"props":231,"children":232},{},[233],{"type":53,"value":234},"本展開の可否を判断する",{"type":48,"tag":193,"props":236,"children":237},{},[238,243,248],{"type":48,"tag":220,"props":239,"children":240},{},[241],{"type":53,"value":242},"対象",{"type":48,"tag":220,"props":244,"children":245},{},[246],{"type":53,"value":247},"希望者、役職者、ITに詳しい人",{"type":48,"tag":220,"props":249,"children":250},{},[251],{"type":53,"value":252},"効果を測りやすい業務を持つ部門",{"type":48,"tag":193,"props":254,"children":255},{},[256,261,266],{"type":48,"tag":220,"props":257,"children":258},{},[259],{"type":53,"value":260},"測り方",{"type":48,"tag":220,"props":262,"children":263},{},[264],{"type":53,"value":265},"終わってから感想を聞く",{"type":48,"tag":220,"props":267,"children":268},{},[269],{"type":53,"value":270},"導入前の数値を測り、同じ方法で導入後も測る",{"type":48,"tag":193,"props":272,"children":273},{},[274,279,284],{"type":48,"tag":220,"props":275,"children":276},{},[277],{"type":53,"value":278},"終わり方",{"type":48,"tag":220,"props":280,"children":281},{},[282],{"type":53,"value":283},"なんとなく継続",{"type":48,"tag":220,"props":285,"children":286},{},[287],{"type":53,"value":288},"基準に照らして Go\u002FNo-Go を判断し、経営に報告する",{"type":48,"tag":49,"props":290,"children":291},{},[292,294,301,303,308],{"type":53,"value":293},"公開事例では、三井化学が2024年7月に研究部門や事業部門も含めた約300ライセンスで検証を始め、2025年7月に約1,700ライセンス、2026年4月時点で4,200以上のライセンスへと段階的に広げています。同社は利用者1人あたり1日約40分の業務時間削減を確認したとしているほか、日間アクティブユーザー（DAU）を指標に採用し、2026年4月の段階で DAU は68%と報告しています（出典：",{"type":48,"tag":56,"props":295,"children":298},{"href":296,"rel":297},"https:\u002F\u002Fwww.microsoft.com\u002Fja-jp\u002Fcustomers\u002Fstory\u002F26949-mitsui-chemicals-microsoft-365-copilot",[60],[299],{"type":53,"value":300},"Microsoft 公式事例",{"type":53,"value":302},"）。規模は違っても、",{"type":48,"tag":83,"props":304,"children":305},{},[306],{"type":53,"value":307},"小さく試し、測りながら広げる",{"type":53,"value":309},"という順番は中堅・中小企業にもそのまま当てはまります。",{"type":48,"tag":161,"props":311,"children":313},{"id":312},"パイロットの設計-対象部門人数期間",[314],{"type":53,"value":315},"パイロットの設計 ― 対象部門・人数・期間",{"type":48,"tag":317,"props":318,"children":320},"h3",{"id":319},"対象部門の選び方",[321],{"type":53,"value":319},{"type":48,"tag":49,"props":323,"children":324},{},[325],{"type":53,"value":326},"パイロットの成否は、対象部門の選び方でほぼ決まります。次の条件を満たす部門から選びます。",{"type":48,"tag":108,"props":328,"children":329},{},[330,340,358,368],{"type":48,"tag":112,"props":331,"children":332},{},[333,338],{"type":48,"tag":83,"props":334,"children":335},{},[336],{"type":53,"value":337},"文書・メール・会議が多い",{"type":53,"value":339}," ―― Copilot が得意な議事録の要約、メールの下書き、資料の作成・要約が日常的に発生している",{"type":48,"tag":112,"props":341,"children":342},{},[343,348,350,356],{"type":48,"tag":83,"props":344,"children":345},{},[346],{"type":53,"value":347},"データが Microsoft 365 の中にある",{"type":53,"value":349}," ―― ファイルが SharePoint や OneDrive、やりとりが Teams や Outlook にある。データが外にある部門では Copilot が参照できる材料がなく、効果が出にくくなります（詳しくは",{"type":48,"tag":56,"props":351,"children":353},{"href":352},"\u002Farticles\u002Fcopilot-data-okiba-box-sharepoint\u002F",[354],{"type":53,"value":355},"第2回（前編）",{"type":53,"value":357},"）",{"type":48,"tag":112,"props":359,"children":360},{},[361,366],{"type":48,"tag":83,"props":362,"children":363},{},[364],{"type":53,"value":365},"業務の所要時間を測りやすい",{"type":53,"value":367}," ―― 月次報告、定例会議の議事録、問い合わせへの回答など、繰り返し発生して前後比較ができる業務がある",{"type":48,"tag":112,"props":369,"children":370},{},[371,376],{"type":48,"tag":83,"props":372,"children":373},{},[374],{"type":53,"value":375},"協力的な現場リーダーがいる",{"type":53,"value":377}," ―― 相談に乗り、使い方を周りに広げてくれる人がいる",{"type":48,"tag":49,"props":379,"children":380},{},[381],{"type":53,"value":382},"逆に、最初のパイロットでは避けたほうがよいのは、秘密情報を多く扱う部門（人事・経営企画など）と、業務の大半が現場作業で PC を使う時間が短い部門です。前者は権限と機密区分の整備が済んでからにします。",{"type":48,"tag":49,"props":384,"children":385},{},[386],{"type":53,"value":387},"部門を決めたら、その中で試す業務を選びます（後述のベースラインで測る対象業務になります）。",{"type":48,"tag":96,"props":389,"children":390},{},[391,399],{"type":48,"tag":49,"props":392,"children":393},{},[394],{"type":48,"tag":83,"props":395,"children":396},{},[397],{"type":53,"value":398},"K.S.Rogers の現場から",{"type":48,"tag":49,"props":400,"children":401},{},[402],{"type":53,"value":403},"製造業の会社様で AI 活用の対象業務を選んだときは、担当の方が「AI で何ができるか」のイメージをまだ持っていないことが多くありました。そこで、まず事例のデモ動画で何ができるかを見てもらい、一緒にブレストして業務を出しました。そのうえで、効果（定量と定性）・難易度（データがそろっているか）・適合性（今の道具で組めるか、現場に合うか）・重要度（部門の方針にとって大事か）の4つで絞り、最初は確実に成功しやすい業務を選んで短期間で運用に乗せ、改善と横展開はその次の段階にしました。",{"type":48,"tag":317,"props":405,"children":407},{"id":406},"人数の目安",[408],{"type":53,"value":406},{"type":48,"tag":49,"props":410,"children":411},{},[412,414,419],{"type":53,"value":413},"おすすめは",{"type":48,"tag":83,"props":415,"children":416},{},[417],{"type":53,"value":418},"業務の種類がそろった1〜2部門で10〜30名程度",{"type":53,"value":420},"です。少なすぎると個人差に結果が左右され、多すぎると研修や相談対応が回りません。",{"type":48,"tag":49,"props":422,"children":423},{},[424,426,431,433,440],{"type":53,"value":425},"もう1つの判断材料が、後述する Copilot ダッシュボードの機能差です。テナントに割り当てた Copilot ライセンスが1〜49の場合、準備状況や導入・影響の指標は見られますが、ベンチマーク、アンケートに基づくセンチメント指標、週・月単位の推移グラフなどは含まれません。",{"type":48,"tag":83,"props":427,"children":428},{},[429],{"type":53,"value":430},"50ライセンス以上",{"type":53,"value":432},"になるとこれらを含むすべての機能が使えます（出典：",{"type":48,"tag":56,"props":434,"children":437},{"href":435,"rel":436},"https:\u002F\u002Flearn.microsoft.com\u002Fja-jp\u002Fviva\u002Finsights\u002Forg-team-insights\u002Fcopilot-dashboard",[60],[438],{"type":53,"value":439},"Microsoft Copilot ダッシュボードに接続する｜Microsoft Learn",{"type":53,"value":441},"）。ダッシュボードの全機能で測りたい場合は50ライセンスを、そうでなければ自社のアンケートと計測で補う前提で人数を決めます。",{"type":48,"tag":317,"props":443,"children":445},{"id":444},"期間の目安",[446],{"type":53,"value":444},{"type":48,"tag":49,"props":448,"children":449},{},[450,455],{"type":48,"tag":83,"props":451,"children":452},{},[453],{"type":53,"value":454},"準備に2〜4週、試行そのものに8〜12週",{"type":53,"value":456},"をとります。",{"type":48,"tag":458,"props":459,"children":460},"picture",{},[461,463,471,472],{"type":53,"value":462},"\n  ",{"type":48,"tag":464,"props":465,"children":470},"source",{"media":466,"srcSet":467,"width":468,"height":469},"(max-width: 768px)","\u002Fimg\u002Fcontents\u002Farticles\u002Fcopilot-pilot-kouka-sokutei\u002Fpilot-schedule-sp.svg",420,528,[],{"type":53,"value":462},{"type":48,"tag":473,"props":474,"children":480},"img",{"src":475,"alt":476,"width":477,"height":478,"loading":479},"\u002Fimg\u002Fcontents\u002Farticles\u002Fcopilot-pilot-kouka-sokutei\u002Fpilot-schedule.svg","Microsoft 365 Copilot パイロットのスケジュール例：準備2〜4週、試行前半4〜6週、中間レビュー、試行後半4〜6週、判定・報告1〜2週",800,292,"lazy",[],{"type":48,"tag":49,"props":482,"children":483},{},[484],{"type":53,"value":485},"期間を短くしすぎないほうがよい理由は、測定の仕組みにあります。",{"type":48,"tag":108,"props":487,"children":488},{},[489,508],{"type":48,"tag":112,"props":490,"children":491},{},[492,494,499,501,506],{"type":53,"value":493},"Copilot ダッシュボードのデータは",{"type":48,"tag":83,"props":495,"children":496},{},[497],{"type":53,"value":498},"過去28日間",{"type":53,"value":500},"を表し、現在の日付から",{"type":48,"tag":83,"props":502,"children":503},{},[504],{"type":53,"value":505},"最大6日間の遅延",{"type":53,"value":507},"があります。ライセンスを割り当ててからデータ処理が始まるまでにも最大7日かかります",{"type":48,"tag":112,"props":509,"children":510},{},[511,513,518],{"type":53,"value":512},"ダッシュボードの「使用レベル」は、",{"type":48,"tag":83,"props":514,"children":515},{},[516],{"type":53,"value":517},"12週間",{"type":53,"value":519},"の利用頻度と一貫性で利用者を分類します。たとえば「習慣的なユーザー」は、週平均1〜14回の Copilot 操作を行い、12週のうち9週以上使った人です",{"type":48,"tag":49,"props":521,"children":522},{},[523],{"type":53,"value":524},"1か月で「使われなかった」と判断すると、慣れる前の数字だけで結論を出すことになります。",{"type":48,"tag":317,"props":526,"children":528},{"id":527},"配る前の研修と業務で使う練習",[529],{"type":53,"value":530},"配る前の研修と、業務で使う練習",{"type":48,"tag":49,"props":532,"children":533},{},[534],{"type":53,"value":535},"パイロットは、ライセンスを配るだけでは始まりません。Copilot は「何を、どう頼むか」で結果が大きく変わる道具です。何も知らずに使い始めた人は、最初の数回で期待した答えが返らないと「思ったほど賢くない」と判断して、そのまま使わなくなります。パイロットの結果が「使われなかった」で終わる原因の多くは、ここにあります。",{"type":48,"tag":49,"props":537,"children":538},{},[539],{"type":53,"value":540},"そこで、配る週に研修を行い、そのあと業務の中で使う練習を続けます。",{"type":48,"tag":458,"props":542,"children":543},{},[544,545,550,551],{"type":53,"value":462},{"type":48,"tag":464,"props":546,"children":549},{"media":466,"srcSet":547,"width":468,"height":548},"\u002Fimg\u002Fcontents\u002Farticles\u002Fcopilot-pilot-kouka-sokutei\u002Fkenshu-renshu-sp.svg",762,[],{"type":53,"value":462},{"type":48,"tag":473,"props":552,"children":556},{"src":553,"alt":554,"width":477,"height":555,"loading":479},"\u002Fimg\u002Fcontents\u002Farticles\u002Fcopilot-pilot-kouka-sokutei\u002Fkenshu-renshu.svg","Copilot パイロットの研修と練習の流れ。1 キックオフ研修（全員・60〜90分）：できること・苦手なこと、入力してよい情報、頼み方の基本。2 部門別の練習（部門ごと・60〜90分）：自部門の業務から3題、練習用の資料で試す、結果を見比べる。3 2週間の練習課題（最初の2週・1日1題）：課題リストから選ぶ、業務の中で使う、使った業務を記録。4 週1回の相談会（試行中ずっと）：うまくいった例を共有、つまずきを記録、次の練習課題に反映。導入前の数値を測ってから、ライセンスを配る週に研修する",258,[],{"type":48,"tag":49,"props":558,"children":559},{},[560],{"type":48,"tag":83,"props":561,"children":562},{},[563],{"type":53,"value":564},"1. キックオフ研修（全員・60〜90分）",{"type":48,"tag":49,"props":566,"children":567},{},[568],{"type":53,"value":569},"パイロットの対象者全員を集めて、次の3つを伝えます。",{"type":48,"tag":108,"props":571,"children":572},{},[573,583,601],{"type":48,"tag":112,"props":574,"children":575},{},[576,581],{"type":48,"tag":83,"props":577,"children":578},{},[579],{"type":53,"value":580},"できること・苦手なこと",{"type":53,"value":582}," ―― 議事録の要約、メールの下書き、資料のたたき台は得意です。一方で、社内のどこにも書かれていない情報は答えられず、計算や最新の数字は間違えることがあります。最初に「苦手なこと」を知っておくと、期待外れで使うのをやめる人が減ります",{"type":48,"tag":112,"props":584,"children":585},{},[586,591,593,599],{"type":48,"tag":83,"props":587,"children":588},{},[589],{"type":53,"value":590},"入力してよい情報",{"type":53,"value":592}," ―― 社内の生成AI利用ルールの要点と、「これは入れてよい／入れてはいけない」の具体例を示します（ルールの作り方は",{"type":48,"tag":56,"props":594,"children":596},{"href":595},"\u002Farticles\u002Fseisei-ai-shanai-rule-sample\u002F",[597],{"type":53,"value":598},"第5回（前編）",{"type":53,"value":600},"）。何を入れてよいか分からない状態では、利用は伸びません",{"type":48,"tag":112,"props":602,"children":603},{},[604,609],{"type":48,"tag":83,"props":605,"children":606},{},[607],{"type":53,"value":608},"頼み方の基本",{"type":53,"value":610}," ―― 「目的」「前提となる情報」「ほしい形（箇条書き、300字、表など）」の3つを入れて頼むこと。一度で決めようとせず、返ってきた答えに追加で指示して直していくこと。そして、答えの根拠になったファイルを開いて確かめることです",{"type":48,"tag":49,"props":612,"children":613},{},[614],{"type":48,"tag":83,"props":615,"children":616},{},[617],{"type":53,"value":618},"2. 部門別の練習（部門ごと・60〜90分）",{"type":48,"tag":49,"props":620,"children":621},{},[622,624,629],{"type":53,"value":623},"研修で一般的な使い方を見せても、「自分の仕事ではどう使うのか」は分かりません。部門ごとに集まり、",{"type":48,"tag":83,"props":625,"children":626},{},[627],{"type":53,"value":628},"自部門の実際の業務から3題",{"type":53,"value":630},"を、その場で全員が試します。",{"type":48,"tag":185,"props":632,"children":633},{},[634,650],{"type":48,"tag":189,"props":635,"children":636},{},[637],{"type":48,"tag":193,"props":638,"children":639},{},[640,645],{"type":48,"tag":197,"props":641,"children":642},{},[643],{"type":53,"value":644},"部門",{"type":48,"tag":197,"props":646,"children":647},{},[648],{"type":53,"value":649},"練習の題材の例",{"type":48,"tag":213,"props":651,"children":652},{},[653,666,679],{"type":48,"tag":193,"props":654,"children":655},{},[656,661],{"type":48,"tag":220,"props":657,"children":658},{},[659],{"type":53,"value":660},"営業",{"type":48,"tag":220,"props":662,"children":663},{},[664],{"type":53,"value":665},"商談メモから議事録と次回までの宿題を作る／提案書のたたき台を作る／お客様からのメールへの返信の下書き",{"type":48,"tag":193,"props":667,"children":668},{},[669,674],{"type":48,"tag":220,"props":670,"children":671},{},[672],{"type":53,"value":673},"管理部門",{"type":48,"tag":220,"props":675,"children":676},{},[677],{"type":53,"value":678},"規程やマニュアルから問い合わせへの回答案を作る／定例会議の議事録を要約する／月次報告の文章を整える",{"type":48,"tag":193,"props":680,"children":681},{},[682,687],{"type":48,"tag":220,"props":683,"children":684},{},[685],{"type":53,"value":686},"企画・マーケティング",{"type":48,"tag":220,"props":688,"children":689},{},[690],{"type":53,"value":691},"過去の企画書を要約して比較する／アンケートの自由記述を分類する／社内向けのお知らせ文を作る",{"type":48,"tag":49,"props":693,"children":694},{},[695],{"type":53,"value":696},"題材には、機密ではない練習用の資料（公開済みの資料や、過去の会議の議事録など）を使います。同じ題材を全員で試し、結果を見比べると、頼み方の違いで答えがどれだけ変わるかが実感できます。うまくいった頼み方は、そのまま部門の「頼み方の例」として残します。",{"type":48,"tag":49,"props":698,"children":699},{},[700],{"type":48,"tag":83,"props":701,"children":702},{},[703],{"type":53,"value":704},"3. 2週間の練習課題（最初の2週・1日1題）",{"type":48,"tag":49,"props":706,"children":707},{},[708,710,715],{"type":53,"value":709},"研修の直後に「では使ってください」と放すと、忙しさに押されて使わない日が続きます。最初の2週間は、",{"type":48,"tag":83,"props":711,"children":712},{},[713],{"type":53,"value":714},"部門ごとの練習課題のリスト（10〜15題）から、1日1題を業務の中で試す",{"type":53,"value":716},"ことを決めておきます。使った業務と、うまくいったかどうかを1行ずつ記録してもらいます。",{"type":48,"tag":49,"props":718,"children":719},{},[720],{"type":53,"value":721},"この記録は、後の効果測定にもそのまま使えます。どの業務で使われ、どの業務で使われなかったかが分かるからです。",{"type":48,"tag":49,"props":723,"children":724},{},[725],{"type":48,"tag":83,"props":726,"children":727},{},[728],{"type":53,"value":729},"4. 週1回の相談会（試行中ずっと）",{"type":48,"tag":49,"props":731,"children":732},{},[733],{"type":53,"value":734},"練習課題で出てきた「うまくいった例」と「つまずいた場面」を、次の相談会で共有します。運営の仕方は次の項で説明します。",{"type":48,"tag":49,"props":736,"children":737},{},[738,740,745,747,753],{"type":53,"value":739},"なお、研修は",{"type":48,"tag":83,"props":741,"children":742},{},[743],{"type":53,"value":744},"導入前の数値（後述のベースライン）を測ってから",{"type":53,"value":746},"行います。研修の後に測ると、研修で仕事のやり方が変わった分が導入前の数値に混ざり、比べる基準がずれるためです。全社展開のときの研修の組み立て方は、",{"type":48,"tag":56,"props":748,"children":750},{"href":749},"\u002Farticles\u002Fcopilot-shanai-kenshu-susumekata\u002F",[751],{"type":53,"value":752},"第7回（後編）：Microsoft 365 Copilotの社内研修の進め方",{"type":53,"value":754},"で扱います。",{"type":48,"tag":317,"props":756,"children":758},{"id":757},"試行中の運営-週1回の相談会と問い合わせ記録",[759],{"type":53,"value":760},"試行中の運営 ― 週1回の相談会と問い合わせ記録",{"type":48,"tag":49,"props":762,"children":763},{},[764],{"type":53,"value":765},"パイロットは、ライセンスを配ったあとの運営で差がつきます。最低限、次の3つを回します。",{"type":48,"tag":108,"props":767,"children":768},{},[769,779,789],{"type":48,"tag":112,"props":770,"children":771},{},[772,777],{"type":48,"tag":83,"props":773,"children":774},{},[775],{"type":53,"value":776},"週1回・30分の相談会",{"type":53,"value":778}," ―― 「今週うまくいった使い方」と「うまくいかなかった場面」を2〜3人に話してもらいます。うまくいった例はその場で全員が試せるようにプロンプトごと共有します",{"type":48,"tag":112,"props":780,"children":781},{},[782,787],{"type":48,"tag":83,"props":783,"children":784},{},[785],{"type":53,"value":786},"問い合わせ記録シート",{"type":53,"value":788}," ―― 日付、部門、使ったアプリ、やりたかったこと、起きたこと、原因の見立て、対処を1行ずつ残します。後の Go\u002FNo-Go 判断と、本展開時の FAQ の材料になります",{"type":48,"tag":112,"props":790,"children":791},{},[792,797],{"type":48,"tag":83,"props":793,"children":794},{},[795],{"type":53,"value":796},"推進役の定例",{"type":53,"value":798}," ―― 推進責任者、情報システム担当、各部門の現場リーダーで隔週に集まり、利用状況と問い合わせの傾向を確認します。利用が伸びない人には、個別に業務を聞いて使いどころを一緒に探します",{"type":48,"tag":49,"props":800,"children":801},{},[802],{"type":53,"value":803},"問い合わせ記録は、原因を「使い方（プロンプト）」「データの置き場所・権限」「ライセンス・設定」「製品の仕様」に分けておくと、試行の後半にどこへ手を打つべきかが見えてきます。",{"type":48,"tag":49,"props":805,"children":806},{},[807],{"type":53,"value":808},"試行中には、事前の想定そのものが違っていたと分かることもあります。",{"type":48,"tag":96,"props":810,"children":811},{},[812,819],{"type":48,"tag":49,"props":813,"children":814},{},[815],{"type":48,"tag":83,"props":816,"children":817},{},[818],{"type":53,"value":398},{"type":48,"tag":49,"props":820,"children":821},{},[822],{"type":53,"value":823},"当社の支援先で業務の自動化を組んだときは、最初のヒアリングで伺ったとおりに集計のロジックを組みましたが、運用を始めてから、そのロジックが正しくないと分かり、修正しました。ヒアリングだけで完璧な仕様は作れず、実際の業務に乗せて初めて分かることがあります。Copilot のパイロットでも、試行中に見つかったずれは問い合わせ記録に残し、中間レビューで直す前提で計画しておきます。",{"type":48,"tag":161,"props":825,"children":827},{"id":826},"導入前に決める物差し-時短だけで測らない",[828],{"type":53,"value":829},"導入前に決める物差し ― 時短だけで測らない",{"type":48,"tag":49,"props":831,"children":832},{},[833,835,840],{"type":53,"value":834},"効果測定というと「何時間削減できたか」に目が行きがちです。もちろん時間は大事な指標ですが、それだけで測ると2つの問題が起きます。1つは、浮いた時間が別の雑務に吸収されて「結局忙しさは変わらない」と感じられること。もう1つは、資料の質が上がった、検討の幅が広がったといった",{"type":48,"tag":83,"props":836,"children":837},{},[838],{"type":53,"value":839},"時間に表れない効果",{"type":53,"value":841},"が報告から抜け落ちることです。",{"type":48,"tag":49,"props":843,"children":844},{},[845,847,852,854,861,863,870],{"type":53,"value":846},"参考になるのがライオンの取り組みです。同社は2023年12月、生成AIと検索システムを組み合わせた「知識伝承のAI化」ツールの開発を発表し、研究領域での検証で",{"type":48,"tag":83,"props":848,"children":849},{},[850],{"type":53,"value":851},"文書の取得時間が従来の情報検索と比べて約5分の1に短縮",{"type":53,"value":853},"されたとしています（出典：",{"type":48,"tag":56,"props":855,"children":858},{"href":856,"rel":857},"https:\u002F\u002Fwww.lion.co.jp\u002Fja\u002Fnewsroom\u002Fnews\u002F2023\u002F4464",[60],[859],{"type":53,"value":860},"ライオン ニュースリリース（2023年12月8日）",{"type":53,"value":862},"）。一方で、同社の執行役員が出演した PIVOT の番組は「生成AIの業務利用は『効率化』だけじゃない」をテーマに、社内AIチャットの全社定着から社員自身がAIを作る「生成AIの民主化」までを語っています（出典：",{"type":48,"tag":56,"props":864,"children":867},{"href":865,"rel":866},"https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=xgBkuYGWFYg",[60],[868],{"type":53,"value":869},"PIVOT「& questions」ライオンに学ぶ生成AIの民主化",{"type":53,"value":871},"）。時間の短縮は入口であって、その先にある仕事の中身の変化まで見る、という考え方です。",{"type":48,"tag":49,"props":873,"children":874},{},[875],{"type":53,"value":876},"この考え方をパイロットの物差しに落とすと、次の3層になります。",{"type":48,"tag":458,"props":878,"children":879},{},[880,881,886,887],{"type":53,"value":462},{"type":48,"tag":464,"props":882,"children":885},{"media":466,"srcSet":883,"width":468,"height":884},"\u002Fimg\u002Fcontents\u002Farticles\u002Fcopilot-pilot-kouka-sokutei\u002Fsokutei-3so-sp.svg",712,[],{"type":53,"value":462},{"type":48,"tag":473,"props":888,"children":892},{"src":889,"alt":890,"width":477,"height":891,"loading":479},"\u002Fimg\u002Fcontents\u002Farticles\u002Fcopilot-pilot-kouka-sokutei\u002Fsokutei-3so.svg","Copilot の効果測定の3層：①利用（使われているか）、②効果（業務が変わったか）、③価値（浮いた時間で何をしたか）と、それぞれの指標の例と取り方",392,[],{"type":48,"tag":185,"props":894,"children":895},{},[896,927],{"type":48,"tag":189,"props":897,"children":898},{},[899],{"type":48,"tag":193,"props":900,"children":901},{},[902,907,912,917,922],{"type":48,"tag":197,"props":903,"children":904},{},[905],{"type":53,"value":906},"層",{"type":48,"tag":197,"props":908,"children":909},{},[910],{"type":53,"value":911},"問い",{"type":48,"tag":197,"props":913,"children":914},{},[915],{"type":53,"value":916},"指標の例",{"type":48,"tag":197,"props":918,"children":919},{},[920],{"type":53,"value":921},"取り方",{"type":48,"tag":197,"props":923,"children":924},{},[925],{"type":53,"value":926},"基準の置き方（例）",{"type":48,"tag":213,"props":928,"children":929},{},[930,958,986],{"type":48,"tag":193,"props":931,"children":932},{},[933,938,943,948,953],{"type":48,"tag":220,"props":934,"children":935},{},[936],{"type":53,"value":937},"① 利用",{"type":48,"tag":220,"props":939,"children":940},{},[941],{"type":53,"value":942},"使われているか",{"type":48,"tag":220,"props":944,"children":945},{},[946],{"type":53,"value":947},"アクティブ利用者の割合、利用日数、アプリ別の利用",{"type":48,"tag":220,"props":949,"children":950},{},[951],{"type":53,"value":952},"使用状況レポート、Copilot ダッシュボード",{"type":48,"tag":220,"props":954,"children":955},{},[956],{"type":53,"value":957},"対象者の過半が毎週使っている",{"type":48,"tag":193,"props":959,"children":960},{},[961,966,971,976,981],{"type":48,"tag":220,"props":962,"children":963},{},[964],{"type":53,"value":965},"② 効果",{"type":48,"tag":220,"props":967,"children":968},{},[969],{"type":53,"value":970},"業務が変わったか",{"type":48,"tag":220,"props":972,"children":973},{},[974],{"type":53,"value":975},"対象業務の所要時間、手戻りの回数、成果物の品質評価",{"type":48,"tag":220,"props":977,"children":978},{},[979],{"type":53,"value":980},"導入前後の計測、アンケート",{"type":48,"tag":220,"props":982,"children":983},{},[984],{"type":53,"value":985},"対象業務の所要時間が導入前より短い",{"type":48,"tag":193,"props":987,"children":988},{},[989,994,999,1004,1009],{"type":48,"tag":220,"props":990,"children":991},{},[992],{"type":53,"value":993},"③ 価値",{"type":48,"tag":220,"props":995,"children":996},{},[997],{"type":53,"value":998},"浮いた時間で何をしたか",{"type":48,"tag":220,"props":1000,"children":1001},{},[1002],{"type":53,"value":1003},"新しい取り組みや顧客対応に使えた時間、検討の質の変化",{"type":48,"tag":220,"props":1005,"children":1006},{},[1007],{"type":53,"value":1008},"アンケート、インタビュー、活用事例",{"type":48,"tag":220,"props":1010,"children":1011},{},[1012],{"type":53,"value":1013},"具体的な事例を部門ごとに複数集める",{"type":48,"tag":49,"props":1015,"children":1016},{},[1017,1019,1024],{"type":53,"value":1018},"「基準の置き方」の数値は、自社の状況に合わせて",{"type":48,"tag":83,"props":1020,"children":1021},{},[1022],{"type":53,"value":1023},"導入前に",{"type":53,"value":1025},"決めます。大切なのは数字の大小より、事前に決めて途中で変えないことです。",{"type":48,"tag":317,"props":1027,"children":1029},{"id":1028},"導入前の数値ベースラインの取り方",[1030],{"type":53,"value":1031},"導入前の数値（ベースライン）の取り方",{"type":48,"tag":49,"props":1033,"children":1034},{},[1035],{"type":53,"value":1036},"②効果を測るには、導入前の数値が欠かせません。準備期間中に次の手順で取ります。",{"type":48,"tag":1038,"props":1039,"children":1040},"ol",{},[1041,1051,1061,1071],{"type":48,"tag":112,"props":1042,"children":1043},{},[1044,1049],{"type":48,"tag":83,"props":1045,"children":1046},{},[1047],{"type":53,"value":1048},"対象業務を3〜5個に絞る",{"type":53,"value":1050}," ―― 例：週次定例の議事録作成、月次報告書の作成、顧客からの問い合わせメールへの返信、社内規程の検索",{"type":48,"tag":112,"props":1052,"children":1053},{},[1054,1059],{"type":48,"tag":83,"props":1055,"children":1056},{},[1057],{"type":53,"value":1058},"1回あたりの所要時間を記録する",{"type":53,"value":1060}," ―― 対象者に2週間ほど、該当業務の開始と終了の時刻をメモしてもらいます。完璧な計測でなくても、同じ方法で前後を比べられれば十分です",{"type":48,"tag":112,"props":1062,"children":1063},{},[1064,1069],{"type":48,"tag":83,"props":1065,"children":1066},{},[1067],{"type":53,"value":1068},"品質の見方を決める",{"type":53,"value":1070}," ―― 上長の手直しの回数、差し戻しの有無など、観察できるもので決めます",{"type":48,"tag":112,"props":1072,"children":1073},{},[1074,1079],{"type":48,"tag":83,"props":1075,"children":1076},{},[1077],{"type":53,"value":1078},"アンケートの初回を取る",{"type":53,"value":1080}," ―― 導入後と同じ質問で、今の業務の負担感を聞いておきます",{"type":48,"tag":49,"props":1082,"children":1083},{},[1084],{"type":53,"value":1085},"品質は感想では比べにくいため、すでにある成果物を物差しにする方法もあります。",{"type":48,"tag":96,"props":1087,"children":1088},{},[1089,1096],{"type":48,"tag":49,"props":1090,"children":1091},{},[1092],{"type":48,"tag":83,"props":1093,"children":1094},{},[1095],{"type":53,"value":398},{"type":48,"tag":49,"props":1097,"children":1098},{},[1099],{"type":53,"value":1100},"医療分野の会社様で資料の自動作成を検証したときは、お客様がすでに作っていた資料を正解として、同じテーマの資料を AI で作り、項目ごとに「◎一致・○一部・×未対応」で比べました。「よさそう」という感想ではなく、既存の成果物との差を数えたことで、どこまで任せられて、どこに手当てが要るかを具体的に話し合えました。Copilot のパイロットでも、議事録や月次報告など導入前の成果物を正解にして、項目ごとに比べる方法が使えます。",{"type":48,"tag":161,"props":1102,"children":1104},{"id":1103},"copilot-の効果測定に使える公式レポート",[1105],{"type":53,"value":1106},"Copilot の効果測定に使える公式レポート",{"type":48,"tag":49,"props":1108,"children":1109},{},[1110],{"type":53,"value":1111},"①利用の層は、Microsoft が提供するレポートで把握できます。主に2つあります。",{"type":48,"tag":317,"props":1113,"children":1115},{"id":1114},"microsoft-365-管理センターの使用状況レポート",[1116],{"type":53,"value":1117},"Microsoft 365 管理センターの使用状況レポート",{"type":48,"tag":49,"props":1119,"children":1120},{},[1121,1123,1128,1130,1137],{"type":53,"value":1122},"IT 管理者向けのレポートです。Copilot ライセンスを持つユーザーの利用状況を見る「Microsoft Copilot 使用状況レポート」と、ライセンスを持たないユーザーの Copilot Chat の利用状況を見る「Copilot Chat 使用状況レポート」があります。Copilot Chat のレポートでは、アクティブユーザー数、送信されたプロンプト数、ユーザーごとの最終利用日などを、過去7日・28日・90日・180日の期間で確認できます。",{"type":48,"tag":83,"props":1124,"children":1125},{},[1126],{"type":53,"value":1127},"ユーザー名などは既定で匿名化",{"type":53,"value":1129},"されており、表示するには管理者が設定を変更します（出典：",{"type":48,"tag":56,"props":1131,"children":1134},{"href":1132,"rel":1133},"https:\u002F\u002Flearn.microsoft.com\u002Fja-jp\u002Fmicrosoft-365\u002Fadmin\u002Factivity-reports\u002Fmicrosoft-copilot-usage",[60],[1135],{"type":53,"value":1136},"Microsoft Copilot Chat の使用状況レポート｜Microsoft Learn",{"type":53,"value":65},{"type":48,"tag":49,"props":1139,"children":1140},{},[1141],{"type":53,"value":1142},"個人名を出して利用状況を見るかどうかは、パイロット開始前に社内で決め、対象者に伝えておきます。「監視されている」と感じると、正直なアンケート回答が得られなくなります。",{"type":48,"tag":317,"props":1144,"children":1146},{"id":1145},"viva-insights-の-copilot-ダッシュボードcopilot-analytics",[1147],{"type":53,"value":1148},"Viva Insights の Copilot ダッシュボード（Copilot Analytics）",{"type":48,"tag":49,"props":1150,"children":1151},{},[1152,1154,1159,1161,1166],{"type":53,"value":1153},"経営層や部門長向けのダッシュボードです。ビジネス向けまたはエンタープライズ向けの Microsoft 365（または Office 365）を契約し、Exchange Online のアカウントがあれば利用でき、",{"type":48,"tag":83,"props":1155,"children":1156},{},[1157],{"type":53,"value":1158},"表示に有料の Viva Insights ライセンスは必要ありません",{"type":53,"value":1160},"。準備状況・導入・影響・センチメント（利用者の受け止め）の指標がまとまっています（出典：",{"type":48,"tag":56,"props":1162,"children":1164},{"href":435,"rel":1163},[60],[1165],{"type":53,"value":439},{"type":53,"value":65},{"type":48,"tag":49,"props":1168,"children":1169},{},[1170],{"type":53,"value":1171},"パイロットで特に使えるのは次の指標です。",{"type":48,"tag":108,"props":1173,"children":1174},{},[1175,1185,1195,1205],{"type":48,"tag":112,"props":1176,"children":1177},{},[1178,1183],{"type":48,"tag":83,"props":1179,"children":1180},{},[1181],{"type":53,"value":1182},"アクティブな Copilot ユーザー",{"type":53,"value":1184}," ―― 過去28日間に少なくとも1回 Copilot を使った人",{"type":48,"tag":112,"props":1186,"children":1187},{},[1188,1193],{"type":48,"tag":83,"props":1189,"children":1190},{},[1191],{"type":53,"value":1192},"使用レベル",{"type":53,"value":1194}," ―― 12週間の頻度と一貫性で、パワーユーザー・習慣的なユーザー・初心者ユーザーなどに分類",{"type":48,"tag":112,"props":1196,"children":1197},{},[1198,1203],{"type":48,"tag":83,"props":1199,"children":1200},{},[1201],{"type":53,"value":1202},"アプリ別の利用",{"type":53,"value":1204}," ―― Teams、Outlook、Word、Excel、PowerPoint などのどこで使われているか",{"type":48,"tag":112,"props":1206,"children":1207},{},[1208,1213],{"type":48,"tag":83,"props":1209,"children":1210},{},[1211],{"type":53,"value":1212},"満足度",{"type":53,"value":1214}," ―― Copilot の応答に付けられた高評価・低評価の割合。28日以内に5人以上から30件以上の反応がある場合に表示",{"type":48,"tag":317,"props":1216,"children":1218},{"id":1217},"copilot-アシスト時間の扱いに注意する",[1219],{"type":53,"value":1220},"「Copilot アシスト時間」の扱いに注意する",{"type":48,"tag":49,"props":1222,"children":1223},{},[1224,1226,1231],{"type":53,"value":1225},"ダッシュボードには「Copilot アシスト時間」という指標があり、経営報告にそのまま使いたくなります。しかし Microsoft は、この指標を",{"type":48,"tag":83,"props":1227,"children":1228},{},[1229],{"type":53,"value":1230},"Copilot の操作回数に、調査に基づく係数を掛けた一般的な推定値",{"type":53,"value":1232},"と説明しています。たとえば検索・要約や作成の操作は1回あたり6分、会議の要約はその会議の時間として計算されます。金額換算の「Copilot アシストバリュー」も、既定では米国の統計に基づく時給で計算されており、設定で変更が必要です。",{"type":48,"tag":49,"props":1234,"children":1235},{},[1236,1238,1243],{"type":53,"value":1237},"また Microsoft 自身が、ダッシュボードの数値の変化は Copilot だけが原因とは限らず、季節性や役割の変化、組織の変化も影響すると注意書きをしています。そのため経営報告では、",{"type":48,"tag":83,"props":1239,"children":1240},{},[1241],{"type":53,"value":1242},"アシスト時間は参考値",{"type":53,"value":1244},"として扱い、②効果の層で自社が実際に測った所要時間と並べて示すのが誠実です。",{"type":48,"tag":161,"props":1246,"children":1248},{"id":1247},"効果測定アンケートの型",[1249],{"type":53,"value":1247},{"type":48,"tag":49,"props":1251,"children":1252},{},[1253],{"type":53,"value":1254},"②効果と③価値の層は、アンケートとインタビューで補います。導入前・中間・終了時の3回、同じ質問で取ります。",{"type":48,"tag":49,"props":1256,"children":1257},{},[1258],{"type":48,"tag":83,"props":1259,"children":1260},{},[1261],{"type":53,"value":1262},"共通の質問（5段階評価）",{"type":48,"tag":49,"props":1264,"children":1265},{},[1266],{"type":53,"value":1267},"Copilot ダッシュボードにアンケート結果を取り込む場合に使われる、次の4つの質問が参考になります（出典：同上）。",{"type":48,"tag":108,"props":1269,"children":1270},{},[1271,1276,1281,1286],{"type":48,"tag":112,"props":1272,"children":1273},{},[1274],{"type":53,"value":1275},"Copilot を使うと、自分の成果物の品質を向上させるのに役立つ",{"type":48,"tag":112,"props":1277,"children":1278},{},[1279],{"type":53,"value":1280},"Copilot を使うと、ありふれた繰り返しの作業による心労が減る",{"type":48,"tag":112,"props":1282,"children":1283},{},[1284],{"type":53,"value":1285},"Copilot を使うことで、タスクを早く完了できる",{"type":48,"tag":112,"props":1287,"children":1288},{},[1289],{"type":53,"value":1290},"Copilot を使うと、生産性が向上する",{"type":48,"tag":49,"props":1292,"children":1293},{},[1294],{"type":48,"tag":83,"props":1295,"children":1296},{},[1297],{"type":53,"value":1298},"自社で追加する質問",{"type":48,"tag":108,"props":1300,"children":1301},{},[1302,1307,1312,1317,1322],{"type":48,"tag":112,"props":1303,"children":1304},{},[1305],{"type":53,"value":1306},"対象業務ごとに、1回あたりの所要時間は導入前と比べてどう変わったか（増えた／変わらない／1〜2割減／3〜5割減／半分以上減）",{"type":48,"tag":112,"props":1308,"children":1309},{},[1310],{"type":53,"value":1311},"浮いた時間を主に何に使ったか（顧客対応、企画・改善、後回しにしていた業務、学習、特になし）",{"type":48,"tag":112,"props":1313,"children":1314},{},[1315],{"type":53,"value":1316},"Copilot を使って、以前はできなかった・やらなかったことができた例（自由記述）",{"type":48,"tag":112,"props":1318,"children":1319},{},[1320],{"type":53,"value":1321},"使いにくかった場面、期待した回答が得られなかった場面（自由記述）",{"type":48,"tag":112,"props":1323,"children":1324},{},[1325],{"type":53,"value":1326},"パイロット終了後も使い続けたいか",{"type":48,"tag":49,"props":1328,"children":1329},{},[1330],{"type":53,"value":1331},"最後の2問は、本展開時の研修内容や、データ・権限の整備の優先順位を決める材料になります。",{"type":48,"tag":161,"props":1333,"children":1335},{"id":1334},"gono-go-判断の基準",[1336],{"type":53,"value":1337},"Go\u002FNo-Go 判断の基準",{"type":48,"tag":49,"props":1339,"children":1340},{},[1341],{"type":53,"value":1342},"パイロットの終わりに、本展開に進むかどうかを判断します。選択肢は「進む」「進まない」の2つではなく、3つに分けておくと現実的です。",{"type":48,"tag":458,"props":1344,"children":1345},{},[1346,1347,1352,1353],{"type":53,"value":462},{"type":48,"tag":464,"props":1348,"children":1351},{"media":466,"srcSet":1349,"width":468,"height":1350},"\u002Fimg\u002Fcontents\u002Farticles\u002Fcopilot-pilot-kouka-sokutei\u002Fgo-nogo-sp.svg",828,[],{"type":53,"value":462},{"type":48,"tag":473,"props":1354,"children":1358},{"src":1355,"alt":1356,"width":477,"height":1357,"loading":479},"\u002Fimg\u002Fcontents\u002Farticles\u002Fcopilot-pilot-kouka-sokutei\u002Fgo-nogo.svg","パイロット後のGo\u002FNo-Go判断：Goは本展開に進む、条件付きGoは効果が出た業務に絞って拡大、No-Goはライセンスを回収して整備を先に進め再試行",380,[],{"type":48,"tag":185,"props":1360,"children":1361},{},[1362,1383],{"type":48,"tag":189,"props":1363,"children":1364},{},[1365],{"type":48,"tag":193,"props":1366,"children":1367},{},[1368,1373,1378],{"type":48,"tag":197,"props":1369,"children":1370},{},[1371],{"type":53,"value":1372},"判定",{"type":48,"tag":197,"props":1374,"children":1375},{},[1376],{"type":53,"value":1377},"判断の目安",{"type":48,"tag":197,"props":1379,"children":1380},{},[1381],{"type":53,"value":1382},"次の打ち手",{"type":48,"tag":213,"props":1384,"children":1385},{},[1386,1404,1422],{"type":48,"tag":193,"props":1387,"children":1388},{},[1389,1394,1399],{"type":48,"tag":220,"props":1390,"children":1391},{},[1392],{"type":53,"value":1393},"Go",{"type":48,"tag":220,"props":1395,"children":1396},{},[1397],{"type":53,"value":1398},"3層の基準をおおむね満たす／重大な情報管理上の問題がない／現場から継続希望が多い",{"type":48,"tag":220,"props":1400,"children":1401},{},[1402],{"type":53,"value":1403},"対象部門を広げる、研修と社内の推進役（チャンピオン）を増やす",{"type":48,"tag":193,"props":1405,"children":1406},{},[1407,1412,1417],{"type":48,"tag":220,"props":1408,"children":1409},{},[1410],{"type":53,"value":1411},"条件付きGo",{"type":48,"tag":220,"props":1413,"children":1414},{},[1415],{"type":53,"value":1416},"効果が出た業務や人が偏っている／一部にデータや権限の課題がある",{"type":48,"tag":220,"props":1418,"children":1419},{},[1420],{"type":53,"value":1421},"効果が出た業務・部門に絞って拡大し、課題の解消を次の拡大の条件にする",{"type":48,"tag":193,"props":1423,"children":1424},{},[1425,1430,1435],{"type":48,"tag":220,"props":1426,"children":1427},{},[1428],{"type":53,"value":1429},"No-Go",{"type":48,"tag":220,"props":1431,"children":1432},{},[1433],{"type":53,"value":1434},"利用が定着しない／権限や置き場所の整備が不足／効果を示す数値が取れていない",{"type":48,"tag":220,"props":1436,"children":1437},{},[1438],{"type":53,"value":1439},"ライセンスを回収・再配分し、整備を先に進めてから再試行する",{"type":48,"tag":49,"props":1441,"children":1442},{},[1443],{"type":53,"value":1444},"判断にあたっての注意点は3つです。",{"type":48,"tag":1038,"props":1446,"children":1447},{},[1448,1458,1468],{"type":48,"tag":112,"props":1449,"children":1450},{},[1451,1456],{"type":48,"tag":83,"props":1452,"children":1453},{},[1454],{"type":53,"value":1455},"基準は導入前に決め、途中で変えない",{"type":53,"value":1457}," ―― 結果を見てから基準を動かすと、経営への説明力がなくなります",{"type":48,"tag":112,"props":1459,"children":1460},{},[1461,1466],{"type":48,"tag":83,"props":1462,"children":1463},{},[1464],{"type":53,"value":1465},"情報管理上の問題は、効果とは別枠で判断する",{"type":53,"value":1467}," ―― 見えてはいけない資料が回答に出た、といった事象があれば、効果が大きくても権限の是正を先にします",{"type":48,"tag":112,"props":1469,"children":1470},{},[1471,1476],{"type":48,"tag":83,"props":1472,"children":1473},{},[1474],{"type":53,"value":1475},"No-Go は失敗ではない",{"type":53,"value":1477}," ―― 整備不足のまま全社に広げて利用が定着しないほうが、はるかに高くつきます",{"type":48,"tag":161,"props":1479,"children":1481},{"id":1480},"経営への報告資料の型",[1482],{"type":53,"value":1480},{"type":48,"tag":49,"props":1484,"children":1485},{},[1486],{"type":53,"value":1487},"判断結果は、A4またはスライドで5〜6枚にまとめて経営に報告します。構成は次のとおりです。",{"type":48,"tag":1038,"props":1489,"children":1490},{},[1491,1501,1511,1521,1531,1541],{"type":48,"tag":112,"props":1492,"children":1493},{},[1494,1499],{"type":48,"tag":83,"props":1495,"children":1496},{},[1497],{"type":53,"value":1498},"結論",{"type":53,"value":1500}," ―― Go／条件付きGo／No-Go と、その理由を3行で",{"type":48,"tag":112,"props":1502,"children":1503},{},[1504,1509],{"type":48,"tag":83,"props":1505,"children":1506},{},[1507],{"type":53,"value":1508},"利用の状況",{"type":53,"value":1510}," ―― アクティブ利用者の割合と推移、使用レベルの分布、よく使われたアプリ",{"type":48,"tag":112,"props":1512,"children":1513},{},[1514,1519],{"type":48,"tag":83,"props":1515,"children":1516},{},[1517],{"type":53,"value":1518},"効果",{"type":53,"value":1520}," ―― 対象業務ごとの所要時間の前後比較、アンケートの前後比較。ダッシュボードのアシスト時間は参考値として注記付きで",{"type":48,"tag":112,"props":1522,"children":1523},{},[1524,1529],{"type":48,"tag":83,"props":1525,"children":1526},{},[1527],{"type":53,"value":1528},"価値と事例",{"type":53,"value":1530}," ―― 浮いた時間の使い道、現場の具体的な活用例を3〜5件。できれば本人の言葉で",{"type":48,"tag":112,"props":1532,"children":1533},{},[1534,1539],{"type":48,"tag":83,"props":1535,"children":1536},{},[1537],{"type":53,"value":1538},"リスクと課題",{"type":53,"value":1540}," ―― 情報管理上の気づき、データの置き場所や権限の課題、ルールへの問い合わせ",{"type":48,"tag":112,"props":1542,"children":1543},{},[1544,1549],{"type":48,"tag":83,"props":1545,"children":1546},{},[1547],{"type":53,"value":1548},"本展開の計画と投資",{"type":53,"value":1550}," ―― 対象範囲、時期、ライセンス数、研修と整備の計画、費用",{"type":48,"tag":317,"props":1552,"children":1554},{"id":1553},"投資対効果の示し方",[1555],{"type":53,"value":1553},{"type":48,"tag":49,"props":1557,"children":1558},{},[1559,1561,1566],{"type":53,"value":1560},"費用対効果は、",{"type":48,"tag":83,"props":1562,"children":1563},{},[1564],{"type":53,"value":1565},"ライセンス費用を回収するのに必要な時間",{"type":53,"value":1567},"で示すと、経営に伝わりやすくなります。",{"type":48,"tag":96,"props":1569,"children":1570},{},[1571],{"type":48,"tag":49,"props":1572,"children":1573},{},[1574],{"type":53,"value":1575},"回収に必要な削減時間（月） ＝ 1ライセンスの月額費用 ÷ 対象者の時間単価",{"type":48,"tag":49,"props":1577,"children":1578},{},[1579,1581,1588],{"type":53,"value":1580},"第1回では、月額約4,500円を時給3,000円で換算し、月1.5時間の削減で回収できると試算しました。ライセンス価格やキャンペーンは時期によって変わるため、報告時点の価格を",{"type":48,"tag":56,"props":1582,"children":1585},{"href":1583,"rel":1584},"https:\u002F\u002Fwww.microsoft.com\u002Fja-jp\u002Fmicrosoft-365-copilot\u002Fpricing",[60],[1586],{"type":53,"value":1587},"Microsoft 365 Copilot の公式価格ページ",{"type":53,"value":1589},"で確認して計算してください。",{"type":48,"tag":49,"props":1591,"children":1592},{},[1593,1595,1600],{"type":53,"value":1594},"このとき、",{"type":48,"tag":83,"props":1596,"children":1597},{},[1598],{"type":53,"value":1599},"使われていないライセンスは回収できない",{"type":53,"value":1601},"点も必ず書き添えます。本展開の計画に「一定期間使われなかったライセンスは回収・再配分する」ルールを入れておくと、投資判断の納得感が高まります。",{"type":48,"tag":161,"props":1603,"children":1605},{"id":1604},"パイロットでよくある失敗",[1606],{"type":53,"value":1604},{"type":48,"tag":49,"props":1608,"children":1609},{},[1610],{"type":53,"value":1611},"最後に、支援の現場でよく見るつまずきをまとめます。",{"type":48,"tag":108,"props":1613,"children":1614},{},[1615,1625,1635,1645,1655],{"type":48,"tag":112,"props":1616,"children":1617},{},[1618,1623],{"type":48,"tag":83,"props":1619,"children":1620},{},[1621],{"type":53,"value":1622},"ITに詳しい人だけを対象にする",{"type":53,"value":1624}," ―― 結果が良く見えても、本展開したときに同じ効果は出ません。平均的な利用者を含めます",{"type":48,"tag":112,"props":1626,"children":1627},{},[1628,1633],{"type":48,"tag":83,"props":1629,"children":1630},{},[1631],{"type":53,"value":1632},"研修なしで配る",{"type":53,"value":1634}," ―― 最初の1〜2週で「思ったほど賢くない」と感じた人は、そのまま使わなくなります。配る週に研修と部門別の練習を行い、最初の2週間は練習課題で業務の中で使う習慣を作ります（前述の「配る前の研修と、業務で使う練習」）",{"type":48,"tag":112,"props":1636,"children":1637},{},[1638,1643],{"type":48,"tag":83,"props":1639,"children":1640},{},[1641],{"type":53,"value":1642},"期待した回答が返らない問題を放置する",{"type":53,"value":1644}," ―― パイロット中には「社内の資料を探してくれない」「古い情報が出てくる」といった問い合わせが必ず出ます。原因の多くはAIの性能ではなく、データの置き場所、権限、ライセンス、プロンプトの側にあります。問い合わせを記録し、原因ごとに対処します",{"type":48,"tag":112,"props":1646,"children":1647},{},[1648,1653],{"type":48,"tag":83,"props":1649,"children":1650},{},[1651],{"type":53,"value":1652},"ルールを後回しにする",{"type":53,"value":1654}," ―― 何を入力してよいか分からないと、利用は伸びません。生成AIの利用ルールはパイロット開始前に施行します",{"type":48,"tag":112,"props":1656,"children":1657},{},[1658,1663],{"type":48,"tag":83,"props":1659,"children":1660},{},[1661],{"type":53,"value":1662},"報告を利用状況の数字だけにする",{"type":53,"value":1664}," ―― アクティブ率だけでは「で、何が良くなったのか」に答えられません。3層をそろえます",{"type":48,"tag":161,"props":1666,"children":1668},{"id":1667},"ksrogers-の支援",[1669],{"type":53,"value":1670},"K.S.Rogers の支援",{"type":48,"tag":49,"props":1672,"children":1673},{},[1674],{"type":53,"value":1675},"K.S.Rogers では、Microsoft 365 Copilot のパイロットを、設計から判定・経営報告まで伴走支援しています。",{"type":48,"tag":108,"props":1677,"children":1678},{},[1679,1684,1689,1694,1699],{"type":48,"tag":112,"props":1680,"children":1681},{},[1682],{"type":53,"value":1683},"対象部門と対象業務の選定、ベースライン測定の設計",{"type":48,"tag":112,"props":1685,"children":1686},{},[1687],{"type":53,"value":1688},"使用状況レポートと Copilot ダッシュボードの設定、アンケートの設計と集計",{"type":48,"tag":112,"props":1690,"children":1691},{},[1692],{"type":53,"value":1693},"パイロット中の相談会、問い合わせの原因切り分けと対処",{"type":48,"tag":112,"props":1695,"children":1696},{},[1697],{"type":53,"value":1698},"Go\u002FNo-Go 判断の基準づくりと、経営向け報告資料の作成",{"type":48,"tag":112,"props":1700,"children":1701},{},[1702],{"type":53,"value":1703},"本展開に向けたデータの置き場所・権限の整備計画",{"type":48,"tag":49,"props":1705,"children":1706},{},[1707,1709,1715],{"type":53,"value":1708},"M365 の環境整備から Copilot の定着までの支援の範囲と進め方は、",{"type":48,"tag":56,"props":1710,"children":1712},{"href":1711},"\u002Fbusiness\u002Fm365-copilot\u002F",[1713],{"type":53,"value":1714},"Microsoft 365 Copilot 導入・活用支援",{"type":53,"value":1716},"のページにまとめています。",{"type":48,"tag":49,"props":1718,"children":1719},{},[1720,1722,1728],{"type":53,"value":1721},"「ライセンスは買ったが効果を説明できない」「これからパイロットを始めたい」といった段階からご相談いただけます。",{"type":48,"tag":56,"props":1723,"children":1725},{"href":1724},"\u002Fcontact\u002F",[1726],{"type":53,"value":1727},"お問い合わせ",{"type":53,"value":1729},"からお気軽にご連絡ください。",{"type":48,"tag":161,"props":1731,"children":1733},{"id":1732},"まとめ",[1734],{"type":53,"value":1732},{"type":48,"tag":108,"props":1736,"children":1737},{},[1738,1749,1759,1771],{"type":48,"tag":112,"props":1739,"children":1740},{},[1741,1743,1747],{"type":53,"value":1742},"パイロットは",{"type":48,"tag":83,"props":1744,"children":1745},{},[1746],{"type":53,"value":121},{"type":53,"value":1748},"です。1〜2部門・10〜30名程度・準備を除いて8〜12週を目安に設計します",{"type":48,"tag":112,"props":1750,"children":1751},{},[1752,1753,1757],{"type":53,"value":128},{"type":48,"tag":83,"props":1754,"children":1755},{},[1756],{"type":53,"value":133},{"type":53,"value":1758},"で測り、導入前の数値を必ず取ります。時間の短縮だけでなく、浮いた時間の使い道まで押さえます",{"type":48,"tag":112,"props":1760,"children":1761},{},[1762,1764,1769],{"type":53,"value":1763},"Copilot ダッシュボードは便利ですが、",{"type":48,"tag":83,"props":1765,"children":1766},{},[1767],{"type":53,"value":1768},"アシスト時間は推定値",{"type":53,"value":1770},"です。自社で測った数値と並べて報告します",{"type":48,"tag":112,"props":1772,"children":1773},{},[1774,1775,1779],{"type":53,"value":140},{"type":48,"tag":83,"props":1776,"children":1777},{},[1778],{"type":53,"value":145},{"type":53,"value":1780},"。No-Go も正しい判断です",{"type":48,"tag":49,"props":1782,"children":1783},{},[1784,1786,1790,1792,1798],{"type":53,"value":1785},"Copilot 導入の全体像は",{"type":48,"tag":56,"props":1787,"children":1788},{"href":76},[1789],{"type":53,"value":79},{"type":53,"value":1791},"、社内規則が導入の壁になっている場合は",{"type":48,"tag":56,"props":1793,"children":1795},{"href":1794},"\u002Farticles\u002Fcopilot-shanai-kitei-edp\u002F",[1796],{"type":53,"value":1797},"特別編：その社内規則、Microsoft 365 Copilotを禁止していますか？",{"type":53,"value":1799},"をあわせてご覧ください。",{"title":7,"searchDepth":1801,"depth":1801,"links":1802},2,[1803,1804,1812,1815,1820,1821,1822,1825,1826,1827],{"id":163,"depth":1801,"text":166},{"id":312,"depth":1801,"text":315,"children":1805},[1806,1808,1809,1810,1811],{"id":319,"depth":1807,"text":319},3,{"id":406,"depth":1807,"text":406},{"id":444,"depth":1807,"text":444},{"id":527,"depth":1807,"text":530},{"id":757,"depth":1807,"text":760},{"id":826,"depth":1801,"text":829,"children":1813},[1814],{"id":1028,"depth":1807,"text":1031},{"id":1103,"depth":1801,"text":1106,"children":1816},[1817,1818,1819],{"id":1114,"depth":1807,"text":1117},{"id":1145,"depth":1807,"text":1148},{"id":1217,"depth":1807,"text":1220},{"id":1247,"depth":1801,"text":1247},{"id":1334,"depth":1801,"text":1337},{"id":1480,"depth":1801,"text":1480,"children":1823},[1824],{"id":1553,"depth":1807,"text":1553},{"id":1604,"depth":1801,"text":1604},{"id":1667,"depth":1801,"text":1670},{"id":1732,"depth":1801,"text":1732},"markdown","content:articles:copilot-pilot-kouka-sokutei.md","content","articles\u002Fcopilot-pilot-kouka-sokutei.md","articles\u002Fcopilot-pilot-kouka-sokutei","md",[1835,1840,1845,1848,1853,1858,1862,1867,1872,1876,1881],{"_path":1836,"title":1837,"seriesNo":1838,"seriesLabel":1839},"\u002Farticles\u002Fm365-copilot-donyu-roadmap","Microsoft 365 Copilot 導入ロードマップ｜非IT企業がライセンス配布前に決めること",1,"第1回",{"_path":1841,"title":1842,"seriesNo":1843,"seriesLabel":1844},"\u002Farticles\u002Fcopilot-shanai-kitei-edp","Copilotのエンタープライズデータ保護（EDP）とは｜「外部AI禁止」の社内規程でも使えるかの判断手順",1.5,"特別編",{"_path":1846,"title":1847,"seriesNo":1801,"seriesLabel":355},"\u002Farticles\u002Fcopilot-data-okiba-box-sharepoint","Copilotは社内データを学習する？｜参照できるデータの条件とSharePoint・OneDrive・Boxの使い分け",{"_path":1849,"title":1850,"seriesNo":1851,"seriesLabel":1852},"\u002Farticles\u002Fcopilot-mail-chat-ikou-checklist","Exchange Online移行の注意点とLINE WORKSからTeamsへの判断｜Microsoft 365 Copilot導入前チェックリスト",2.5,"第2回（後編）",{"_path":1854,"title":1855,"seriesNo":1856,"seriesLabel":1857},"\u002Farticles\u002Fm365-copilot-iranai-google-hikaku","Microsoft 365 Copilotはいらない？無料版との違い・料金と「Googleより高い」への答え方",2.8,"番外編",{"_path":1859,"title":1860,"seriesNo":1807,"seriesLabel":1861},"\u002Farticles\u002Fcopilot-joho-rouei-sharepoint-kengen","Microsoft 365 Copilotの情報漏洩対策｜SharePoint・OneDrive・Teamsの権限を棚卸しして是正する手順","第3回",{"_path":1863,"title":1864,"seriesNo":1865,"seriesLabel":1866},"\u002Farticles\u002Fcopilot-security-settei-chusho","Microsoft 365 Copilotのセキュリティ設定｜中小企業に秘密度ラベルとDLPは必要か",4,"第4回（前編）",{"_path":1868,"title":1869,"seriesNo":1870,"seriesLabel":1871},"\u002Farticles\u002Fcopilot-sensitivity-label-dlp","Microsoft 365 Copilotの秘密度ラベルとDLP｜「警告」から始める段階設計とライセンス要件",4.5,"第4回（後編）",{"_path":1873,"title":1874,"seriesNo":1875,"seriesLabel":598},"\u002Farticles\u002Fseisei-ai-shanai-rule-sample","生成AIの社内ルールの作り方【サンプル条文付き】｜Microsoft 365 Copilot時代の利用ガイドライン",5,{"_path":1877,"title":1878,"seriesNo":1879,"seriesLabel":1880},"\u002Farticles\u002Fkaihatsu-gaichu-ai-riyou-rule","システム開発を外注するときのAI利用ルール｜開発会社に求める5つの約束と秘密情報の扱い",5.2,"第5回（後編）",{"_path":4,"title":8,"seriesNo":13,"seriesLabel":14},1792682584678]