Intelligence in practice

Ideas connect.
Possibilities take shape.

Explore how people and teams can use connected intelligence to create, research and make more informed decisions.

Discover 25 practical use cases

Quantumπetics · Gateway Compass

Start with what you want to change.

One idea can travel across many disciplines. Choose a goal, explore the connections and take a practical next step.

Explore the connected Gateways

Creative intelligence
Create a first draft, then bring human judgment to every release.
Explore AI ↗

Your suggested route · Create a campaign

Shape an idea into a brief, a visual direction and a story in motion.

01 / AI

Turn source material into a clear brief

An editable brief for your team to review.

See the workflow ↗
02 / AI

Explore a campaign’s visual direction

A visual direction ready for creative review.

See the workflow ↗
03 / AI

Plan a product story in motion

A structured video concept and editable scene plan.

See the workflow ↗

A curated planning guide. Choosing a route does not create accounts, connect providers or execute actions. Save and clear choices affect only this browser.

Spotlight

From a question to a next step.

Quantumπetics perspectives / 01

Ideas into action.
People at the center.

Explore nine in-depth scenarios across our Gateways: the challenge, the approach and what a team should evaluate before taking the next step.

Explore the case-study journal

Illustrative case studies · Original articles · Independent research links

9 of 9 articles

AI / Media & marketing01

A campaign brief becomes a creative system.

Connect the written brief, image directions, motion plan and sound palette with one accountable review process.

Scenario article · 2 min read
Read the full article

Illustrative scenario. No customer deployment or measured results are claimed.

The challenge

A small creative team needs several formats from one product brief. Generating each asset in isolation makes the campaign drift: the wording promises one thing while the images and music communicate another.

A practical approach

Begin with an approved message, audience and usage-rights checklist. Use QGEN to draft a content outline, QMAGE to explore visual directions, QVUE to plan scenes and QMUE to develop a sound direction. Keep the original brief beside each draft and record why a reviewer selects or rejects an option. Treat provider outputs as material for an editor rather than an automatic release.

What to evaluate

Compare consistency across formats, revision rounds, factual corrections and the time a human spends preparing assets for release. Run a small internal pilot before making a public campaign. Confirm rights and export capabilities with the connected providers.

Continue exploring

Explore the related AI workflow ↗Article permalink ↗

Independent further reading

Deloitte · AI & Data ↗ (opens in a new tab)
API / Technology & operations02

Make the handoff as reliable as the application.

Design an integration around ownership, explicit contracts and a recovery path.

Scenario article · 2 min read
Read the full article

Illustrative scenario. No customer deployment or measured results are claimed.

The challenge

An operations team wants two applications to exchange records. A successful demonstration is only the beginning: a production connection also needs to explain what happens when credentials expire, requests repeat or a destination is unavailable.

A practical approach

Write down the business event, record owner, request schema and expected response before selecting endpoints. Use a test environment and synthetic records to document authentication, timeouts and error responses. Where the destination supports it, design an idempotency key and a bounded retry policy. Separate configuration from secrets and name the person responsible for each credential.

What to evaluate

Exercise duplicate requests, malformed input and simulated provider outages. Record recovery time, rejected records and the quality of operational logs. The pilot should include a manual recovery procedure and a rollback decision, not just a successful request.

Continue exploring

Explore the related API workflow ↗Article permalink ↗

Independent further reading

Deloitte · Hybrid Cloud & Infrastructure ↗ (opens in a new tab)
GOV / Government & public services03

Keep a case review accountable from intake to decision.

Organize permitted evidence, reviewer responsibilities and the record of a human decision.

Scenario article · 2 min read
Read the full article

Illustrative scenario. No customer deployment or measured results are claimed.

The challenge

An approved agency team needs to understand how a case reached its current decision point. Records may be incomplete, a source may change and different reviewers may interpret the same material differently.

A practical approach

Start with non-sensitive sample records in the appropriate agency workspace. Assign a case owner and define which references each reviewer may access. Separate source material from interpretations and make missing information visible. Draft the review sequence, then require a named human decision before any consequential action. Preserve the reason for an approval, a rejection or a request for more evidence.

What to evaluate

