What practitioners say
What practitioners say
This page summarises structured review feedback generated during development using AI-based reviewer simulations.
Five reviewer perspectives were generated to represent different roles involved in service management and CMDB design, including IT leadership, service management, CMDB administration, security, and ITIL consulting.
Each review was generated independently, using the full documentation set as the only input, with no additional context or prompting beyond a standard evaluation brief.
The purpose of this process was to challenge the structure of the service models, identify gaps or unclear areas, and evaluate how the product would be perceived by different roles. The outputs below reflect these simulated perspectives.
This is not a formal audit, certification, endorsement, or real-world deployment validation. It is a structured design validation process used to refine the product before release.
The reviewers
| Role | Organisation profile | Experience |
|---|---|---|
| IT Director | 2,000-person company | Budget holder, evaluating build-vs-buy |
| IT Service Manager | Mid-size organisation, 40 IT staff | Runs the service desk, owns the tooling roadmap |
| CMDB Administrator | Assets power user | Two years of daily CMDB work, came in sceptical |
| Security and Compliance Lead | InfoSec background | ISO 27001 and SOC 2 audit experience |
| ITIL Consultant | Senior, independent | A dozen CMDB implementations across different organisations |
Each perspective received the same brief: read the documentation, evaluate whether this product would be worth adopting, and score it honestly.
The IT Director perspective: "I would install this week"
The IT Director perspective evaluated LaunchPad as a proof-of-concept candidate. The question was simple: could this replace the weeks of internal design work that typically precede a CMDB rollout?
"I would install Basic CMDB this week as a proof of concept with zero financial commitment."
What stood out was the low-risk entry point. Basic CMDB is free, deploys in minutes, and produces a working schema that the team can evaluate immediately. No procurement cycle, no vendor call, no consulting engagement required to see whether the product does what it claims.
The value proposition landed clearly: "LaunchPad replaces the weeks of CMDB schema design work that kills most JSM Assets implementations." Credibility scored 8 out of 10. Value proposition clarity scored 9 out of 10.
Where this perspective pushed back: pricing was not visible in the documentation, and there was no obvious path from "I like this" to "here is what it costs." For a budget holder, that is a conversation stopper.
The IT Service Manager perspective: "The documentation is a competitive advantage"
This perspective evaluated LaunchPad through the lens of someone who would have to champion it internally, train a team on it, and live with the decision.
"Fix those gaps and this documentation would be a competitive advantage, not just a support resource."
Two things built trust quickly. First, the What JSM LaunchPad does and does not do page. Being upfront about limitations, rather than burying them, signalled that the product was built by practitioners who understand how IT teams actually evaluate tools. Second, the governance playbooks. Having review cadences, ownership patterns, and data quality guidance built into every schema told the reviewer that this was not just a deployment tool with no aftercare.
Clarity scored 9 out of 10. Trustworthiness scored 8 out of 10.
The gaps: this perspective wanted a "zero to first schema in 30 minutes" quickstart guide, and flagged that some governance content was heavier than a mid-market team would need on day one.
The CMDB Administrator perspective: scepticism lowered
This perspective represented the toughest audience: someone who builds and maintains CMDB schemas daily, who has seen tools promise structure and deliver chaos, and who would arrive expecting the usual consultant-grade handwaving.
"The documentation reads like it was written by someone who has actually run a CMDB, not someone who read about it in a consultant's slide deck."
What earned credibility was specificity. The schemas ship with real attribute configurations, sensible reference types, and documented rationale for design decisions. The common mistakes page was called out as evidence of genuine operational experience: you do not write about those failure modes unless you have lived through them.
Technical accuracy scored 8 out of 10. Practical usefulness scored 8 out of 10.
Where this perspective wanted more: advanced AQL patterns (nested traversals, performance tips for large schemas), automation rule builder walkthroughs with screenshots, and API documentation for integration builders. Power users will extend these schemas, and the documentation needs to support that trajectory.
The Security and Compliance perspective: a clear framing for the CISO
This perspective assessed LaunchPad through the lens of audit readiness, data classification, and whether the schemas would support compliance frameworks without extensive rework.
"JSM LaunchPad gives you 70% of the data model for 10% of the cost and implementation time."
The Cybersecurity schema and the compliance-related attributes across other schemas were evaluated against ISO 27001 and SOC 2 requirements. The reviewer concluded that the schemas provide a strong foundation for compliance mapping, though they noted that the documentation itself does not include a vendor security page, data processing details, or explicit Forge security architecture information.
Security coverage scored 7 out of 10. Compliance readiness scored 7 out of 10.
The recommendation was conditional but positive: this perspective would present LaunchPad to a CISO with specific framing around what the schemas provide out of the box versus what the organisation would need to layer on top.
The ITIL Consultant perspective: "Buy this and hire me for three months instead of six"
This perspective brought the broadest frame of reference: a dozen CMDB implementations, each with its own set of design debates, stakeholder negotiations, and schema rewrites. The evaluation was whether LaunchPad could genuinely compress the early phases of a CMDB programme.
"Buy LaunchPad and hire me for three months instead of six. They would get a better outcome in less time for less money. That is not something I say about most products in this space."
The schemas were evaluated against ITIL 4 configuration management practices. The assessment: structurally sound, with sensible defaults that reflect how mature IT organisations actually operate. The maturity model content was praised for being honest about the journey rather than pretending that deploying a schema is the same as achieving configuration management maturity.
The common mistakes page was singled out as "battle-scarred experience," the kind of guidance that only comes from having watched real implementations fail.
ITSM rigour scored 8 out of 10. Practical value scored 9 out of 10. Documentation quality scored 9 out of 10.
Where this perspective pushed back: maturity model timelines (how long does Level 1 to Level 2 actually take?), and a migration guide for teams replacing a failed first CMDB attempt. Both are common scenarios that the documentation does not yet address.
Summary of scores
| Dimension | IT Director | IT Service Manager | CMDB Administrator | Security Lead | ITIL Consultant |
|---|---|---|---|---|---|
| Credibility | 8/10 | 8/10 | 8/10 | 6/10 | 8/10 |
| Clarity | 9/10 | 9/10 | 9/10 | ||
| Practical value | 8/10 | 9/10 | |||
| Technical depth | 7/10 | 7/10 | 8/10 | ||
| Schema quality | 8/10 |
Empty cells indicate dimensions that the perspective did not score, not low marks.
What they agreed on
Across all five perspectives, three themes came up consistently:
-
The writing is authentic. Every perspective commented on the practitioner voice. The documentation reads like it was written by someone who has done this work, not someone describing it from a distance.
-
The "does and does not do" honesty builds trust. Being explicit about limitations is unusual for product documentation. Multiple perspectives cited it as the moment their evaluation shifted from cautious to engaged.
-
The entry point is low-risk. Basic CMDB as a free, zero-commitment starting point removes the procurement friction that stalls most CMDB initiatives before they begin.
What they wanted next
The perspectives also converged on gaps:
- Pricing visibility. Every perspective that indicated purchase intent also noted pricing was not visible.
- A quickstart guide. A single walkthrough from install to first linked ticket, under 30 minutes.
- Advanced content for power users. AQL cookbook, automation walkthroughs, API reference.
- Vendor security documentation. Data processing, Forge architecture, audit-relevant details.
- Customer stories. Even one or two informal case studies would close the remaining credibility gap.
This feedback is actively shaping the documentation roadmap. If you are reading this and have deployed a LaunchPad schema in production, we would like to hear your story.