MapleJockey design partner interview guide

· Download Markdown

Draft | 12 November 2026 | 30 minutes | No outreach authorised by this document

Purpose: establish whether a specific workload decision is important enough to justify an assessment, whether useful evidence is available, and whether the proposed package is better than the buyer’s current approach. This is research, not a sales commitment or compliance assessment.

Opening and context | 3 minutes

“We’re developing MapleJockey to help Canadian organisations understand workload control and recovery. We’re testing a narrow assessment, not offering a sovereignty certification. I’d like to understand a recent real decision and what would have helped. Please avoid sharing personal information, credentials or restricted customer material.”

Ask permission before recording; default to written, minimum-necessary notes. Do not request raw customer data during an interview.

Last real decision | 7 minutes

  1. Tell me about the last time a customer, procurement team or executive asked where a workload’s data went or who could access it. What happened?
  2. Which workload was involved? What deadline, renewal, bid or operational decision depended on the answer?
  3. Who needed to approve it, and what evidence did they accept or reject?
  4. How did you produce the answer? Which people, tools and outside advisers were involved? What did it cost in time or money?
  5. What remained unresolved, and what was the practical consequence? If there was no consequence, record that too.

Segment probes: For an MSP, distinguish its own obligations from each customer’s and identify repeatable work. For a public-sector/defence supplier, ask for the exact contractual trigger rather than assuming all government guidance applies. For an AI adopter, trace prompts, source documents, retrieved context, outputs, retention, training use, telemetry and support separately.

Evidence and recovery feasibility | 8 minutes

  1. Which 5–10 services keep that workload usable, including identity, DNS, email, backup, logging and support?
  2. Which facts could you substantiate today: storage/processing locations, contracting entity, support access, key-use permissions and export capability? What is only a supplier statement?
  3. Can your team inspect configuration and contracts or obtain scoped evidence? Which documents cannot be copied or shared?
  4. When was recovery or switching last tested? What actually worked in the destination, how long did it take, and what was not tested?
  5. What small, sanitised workload slice could be tested safely? Who could approve and operate it? Which production dependencies would remain unresolved?

Do not treat confidence, cloud-region labels or “customer-managed key” branding as proof. Ask what observation or document supports the answer. Record Unknown when evidence is unavailable.

Package and commercial test | 8 minutes

Show the fixed-scope offer only after the behavioural questions.

  1. Which deliverable would change your next decision? Which would you remove?
  2. Would your current MSP, GRC tool or internal team already produce this? What would justify using MapleJockey?
  3. Who controls a budget for this problem? What paid alternative or internal effort would it replace? What approval and procurement steps are required?
  4. What price range would trigger approval, escalation or rejection for this exact scope, and why? Do not suggest the charter’s assumed price first.
  5. How often do meaningful changes occur? Would a quarterly evidence review be useful, or would reassessment only at renewal or migration make more sense?

Close and qualification | 4 minutes

Confirm the important decision, owner, available evidence, safe test slice and unresolved constraints. Ask what would have to be true for a later pilot proposal to be credible. Do not promise a delivery date, accept a contract or imply a place has been reserved.

Capture Record
Organisation and role Minimum necessary identifiers; no customer secrets
Trigger and consequence Actual event, date and decision owner
Current alternative Tool/adviser, effort, cost and dissatisfaction
Evidence readiness Available, inaccessible, withheld or unknown; source owner
Exercise readiness Proposed sample, operator, target, constraints and approval route
Commercial signal Budget process and stated range; distinguish interest from commitment
Next research decision Qualified, defer or unsuitable, with reason

Pilot gate: a real buying event, a named owner/operator, accessible scoped evidence and a safe test path. Interview enthusiasm, referrals and stated willingness to pay are not revenue. Seek permission separately before any follow-up or sharing of notes.

Interviewer resources. Draft pilot offer · Evidence requests.