/* global React, Card, CardHeader, PageHeader, leadershipBuckets, orgRolePhases, healthCategories, stack, automationDomains, accents */ // --------------------------------------------------------------------------- // 90 Day Plan — question as header, answer as subheader, supporting cards below // --------------------------------------------------------------------------- const plan90Sections = [ { id: "inventory", phase: "Phase 01", range: "Days 1–14", navTitle: "Priorities", topics: [ { q: "What are the first three priorities for the first 90 days?", a: "In order to support the CEO, it is paramount that the CoS has integrated with the team and gained a 360° perspective of the business. The first 90 days should be a ramp from integration to execution.", blocks: [ { type: "priorities", items: [ { n: 1, title: "Discovery & Definition", body: "Develop a comprehensive understanding of the organization across every dimension that affects execution, through the people and processes that exist today, and define the gaps for bringing strategy into execution. Identify team strengths, weaknesses, and opportunities for infrastructural improvement. Build depth of knowledge in how all aspects of the product and business align with the people and processes today.", subitems: [ "KPIs, metrics, key initiatives, platform architecture, integrations, and customer dynamics", "Hands-on project work with teams to build trust and understanding of problems before jumping in with solutions", "Actionable improvements for operational bottlenecks, process quality, data hygiene, project management, and meeting effectiveness", "Validate performance levers that can unlock organizational capability, efficiency, and automation", ], }, { n: 2, title: "Operational Cadence", body: "Implement and facilitate best practices for team collaboration, communication, and decision-making.", subitems: [ "Calibrate meeting efficiency and project calendar around priority initiatives", "Adjust meeting schedules and check-ins to drive project milestones and department goals", "Ladder daily, weekly, and monthly tasks and meeting schedules to KPIs", "Leverage cross-functional project management frameworks to bring the whole team into the same rhythm", ], }, { n: 3, title: "Foundation for Accountability", body: "Clarity of ownership, acknowledgement of success, and consistent communication of expectations enforce social workplace norms that create a culture of accountability.", subitems: [ "Creating a visible, laddered structure for cascading goals from company level through department to daily work — everyone knows how they impact company goals and feels responsible to the team, not just leadership", "Establishing clear decision rights and ownership for every project and department function", "Building channels to celebrate wins and reinforce a culture of accountability", "Making KPIs the primary topic of conversation across the organization", "Calibrating performance mechanics with team leads and metric-led management in areas that are not keeping pace", "Implementing time-saving automations, workflow improvements, and a layer of visibility across the company where it can eliminate communication gaps or data silos", ], }, ], }, ], }, { q: "Why that sequence?", blocks: [ { type: "priorities", numbered: true, items: [ { n: 1, title: "Discovery & Definition", body: "Understanding current company and business dynamics is critical to lead and get buy-in from the team and executive leadership. Aligning an execution strategy with Ryan and Ari first will allow the CoS to work directly with the team and free up Ryan from day-to-day management.", }, { n: 2, title: "Operational Cadence", body: "With an understanding of the team's capacity, capabilities, and workload, the CoS will have the knowledge to streamline the workforce around priorities and provide the right level of hands-on support to transition to an accelerated pace.", }, { n: 3, title: "Foundation for Accountability", body: "Systems infrastructure can be implemented more seamlessly around a team that has clear ownership structure around goals and deadlines. Systems will complement this through visibility first. This will also give leadership better insight into human-reliant workflows and areas for agentic automation.", }, ], }, ], }, { q: "What must stabilize before anything else is optimized?", a: "Clarity, decision velocity, and reliable execution towards KPIs. Aligning platform tools is paramount to stabilize. And as the pace accelerates, it will elevate and prioritize technical solutions to be implemented. The team must also be able to operate without relying on Ryan's operational skillset or tribal knowledge to make decisions and get things done.", blocks: [ { type: "bullets", label: "Immediate focus area to address", flat: true, circle: true, items: [ "Multiple initiatives active with inconsistent visibility", "Ownership unclear when projects stall", "Heavy manual coordination in Slack", "Critical knowledge lives in people, not systems", ], }, ], }, ], }, { id: "rhythm", phase: "Phase 02", range: "Days 7–21", navTitle: "Operating rhythm", topics: [ { q: "How do initiatives move from decision → execution → completion?", a: "Set standards for ownership in each department function, department KPIs, project objectives, and company-wide initiatives, reinforced in practice through project management software: assignments, task tracking, dependencies, meeting structure, and scheduling. Projects should have formal kick-offs with key stakeholders only after meeting with the CoS to align objectives and outcomes with priorities and team bandwidth. Staged milestones should be set for completing key deliverables so the execution pipeline does not bottleneck. This is also a key element to drive accountability in practice.", }, { q: "What rhythms and systems come first?", a: "Weekly syncs across leadership, departments, and core functions. Paired with systems work to align ClickUp, Slack, sales and marketing platforms, ERP, and the knowledge base around KPIs and goals.", blocks: [ { type: "split", label: "Rhythm & systems", flat: true, cols: [ { title: "Operating rhythm", items: [ "Weekly leadership team sync", "Weekly department leads sync", "Sales and marketing funnel weekly", "Weekly production sync", "Project-based check-in schedule", "Bi-weekly finance / HR sync", ], }, { title: "Systems", items: [ { title: "ClickUp + Slack", detail: "Optimize sync between ClickUp, Slack, and meeting schedule around KPIs and goals", }, { title: "Sales & marketing", detail: "Review sales and marketing processes and platform utilization", }, { title: "ERP", detail: "Review ERP and production forecasting", }, { title: "Knowledge base", detail: "Knowledge base / data lake (department and company)", }, ], }, ], }, ], }, { q: "How do you handle leaders who miss commitments?", paragraphs: [ "Diagnose missed commitments on the first miss with the team lead and individual. Log conversations and action plans. Discuss hurdles and priorities to ensure the employee knows the expectations and has the right information to do the job.", "Continued misses should be evaluated in a more serious manner. A conversation about the responsibilities of the role may be in order depending on the reason for the miss. Weekly check-ins should be set against a target commitment date.", "If the target commitment date is missed, a PIP should be set with the aid of the HR manager and signed off by the CEO. The CEO may meet with the employee based on the nature of the missed commitments.", "At this point it is an up-or-out decision for the employee. The company can manage next steps based on performance.", "This approach does not take every scenario into account but creates multiple documented touchpoints with escalating cause and effect for under performers.", ], }, ], }, { id: "knowledge", phase: "Phase 03", range: "Days 14–60", navTitle: "Knowledge & visibility", topics: [ { q: "Which tribal knowledge puts the business at greatest risk?", a: "Regulatory and compliance: This is a landscape that is moving quickly, with many agencies and protocols to consider. Starting over would be a big headache for the business and would likely rely on expensive outside consulting if that tribal knowledge was lost. This dovetails into every production-floor process that touches the product.", }, { q: "What should leadership see in real time?", a: "Four internal health lenses plus external events in the regulatory landscape.", blocks: [ { type: "healthGrid", label: "Core health lenses" }, ], }, { q: "How do KPIs connect to the operating roadmap?", paragraphs: [ "All KPIs should originate from and contribute to company goals. Company goals are achieved through milestones and project completion. Those are achieved by hitting the defined KPIs.", "All KPIs should be plotted by the department or project team and tie directly to projects in Asana or ClickUp. Projects should tie to a major initiative, milestone, or subset of KPIs.", "KPIs also connect to the day-to-day operations of teams across marketing, sales, support, and supply chain. Any KPI can be boiled down to the daily metrics needed to hit quarterly KPIs.", "These all tie to the operating budget: how we track to forecast, where we need to increase spend, or where spend has increased without improvement to our KPIs. Performance against KPIs should inform quarterly strategy and planning decisions.", ], }, ], }, { id: "systems", phase: "Phase 04", range: "Days 60–90", navTitle: "Systems & leverage", topics: [ { q: "What Should Be Automated First", a: "Focus on workflows that are high-volume, repetitive, and low-risk:", blocks: [ { type: "table", label: "Automation opportunities", flat: true, rows: [ { label: "Order communications", value: "Confirmation emails, shipping notifications, reorder reminders, and status updates are nearly fully automatable", }, { label: "Internal reporting", value: "Real-time dashboards replace manual data aggregation entirely", }, { label: "Supplier communication", value: "PO monitoring, overdue delivery flags, and follow-up sequences can be automated", }, { label: "Compliance documentation", value: "COA summaries, certificate expiration tracking, compliance first drafts, and regulatory change alerts can be automated", }, ], }, ], }, { q: "What Must Remain Human", a: "Anything touching product integrity, wholesale partner trust, or regulatory standing must remain human-led with system support — not system-led with human oversight.", blocks: [ { type: "bullets", flat: true, circle: true, items: [ "Quality control decisions on raw botanical material", "Key wholesale account relationships with meaningful revenue concentration", "Regulatory strategy in a scrutinized category", "All hiring, performance, and culture decisions", "Brand direction and product strategy", ], }, { type: "bullets", label: "Where AI Realistically Solves Bottlenecks", flat: true, items: [ "Near-term genuine value comes from knowledge retrieval, operational pattern detection, first-draft generation for high-volume documents, and meeting intelligence. AI can capture decisions and action items accurately without manual effort, eliminating rework and communication delays.", ], }, ], }, { q: "What is the operating intelligence stack?", blocks: [{ type: "stackPath", label: "Operating intelligence stack" }], }, { q: "Give examples of AI-enabled workflows, automations, dashboards, agents, or operational systems you would explore implementing.", blocks: [ { type: "priorities", items: [ { n: 1, title: "Internal Knowledge Agent", body: "Build a searchable, AI-queryable knowledge base indexed against documented processes, compliance requirements, supplier standards, product specifications, and SOPs. Any team member can ask a natural language question and receive a sourced, accurate answer instead of interrupting a colleague. This is the first priority because it multiplies the effectiveness of existing documentation and frees leadership from answering routine questions.", }, { n: 2, title: "Wholesale Account Health Monitoring", body: "Use sales data, order frequency, and account history to surface early churn signals and trigger automated human follow-up workflows. This enables proactive relationship management before customers slip away.", }, { n: 3, title: "Compliance Monitoring and Documentation Assistant", body: "Track regulatory developments relevant to kava and kratom, summarize changes in plain language, and draft required documentation for human review. This is risk management infrastructure, not a convenience feature.", }, { n: 4, title: "Operational Anomaly Detection", body: "Monitor batch yields, raw material quality metrics, supplier lead times, and inventory levels against historical baselines. Surface deviations before they become crises.", }, ], }, { type: "stackLayer", label: "Dashboard modules", layer: "dashboard", flat: true }, ], }, { q: "What is the operating intelligence architecture — and where does automation apply?", blocks: [ { type: "architecture", label: "Architecture" }, ], }, { q: "Where do you believe AI creates the greatest leverage operationally?", a: "AI creates greatest operational leverage in integrations, systems administration, workflow automation, data intelligence, prototyping, and elimination of busywork. The common thread: AI excels where volume is high, the task is repetitive, and the stakes of a single error are low.", blocks: [], }, { q: "Where do you think companies misuse AI operationally?", a: "Summaries without data, chatbots on broken workflows, and automation before ownership exists.", blocks: [ { type: "accentCards", label: "Anti-patterns", cards: [ { title: "No data layer", accent: "orange", lines: ["Strategy theater", "Untrusted summaries"] }, { title: "Broken workflow", accent: "orange", lines: ["Chatbot on chaos", "Vanity dashboards"] }, { title: "Wrong sequence", accent: "neutral", lines: ["Automate before ownership", "No single owner"] }, ], }, { type: "priorities", items: [ { n: 1, title: "Automating Unclean Processes", body: "Deploying AI before underlying data is clean and processes are documented amplifies garbage. Garbage in moves faster with AI. Always establish process clarity and data quality first.", }, { n: 2, title: "Cost Cutting Instead of Capability Expansion", body: "Treat AI deployment as capability expansion, not headcount reduction. Hollowing out human functions before AI systems are reliable enough to replace them creates risk and destroys morale.", }, ], }, ], footer: "The right approach: AI handles scaling and repetition; humans focus on judgment, exceptions, and relationships.", }, { q: "What should Ryan and Ari stop doing because of this role?", a: "Initiative tracking, cross-functional coordination, status loops, operational admin, and routine approvals within documented thresholds. They keep strategy, capital, partnerships, brand, senior talent, and external regulatory matters.", blocks: [ { type: "buckets", label: "Leadership leverage model", lead: "Ryan's highest-value work is direction, capital, partnerships, and culture — not operational coordination.", buckets: leadershipBuckets, }, ], }, { q: "How does the role evolve as the company matures?", paragraphs: [ "The business has a strong footing to reach steady state growth in the current regulatory environment and can be set up to absorb additional wins if positive direction as well as be set up for self balanced business. The outcome for the company hinges on the regulatory landscape but is currently positioned to execute against multiple scenarios.", "The role will transition from optimizing the team, workflows and process into scaling systems to grow the business with less resources.", "Operationally the business harness that is created will give the optionality for net-new value creation and/or a copy+paste to expansion strategy in the same market or across different industries.", ], blocks: [ { type: "phases", label: "Role evolution", phases: orgRolePhases, }, ], }, ], }, ]; // --------------------------------------------------------------------------- // Systems-derived visuals (from Automation.jsx / AutomationData.jsx) // --------------------------------------------------------------------------- const STACK_PATH_IDS = ["sources", "etl", "store", "dashboard", "ai"]; function Plan90StackPath({ label }) { return (
{STACK_PATH_IDS.map((id) => { const layer = stack.find((l) => l.id === id); if (!layer) return null; return (
{layer.label}

{layer.note}

); })}
); } function Plan90StackLayerCards({ label, layerId, flat }) { const layer = stack.find((l) => l.id === layerId); if (!layer?.cards) return null; const cols = layer.cards.length >= 6 ? 3 : layer.cards.length >= 5 ? 3 : layer.cards.length <= 2 ? 2 : 3; const tiles = (
{layer.cards.map((c, i) => (
{c.title}
{c.lines && ( )} {(c.cadence || c.source) && (

{[c.cadence, c.source].filter(Boolean).join(" · ")}

)} {c.meta && !c.cadence &&

{c.meta}

}
))}
); if (flat) { return (
{label &&
{label}
} {layer.note &&

{layer.note}

} {tiles}
); } return ( {tiles} ); } function Plan90HealthGrid({ label }) { return (
{label &&
{label}
}
{healthCategories.map((h, i) => (
{String(i + 1).padStart(2, "0")} {h.title}
{h.cadence}
    {h.items.map((it, j) =>
  • {it}
    • )}
))}
); } function Plan90Alerts({ label }) { const store = stack.find((l) => l.id === "store"); const rules = store?.threeCol?.find((c) => c.rules)?.rules || []; return (
{rules.map((r, i) => (
{r.rule}
))}
); } function Plan90Architecture({ label }) { const Diagram = window.SystemsStackDiagram; if (!Diagram) return null; return (
{label &&
{label}
}
); } function Plan90Domains({ label }) { const Domains = window.SystemsAutomationDomains; if (!Domains) return null; return (
{label &&
{label}
}
); } function Plan90AccentCards({ label, cards }) { const cols = cards.length <= 2 ? 2 : 3; return (
{cards.map((c, i) => (
{c.title}
    {c.lines.map((line, j) =>
  • {line}
    • )}
))}
); } // --------------------------------------------------------------------------- // Card shell — supporting content only // --------------------------------------------------------------------------- function Plan90Card({ label, note, lead, children }) { return (