Walk a second reviewer through the case without an oral explanation. Check whether they can identify the source, owner, outstanding questions and final decision. Review tenant access and retention requirements with the agency before deployment. This scenario is not an authorization for classified or CUI processing.

Continue exploring

Explore the related GOV workflow ↗Article permalink ↗

Independent further reading

Deloitte · Defense, Security & Justice research ↗ (opens in a new tab)
IO / Financial research04

Turn market headlines into a research trail.

Connect observations to sources and assumptions before deciding what a headline means.

Scenario article · 2 min read
Read the full article

Illustrative scenario. No customer deployment or measured results are claimed.

The challenge

A research team sees a sharp price move and several competing explanations. A headline alone does not establish causation, and prices from different venues or observation windows can tell different stories.

A practical approach

Choose the market, observation period and research question first. Capture source links and timestamps, distinguish a reported fact from an interpretation and compare available market views over consistent windows. Maintain alternative explanations alongside the leading hypothesis. Use the IO research workspace to organize the briefing and revisit it when new information becomes available.

What to evaluate

Have another analyst reproduce the observations from the original sources. Check missing timestamps, conflicting definitions and changes to the hypothesis. Track research completeness and reproducibility rather than presenting a simulated trading return. This is an information-review workflow, not a personalized investment recommendation.

Continue exploring

Explore the related IO workflow ↗Article permalink ↗

Independent further reading

Deloitte · Global Economics Research Center ↗ (opens in a new tab)
MCP / Enterprise AI05

Give an assistant context with a clear boundary.

Make each tool connection understandable, scoped and reviewable before execution.

Scenario article · 2 min read
Read the full article

Illustrative scenario. No customer deployment or measured results are claimed.

The challenge

A team wants an assistant to retrieve business context and prepare a response. A tool can also expose data or trigger a write, so giving the assistant more connections does not automatically make the workflow better.

A practical approach

Map the task to the minimum context needed. Inventory each provider, available tool, permission scope and data owner. Start with read-only requests and sample data. Treat retrieved text as reference material rather than authority to expand the task. Separate a proposed external action from its approval and document how a user revokes the connection.

What to evaluate

Test denied permissions, unavailable providers and misleading instructions embedded in retrieved content. Verify that the assistant can stop, explain the missing permission and escalate. Record which access controls belong to the provider and which belong to your application so that neither is assumed.

Continue exploring

Explore the related MCP workflow ↗Article permalink ↗

Independent further reading

Deloitte · Cyber AI Services ↗ (opens in a new tab)
QI / Identity & customer experience06

Build an identity journey people can understand.

Design the explanation, consent and recovery path together with the verification step.

Scenario article · 2 min read
Read the full article

Illustrative scenario. No customer deployment or measured results are claimed.

The challenge

A product team needs confidence in who is using a service while respecting the person completing the process. An unexplained request for identity information can create friction even when the technical check works.

A practical approach

Describe why information is requested, who can access it and how long it is needed. Evaluate the public QI capabilities with test accounts, then map the portal steps with product and privacy reviewers. Keep account recovery and a human appeal path visible. For a Continuum narrative, let the person decide what context belongs in their story and review what is shared.

What to evaluate

Observe whether test users can explain the request, locate their choices and recover from an unsuccessful step. Review accessibility and privacy requirements alongside completion rates. Do not equate a successful identity flow with a universal guarantee of trust or regulatory compliance.

Continue exploring

Explore the related QI workflow ↗Article permalink ↗

Independent further reading

Deloitte · Digital Trust & Privacy ↗ (opens in a new tab)
QSI / Research & emerging technology07

Start a quantum experiment with a benchmark.

Define a reproducible comparison before making a performance claim.

Scenario article · 2 min read
Read the full article

Illustrative scenario. No customer deployment or measured results are claimed.

The challenge

A research team has an optimization question and wants to explore quantum-related techniques. Without a classical baseline, a small demonstration cannot show whether a new approach is useful for the actual problem.

A practical approach

Define a small test instance, a known reference result and the resource budget. Review the Qyberia SDK resources in the Quantum Lab and document whether an experiment uses a simulator, classical code or a separately connected hardware provider. Save the inputs, configuration and observations. Increase problem size only after the smallest instance is understood.

