Vendor Management Rhythms ========================= Slide 1: Vendor Management Rhythms Narration Anna: This section sets up Vendor Management Rhythms. Treat it as the frame for the decisions, handoffs, and evidence that appear in the next slides. Greg: The practical question is simple: by the end, what should a junior IT professional be able to explain, check, or document in a real workplace? On-screen text Vendor Management Rhythms Keep outsourced partners aligned with start-up velocity - Ever had a vendor who thinks "urgent" means "next week"? Rhythms fix that. Slide 2: Why cadence matters Narration Vendor Management Rhythms — Narrative High-growth teams lean on vendors to fill capability gaps long before they can hire specialists. That leverage only works when everyone is working to the same beat. Rituals create shared expectations about responsiveness, decision velocity, and quality gates. Without them, a managed service provider can unknowingly slow the roadmap or miss critical context about upcoming launches. This segment frames cadence as a strategic control system rather than polite catch-ups. We also remind founders that rhythms reduce emotional escalations. When partners know there is a weekly forum to raise blockers, they do not resort to panicked emails at midnight. When the leadership team sees trend data every month, they can intervene early instead of issuing broad-brush ultimatums. Process gives both sides psychological safety to be candid about risks. On-screen text Why cadence matters - Vendors extend your team but follow different incentives and clocks. - Predictable rituals surface risks early before they hit customers. - Rhythm builds trust: expectations, response times, and accountability tighten. Slide 3: Core meeting cadence Narration Establishing cadence rituals Coming out of the "why rhythms matter" segment, we hand learners a concrete operating drumbeat they can deploy on Monday. We outline a three-tier rhythm that keeps partners plugged into strategy and execution. Weekly operations syncs are deliberately short and tactical: review ticket queues, note any SLA breaches, and unblock near-term tasks. Monthly service reviews go a level higher to interrogate trend lines, incident learnings, and improvement experiments. Quarterly business reviews reconnect the relationship to company strategy, budgets, and roadmap shifts. Emphasise that cadence is anchored to meaningful triggers. Align the weekly call before your release deploys, schedule the monthly review after financial close so real cost data is available, and run the quarterly session ahead of contract renewal windows. When rituals connect to existing beats, the right stakeholders attend prepared instead of treating meetings as optional. Close every meeting by logging owners, deadlines, and notes in the shared workspace so momentum compounds instead of evaporating between calls. On-screen text Core meeting cadence - Weekly ops sync (30 min): Ticket queues, blockers, near-term deliverables. - Monthly service review (60 min): KPI scorecard, incident retros, improvement backlog. - Quarterly business review (90 min): Strategic alignment, contract health, roadmap shifts. - Anchor rituals to billing or release cycles so stakeholders show up prepared. - Document outcomes in the shared workspace—no meeting closes without follow-up artefacts. Slide 4: Vendor security assessments Narration Anna: Vendor security assessments focuses attention on a concrete part of the work. Treat security reviews as recurring rituals, not a one-off procurement hurdle, Require up-to-date SOC 2 / ISO 27001 evidence and map controls to your data flows, and Run data-handling tabletop drills: breach notification timing, encryption practices, off-boarding. Greg: In practice, ask who owns the work, what evidence proves it happened, and what handoff comes next. Use the supporting details as a checklist: Require up-to-date SOC 2 / ISO 27001 evidence and map controls to your data flows; Run data-handling tabletop drills: breach notification timing, encryption practices, off-boarding; Align vendor access reviews with your internal identity governance cadence. On-screen text Vendor security assessments - Treat security reviews as recurring rituals, not a one-off procurement hurdle. - Require up-to-date SOC 2 / ISO 27001 evidence and map controls to your data flows. - Run data-handling tabletop drills: breach notification timing, encryption practices, off-boarding. - Align vendor access reviews with your internal identity governance cadence. Slide 5: Contract negotiation basics Narration Anna: Contract negotiation basics focuses attention on a concrete part of the work. Define the difference: SLAs commit to performance, SLRs describe reporting—negotiate both, Tie penalty clauses to business impact (credit for downtime, remediation timelines, escalation paths), and Specify exit strategies: data export formats, transition assistance, knowledge transfer windows. Greg: In practice, ask who owns the work, what evidence proves it happened, and what handoff comes next. Use the supporting details as a checklist: Tie penalty clauses to business impact (credit for downtime, remediation timelines, escalation paths); Specify exit strategies: data export formats, transition assistance, knowledge transfer windows; Capture renewal notice periods and price-uplift caps inside the master services agreement. On-screen text Contract negotiation basics - Define the difference: SLAs commit to performance, SLRs describe reporting—negotiate both. - Tie penalty clauses to business impact (credit for downtime, remediation timelines, escalation paths). - Specify exit strategies: data export formats, transition assistance, knowledge transfer windows. - Capture renewal notice periods and price-uplift caps inside the master services agreement. Slide 6: Cultural fit checkpoints Narration Anna: Cultural fit checkpoints focuses attention on a concrete part of the work. Observe vendor-team rituals: stand-ups, retros, documentation habits—do they match your pace?, Meet the delivery leads who will work day-to-day, not just the sales crew, and Align on communication norms (channels, response times, decision logs) before signing. Greg: In practice, ask who owns the work, what evidence proves it happened, and what handoff comes next. Use the supporting details as a checklist: Meet the delivery leads who will work day-to-day, not just the sales crew; Align on communication norms (channels, response times, decision logs) before signing; Use pilot projects or trial sprints to test collaboration chemistry safely. On-screen text Cultural fit checkpoints - Observe vendor-team rituals: stand-ups, retros, documentation habits—do they match your pace? - Meet the delivery leads who will work day-to-day, not just the sales crew. - Align on communication norms (channels, response times, decision logs) before signing. - Use pilot projects or trial sprints to test collaboration chemistry safely. Slide 7: Designing the scorecard Narration Anna: Designing the scorecard focuses attention on a concrete part of the work. Blend SLAs/SLRs (uptime, response) with adoption and satisfaction signals, Track leading indicators: backlog age, staffing ratios, change failure rate, and Pull data from shared dashboards; freeze snapshots before each review. Greg: In practice, ask who owns the work, what evidence proves it happened, and what handoff comes next. Use the supporting details as a checklist: Track leading indicators: backlog age, staffing ratios, change failure rate; Pull data from shared dashboards; freeze snapshots before each review; Use traffic-light status to trigger escalations and executive visibility. On-screen text Designing the scorecard - Blend SLAs/SLRs (uptime, response) with adoption and satisfaction signals. - Track leading indicators: backlog age, staffing ratios, change failure rate. - Pull data from shared dashboards; freeze snapshots before each review. - Use traffic-light status to trigger escalations and executive visibility. - Example metric bands: API response time <200ms (green), 200–500ms (yellow), >500ms (red). Image: Weekly, monthly and quarterly vendor meeting cadence feeding a shared scorecard of availability, response time, change failure, backlog age and compliance metrics Meeting cadence on the left feeds the shared scorecard on the right Slide 8: Scorecard template snapshot Narration Anna: Scorecard template snapshot focuses attention on a concrete part of the work. Availability (SLA): Green ≥ 99.9%, Yellow 99.5–99.89%, Red 4x target, and Change failure rate: Green 20%. Greg: In practice, ask who owns the work, what evidence proves it happened, and what handoff comes next. Use the supporting details as a checklist: First-response time (SLR): Green 4x target; Change failure rate: Green 20%; Backlog age (critical tickets): Green 5. On-screen text Scorecard template snapshot - Availability (SLA): Green ≥ 99.9%, Yellow 99.5–99.89%, Red < 99.5%. - First-response time (SLR): Green <15m P1 / <1h P2, Yellow double the target, Red >4x target. - Change failure rate: Green <10%, Yellow 10–20%, Red >20%. - Backlog age (critical tickets): Green <3 days, Yellow 3–5, Red >5. - Stakeholder NPS: Green ≥50, Yellow 20–49, Red <20. - Compliance status: Green = audits current, Yellow = evidence pending, Red = gap identified. Slide 9: Running the weekly sync Narration Running the weekly ops sync The weekly sync should feel like a high-signal stand-up, not a status monologue. Encourage learners to cap the session at 30 minutes with a three-slide deck: performance snapshot, escalations, and upcoming changes. Assign owners to every yellow or red metric before the call ends and log due dates in the shared tracker. Anything without a name or deadline will resurface as an incident later. Use the final minutes for a "no surprises" scan. Ask explicitly about launches, audits, marketing campaigns, or staffing changes that could impact capacity. Offer a concrete prompt: "We're launching the Black Friday campaign next week and expect 10x traffic—can your monitoring handle the alert volume?" That habit gives vendors permission to flag constraints before they become outages and reinforces that the start-up wants partnership, not heroics. It also prevents the 3 a.m. vendor panic call that starts with "We didn't know you were deploying today...". On-screen text Running the weekly sync - Start with a three-slide deck: numbers, escalations, upcoming changes. - Confirm ownership on every red/yellow metric with due dates. - Capture blockers requiring internal help (access, decisions, budget). - Close with "no surprises" check: launches, audits, peak demand. Slide 10: Monthly service review ritual Narration Anna: Monthly service review ritual focuses attention on a concrete part of the work. Walk through the scorecard trend lines, not just last month's value, Highlight incident learnings and verify action item closure, and Revisit capacity forecasts and staffing assumptions for the next 60 days. Greg: In practice, ask who owns the work, what evidence proves it happened, and what handoff comes next. Use the supporting details as a checklist: Highlight incident learnings and verify action item closure; Revisit capacity forecasts and staffing assumptions for the next 60 days; Agree on 2-3 experiments or optimisations before the next review. On-screen text Monthly service review ritual - Walk through the scorecard trend lines, not just last month's value. - Highlight incident learnings and verify action item closure. - Revisit capacity forecasts and staffing assumptions for the next 60 days. - Agree on 2-3 experiments or optimisations before the next review. - Celebrate wins and recognise vendor team contributions to maintain relationship health. Slide 11: Crisis management drills Narration Anna: Crisis management drills focuses attention on a concrete part of the work. Pre-build a shared incident channel, escalation ladder, and on-call rotation map, Run joint simulations for vendor outage, data breach, and sudden demand spikes, and Define decision authority for rollback, customer comms, and regulatory notifications. Greg: In practice, ask who owns the work, what evidence proves it happened, and what handoff comes next. Use the supporting details as a checklist: Run joint simulations for vendor outage, data breach, and sudden demand spikes; Define decision authority for rollback, customer comms, and regulatory notifications; Capture learnings in a post-mortem template shared across companies. On-screen text Crisis management drills - Pre-build a shared incident channel, escalation ladder, and on-call rotation map. - Run joint simulations for vendor outage, data breach, and sudden demand spikes. - Define decision authority for rollback, customer comms, and regulatory notifications. - Capture learnings in a post-mortem template shared across companies. Slide 12: Make-vs-buy guardrails Narration Anna: Make-vs-buy guardrails focuses attention on a concrete part of the work. Reassess quarterly: does outsourcing still unlock speed or introduce drag?, Model total cost: subscription, integration effort, shadow teams, compliance overhead, and Evaluate strategic control: IP sensitivity, customer intimacy, regulatory obligations. Greg: In practice, ask who owns the work, what evidence proves it happened, and what handoff comes next. Use the supporting details as a checklist: Model total cost: subscription, integration effort, shadow teams, compliance overhead; Evaluate strategic control: IP sensitivity, customer intimacy, regulatory obligations; Document thresholds that trigger RFPs or insourcing explorations. On-screen text Make-vs-buy guardrails - Reassess quarterly: does outsourcing still unlock speed or introduce drag? - Model total cost: subscription, integration effort, shadow teams, compliance overhead. - Evaluate strategic control: IP sensitivity, customer intimacy, regulatory obligations. - Document thresholds that trigger RFPs or insourcing explorations. Slide 13: Case study: Stripe vs. building payments Narration Anna: Case study: Stripe vs. building payments focuses attention on a concrete part of the work. Speed: Stripe SDKs let you launch in weeks; in-house build requires new headcount, Cost: Fees look high, but compare to hiring, PCI scope, 24/7 monitoring, and Control: Outsourcing reduces roadmap control; negotiate premium support for reliability. Greg: In practice, ask who owns the work, what evidence proves it happened, and what handoff comes next. Use the supporting details as a checklist: Cost: Fees look high, but compare to hiring, PCI scope, 24/7 monitoring; Control: Outsourcing reduces roadmap control; negotiate premium support for reliability; Risk: Stripe's redundancy is proven; your custom stack must reach the same bar. On-screen text Case study: Stripe vs. building payments - Speed: Stripe SDKs let you launch in weeks; in-house build requires new headcount. - Cost: Fees look high, but compare to hiring, PCI scope, 24/7 monitoring. - Control: Outsourcing reduces roadmap control; negotiate premium support for reliability. - Risk: Stripe's redundancy is proven; your custom stack must reach the same bar. Slide 14: Case study: Zendesk vs. building support ops Narration Anna: Case study: Zendesk vs. building support ops focuses attention on a concrete part of the work. Speed: Zendesk templates, macros, and AI triage accelerate support launch within days, Cost: Subscription plus integration vs. hiring, training, and managing a 24/7 support desk, and Control: Platform roadmap dictates feature availability; in-house team can craft bespoke workflows. Greg: In practice, ask who owns the work, what evidence proves it happened, and what handoff comes next. Use the supporting details as a checklist: Cost: Subscription plus integration vs. hiring, training, and managing a 24/7 support desk; Control: Platform roadmap dictates feature availability; in-house team can craft bespoke workflows; Risk: Vendor outage impacts customer service; internal team faces burnout without mature processes. On-screen text Case study: Zendesk vs. building support ops - Speed: Zendesk templates, macros, and AI triage accelerate support launch within days. - Cost: Subscription plus integration vs. hiring, training, and managing a 24/7 support desk. - Control: Platform roadmap dictates feature availability; in-house team can craft bespoke workflows. - Risk: Vendor outage impacts customer service; internal team faces burnout without mature processes. Slide 15: Documentation + tooling Narration Anna: Documentation + tooling focuses attention on a concrete part of the work. Centralise agendas, scorecards, and action logs in a shared workspace, Version notes and decisions to protect institutional memory through turnover, and Automate reminders via your ticketing or CRM to chase overdue items. Greg: In practice, ask who owns the work, what evidence proves it happened, and what handoff comes next. Use the supporting details as a checklist: Version notes and decisions to protect institutional memory through turnover; Automate reminders via your ticketing or CRM to chase overdue items; Store vendor runbooks alongside incident response and onboarding guides. On-screen text Documentation + tooling - Centralise agendas, scorecards, and action logs in a shared workspace. - Version notes and decisions to protect institutional memory through turnover. - Automate reminders via your ticketing or CRM to chase overdue items. - Store vendor runbooks alongside incident response and onboarding guides. - Future you will thank present you for taking notes—future you is less patient with mystery decisions. Slide 16: Takeaways for founders Narration Building a meaningful scorecard Scorecards convert gut feel into shared evidence. Coach learners to combine SLA/SLR metrics—response time, resolution time, uptime—with adoption and satisfaction data such as NPS from internal stakeholders or product usage analytics. Leading indicators like backlog age, staffing ratios, and change failure rate provide early warning signals before contractual breaches occur. Stress the importance of data hygiene. Partners should pull metrics from a single source of truth, snapshot them before the review, and annotate anomalies. Colour coding helps executives parse quickly, but it must link to predefined thresholds that automatically trigger escalation or executive awareness. The scorecard becomes a living document for accountability. Show an example template to make the abstract concrete: availability ≥99.9% stays green, 99.5–99.89% is yellow, anything lower turns red. Pair that with first-response targets (green <15 minutes for P1 tickets), change failure rate bands (<10% green, 10–20% yellow), backlog age for critical tickets (<3 days green), stakeholder NPS (≥50 green), and compliance evidence status. When facilitators can point to six crisp metrics with thresholds, learners understand how to translate principles into dashboards. On-screen text Takeaways for founders - Ritualise touchpoints so vendors feel part of the operating rhythm. - Keep scorecards visible—green metrics get celebrated, red ones trigger swift support. - Treat make-vs-buy as a living decision, not a one-off slide. - Document relentlessly; future you (or your successor) will need the receipts.