{label}

{lead &&

{lead}

} {note &&

{note}

}
{children}
 ); } function PlanBlock({ block }) { if (block.type === "stackPath") { return ; } if (block.type === "architecture") { return ; } if (block.type === "domains") { return ; } if (block.type === "stackLayer") { return ( ); } if (block.type === "healthGrid") { return ; } if (block.type === "alerts") { return ; } if (block.type === "accentCards") { return ; } if (block.type === "priorities") { return (
    {block.items.map((p) => (

  • {p.title}

    {p.body &&

    {p.body}

    } {p.subitems?.length > 0 && (
      {p.subitems.map((text, i) =>
    • {text}
      • )}
    )} {!p.body && ( <> {p.summary &&

    {p.summary}

    } {p.rows?.length > 0 && (
      {p.rows.map((row, i) => (
    • {row.label} {row.value}
      • ))}
    )} )}
    • ))}
); } if (block.type === "bullets") { const list = (
    {block.items.map((t, i) =>
  • {t}
    • )}
); if (block.flat) { return (
{block.label &&
{block.label}
} {list}
); } return {list}; } if (block.type === "table") { const table = (
{block.rows.map((row, i) => (
{row.label}
{row.value}
))}
); if (block.flat) { return (
{block.label &&
{block.label}
} {block.note &&

{block.note}

} {table}
); } return ( {table} ); } if (block.type === "tiles") { const cols = block.tiles.length === 4 ? 4 : block.tiles.length <= 2 ? 2 : 3; return (
{block.tiles.map((t, i) => (
{t.title}
{t.body &&

{t.body}

}
))}
); } if (block.type === "split") { const split = (
{block.cols.map((col, i) => { const simpleItems = col.items?.length > 0 && col.items.every((item) => typeof item === "string"); return (
{col.title}
{col.items?.length > 0 ? (
    {col.items.map((item, j) => (
  • {typeof item === "string" ? ( item ) : ( <> {item.title} {item.detail && {item.detail}} )}
    • ))}
) : (
{col.rows.map((row, j) => (
{row.label}
{row.value}
))}
)}
); })}
); if (block.flat) { return (
{block.label &&
{block.label}
} {split}
); } return {split}; } if (block.type === "groups") { return (
{block.groups.map((g, i) => (
{g.title} {g.meta && {g.meta}}
{g.rows.map((row, j) => (
{row.label}
{row.value}
))}
))}
); } if (block.type === "buckets") { return (
{block.buckets.map((b, i) => (
{b.title}
    {b.items.map((item, j) =>
  • {item}
    • )}
))}
); } if (block.type === "phases") { const cols = block.phases.length <= 2 ? 2 : 3; return (
{block.phases.map((p, i) => (
{p.phase}

{p.desc}

    {p.focus.map((f, j) =>
  • {f}
    • )}
))}
); } if (block.type === "matrix") { return (
{block.rows.map((row, i) => (
{row.area}
Why it matters

{row.why}

Approach

{row.approach}

))}
); } if (block.type === "prose") { return ( {block.paragraphs.map((p, i) => (

{p}

))} ); } return null; } function Plan90Tasks({ items }) { return (
Tasks
    {items.map((m, i) => (

  • {m.title}

    {m.desc &&

    {m.desc}

    }
    • ))}
); } // --------------------------------------------------------------------------- // Question unit — header = question, subheader = answer, cards below // --------------------------------------------------------------------------- function Plan90Topic({ topic, isLast, topicId }) { return (