What to evaluate

Compare solution quality, reproducibility and total resources with the baseline. Report setup costs and limitations, including simulation constraints. Decide whether to continue, change the experiment or stop. A demonstration is a learning result; quantum advantage requires evidence for the specific workload.

Continue exploring

Explore the related QSI workflow ↗Article permalink ↗

Independent further reading

Deloitte · Quantum computing readiness ↗ (opens in a new tab)
SI / Business & workforce08

Redesign the work before adding an agent.

Turn a recurring service request into a supervised process with named ownership.

Scenario article · 2 min read
Read the full article

Illustrative scenario. No customer deployment or measured results are claimed.

The challenge

A growing business receives the same operational questions across several channels. The goal is not simply to generate more responses; it is to help staff reach a consistent, reviewable next step.

A practical approach

Choose one request type and map the current handoffs. Organize approved knowledge, define what the assistant may draft and name the human responsible for a final response. Explore the SI knowledge and business workspace with representative sample requests. Keep exceptions visible and require approval before a connected action changes an external system.

What to evaluate

Compare the proposed process with the existing one using answer accuracy, correction effort, escalation quality and staff feedback. Include unusual requests and outdated source material. Expand to additional request types only when the team can explain failures and maintain the knowledge it depends on.

Continue exploring

Explore the related SI workflow ↗Article permalink ↗

Independent further reading

Deloitte · Human Capital Services ↗ (opens in a new tab)
SI / Energy & industrial operations09

Give an equipment alert a path to a human decision.

Connect telemetry context, an investigation checklist and accountable maintenance review.

Scenario article · 2 min read
Read the full article

Illustrative scenario. No customer deployment or measured results are claimed.

The challenge

An industrial team receives an equipment alert, but the signal alone does not explain whether the cause is a sensor fault, a process change or deteriorating equipment. An assistant needs a bounded role in that investigation.

A practical approach

Use a synthetic equipment dataset to map the asset, timestamp, sensor units and source system. Define the proposed API contract and MCP tool permissions separately from the operating equipment. An SI assistant can be evaluated as a planner that organizes permitted context and drafts questions for a qualified engineer. Keep control commands outside the pilot and retain the existing operational safety procedures.

What to evaluate

Test missing readings, stale timestamps, unit mismatches and false alerts. Ask an engineer whether the draft identifies the uncertainty and the right escalation route. Measure review usefulness and reproducibility before considering a production integration. Live telemetry, anomaly detection and equipment control require separately implemented and validated systems; this article does not imply those capabilities are provisioned.

Continue exploring

Explore the related SI workflow ↗Article permalink ↗

Independent further reading

Halliburton · Geothermal pump monitoring case study ↗ (opens in a new tab)

From the wider industry

Published stories & industry innovation

Third-party case studies, presented by their original publisher.

Deloitte / Published case study

Government · Generative AI

Government knowledge, with staff in control

Deloitte’s account of a state Medicaid program exploring AI-assisted access to policy information.

Read on Deloitte ↗
Deloitte / Published case study

Enterprise AI · Governance

AI model monitoring at Thomson Reuters

A published story about a shared interface for model monitoring, data drift and bias review.

Read on Deloitte ↗
Deloitte / Published case study

Workforce · Cloud

Building the skills for a cloud transition

How Deloitte describes role-based learning pathways for a global financial institution.

Read on Deloitte ↗
Halliburton / Published case study

Energy · Real-time analytics

A closer view of geothermal pump reliability

Halliburton’s published account of monitoring geothermal pump performance and identifying abnormal operating conditions.

Read on Halliburton ↗
Halliburton / Product announcement

Energy · AI & connected workflows

Connecting technical and economic asset decisions

Halliburton’s announcement describes a shared environment for comparing asset-development alternatives and retaining the assumptions behind decisions.

Read on Halliburton ↗

Discover

Find a workflow for your next idea.

25 use cases · Illustrative workflows, not customer case studies or measured impact claims.

AI · QGEN

Turn source material into a clear brief

An editable brief for your team to review.

