How to use this page: Open the SPI Reference below to keep the persona's Situation, Pain, and Impact visible while you write. Your work saves automatically. Come back ready to share what you created and what felt hard to write.
Your Assignment
Using the Uptime Owner's Situation, Pain, and Impact — write a short outbound prospecting email that would earn a reply. Don't pitch features. Connect to something they already feel. Aim for something you'd actually send.
Situation
Owns asset uptime, reliability, and availability across one or more facilities
Manages maintenance programs and work order workflows — reactive, preventive, and predictive
Oversees maintenance crews, contractors, and skilled trades — accountable for productivity and safety
Monitors asset performance metrics and reports to senior leadership
Manages maintenance budgets and builds the business case for capital investments
Pain
Stuck reacting to failures instead of preventing them — Most maintenance capacity gets consumed by unplanned work, leaving no bandwidth to build the preventive programs that would stop the cycle.
No real-time visibility into what field teams are doing — Work status, permit activity, and field execution get pieced together through verbal check-ins and end-of-shift reports — not live data.
Can't justify the investment without data to back it up — Without connected data linking maintenance activity to asset availability and avoided risk, the business case to leadership is anecdotal at best.
Impact
Finally get ahead of the work — When asset data, systems, and workflows connect, the reactive cycle starts to break — and maintenance teams have bandwidth to run the programs that reduce the very failures they've been chasing.
Eyes on the field, all the time — Getting live work order status, permit activity, and field progress means interventions happen when they're still useful — not after the shift report lands.
ROI you can actually prove — Connected data linking maintenance activity to asset availability, avoided failures, and production output makes the investment case quantifiable — so the ask stops being anecdotal.
Write Your Email
Room 2
Discovery Call Questions
Persona: Project Leader
How to use this page: Open the SPI Reference to keep the persona visible. Write 2–3 questions per category. Good discovery questions earn the right to go deeper — they don't feel like an interrogation.
Your Assignment
Using the Project Leader's SPI, prepare discovery questions for a first call. Your goal: understand their situation, surface a pain worth solving, and start quantifying the impact. Write 2–3 questions per category — be specific enough that they couldn't apply to any other persona.
Situation
Lead capital project delivery from concept and FEED through construction, commissioning, and handover
Manage EPCs, engineering consultants, and contractors across all project phases
Control project schedule, cost, and scope — accountable for on-time, on-budget delivery
Own engineering documentation and as-built accuracy through to handover
Define and enforce standards for engineering tools, data formats, and project controls
Pain
The as-built rarely matches what was actually designed — Field changes, procurement substitutions, and design revisions pile up throughout a project without getting fully captured — leaving Ops to inherit and address a gap they didn't create.
No single source of truth across a multi-contractor program — With every contractor working in their own systems and formats, project status is always a manual aggregation — and always slightly out of date.
Project closeout is always rushed and always incomplete — As budgets run out and contractors demobilize, the complex docs that operations will rely on for 20 years gets compressed into the final weeks of a multi-year project.
Impact
Handovers worth trusting — When the engineering record stays current throughout the project — not just at closeout — what gets handed over reflects what was actually built, not a best-effort reconstruction.
One version of project truth — A single connected environment where deliverables, changes, and progress feed into one place means project controls work from current data — not a spreadsheet already out of date before it's finished.
Closeout that doesn't crater — Completions and documentation embedded in day-to-day execution mean the final deliverable is always close to done — so the last weeks aren't the most chaotic ones.
Your Discovery Questions
Part 1 — Warm up the conversation with questions that can be easily answered with a "yes," "no," or fact. Get basic context and confirmation of their Situation.
Part 2 — Get them talking and venting. Ask questions that get them to describe their process and the Pain in more detail.
Part 3 — Get them to think and talk about how a solution to their Pain would Impact their business and/or them and their team. What would status quo mean (negatively)?
Room 3
Demo Outline
Persona: Digital Architect
How to use this page: Open the SPI Reference. For each of your 3 impact moments: start with the pain you're addressing, describe exactly what you show (2–3 clicks), connect it to a real customer outcome, then write a question that checks whether they see themselves in it.
Your Assignment
Structure a demo for the Digital Architect. Choose 3 pains from their SPI that your demo can directly address. For each: identify the specific feature or product moment that solves it, bring it to life with a real customer impact, and write a question that gets them thinking about their own version of that result.
Situation
Own enterprise technology architecture and set roadmap and standards across the organization
Evaluate, procure, and govern enterprise software — ERP, CMMS, APM, cloud, and data platforms
Lead or sponsor digital transformation programs — Industry 4.0, connected worker, predictive analytics
Bridge operational technology (OT) field systems and corporate IT infrastructure
Pain
Decades of systems that were never meant to connect — Technology integrations and customizations accumulate over time and create a fragmented landscape that requires significant custom development just to share data.
Digital transformation without real authority or architecture — Ops teams buy point solutions, engineering runs cloud pilots, and IT is accountable for outcomes it doesn't control — disconnected initiatives that generate data but not insight.
Cybersecurity risk is expanding faster than we can keep up — Connecting operational technology to enterprise systems creates exposures that standard IT security wasn't built to handle — especially on OT systems that can't be patched or rebooted.
Impact
Connected without starting over — A platform that bridges disparate OT systems instead of replacing them gives technology leaders something to build analytics and workflows on — without a multi-year infrastructure overhaul.
Transformation that sticks — Connected platforms with clear ownership and measurable outcomes give IT leaders the cross-functional foundation needed to move programs from pilot status to something the business actually runs on.
No more security nightmares — Governance designed for operational environments — not retrofitted from IT playbooks — means the infrastructure running physical operations stays protected as the two worlds converge.
Your Demo — 3 Impact Moments
Impact Moment 1
Pain the customer is dealing with
Feature to demo that addresses the PainOutline 2–3 clicks
Impact exampleThe benefit similar customers see from this feature
Impact questionHow they might benefit from a feature like this
Impact Moment 2
Pain the customer is dealing with
Feature to demo that addresses the PainOutline 2–3 clicks
Impact exampleThe benefit similar customers see from this feature
Impact questionHow they might benefit from a feature like this
Impact Moment 3
Pain the customer is dealing with
Feature to demo that addresses the PainOutline 2–3 clicks
Impact exampleThe benefit similar customers see from this feature
Impact questionHow they might benefit from a feature like this
Room 4
Business Case Summary
Persona: Exec Sponsor
How to use this page: Open the SPI Reference. The Exec Sponsor doesn't want features — they want to know the problem is real, the cost is quantifiable, and the outcome is defensible. Every field below maps to something they'll need to approve or report upward.
Your Assignment
Outline a business case summary for an Exec Sponsor (COO or CFO). Choose a segment's pains and impacts and lay out how they connect to a proposed solution. Keep it executive-tight: one sentence per field where possible.
Situation
Own P&L and strategic performance of an industrial business unit, division, portfolio or ownership group
Set investment priorities and approve CAPEX and OPEX budgets
Hold accountability for safety, regulatory compliance, and operational resilience
Drive transformation programs — digitalization, workforce modernization, energy transition
Align cross-functional leadership on strategic programs and evaluate major technology decisions
Pain
Making major decisions on data that's already weeks old — By the time asset performance, project status, and risk exposure reach the executive level, the underlying situation has already changed.
Too many structural pressures compounding at once — Energy transition, tightening regulation, workforce attrition, and capital scrutiny are all hitting simultaneously — and yesterday's tools and processes weren't built for any of them.
Digital spend is growing but the business case is harder to make — Disconnected implementations, low adoption, and no outcomes framework make it nearly impossible to connect technology investment to measurable operational improvement.
Impact
Decisions on today's data — A real-time view of asset performance, project status, and operational risk means strategic calls get made on current intelligence — not a summary of a situation that's already changed.
Built to take the pressure — Connected systems across engineering, maintenance, and field execution give organizations the resilience to navigate compounding demands — without depending on institutional knowledge that's walking out the door.
ROI that shows — When systems connect across the asset lifecycle instead of isolated pockets, the relationship between technology spend and operational improvement becomes visible, trackable, and reportable.