{topic.q}

{topic.paragraphs?.length > 0 ? topic.paragraphs.map((p, i) =>

{p}

) : topic.a &&

{topic.a}

}
{topic.blocks && topic.blocks.length > 0 && (
{topic.blocks.map((block, i) => ( ))}
)} {topic.footer &&

{topic.footer}

}
); } function Plan90Section({ section, isLast, registerRef }) { return (
{section.topics.map((topic, i) => ( ))}
{section.milestones?.length > 0 && (
)}
); } function Plan90Outline({ sections, activeId, expandedId, onPhaseClick, onQuestionJump }) { return (
    {sections.map((sec) => { const active = sec.id === activeId; const expanded = sec.id === expandedId; return (
  1. {expanded && sec.topics?.length > 0 && (
      {sec.topics.map((topic, i) => (
      • ))}
    )}
    2. ); })}
); } function Plan90() { const sectionRefs = React.useRef({}); const [activeId, setActiveId] = React.useState(plan90Sections[0].id); const [expandedId, setExpandedId] = React.useState(null); React.useEffect(() => { const scroller = document.querySelector("main"); if (!scroller) return; const onScroll = () => { const anchor = scroller.getBoundingClientRect().top + 140; let current = plan90Sections[0].id; for (const sec of plan90Sections) { const el = sectionRefs.current[sec.id]; if (el && el.getBoundingClientRect().top <= anchor) current = sec.id; } setActiveId((prev) => (prev === current ? prev : current)); }; onScroll(); scroller.addEventListener("scroll", onScroll, { passive: true }); return () => scroller.removeEventListener("scroll", onScroll); }, []); const scrollMainTo = (el, offset = 24) => { const scroller = document.querySelector("main"); if (!scroller || !el) return; const top = el.getBoundingClientRect().top - scroller.getBoundingClientRect().top + scroller.scrollTop - offset; scroller.scrollTo({ top, behavior: "smooth" }); }; const scrollToSection = (id) => { scrollMainTo(sectionRefs.current[id]); }; const handlePhaseClick = (id) => { setExpandedId((prev) => (prev === id ? null : id)); scrollToSection(id); }; const scrollToQuestion = (sectionId, topicIndex) => { const el = document.getElementById(`plan90-${sectionId}-q${topicIndex}`); scrollMainTo(el, 20); }; return (
{plan90Sections.map((sec, i) => ( { sectionRefs.current[sec.id] = el; }} /> ))}
); } Object.assign(window, { Plan90 });