Explore the workflow
  1. Supply your source material
  2. Generate an outline and draft
  3. Check references and edit before sharing

Start with test data and review permissions, provider availability and outputs before production use.

Explore AI capabilities ↗
Link to this use case ↗
AI · QMAGE

Explore a campaign’s visual direction

A visual direction ready for creative review.

Explore the workflow
  1. Describe the visual brief
  2. Create and compare image directions
  3. Refine the selection for your campaign

Start with test data and review permissions, provider availability and outputs before production use.

Explore AI capabilities ↗
Link to this use case ↗
AI · QVUE

Plan a product story in motion

A structured video concept and editable scene plan.

Explore the workflow
  1. Write a scene-by-scene brief
  2. Build the storyboard and motion edit
  3. Review the result before export

Start with test data and review permissions, provider availability and outputs before production use.

Explore AI capabilities ↗
Link to this use case ↗
AI · QMUE

Develop a sound for your next project

An audio direction for your creative project.

Explore the workflow
  1. Describe mood and instrumentation
  2. Explore a composition and arrangement
  3. Listen, refine and review usage rights

Start with test data and review permissions, provider availability and outputs before production use.

Explore AI capabilities ↗
Link to this use case ↗
API · Developers

Prototype a connected product

A scoped integration plan with explicit test steps.

Explore the workflow
  1. Define an integration requirement
  2. Review the API gateway and credentials
  3. Test your application against documented endpoints

Start with test data and review permissions, provider availability and outputs before production use.

Explore API capabilities ↗
Link to this use case ↗
API · Platform teams

Organize application credentials

Clear ownership for application access.

Explore the workflow
  1. Identify each application owner
  2. Create and store credentials securely
  3. Review access and rotate credentials when required

Start with test data and review permissions, provider availability and outputs before production use.

Explore API capabilities ↗
Link to this use case ↗
API · Operations

Map an operations integration

A practical handoff specification for your developers.

Explore the workflow
  1. Describe the system handoff
  2. Map the required request and response
  3. Review permissions and failure handling

Start with test data and review permissions, provider availability and outputs before production use.

Explore API capabilities ↗
Link to this use case ↗
GOV · Case operations

Coordinate a case review

A case review workflow with explicit responsibility.

Explore the workflow
  1. Select the approved agency workspace
  2. Organize case records and review tasks
  3. Record human approvals before consequential action

Start with test data and review permissions, provider availability and outputs before production use.

Explore GOV capabilities ↗
Link to this use case ↗
GOV · Agency teams

Connect knowledge and records

A navigable set of references for agency review.

Explore the workflow
  1. Define the records needed for a review
  2. Organize permitted references
  3. Review access and retention requirements

Start with test data and review permissions, provider availability and outputs before production use.

Explore GOV capabilities ↗
Link to this use case ↗
GOV · Program teams

Design an approval process

A draft approval process for agency validation.

Explore the workflow
  1. Outline the procedure and decision points
  2. Assign review responsibilities
  3. Test the workflow with non-sensitive sample data

Start with test data and review permissions, provider availability and outputs before production use.

Explore GOV capabilities ↗
Link to this use case ↗
IO · Research

Build a market research routine

A research notebook rather than a trading recommendation.

Explore the workflow
  1. Choose a market and observation period
  2. Compare available charts and context
  3. Document uncertainty and revisit assumptions

Start with test data and review permissions, provider availability and outputs before production use.

Explore IO capabilities ↗
Link to this use case ↗
IO · Analysis

Compare markets in context

A structured cross-market research checklist.

Explore the workflow
  1. Select related markets
  2. Review available price and trend views
  3. Record the limits of each comparison

Start with test data and review permissions, provider availability and outputs before production use.

Explore IO capabilities ↗
Link to this use case ↗
IO · Teams

Prepare a daily market briefing

A repeatable briefing process with source context.

Explore the workflow
  1. Define the instruments to watch
  2. Collect observations from available views
  3. Write a dated summary for human review

Start with test data and review permissions, provider availability and outputs before production use.

Explore IO capabilities ↗
Link to this use case ↗
MCP · AI builders

Plan a context-aware assistant

An assistant integration plan grounded in scope.

