Frame the transformation before it is scoped.
Choose the transformation you are facing. The questions adapt to it, and your answers are drawn together into an initial framing across Human, Business, and Technology — including what an assessment would still need to establish.
Nothing you select is submitted to HBT. Your answers are carried in the page link, so you decide who sees them.
A platform decision is not a transformation plan.
Most transformations are scoped around a technology event — a version, a platform, a tool — and then stall on everything that was never technical. A blueprint frames the change across people, operating structure, and architecture before a single environment is built.
- 01
What exists is older than the plan
Customisations, integrations, automations and informal use accumulate faster than documentation. They surface in scope only when they block it.
- 02
Ownership decides what moves
Content, processes and decisions have owners who have moved on. Without someone who can decide, everything is carried forward by default.
- 03
The target is assumed, not chosen
The newest version, the next platform or the popular tool becomes the destination without asking what the organization intends to operate.
Transformation snapshot
Where you are, where you intend to go, and the nature of the change between them.
What the current state tells us
What your answers imply about the estate, the organization and its constraints.
Human, Business, Technology
The considerations each orbit raises, each one showing the answers it is based on.
Items to validate
What a few answers cannot safely establish, stated plainly rather than guessed.
Indicative next movement
Where the HBT approach would begin for this kind of transformation.
Every blueprint applies the same HBT approach — Understand, Align, Architect, Deliver, Evolve — to one kind of transformation. See how HBT works
What are you transforming?
These are the transformation blueprints available today — not the full range of technology HBT works with. Each one asks only what matters for its kind of change.
Define: What is being transformed
The subject of the transformation and the direction intended for it.
What this blueprint covers
Platform transition. Follows the estate from its current version and topology to the intended direction — upgrade, SaaS or replatform — through experience data, solution and delivery, and frames the ownership and editorial change around it.
Sitecore versions
Sitecore 6.x: Sitecore 6.0 · Sitecore 6.1 · Sitecore 6.2 · Sitecore 6.3 · Sitecore 6.4 · Sitecore 6.5 · Sitecore 6.6
Sitecore 7.x: Sitecore 7.0 · Sitecore 7.1 · Sitecore 7.2 · Sitecore 7.5
Sitecore 8.x: Sitecore 8.0 · Sitecore 8.1 · Sitecore 8.2
Sitecore 9.x: Sitecore 9.0 · Sitecore 9.1 · Sitecore 9.1.1 · Sitecore 9.2 · Sitecore 9.3
Sitecore 10.x: Sitecore 10.0 · Sitecore 10.1 · Sitecore 10.2 · Sitecore 10.3 · Sitecore 10.4 · Sitecore 10.5
Roles and capabilities, by version
- Sitecore 6.x — Content Management · Content Delivery · SQL Server · Search index
- Sitecore 7.x – 8.x — Content Management · Content Delivery · Processing · Reporting · xDB collection · SQL Server · Search index
- Sitecore 9.0 — Content Management · Content Delivery · Processing · Reporting · xConnect Collection · Marketing Automation · Solr / SearchStax · Redis session · SQL Server
- Sitecore 9.1 – 10.0 — Content Management · Content Delivery · Processing · Reporting · xConnect Collection · Marketing Automation · Identity Server · Solr / SearchStax · Redis session · SQL Server
- Sitecore 10.1 – 10.5 — Content Management · Content Delivery · Processing · xConnect Collection · Marketing Automation · Identity Server · Solr / SearchStax · Redis session · SQL Server
Questions asked
- Intended direction — What is the intended direction?
- Current version — Which Sitecore version is deployed?
- Topology & roles — How is the estate deployed?
- Hosting & operations — Where does Sitecore run today?
- Experience data — How is experience data used today?
- Solution & delivery — How are pages delivered? What else is part of the solution?
- Integrations — Which systems does it exchange information with?
- Destination version — Which Sitecore version do you intend to reach?
- Ownership & content operations — Who owns the direction of the digital experience? How many people author or publish content?
- People & adoption — How much will the authoring and publishing experience change?
- Drivers & constraints — What is driving the transformation? How fixed is the timeline?
What this blueprint covers
Readiness & governance. Frames AI adoption through use cases, the information AI would reach, decision authority, accountability, risk and controls — with no version path, because there is nothing to upgrade.
Questions asked
- What is prompting this — What is prompting the AI work?
- Where AI would act — Where would AI be used?
- Use cases — Which kinds of use are in view?
- Current AI use — How is AI used in the organization today?
- Information & access — What information would AI work with? How well governed is access to that information? Is information classified or labelled?
- Decision authority — What role would AI play in decisions? Who is accountable for the outcomes of AI use?
- Risk & obligations — Which obligations or exposures apply? Is the organization's appetite for AI risk defined?
- Governance & controls — Which controls are in place today?
- Capability & value — How prepared are people to work with AI? Are the measures of value defined?
In preparationPower Platform estate & governance · .NET application modernization · Azure & cloud modernization · Integration & API modernization · Workflow & orchestration · Identity & access. Not listed? Describe your transformation to us
Describe: The current state
The operating and technical state as it stands today.
Choose a blueprint above. Each one asks its own questions, and they appear here once you do.
Frame: Direction and constraints
Destination, ownership, obligations, and the people the change reaches.
Choose a blueprint above. Each one asks its own questions, and they appear here once you do.
Blueprint: The initial framing
What your answers imply — and what still needs validating.
The framing appears here once a blueprint's required questions are answered.
Bring the blueprint to a conversation.
Share the link to your blueprint and HBT will frame the assessment it points to — across people, operating structure, and architecture.