https://leadous.com/assets/PlatformInitiativeChecklist-DRSTKoFV.js

1import{R as h,u as m,j as e,I as p}from"./index-M8ZQ3eHS.js";import{G as u,e as r}from"./GuideDocumentLayout-CKO47e5D.js";import"./download-6Prx1PYF.js";import"./arrow-left-D1gFAr24.js";const c=[["Defined the business problem","A clear problem keeps the initiative focused on a business need rather than a platform feature."],["Defined measurable outcomes","Measurable outcomes make it possible to prove whether the initiative created value."],["Identified the initiative type","The initiative type clarifies the work, risks, stakeholders, and delivery approach required."],["Documented scope and exclusions","Explicit boundaries prevent scope drift and make tradeoffs visible before work begins."],["Defined the minimum viable outcome","A minimum viable outcome gives the team a practical first milestone and protects the launch from unnecessary complexity."],["Assigned an executive sponsor","An executive sponsor provides decision support, removes obstacles, and keeps the initiative connected to organizational priorities."],["Assigned business and platform owners","Named owners create accountability for both the operating need and the technology that supports it."],["Assigned a project manager","A project manager coordinates dependencies, decisions, timing, and communication across the work."],["Established the working team","A cross-functional team brings the operational, technical, data, and change perspectives required for a durable result."],["Defined decision rights","Decision rights prevent stalled work and clarify who can approve, reject, or escalate important choices."],["Created a RACI matrix","A RACI makes responsibility visible and reduces gaps or duplicated effort between teams."],["Established baseline measurements","A baseline gives the organization a reliable point of comparison for performance after launch."],["Defined business, operational, and technical success metrics","Balanced metrics show whether the initiative works for the business, the operating team, and the platform."],["Audited the current environment","An environment audit surfaces constraints, dependencies, risks, and assets that could affect the initiative."],["Documented current processes","Current-state documentation prevents the team from automating assumptions or losing important operating knowledge."],["Identified technical debt","Known technical debt can change sequencing, cost, risk, and the feasibility of the future state."],["Documented priority use cases","Prioritized use cases focus delivery on the work most likely to create meaningful value."],["Prioritized requirements","Prioritization helps the team make consistent tradeoffs when time, budget, or capacity is limited."],["Defined acceptance criteria","Acceptance criteria create a shared definition of done and make validation less subjective."],["Designed the future-state architecture","A future-state architecture shows how the solution will operate, scale, integrate, and be governed."],["Defined systems of record","Clear systems of record protect data consistency and prevent conflicting ownership of important information."],["Developed the data model","A data model establishes the structure and relationships needed for reliable reporting, operations, and integration."],["Documented integrations","Integration documentation exposes data movement, dependencies, failure points, and ownership before implementation."],["Assessed data quality","Data-quality assessment prevents unreliable or incomplete information from undermining the initiative."],["Developed data mappings","Data mappings make transformations explicit and reduce errors during migration or system connection."],["Reviewed consent and suppression requirements","Consent and suppression decisions protect customer choice, compliance, and channel trust."],["Inventoried campaigns, journeys, workflows, and assets","An inventory reveals what must be preserved, redesigned, retired, or tested."],["Established naming and governance standards","Shared standards improve findability, consistency, reporting, and long-term maintainability."],["Reviewed privacy, security, and compliance requirements","Early review prevents avoidable rework and identifies controls required before launch."],["Identified workstreams and dependencies","Workstream planning shows how teams rely on one another and where sequencing risk exists."],["Developed the project timeline","A realistic timeline aligns expectations and makes critical milestones and decision points visible."],["Established change control","Change control prevents uncontrolled modifications from creating hidden scope, qual

1ity, or operational risk."],["Developed a testing plan","A testing plan ensures the solution is evaluated across requirements, integrations, data, and real operating scenarios."],["Assigned testing owners","Named testing owners make validation work accountable instead of leaving defects between teams."],["Defined future operating roles","Future roles ensure the platform can be administered, supported, governed, and improved after launch."],["Developed training and documentation plans","Training and documentation turn a technical implementation into something teams can use correctly and consistently."],["Established launch-readiness criteria","Launch criteria create an objective gate so enthusiasm does not outrun operational readiness."],["Developed the cutover plan","A cutover plan coordinates the move to the new state while protecting continuity and data integrity."],["Defined stabilization support","Stabilization support gives users and owners a clear path for resolving issues immediately after launch."],["Established post-launch measurement","Post-launch measurement confirms adoption, performance, quality, and value after the initiative is live."],["Created an optimization roadmap","An optimization roadmap turns launch into an operating improvement cycle rather than a finish line."]].map(([t,a])=>({item:t,why:a})),d="A Leadous readiness gate for confirming business, technical, data, governance, launch, and optimization readiness before a platform initiative.",f={structuredData:p("/resources/guides-documentation/platform-initiative-checklist","Platform Initiative Readiness Checklist",d,["How to use this checklist","Platform Initiative Readiness Checklist"])};function g(t){return`<h2>How to use this checklist</h2><div class="checklist-example"><span class="checklist-box is-checked">✓</span><p><strong>Check the circle when the item is complete.</strong> Use the explanation beneath each item to understand what decision or evidence should exist before checking it off.</p></div><h2>Platform Initiative Readiness Checklist</h2><ul class="checklist-form">${c.map(({item:a,why:s},n)=>`<li class="checklist-form-item${t.has(n)?" is-checked":""}"><span class="checklist-box">${t.has(n)?"✓":""}</span><span class="checklist-form-number">${String(n+1).padStart(2,"0")}</span><span><strong>${r(a)}</strong><small>${r(s)}</small></span></li>`).join("")}</ul>`}function y(){const[t,a]=h.useState(()=>new Set);return m("Platform Initiative Readiness Checklist — Leadous",d,void 0,f),e.jsxs(u,{title:"Platform Initiative Readiness Checklist",intro:"The readiness gate for moving from a platform idea to an initiative the organization can govern, launch, and operate.",downloadFileName:"leadous-platform-initiative-readiness-checklist.html",downloadLabel:"Download checklist",downloadBody:g(t),children:[e.jsx("p",{className:"guide-lede",children:"Before beginning a platform initiative, confirm that the organization has made the decisions below. This is a launch gate—not a substitute for the work behind each decision."}),e.jsxs("div",{className:"checklist-instructions",children:[e.jsx("span",{className:"checklist-box is-checked","aria-hidden":"true",children:"✓"}),e.jsxs("div",{children:[e.jsx("strong",{children:"How to use this checklist"}),e.jsx("p",{children:"Check the circle when the item is complete. The explanation beneath each item describes why it matters and what the decision helps protect."})]})]}),e.jsx("div",{className:"guide-checklist-grid",children:c.map(({item:s,why:n},i)=>e.jsxs("label",{className:`guide-checklist-item${t.has(i)?" is-checked":""}`,children:[e.jsx("input",{type:"checkbox",checked:t.has(i),onChange:()=>a(l=>{const o=new Set(l);return o.has(i)?o.delete(i):o.add(i),o})}),e.jsx("span",{className:"checklist-box","aria-hidden":"true",children:t.has(i)?"✓":""}),e.jsx("span",{className:"guide-checklist-number",children:String(i+1).padStart(2,"0")}),e.jsxs("span",{className:"guide-checklist-copy",children:[e.jsx("strong",{children:s}),e.jsx("small",{children:n})]})]},s))})]})}export{y as PlatformInitiativeChecklist};