Explore the workflow
  1. Define the assistant’s task
  2. Identify the permitted context sources
  3. Review tool access and approval points

Start with test data and review permissions, provider availability and outputs before production use.

Explore MCP capabilities ↗
Link to this use case ↗
MCP · Integration teams

Review a tool connection

A reviewed tool connection for further testing.

Explore the workflow
  1. Choose a provider and connection
  2. Review the tool’s permissions
  3. Test the connection with a low-impact request

Start with test data and review permissions, provider availability and outputs before production use.

Explore MCP capabilities ↗
Link to this use case ↗
MCP · Operations

Specify an agent handoff

A handoff specification your team can evaluate.

Explore the workflow
  1. Map the task and tool boundary
  2. Define what needs human approval
  3. Document error handling and escalation

Start with test data and review permissions, provider availability and outputs before production use.

Explore MCP capabilities ↗
Link to this use case ↗
QI · Individuals

Shape a narrative in Continuum

A personal narrative workspace you can revisit.

Explore the workflow
  1. Create a narrative Orb
  2. Add the people, things and context you choose
  3. Review and update the story as it changes

Start with test data and review permissions, provider availability and outputs before production use.

Explore QI capabilities ↗
Link to this use case ↗
QI · Product teams

Explore an identity onboarding flow

An identity journey for product and privacy review.

Explore the workflow
  1. Review the public identity capabilities
  2. Define the consent and access requirements
  3. Evaluate the portal experience with test accounts

Start with test data and review permissions, provider availability and outputs before production use.

Explore QI capabilities ↗
Link to this use case ↗
QI · Communities

Design a human trust experience

A draft trust journey with room for human judgment.

Explore the workflow
  1. Identify the decision that requires trust
  2. Review available identity and trust experiences
  3. Define a human review and appeal process

Start with test data and review permissions, provider availability and outputs before production use.

Explore QI capabilities ↗
Link to this use case ↗
QSI · Developers

Explore Qyberia in the Quantum Lab

A reproducible learning exercise with documented limits.

Explore the workflow
  1. Open the Quantum Lab in your portal
  2. Review Qyberia examples and SDK resources
  3. Run a scoped experiment and record observations

Start with test data and review permissions, provider availability and outputs before production use.

Explore QSI capabilities ↗
Link to this use case ↗
QSI · Research teams

Design a supervised agent plan

An agent plan with human oversight.

Explore the workflow
  1. Define the goal and permitted context
  2. Draft steps in Agent Studio
  3. Review checkpoints before any execution

Start with test data and review permissions, provider availability and outputs before production use.

Explore QSI capabilities ↗
Link to this use case ↗
QSI · Knowledge teams

Organize a research workspace

A more navigable research process.

Explore the workflow
  1. Identify permitted research sources
  2. Structure the workspace around the question
  3. Review outputs against the original material

Start with test data and review permissions, provider availability and outputs before production use.

Explore QSI capabilities ↗
Link to this use case ↗
SI · Teams

Prepare a team knowledge workflow

A draft knowledge workflow for the team to test.

Explore the workflow
  1. Identify a recurring team question
  2. Organize the relevant knowledge
  3. Review the assistant’s response with a domain expert

Start with test data and review permissions, provider availability and outputs before production use.

Explore SI capabilities ↗
Link to this use case ↗
SI · Business

Map a supervised operations process

An operations blueprint with accountable review.

Explore the workflow
  1. Describe the goal and constraints
  2. Define agent steps and review points
  3. Evaluate the plan before connecting external actions

Start with test data and review permissions, provider availability and outputs before production use.

Explore SI capabilities ↗
Link to this use case ↗
SI · Small businesses

Bring business work into one place

A practical workspace setup plan.

Explore the workflow
  1. Define ownership and customer workflows
  2. Explore the Business Suite and Commerce workspace
  3. Configure only the integrations you need

Start with test data and review permissions, provider availability and outputs before production use.

Explore SI capabilities ↗
Link to this use case ↗

These workflows help you evaluate the platform. Features depend on configuration and connected providers; human review remains essential. GOV access is limited to approved agency users and is not for classified or CUI workloads.